Change the Version of a PDF File
Changing a PDF's version means rewriting the %PDF-x.y header (and catalog Version entry) that declares which edition of the format the file claims to follow — the value upload portals and print shops check. This tool rewrites the file with qpdf in your browser: raising the version is always safe, while forcing a downgrade can strip features the older version cannot express. Your file never leaves your device.
How it works
The first bytes of every PDF are a comment line such as %PDF-1.6. It declares which edition of the format the file follows — 1.0 (1993) through 1.7 (standardized as ISO 32000-1) and 2.0 (ISO 32000-2). Since PDF 1.4, a Version entry in the document catalog may override the header upward. Validators at government upload portals, court e-filing systems, and prepress workflows often check this declared version against an allowed list before they even parse the content, which is how a perfectly renderable file gets rejected with a message like "PDF version not supported".
This tool rewrites the file with qpdf, the open-source PDF transformation tool, compiled to WebAssembly (about 1.2 MB, downloaded once on first use and cached; everything runs locally). It offers qpdf's two distinct modes. Raise (min-version) uses --min-version: the declared version is lifted to your target and never lowered. Because every newer PDF version is a strict superset of the older ones, relabeling a 1.4 file as 1.7 requires no content changes at all — it is always safe, and it is the right fix when a portal demands "at least PDF 1.6".
Force (exact version) uses --force-version and writes exactly the header you ask for, even if that is a downgrade. This is not just a relabel: qpdf actively removes constructs the target version cannot express, because a strict consumer of, say, PDF 1.4 must be able to parse the result. Forcing below 1.5 expands compressed object streams and cross-reference streams into classic uncompressed form (the file grows). Forcing below 1.6 replaces AES encryption with the weaker RC4. Features tied to 1.7 or 2.0 — certain annotation types, layer configurations, extended transparency — can be dropped outright. Pages, text, and images survive, but the output may genuinely differ from the input, so treat force mode as a conversion, check the result in a viewer, and keep your original.
Note what this tool does not do: it neither converts to the PDF/A archival profile (see the PDF to PDF/A guide — that involves fonts, color spaces, and metadata, not a header) nor optimizes the file for the web (that is a separate operation).
Worked example: a court portal that caps uploads at PDF 1.7
A 22-page, 3.4 MB scanned exhibit exported from a 2025 macOS app carried a %PDF-2.0 header. A state e-filing portal rejected it instantly: "Accepted formats: PDF 1.4–1.7". The document used nothing exclusive to 2.0 — the exporter simply stamps every file 2.0.
Loaded into this tool, the detected version showed 2.0. Force mode with target 1.7 rewrote the file in about 3 seconds; because no 2.0-only features were present, nothing was stripped and the output was 3.3 MB — marginally smaller, since qpdf also writes a clean single revision. The portal accepted the resubmission. The reverse case from the same week: a print shop running an older RIP asked for "PDF 1.3, no transparency". Forcing that file (a 1.6 brochure with object streams) down to 1.3 grew it from 8.1 MB to 9.8 MB as object streams were unpacked, and qpdf's warnings listed the transparency it could not represent — the honest signal to re-export flattened artwork rather than trust a silent conversion.
Frequently asked questions
How do I check which PDF version a file is?
Open the file in any text or hex editor and look at the first line, which reads %PDF-1.7 or similar; a Version entry in the document catalog can override it upward. Most viewers also show the version under document properties. This page displays the detected version as soon as you load a file.
Why does an upload portal reject my PDF because of its version?
Many government portals, court filing systems, and print shops validate the header against an allowed range, commonly PDF 1.4 through 1.7, and reject anything outside it before looking at the content. A file stamped PDF 2.0 by a modern exporter can fail such checks even though its actual features would render fine. Setting the header to an accepted value usually satisfies the validator.
Is it safe to change the version number of a PDF?
Raising the version is always safe, because every newer version is a superset of the older ones and no content changes. Downgrading the header only relabels the file; if the document uses features the older version lacks, a strict downgrade must remove them, which can change behavior. That is why this tool separates the safe minimum-version mode from the force mode.
What is the difference between raising and forcing the PDF version?
Raise mode uses a minimum-version rule: the header is increased to the value you choose and never lowered, so nothing in the file needs to change. Force mode writes exactly the version you request even if that is lower, and qpdf then strips constructs the target version cannot express, such as object streams below 1.5 or AES encryption below 1.6. Use force only when a workflow genuinely demands an older header.
What can break when I downgrade a PDF to an older version?
Forcing below 1.5 unpacks compressed object streams and cross-reference streams into classic uncompressed form, which grows the file. Forcing below 1.6 downgrades AES encryption to RC4, weakening protection, and files using 1.7 or 2.0 extensions can lose transparency groups, layer settings, or annotation types. Pages and text are preserved, but verify the output in a viewer before submitting it.
Does changing the PDF version convert the file to PDF/A?
No. PDF/A is an archival profile defined by ISO 19005 that imposes requirements far beyond the header, including embedded fonts, device-independent color, and XMP metadata. A portal that demands PDF/A needs a real conversion with a validator, not a version stamp. See the PDF to PDF/A guide for routes that actually pass verification.