Your PDF/A conversion failed on fonts. One typeface in the document could not be embedded, and the standard has no tolerance for that.
What makes this maddening is that the document looks perfect. Everything renders, nothing is visibly wrong, and the rejection notice names a font you do not remember choosing. Worse, one cause of this error cannot be fixed by any conversion tool at all — so working out which cause you have is the first useful step, not trying remedies at random.
Why PDF/A insists you embed fonts in a PDF
An ordinary PDF may reference a font by name and trust the reader to supply it. That works until it does not. Open the file on a machine without that typeface and the reader substitutes something else, at which point spacing shifts, lines rewrap and page breaks move.
Archival files remove that possibility by carrying the glyphs inside the document. Every font, no exceptions, which is why a single unembedded typeface fails the whole file.
Here is the part that surprises people. The old standard fourteen fonts — Helvetica, Times, Courier and the rest — used to be exempt, because every reader was assumed to have them. PDF/A withdrew that exemption. A plain document set in Helvetica with nothing embedded is one of the most common failures we see, precisely because it looks like the safest possible choice.
Find out which font broke before you fix anything
Guessing wastes more time than checking. You want a name.
Our PDF/A validator lists every font in the document with its embedding status, reading the file in your browser. If you have Acrobat, the same information is under File, Properties, on the Fonts tab, where embedded fonts are annotated and the rest are not.
The name usually explains the failure on its own. A commercial or downloaded display typeface points at a licence restriction. Symbol or Wingdings points at a bullet or an operator you never consciously chose. A base font like Arial or Helvetica points at a converter that simply did not embed the standard set.
When a font licence blocks embedding and no tool can help
Fonts carry permission bits, and one of them says whether the font may be embedded in a document. Some commercial typefaces set it to forbid embedding entirely.
When that bit is set, no converter will embed the font. Not ours, not Acrobat, not a paid desktop tool. Any tool that did would be circumventing a licence restriction, and one that claims to is doing something you should not want in a document you are about to file officially.
So the fix is in the source document: change the typeface to one that permits embedding, then export again. Widely used families such as the open-source Google Fonts or the standard system faces are safe. Check the metrics afterwards, because swapping typefaces moves line breaks, and a thesis with fixed pagination or a contract with clause positions will care.
We would rather tell you this at the start than let you cycle through five tools discovering it. It is the one branch of this problem with no technical answer.
The other four causes, and what actually fixes them
The font is not installed on the converting machine. A converter can only embed a font it can reach. Install the typeface on the machine doing the export and regenerate the PDF from the source document.
The converter never embeds the base fourteen. Some tools still treat Helvetica and Times as exempt. Use a converter built for archiving rather than a general PDF printer — ours embeds every font it encounters, including the standard set.
The embedded copy is damaged. This produces messages about not being able to extract the embedded font. The font data is present but unreadable. Reinstall the font locally and regenerate the PDF from the source; repairing the PDF itself is much harder than rebuilding it.
The subset is incomplete. Fonts are usually embedded as subsets containing only the characters used. Edit the document afterwards and add a character that was not in the subset, and the file references a glyph it does not carry. Regenerate rather than patch.
The convert text to outlines fallback, and its real cost
If nothing else works, turning text into vector shapes satisfies the rule by removing the text. There is no font to embed because there are no longer any letters, only outlines.
It is a legitimate last resort and a bad default. An outlined document cannot be searched, cannot be copied from, and cannot be read by a screen reader. For a thesis, a contract or anything anyone will need to quote from, that is a serious loss.
Use it narrowly. A logo with a licensed display face, a decorative heading, a single stubborn element — outline that and leave the body text alone. Outlining an entire document to clear a compliance error trades one problem for a worse one.
Rebuild, then check before you submit
Once you know the cause, the sequence is short. Fix the font in the source, export a fresh PDF, convert it with our PDF/A converter at the level you were asked for, then validate the actual file you plan to send.
That last point matters more than it sounds. Embedding depends on what the converting machine can access, so the same source document can produce a compliant file on your laptop and a broken one somewhere else. Check the file itself, not a file like it.
If the failure is on a Word document heading for a repository, the export settings have their own traps, covered in saving a Word document as PDF/A. If the document came from a scanner, fonts work differently again and OCR before archiving is the relevant guide. And if you are unsure which level to target, see PDF/A-1b versus PDF/A-2b. Where the text itself is the thing you need rather than the layout, extracting it with our PDF to Word converter sidesteps the problem entirely.