How to check if fonts are embedded in a PDF without uploading it
An unembedded font is the quietest way a PDF breaks: it looks perfect on your machine, because your machine has the font, and reflows on your client's, your printer's, or your publisher's — different spacing, different line breaks, sometimes different characters. The usual advice is to open Acrobat's Fonts tab or run pdffonts on the command line, but neither gives you a verdict, a batch check, or a report you can send to the person who made the file.
This tool does exactly that, where the file already is: on your own device. When you drop a PDF here, your browser:
- Checks the file is really a PDF — by its %PDF magic bytes, not its
name — and that pdf.js can open it, so a corrupt or truncated file is refused with a
clear message instead of producing a wrong report. A JPEG renamed to
.pdfis refused the same way, and a PDF renamed to.txtstill inspects. - Reads every font dictionary the pages actually use — including fonts stored in compressed object streams, which most modern producers use, and fonts used only inside Form XObjects — and checks each font's descriptor for an embedded font program, exactly the way pdffonts does it. A six-letter tag plus a plus sign in the name, like ABCDEF+Georgia, marks a subset.
- Gives each file a verdict — Print-ready, Mostly ready, or Risky — with the unembedded fonts named and the pages they affect, so you know what to fix and where. A downloadable text report per file (or one combined report for the batch) carries the same detail to whoever needs it.
What makes this inspector different
The pages that top the results for this search mostly check one file on a server, charge for the detailed report, or need an account — and the one dedicated client-side rival we found checks a single file with no verdict and no downloadable report. This page is the only fully client-side dedicated PDF font inspector we found that combines a batch of 20 PDFs with a print-ready verdict per file, per-font subset, encoding and ToUnicode detail, the pages each font is used on, and a free downloadable report for every file — with no daily limits, no account and no watermark — plus a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to.
When is inspecting the right choice — and when is it the wrong one?
Inspecting is right whenever a PDF has to look identical somewhere else: a print-ready file for a printer or publisher, a book manuscript for KDP or IngramSpark, a contract or proposal sent to a client, or an archived PDF/A document. It is the wrong choice for a scanned PDF — a scan has no fonts, so there is nothing to embed — and for a file you only ever open yourself, where substitution never bites. If the destination accepts the source document, fix the fonts there instead of patching the PDF.
Honest limitations
Font dictionaries, not full preflight
This tool reads font dictionaries — it is not a preflight engine. It cannot judge colour spaces, image resolution, overprint, or any other print condition.
No licence checks
An embedded font's licence is not read, so this tool cannot tell you whether the font's licence allows embedding. Check the licence you bought separately.
Font programs are not opened
The font program streams are never opened, so a corrupt embedded font program is not detected — only whether a program is present at all.
Some fonts are invisible
Fonts used only inside annotation appearances (for example filled form fields) or patterns are not always listed, because they live outside the page resources.
No password-protected PDFs
Password-protected PDFs are refused, and this tool never asks for a password. Remove the password in a desktop PDF tool first, then inspect the unlocked copy.
Scanned PDFs have no fonts
A scanned PDF contains no fonts — only page renders. Inspection correctly returns no fonts for it. Use PDF to JPG to turn each scanned page into an image instead.