See Which Fonts a PDF Uses and on Which Pages
Scans every page with pdf.js and lists each font family found, along with the pages it appears on. It identifies the typefaces in a document — it does not download the font files themselves.
About the PDF Font Extractor
Start with the honest version, because the name promises more than the tool delivers: this lists fonts, it does not extract them. You will get a table of font families with the page numbers where each one is used, which answers the question most people are actually asking — what typeface is this document set in, and is it used consistently. What you will not get is a downloadable font file, and no tool on this site produces one, because pulling an embedded font out of a document and installing it is a licensing problem rather than a technical one.
There are no settings. Add a document, press the button, and the scan works through every page collecting the styles that pdf.js reports for the text on it. Pages are listed against each family, truncated after twelve to keep the table readable on a long document.
Key Features
- Family names with page numbers: Each font is listed alongside where it appears, so you can see whether a stray typeface is used throughout or crept in on one page.
- Whole-document scan: Every page is read rather than a sample, which is what makes it reliable for catching an inconsistency buried at page 90.
- Doubles as a scan detector: If no fonts are found at all, the document contains no text — it is a set of images, and the tool says so plainly.
- Long page lists are trimmed: A font used on two hundred pages shows the first twelve followed by an ellipsis rather than filling the screen.
- Read-only: The document is inspected and nothing is written, so there is no output file and no possibility of altering the original.
- Inspected without disclosure: pdf.js runs from this domain inside your browser, so examining an unreleased document's typography does not involve showing it to anyone.
How to Use the PDF Font Extractor
- Add the PDF you want to inspect.
- Press List Fonts and let the scan run through the pages.
- Read the table of font families and the pages each appears on.
- If the result is empty, the document has no text layer — it is a scan.
How It Works
The scan asks pdf.js for the text content of each page and reads the style information it reports, collecting font family names into a set of page numbers per family. Because the names come from what pdf.js exposes rather than from the raw font dictionaries, they arrive in a normalised form: you will usually see a recognisable family name, but embedded subset fonts sometimes carry a prefix, and a font the renderer cannot resolve may appear under a generic family instead of its real name.
That means this is a good identification tool and an imperfect forensic one. It will not tell you whether a font is fully embedded or subsetted, whether it is licensed for embedding, what weights and sizes are in use, or whether two similarly named entries are genuinely the same face. For matching typography or auditing consistency it is exactly enough; for a pre-press embedding check you want a dedicated preflight tool.
When You Need It
A freelance designer inherits a brochure as a PDF with no source files and a client who needs a matching one-page insert. Identifying the typeface is the first step in rebuilding the layout, and doing it from the document itself is faster than sending screenshots to a font identification service — which would also mean putting a client's unreleased collateral in front of a third party for the sake of a name.
Someone about to pay for optical character recognition on a stack of documents can check first whether the recognition is needed at all. If the font list comes back populated, the text is already in there and the money can be saved. If it comes back empty, the document really is a set of images and recognition is the right purchase.