Most of the time you don't think about which version a PDF declares in its header. Then a portal rejects your file with "PDF version not supported" or an old print system refuses to render it, and suddenly the version is the only thing that matters.
This guide walks through changing a PDF's version — what the operation actually does, when to use it, and which version to target. For the longer background on what PDF versions are and what each version adds, see PDF Versions Explained.
When you need to change a PDF's version
You don't change a PDF's version "just because". Three common triggers:
- An intake system rejects your file with a message like "PDF version not supported" or "requires PDF 1.4 or earlier". Downgrade to the version it asks for.
- An older print RIP, scanner driver, or document management system silently fails on the file. These typically max out at PDF 1.4 or 1.5 and balk at 1.7+ headers even if the content itself would be readable.
- You're producing files for a workflow that requires ISO 32000-1 (PDF 1.7) specifically. Submissions to courts, regulators, or institutional archives sometimes pin the required version.
If the file opens fine everywhere you need it to open, you don't need to change the version. The operation is purely about satisfying a downstream consumer's check.
The steps
- Open the Change PDF Version tool and upload your PDF.
- Pick the target version. The choices are 1.3, 1.4, 1.5, 1.6, 1.7, and 2.0. If the system you're submitting to didn't specify a version, pick 1.7 — it's the ISO 32000-1 standard and the widest compatibility target.
- Click Change Version.
- Download the result. The filename is prefixed with the version
(e.g.
v1.4_invoice.pdf) so you can keep multiple variants without overwriting the original.
That's the entire flow. The operation takes the same time on a 1-page document as on a 1000-page one because only the header is rewritten.
Which version should I pick?
If the receiving system didn't specify a target, use this as a default map:
- 1.4 — legacy intake portals, government mainframes, PDF/A-1 archival prep. The most common "lowest common denominator".
- 1.5 — older RIPs and document management systems that still need an upgrade past 1.4 but don't handle 1.7.
- 1.7 — the modern safe default and the ISO 32000-1 standard. Pick this if you don't have a specific reason to pick something else.
- 2.0 — only when a workflow explicitly requires ISO 32000-2. Some older readers still struggle with 2.0 files; don't pick this if your audience isn't certain to be on modern viewers.
1.3 and 1.6 are rarely the right targets. 1.3 is older than most deployed systems require; 1.6 is a stepping stone to 1.7 with no unique advantage.
What "change version" actually does
The tool rewrites a single field in the PDF's header — the
%PDF-X.Y line at the start of the file. Page content, fonts,
images, and compression are not touched. That means:
- Quality is identical. No re-encoding, no recompression.
- File size doesn't meaningfully change. The header rewrite shifts a handful of bytes.
- Features inside the file are preserved. A 1.7 file with transparency, downgraded to 1.4, still contains transparency. The downgraded file declares 1.4 in the header but its body is technically what 1.7 would have looked like.
That last point matters: this is a header rewrite, not a true downgrade. Modern viewers handle the discrepancy fine. Strict consumers that only check the header (the common case for intake systems) also accept the file. The edge case is a strict consumer that parses every object and rejects features illegal for the declared version — rare, but it happens. If you hit that, you'd need to re-render the PDF without the newer features, which is a different (lossy) operation.
For most users in the common case — passing an intake check — the header rewrite is exactly the right tool.
Common questions
Will this change the file's appearance or contents?
No. The operation only touches the version header. Open the result next to the original and they should be visually and structurally identical except for the version number.
Will changing the version reduce file size?
No. If size is the goal, compress the PDF — that's a separate operation. You can do both: change the version, then compress, in either order.
Does changing the version break a digital signature?
Yes for certificate-based signatures, no for visual signature stamps. A certificate-based signature cryptographically covers a byte range; rewriting the header changes those bytes and invalidates the signature. Visual signatures (drawn or typed signatures with no cryptographic metadata) are just rendered marks on the page and stay intact. If you need to keep a digital signature valid, change the version before signing, not after.
Can I change the version of a password-protected PDF?
Not directly. Unlock PDF first (you'll need the original password), change the version, then re-apply protection with Protect PDF if needed.
What if I downgrade and the file stops working?
The file's header now declares an old version, but features inside might be newer than that version allows. Most modern viewers ignore this and render the file anyway. If a strict consumer rejects it, you either need a less aggressive target version (try 1.5 instead of 1.3) or a true re-render without the newer features. The latter is outside what a header rewrite can do — it requires re-generating the PDF from source.
How do I find out which version my PDF currently uses?
Open in Acrobat → File → Properties → "PDF Version" field.
On Mac, Preview → Tools → Show Inspector → General. Or in
the file itself, the very first line is %PDF-1.7 (or whatever
the version is).
Is "change version" the same as "convert to PDF/A"?
No. PDF/A is a much stricter constrained subset of PDF — it mandates embedded fonts, no encryption, no JavaScript, embedded color profiles, and more. A version change only rewrites the header. If you need archival-grade output, use PDF to PDF/A instead. The two operations have different goals: version change satisfies a header check; PDF/A satisfies an archival standard.
Wrap-up
Changing a PDF's version is a small operation with a narrow purpose: pass a downstream consumer's header check. It's lossless, preserves everything inside the file, and takes seconds regardless of document size. The decision-making is in the target version, not in the operation itself.
If you find yourself doing this regularly for the same workflow, look at your authoring step — most tools that export PDFs let you pick the version at export time. The change-version tool is for fixing existing files; if a known workflow always needs PDF 1.4, configure the exporter to produce 1.4 in the first place.