PDFJadoo › Blog › PDF Inspector: File Checkup

PDF Inspector: one report that explains the whole file

Every PDF problem is a symptom; the cause lives in the file's structure. Prints wrong? The page sizes may vary inside one document. Looks wrong on another machine? The fonts may not be embedded. Forty megabytes for nine pages? The images' real resolutions tell the story. Behaves oddly on open? JavaScript may be riding along. PDF Inspector reads the structure and writes the chart: page sizes, fonts embedded or not, image resolutions, form fields, JavaScript, encryption and metadata — in plain language, downloadable as a text file. This article is a guided tour of the chart: what each line means, and what to do about the answers you don't like.

Free, in your browserFiles never uploadedStructure · fonts · security — one report
PDFJadoo logoBy the PDFJadoo Team6 min read
Diagram: a PDF under a magnifier, revealing a checklist of fonts, images, fields and encryption
Diagnose before you treat: the chart first, the tool second.

Reading the chart, line by line

Page sizes. A healthy document is uniform — all A4, all Letter. Mixed sizes explain a shelf of printing mysteries (the printer “choosing” paper, pages scaling oddly) and usually mean merged sources: the cure is resizing to one size. Fonts embedded? Embedded fonts travel with the file, so it renders identically everywhere; unembedded fonts are borrowed from the viewer's machine, and a missing one is silently substituted — the document that “looks wrong on their computer”. For anything published or archived, embedded is the only acceptable answer. Image resolutions. The 40 MB mystery lives here: images stored at resolutions far beyond print need. The chart names the effective resolution; the cure is the compression conversation (compress honestly), chosen with the numbers in hand.

Form fields — their presence and count: a “flat” document that secretly carries fields explains fill-behaviour surprises, and a form whose fields the chart cannot find is not a form at all. JavaScript — present or absent: in your own form, expected; in a stranger's attachment, a reason to sanitize before keeping. Encryption — whether the file is protected and how: the answer that explains a tool refusing to process it, and the prompt to unlock it with its known password first. Metadata — the identity card, shown alongside: title, author, lineage — the fields the metadata editor fixes.

Diagnosis before treatment

The inspector changes nothing — and that is its place in the kit. Every other tool in this batch treats: sanitizes, repairs, flattens, linearizes. Treating without a chart is guessing with side effects. The professional sequence is inspect → decide → treat → (often) inspect again to confirm. The downloadable report makes the chart a record: attach it to the job ticket, the production log, the email that says “here is what was wrong with the file you sent us”.

Inspect a PDF, step by step

Step 1 — drop the PDF onto PDF Inspector. The reading is structural and local — the file is examined in your browser, not uploaded for examination.

Step 2 — read the chart top to bottom. Page sizes uniform? Fonts embedded? Images proportionate? Fields as expected? JavaScript accounted for? Encryption understood? Metadata respectable?

Step 3 — download the report if the file matters. The chart as a text file, filed with the job.

Step 4 — treat what the chart indicts. Each finding maps to a tool: mixed sizes → resize; bloat → compress; scripts → sanitize; wrong identity → metadata editor; damage symptoms → repair.

The pre-flight habit

Files that will be published, produced in litigation, archived or printed at scale deserve the chart before the event, not after the mystery. Thirty seconds of inspection is the cheapest gate in document work — the inspector is built to be that gate.

Read the chart before you treat the file.

Page sizes, fonts, images, fields, scripts, encryption, metadata — one plain-language report, downloadable.

Open PDF Inspector

A worked example: the brochure that printed wrong

A 24-page brochure prints with three pages scaled oddly and the print shop blames the file; the designer's machine shows perfection. The chart settles it in one read: pages 7, 13 and 19 are a different size (an ad supplier's pages, merged in), and one font is not embedded — on the shop's system it substitutes, on the designer's it was present all along. Two findings, two cures: resize the set to one size, and re-export the designer's pages with fonts embedded (then re-inspect to confirm). The argument between shop and designer ends — replaced, as arguments should be, by a chart.

Edge cases

Encrypted files. A file locked with an open password must be unlocked (password known) before its structure can be read — the chart reports the lock it can see.

Damaged files. A file too broken to parse gives a short chart; that shortness is itself the diagnosis pointing at repair.

“Everything green, still wrong.” Structure can be healthy while content is wrong — the chart certifies the file's mechanics, never its meaning. Proofreading remains a human tool.

Before you finish: the 60-second check

Fair questions

How do I check if a PDF's fonts are embedded?

Drop the file onto PDF Inspector: the report lists the fonts and whether they are embedded. Unembedded fonts are borrowed from the viewer's machine and may be substituted — the classic cause of “looks wrong on their computer”.

What does the inspector check?

Page sizes, font embedding, image resolutions, form fields, JavaScript, encryption and metadata — read from the file's structure and reported in plain language, downloadable as a text file.

Why is my PDF so large?

Usually images stored at far higher resolution than their printed size needs. The inspector's image lines show the effective resolutions; with the numbers known, compression can be chosen honestly instead of blindly.

Can the inspector tell me if a PDF is encrypted?

Yes — encryption status is one of the chart's lines, which explains tools refusing to process a file and points to unlocking it first (with its known password).

Does inspecting change the file?

No — the inspector only reads. It is the diagnosis step: inspect, decide, then treat with the right tool, and re-inspect to confirm if the file matters.

Is my file uploaded for inspection?

No — the file is examined in your browser; nothing leaves your device.

Tool behaviour — the structural report covering page sizes, font embedding, image resolutions, form fields, JavaScript, encryption and metadata, in plain language with a downloadable copy — is from PDFJadoo's own PDF Inspector page. Checked 18 November 2026.

Keep reading