PDF Info Viewer, Size, Font & Print Preflight Check
PDF info, size, fonts, image resolution and print preflight
PDF info, size, fonts, image resolution and print preflight
Files are processed only in this browser. Nothing is uploaded to a server.
See a PDF’s version, page sizes, encryption, signatures, forms, layers and attachments on one screen
This PDF is password-protected.
Continue in another tool
Processing…
Everything runs inside this browser. Your file is never sent to a server.
Your file is ready to download
Continue with this result
Open page preview
Changing a setting hides the previous result. Run it again to save the latest settings.
Remove the password from an encrypted PDF first. Processing focuses on page content, so bookmarks, attachments, forms and signatures may not be preserved. Keep the original and check the result.
Loading…
Working…
0.0
It hasn't frozen — the result will appear when the calculation finishes.
About PDF Info Viewer, Size, Font & Print Preflight Check
PDF Info is a read-only inspector. The default view sums up the version, page sizes, encryption permissions, signatures, forms, layers, attachments and JavaScript as cards. Switching tabs gives you separate reports for file size, fonts, image resolution, page boxes, ink coverage and print preflight.
Which tab to open first depends on why you have the file. If it bounces as an email attachment, start with the size report. If text looks wrong on someone else's computer, go to fonts. If it's heading to a print shop, preflight is the quickest overview.
Three things people misread on the summary cards
A PDF/A or PDF/X badge is only the claim written in the XMP metadata, not a validation result. The signature card shows signer and time but does not check the certificate. The incremental-save count is estimated by counting %%EOF markers; if there is one more save after the signature, something was appended after signing.
Password-protected files still open in the summary view, because permissions and the encryption method are stored in plain form in the file structure. The size, font, resolution, page box and preflight tabs cannot analyze encrypted files, so remove the password first.
Each tab measures something different
Numbers from different tabs can disagree without either being wrong, because each tab looks at different data in a different way.
- Size: splits compressed bytes per object into images, fonts, content streams, attachments and so on. The total matches the file size; objects packed inside object streams are estimated by proportional allocation.
- Fonts: follows the resources of pages, form XObjects and annotation appearances to report embedding and whether a ToUnicode map exists. “Used on page” is based on resource references, so a page that never draws a glyph in that font can still be listed.
- Image resolution: works out the placed size from the transformation matrix, computes horizontal and vertical effective DPI separately and judges by the lower one. Anything above twice the target is flagged as oversized.
- Page boxes: compares the five boxes against the MediaBox. A missing box is treated as equal to the MediaBox, as the spec says, and is not counted as a mismatch.
- Ink coverage: renders each page, converts the RGB pixels to CMYK with a naive formula and reports the channel averages, their sum (average ink coverage) and the per-pixel maximum TAC. The maximum is the figure to compare with a printer's limit, but the naive conversion never goes above 200% and counts rich black as K 100%. Spot colors are only listed as present.
- Print preflight: reads the structure without rendering and sorts findings into pass, warning and fail — resolution, RGB use, maximum TAC of vector colors and non-JPEG CMYK images, bleed, lines under 0.25 pt, transparency and overprint. The offset preset uses 300 dpi, 300% TAC and 3 mm bleed; the digital preset uses 200 dpi, 320% and 2 mm.
Worked examples
Why the ink tab and the preflight tab give different TAC
- Input
A pure red RGB(255,0,0) logo covers 10% of the page; the rest is white- Output
Ink coverage tab: average ink coverage about 20%, max TAC (per pixel) 200% (the logo pixels, M100 + Y100)
Average ink coverage is a page average, which cannot be compared with a printer's TAC limit (a maximum at any single point); the max TAC is the figure to compare. The ink tab's max TAC comes from a naive conversion of rendered RGB and never exceeds 200%, though, so use the maximum TAC in the preflight tab to check the limit. Preflight does not convert RGB objects to get a TAC; it flags RGB use as its own item instead.
One 1000-pixel photo placed at two sizes
- Input
The same 1000×750 px image at 85 mm wide on page 1 and 200 mm wide on page 3- Output
Page 1 about 299 dpi, page 3 about 127 dpi — two rows in the resolution tab
1000 px ÷ (85 mm ÷ 25.4) ≈ 299 and 1000 ÷ (200 ÷ 25.4) ≈ 127. Against a 300 dpi target, only page 3 is low resolution.
How to use it
- Add a PDF; the summary cards appear first.
- Switch to the tab you need: size, fonts, resolution, page boxes, ink or preflight.
- Save the report (Markdown, CSV, JSON and so on) or follow a card's link to a fixing tool.
Frequently asked questions
If it says PDF/A, does the file pass archival validation?
No. Only the XMP claim is read. For what the standard actually requires, see the guide “PDF/A and PDF/X”, and use a dedicated validator for conformance.
Why is the per-page total in the size tab larger than the file?
An image used on several pages is added to each of them. The per-category totals count every object once and add up to the file size. Which parts shrink under compression is covered in the guide “Why PDF compression varies”.
If preflight passes, will the printer accept the file?
Not guaranteed. It cannot see ink totals after overlapping or transparency blending, the ink in JPEG-compressed CMYK images, or white objects set to overprint. Enter the values from your printer's spec sheet before running it.
Related guides
Sources
Last reviewed: