Skip to content
MyPDFilesLocal PDF tools

Developer Tools

PDF Version Checker

Check which PDF version a file claims, and what that version can and cannot do.

Processed locally in your browser. Your file is not uploaded to any server. How this works

  1. 01Add your file
  2. 02PDF Version Checker
  3. 03Download

Runs in your browser · nothing uploaded

About PDF version checker

Every PDF opens with a header line such as %PDF-1.7 that declares which version of the specification it was written against. That number is not decoration: it is a contract about which features a reader may expect to encounter. But it is only one of two places a version can be recorded. The document catalogue may also carry a /Version entry, and when the two disagree the catalogue wins, because it is the one an editor can update cheaply after adding a feature that the original header predates. This tool reports both values, tells you which one a conforming reader will honour, and explains what the declared level implies — which encryption strengths are available, whether transparency and optional content are permitted, whether the file may use compressed cross-reference streams. It is the quick answer when a downstream system rejects a file for being "too new", or when you need to know whether a target platform from a decade ago will cope.

How to PDF version checker

  1. 01

    Drop the PDF in

    The header line is read from the first bytes; the catalogue entry is resolved from the trailer.

  2. 02

    Compare the two values

    Both are shown, with the effective version a reader will use called out explicitly.

  3. 03

    Read the implications

    The report lists what the effective level allows, so you can judge compatibility with a specific target.

What this tool does

  • Header version read from the %PDF- line at the start of the file
  • Catalogue /Version entry resolved and compared, with precedence explained
  • Effective version stated plainly rather than left for you to work out
  • Feature implications per level: encryption strength, transparency, object and xref streams, optional content, attachments
  • A note when the declared version is older than features actually used in the file

Limitations worth knowing

Every PDF tool has constraints. Stating them plainly is more useful than discovering them halfway through your work.

  • A declared version is a claim, not a guarantee. Producers regularly stamp a conservative header while using newer constructs.
  • The feature notes describe what the specification permits at each level; they do not test whether a particular reader implements it.
  • PDF 2.0 files are identified as such, but this tool does not assess conformance to ISO 32000-2.
  • A file whose header is missing or malformed is reported as unknown rather than guessed at.

How your file is handled

This tool runs entirely inside this browser tab. When you choose a file, your browser reads it from your own disk and hands the bytes to JavaScript running on this page — no network request carries your document anywhere. You can confirm that yourself: open your browser’s developer tools, switch to the Network panel, and run the tool. You will see no upload.

Nothing is stored after the fact. Closing or reloading this tab discards the file, the result and everything derived from them, because none of it ever left your machine. Read how local processing works.

Questions about PDF version checker

Which version wins when the header and the catalog disagree?

The catalogue /Version entry. A conforming reader treats it as authoritative precisely so that an editor adding a newer feature can record the higher version without rewriting the file header. If your tooling reads only the header, it may be working from an outdated number.

What do the version levels actually change?

Briefly: 1.4 brought transparency and 128-bit RC4 encryption; 1.5 added cross-reference streams, object streams and optional content groups, which is where layers come from; 1.6 added embedded file collections and AES-128; 1.7 is the ISO 32000-1 baseline most tools target, with AES-256 arriving in an extension level; 2.0 formalises AES-256 and removes long-deprecated constructs.

A system rejected my PDF as too new. What do I do?

Check the effective version here first, because the rejection may be triggered by the catalogue value rather than the header. If the file genuinely uses newer constructs, the practical fix is to re-save it through a producer targeting the older level, accepting that features the older level cannot express will be flattened or dropped.

Does a newer version mean a better or smaller file?

Not by itself. Later versions make smaller files possible — compressed xref and object streams are genuine savings — but the version number only permits those constructs, it does not apply them. To find out whether your file uses them, check its structure.

Tools that pair with this one

Read more about this

Background