Are your PDF's fonts really embedded? Find out before you send it.

Drop PDFs below — get every font listed with embedded or not, subset or full, encoding, and the pages that use it, plus a print-ready verdict per file. Inspected entirely on your device.

  • Your file data never leaves the device
  • Batch up to 20 PDFs + reports
  • Print-ready verdict per file
  • Password-protected PDFs refused

Add your PDF files

Drag & drop PDF files here

or browse your files · you can also paste from clipboard (Ctrl+V)

Inspected in your browser with pdf.js — every font dictionary is read on your device and checked for an embedded font program. Nothing is uploaded.

    No files yet. Everything stays on this device. Reports download instantly.

    Privacy you can verify, not just trust

    Most online font checkers upload your documents to their servers first — and several charge for the detailed report. This one can't: pdf.js opens your PDF and its font dictionaries are read entirely in your browser. Your file data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no file fetched after load for the inspection itself. Don't take our word for it:

    New cross-origin requests during use: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Inspect any PDF above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no file data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — inspection still works.

    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:

    1. 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 .pdf is refused the same way, and a PDF renamed to .txt still inspects.
    2. 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.
    3. 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.

    Frequently asked questions

    Do my PDFs upload anywhere?

    No. Your PDFs are opened and their font dictionaries are read entirely in your browser with pdf.js — your file data never leaves the device, and the only third-party requests are the site's own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the inspector.

    How do I check if fonts are embedded in a PDF?

    Drop the PDF on this page and read the verdict: every font is listed with Embedded yes (full or subset) or No (referenced only), plus the pages that use it. In Adobe Acrobat, the same information is under File, then Properties, then the Fonts tab — entries marked Embedded or Embedded Subset travel with the file, and an entry with no such marker is only named. On the command line, the pdffonts utility prints the same thing in its emb column.

    What does embedded subset mean?

    Embedded subset means only the glyphs the document actually uses are stored inside the PDF, instead of the whole font. The font name then starts with a six-letter tag and a plus sign, such as ABCDEF+Georgia. A subset is fully embedded for the characters in the document and prints identically everywhere — it is normal, and it keeps the file small. Only a font with no embedding at all is a problem.

    What should I do if a font is not embedded?

    Re-export the PDF with font embedding turned on, from the application that made it. In Word, go to File, then Options, then Save, and tick Embed fonts in the file. In InDesign, use Export Adobe PDF, then Advanced, and make sure Subset fonts is on. In Acrobat, run Preflight and use a PDF/A profile or the Embed fonts fixup. Then drop the new PDF here and check the verdict flips to Print-ready.

    Are the standard 14 fonts a problem if they are not embedded?

    Usually not for viewing: Helvetica, Times, Courier, Symbol and ZapfDingbats and their styles are the 14 standard PDF fonts, and every conforming viewer substitutes them acceptably, so the document will look right. This tool still flags them, because PDF/A archiving and many print services require every font, including the standard 14, to be embedded — that is why a PDF with only standard fonts unembedded gets Mostly ready instead of Print-ready.

    Can I inspect several PDFs at once?

    Yes. Drop up to 20 PDFs at a time, up to 25 MB each, and inspect them all in one go. Every file gets its own verdict and font table, the summary strip totals the batch, and Download all reports collects every file's report into one text file (or a ZIP). There is no daily limit, no account and no watermark — a 200-page cap per PDF applies because very page-heavy PDFs are memory-bound in the browser.

    Can I inspect a password-protected PDF?

    No. Password-protected PDFs are refused with a clear message, and this tool never asks for a password. Remove the password in a desktop PDF tool first, then inspect the unlocked copy here.

    What does this tool NOT check?

    It reads font dictionaries; it is not a full preflight engine. It cannot tell you whether an embedded font's licence allows embedding, check glyph shapes for corruption, or see fonts used only inside annotation appearances such as filled form fields, or inside patterns. It never opens the font programs themselves, so a corrupt embedded font program is not detected. For a full preflight, use Acrobat Preflight or a dedicated validator.

    Why does my PDF show no fonts at all?

    Because the PDF uses no fonts — it is most likely a scanned document, where every page is a picture of a page rather than text. There is nothing to embed in a scan, so No fonts found is the correct result, not an error. If the document should have text, it was probably exported as images; re-export it from the original application as a real text PDF.