See which fonts your PDF uses — and whether they will copy, edit, share and print correctly.
Understand how every font behaves inside your PDF
A font name alone does not tell you whether a PDF will copy correctly, remain editable or print consistently. The inspector reads the document’s font resources and its content streams to show what is actually used — not merely what appears in the resource list.
Identify fonts
See the normalised family name, the original PDF font name, style, type and resource aliases.
Locate font usage
Select a font to highlight its text directly on the PDF and move between occurrences.
Check embedding
Distinguish fully embedded, subset embedded, not embedded and unverifiable fonts.
Test copy & search
Check whether the characters you see reliably map to Unicode text.
Assess editing readiness
Understand whether a font can support layout-safe text changes.
Review printing risks
Detect non-embedded fonts and unusual structures that may cause substitution.
Inspect PDF fonts in three steps
- Upload your PDF
Your file is analyzed without converting or modifying its pages.
- Review fonts and warnings
See font families, technical font objects, sizes, page usage, embedding and copy/search status.
- Click a font to find it
The preview highlights text using that font and shows its properties on hover.
Why the same font can appear more than once
A PDF can contain several technical font objects that all represent the same visible family. They may use different character subsets, encodings, resource names or page scopes — which is why a report can honestly show 25 font objects and only three families.
The inspector groups them by family for clarity while keeping every underlying object available for technical review, because two objects sharing a name can differ in everything that matters: subset, encoding, and embedded program.
Are the fonts actually inside the PDF?
Font embedding is what lets a PDF preserve its intended appearance across devices and printers. The report separates four states, and never collapses the last one into “not embedded”:
| Status | Meaning |
|---|---|
| Fully embedded | A complete font program appears to be included. |
| Subset embedded | Only the glyphs the original document needed appear to be included. |
| Not embedded | The PDF may depend on a font installed elsewhere, or be substituted. |
| Could not verify | The file structure did not provide enough reliable evidence. |
Is a subset font bad?
No. Subsetting is common and reduces file size. The limitation appears mainly when editing: a character that was not used in the original PDF may not exist in the embedded subset.
Why text can look correct but copy incorrectly
A PDF viewer can display a glyph even when the document lacks a dependable mapping from that glyph to a Unicode character. The page looks perfect on screen, then the text becomes wrong when copied, searched, extracted or read by accessibility software.
For every font, the inspector checks:
- Whether a
/ToUnicodemap exists. - Whether it can be parsed.
- Whether the character codes actually used are mapped.
- Whether unexpected or private-use mappings appear.
- Whether mapping coverage is complete or partial.
Can an embedded font still copy incorrectly?
Yes. Embedding controls rendering; copying depends on character encoding and Unicode mapping. That is why Embedded and Copy & search are reported as separate results rather than one status.
Know before you edit
Whether a PDF font can be edited is not determined by its name. A document may contain only a limited subset of the font, a custom encoding, no reliable Unicode map, Type 3 drawn glyphs, a font that is not embedded, or several incompatible font objects sharing one name. The report combines these signals into an editing-readiness assessment, and shows which signal produced it.
Example
Confirmed: the font stream is embedded.
Assessment: editing readiness is limited, because only a subset is available — existing characters are editable, new symbols may require a compatible replacement.
Reduce unexpected font changes when printing
Before sending a PDF to a client, printer or production team, check whether the actively used fonts are embedded and whether the document contains unusual font structures. The report reviews active font embedding, font descriptor consistency, subset usage, Type 3 fonts, very small text, substitution risk and invalid or unverifiable metrics.
We do not claim guaranteed print output. The strongest honest statement is: no obvious font-substitution risk was detected.
What if no fonts are found?
A PDF can show visible words without containing normal PDF text. The page may be a scanned image, the text may have been converted to vector outlines, the glyphs may be drawn through Type 3 instructions, the real text may live only in a hidden OCR layer, or the whole design may be flattened.
In that case the report says so plainly — no standard visible font resources were found; this page may be scanned, outlined or image-based — rather than guessing at a typeface from the picture.
Why use this instead of PDF properties?
| Capability | Basic PDF properties | This font inspector |
|---|---|---|
| List document font names | Yes | Yes |
| Normalise subset names | Limited | Yes |
| Group by font family | Limited | Yes |
| Show actual page usage | Limited | Yes |
| Highlight the font on the PDF | No | Yes |
| Show font sizes | Limited | Yes |
| Check embedding | Yes | Yes |
| Explain subset limitations | Limited | Yes |
| Check copy & search reliability | Usually no | Yes |
| Assess editing readiness | No | Yes |
| Assess printing risk | Limited | Yes |
| Export report | Product-dependent | Yes |
How the inspection works
Used fonts vs unused resources
Every page’s content stream is parsed and the Tf operators are resolved against the resource dictionary in scope. A font is “used” only if the content actually selects it; anything else is reported as an unused resource.
Embedding verification
The font descriptor is read for FontFile, FontFile2 and FontFile3 streams and the bytes are loaded. A stream that cannot be read yields “could not verify” — never “not embedded”.
Subset determination
Multiple signals are combined: a valid six-letter prefix, the glyph count in the embedded program, a /CharSet list, and a descendant /CIDSet. The confidence level and the reasons are both shown.
Unicode coverage
Coverage is measured against the character codes the document actually uses, collected while walking the content streams — not against every code the font theoretically defines.
XObjects and inheritance
Page resources are resolved through the page tree, and Form XObjects are walked recursively with cycle protection — a font used only inside a reusable form is still found and labelled as such.
Where the highlights come from
Each text run’s box is computed from the text and transformation matrices using the font’s real glyph widths, then mapped to the page. Rotated text is marked as a bounding box rather than presented as an exact fit.
What cannot be determined reliably
- A font resource may exist in a PDF without ever being used by page content.
- A scanned page may contain no identifiable PDF font at all.
- A six-letter subset prefix is not, by itself, proof of subsetting.
- A present ToUnicode map is not proof that all of its mappings are correct.
- Font embedding does not guarantee that text is safe to edit.
- Print behaviour cannot be guaranteed across every workflow or RIP.
Glossary
- Embedded font
- A font whose program is stored inside the PDF, so the file does not depend on the reader having it installed.
- Subset font
- An embedded font containing only the glyphs the document used. Usually named with a six-letter prefix such as ABCDEE+Arial-BoldMT.
- Type 3 font
- A font whose characters are PDF drawing instructions rather than a conventional typeface outline.
- CID font
- A composite font addressed by character IDs rather than single bytes, used for large character sets and most modern embedded fonts.
- ToUnicode
- A CMap that maps the PDF’s internal character codes to Unicode, so text can be copied, searched and extracted correctly.
- Font descriptor
- The dictionary holding a font’s metrics and flags — ascent, descent, italic angle, stem width — and the embedded font stream.
- Font substitution
- What a viewer does when a font is not embedded: it renders with the closest installed match, which usually has different widths.
- OCR text layer
- Invisible text placed over a scanned image so the page can be searched and selected.
- Outlined text
- Text converted to vector shapes. It looks like type but contains no font and no characters.
Your PDF stays unchanged
The inspector reads font resources and document structure without modifying your pages. There is no modified file to download, because nothing is modified.
- No signup
- No watermark
- No PDF conversion
- No document editing
- Files removed after your session
See our privacy policy and file handling policy for retention details.
Related tools
- PDF Editor — edit text and images on the original layout.
- PDF to Markdown — extract the text, once you know it extracts correctly.
- Compress PDF — reduce file size, including duplicated font programs.
- Remove Watermark — detect and remove watermark objects.
- All PDF tools
PDF font inspector — frequently asked questions
Upload the document to the PDF Font Inspector. It reads the font resources the PDF actually uses and lists each font family, style, type, page usage and embedding status. Select a font to highlight its occurrences in the document preview.
Select the font from the results table. The document preview highlights the text runs that use it, and hovering any text shows which font object drew it, at what size and in what colour. You can move between pages from the thumbnail rail.
The inspector reads each font descriptor and its associated font streams (FontFile, FontFile2, FontFile3). Every active font is classified as fully embedded, subset embedded, not embedded, or could not verify — the last one meaning the file structure did not provide enough evidence either way.
A subset embedded font contains only the glyphs the original document used, not the complete typeface. It normally displays correctly everywhere. The limitation appears when editing: a character that was never used in the original PDF may not exist in the embedded subset.
Usually not for viewing or printing. Subsetting is standard practice and reduces file size. It becomes a limitation only when editing, because unused letters, symbols or language characters may not be included in the file.
Because the PDF lacks a dependable mapping from its displayed glyphs to Unicode characters. Custom encodings, a missing or malformed /ToUnicode map, and unusual font data all cause copied, searched or extracted text to come out wrong even though the page looks perfect on screen.
Yes. Embedding supplies the glyph outlines used for rendering, while copying and searching depend on character encoding and Unicode mapping. One can work perfectly while the other does not, which is why this tool reports them as separate dimensions.
The font is most likely not embedded, so the viewer substitutes the closest match it has installed. Substitutes rarely share the original character widths, so spacing, line breaks and pagination can shift. Damaged font data and unusual font structures can cause the same effect.
A PDF can contain separate font objects for different pages, subsets, encodings, form fields or resource scopes, all representing the same visible family. The inspector groups them under one family for clarity while keeping each technical object available for review.
A Type 3 font defines each character using PDF drawing instructions rather than a conventional typeface outline. It displays normally, but identifying, copying, searching and editing it are less reliable than with TrueType or Type 1 fonts.
Not from PDF font resources — a scanned page is an image and usually contains no font objects at all. The tool labels such pages as image-based rather than guessing. Recognising a typeface from the picture itself would need a separate visual identification system.
Embedding helps, but it is not the only requirement. Check whether the font is subsetted, whether Unicode mapping is reliable, and whether the characters you need are actually present. The inspector combines those signals into an editing-readiness assessment for each font.
No. The inspection reads the document structure and produces a report without rewriting, converting or changing the PDF in any way. There is no modified file to download because nothing is modified.
No. Embedded fonts are frequently subsetted and technically incomplete, and they are covered by the foundry’s licence, which normally permits embedding in a document but not extraction and reuse. The inspector reports what a font declares about its own embedding permissions and stops there.
No absolute guarantee is possible, but embedding substantially reduces dependence on fonts installed on the receiving system. The report also checks for structural risks such as Type 3 fonts, invalid metrics and unusually small text that can affect print output.
A /ToUnicode map connects the character codes used inside a PDF to Unicode text. It is what lets copying, searching, extraction and accessibility software understand which characters the displayed glyphs represent. The inspector checks whether it exists, parses, and covers the codes the document actually uses.
No. The file is processed for the analysis and then removed — it is not kept, shared, indexed or used for training. Only structural metadata such as page and font counts is logged; document text is not.