PDF Font Inspector
Identify fonts referenced on PDF pages and review page-level font usage.
Scan fonts page by page
Identify fonts referenced on PDF pages and review page-level font usage.
Scan fonts page by page
PDF Font Inspector is a focused ANU PDFLAB utility designed to help users complete a common document task without installing a large desktop program. Identify fonts referenced on PDF pages and review page-level font usage. The interface follows the same lightweight structure as the existing tools, making it easy to understand on desktop, tablet, and mobile screens.
PDF files can reference multiple embedded or system fonts. Inspecting them helps troubleshoot substitution, printing, branding, and text-rendering problems. This can support students, office teams, freelancers, teachers, publishers, administrators, and everyday users who need a quick result while keeping the original source file available as a backup.
PDF files can reference multiple embedded or system fonts. Inspecting them helps troubleshoot substitution, printing, branding, and text-rendering problems. The page provides only the controls required for this task, reducing confusion and unnecessary processing. Results are prepared inside the current browser session wherever the selected operation allows it, and the user remains in control of the source file and downloaded output.
Processing time depends on file size, page count, image resolution, browser capability, and available device memory. For smoother performance on mobile devices, close unused tabs and begin with a reasonably sized file.
A dedicated browser tool can be faster than opening a full editor for a small, repeatable job. It is useful for document preparation, office records, assignments, client files, publishing checks, research, and routine quality control. The consistent ANU PDFLAB layout also reduces the learning time when moving between different utilities.
The tool uses page-specific libraries only when they are needed, rather than loading heavy code across the whole website. This helps preserve the speed of normal pages and the wider tool directory. Large scans and complex PDFs can still consume significant memory because the browser must decode and process their contents.
Some PDFs convert letters to vector paths or use custom font subsets with shortened names. In those cases the reported name may not match the commercial font family exactly. Automated results should therefore be treated as an aid, not as a substitute for professional legal, accessibility, archival, security, or print review. The user is responsible for confirming that the output is suitable for its intended purpose.
Yes. It is designed for everyday browser-based use without requiring account creation. Practical limits depend on the selected file and the memory available on your device.
No. The source file remains unchanged. When an output file is created, it is downloaded as a separate copy.
Large images, many PDF pages, complex fonts, and high-resolution scans require more browser memory and processing time.
Yes, but important business, legal, accessibility, print, or archival material should always be reviewed after automated processing.