How to update an old pdf to a newer version standard
- Step 1Confirm why you're upgrading — Upgrade when a downstream tool wants the 1.7 baseline, or to re-serialize an old 1.3/1.4 file into the compact object-stream form. Don't expect the version bump alone to add accessibility tags or new features — those are separate steps the new version merely allows.
- Step 2Open the converter and drop the old PDF — Load the document into the PDF Version Converter. It runs in your browser through pdf-lib — nothing is uploaded. One file at a time.
- Step 3Select 1.5, 1.6, or 1.7 in the dropdown — The control lists PDF 1.4, 1.5, 1.6, and 1.7 (default 1.7). Pick 1.7 for the modern baseline. Any target above 1.4 saves with object streams on. There is no 2.0 option.
- Step 4Run the conversion — Each page is copied into a new document, saved with
useObjectStreams: true, and the header is set to your chosen version. The structure is modernised; the content is preserved. - Step 5Add the modern features you actually need, separately — Now that the version permits them, apply the real features as their own steps: XMP/metadata cleanup with PDF Metadata Scrubber, or an archival/accessible profile via PDF to PDF/A. The version bump itself doesn't add these.
- Step 6Download and verify in your target tool — Save
<name>.version-converter.pdfand confirm it loads in the toolchain that wanted the newer baseline. Check that nothing you needed (forms, bookmarks) was lost — re-add if so.
What 'updating the version' actually changes
Re-serialization vs. the features people often assume an upgrade adds.
| Expectation | Reality with this tool | How to actually get it |
|---|---|---|
| Smaller / cleaner file structure | Yes — object streams + compressed xref (targets above 1.4) | Built in; pick 1.5/1.6/1.7 |
| Tagged PDF (accessibility) | Not added by a version bump | A tagging/PDF-UA tool; PDF to PDF/A for an archival pass |
| XMP metadata | Not added; existing metadata's Producer/ModDate are rewritten | A metadata editor; clean with Metadata Scrubber |
| PDF 2.0 features | Not available — max target is 1.7 | A desktop tool that outputs ISO 32000-2 |
| Stronger encryption (AES) | Not added — output is unencrypted | PDF Password Protect after converting |
Target versions this tool offers (upgrade direction)
1.7 is the highest available and the modern baseline. 2.0 is not supported.
| Target | Object streams | Best for upgrading to | Available? |
|---|---|---|---|
| 1.5 | ON | Minimum for the compact object-stream structure | Yes |
| 1.6 | ON | Adds AES-128 capability to the version flag | Yes |
| 1.7 | ON (default) | ISO 32000-1 baseline — recommended modern target | Yes |
| 2.0 | — | ISO 32000-2 features | No (use a desktop tool) |
Cookbook
What you really get when you 'update' an old PDF, and the upgrades that need a different tool.
Old 1.4 file modernised to 1.7
A 1.4 document with the classic uncompressed xref, bumped to 1.7. It's re-serialized with object streams and is usually a touch smaller.
Input header: %PDF-1.4 (plain xref, no object streams) Target: PDF 1.7 Output header: %PDF-1.7 Structure: object streams ON + compressed xref Size: typically slightly smaller Text: still selectable
Strict toolchain wanted the 1.7 baseline
A modern PDF library refused to ingest a 1.3 file. Upgrading to 1.7 gives it the baseline it expects.
Symptom: downstream library warns 'legacy PDF version' Target: PDF 1.7 Output: %PDF-1.7, modern serialization → library ingests it
Version bump did NOT add accessibility tags
A common misconception: upgrading to 1.7 doesn't tag the PDF. Tagging is a separate operation the higher version merely permits.
Goal: accessible (tagged) PDF
Target: PDF 1.7
Result: %PDF-1.7 but STILL untagged
Real fix: run a tagging/PDF-UA tool, or PDF to PDF/A for an
archival+structure pass — the version bump alone won't.Asked for 2.0 — not available
There's no PDF 2.0 option. The highest target is 1.7. If you genuinely need ISO 32000-2, this isn't the tool.
Wanted: PDF 2.0 (ISO 32000-2) Dropdown: 1.4 / 1.5 / 1.6 / 1.7 only Closest available: 1.7 For real 2.0 output, use a desktop tool (e.g. Acrobat).
Forms and bookmarks lost in the upgrade
Upgrading a 1.4 form to 1.7 drops the AcroForm and outlines, because the page-copy rebuild doesn't carry document-level structures.
Input: 1.4 with fillable fields + bookmarks Target: PDF 1.7 Output: %PDF-1.7, FIELDS + BOOKMARKS dropped If the values must stay visible: PDF Flatten first, then upgrade.
Edge cases and what actually happens
You expected PDF 2.0 output
Not supportedThe Target version dropdown tops out at 1.7 — there is no 2.0 (ISO 32000-2) option. Selecting the highest available value gives you 1.7. For genuine PDF 2.0 features (associated files, improved encryption, PDF/UA-2), use a desktop tool such as Acrobat or a library that supports ISO 32000-2.
Upgrading didn't add accessibility tags
Not addedBumping the version permits tagged PDF but does not create the structure tree. An untagged 1.4 file becomes an untagged 1.7 file. Use a dedicated tagging / PDF-UA tool, or run the PDF to PDF/A pipeline for an archival+structure pass — the version number alone changes nothing about accessibility.
No XMP metadata appeared after upgrading
Not addedVersion conversion doesn't synthesise XMP metadata. In fact the save rewrites the existing Producer and ModDate. If you need clean or specific metadata, edit it separately — PDF Metadata Scrubber removes identifying fields losslessly.
File didn't get smaller (or got bigger)
Depends on sourceUpgrading from a 1.3/1.4 file to 1.7 usually shrinks it slightly because object streams compress the structure. But if the source was already 1.5+ with object streams, re-serializing won't meaningfully reduce size. For real size reduction use PDF Compress (Lossless) or the Font Subsetter.
Form fields, bookmarks, or signature gone
Dropped by designThe page-copy rebuild doesn't carry AcroForm fields, outlines, document JavaScript, or signatures — upgrading the version doesn't change that. Flatten forms first with PDF Flatten to keep values visible; re-sign after with PDF Digital Signature.
Source was encrypted
DecryptedThe upgrade output is unencrypted regardless of the input — the converter reads past encryption and rebuilds without a security handler, and there's no password field on this tool. Re-apply protection afterward with PDF Password Protect if needed; targeting 1.6+ permits AES, but you set that in the protect tool, not here.
Upgrading a very old 1.0/1.1 PDF
Header set to targetpdf-lib reads older 1.x files and rebuilds them; the output header is set to your chosen target (e.g. 1.7). Extremely old PDFs occasionally use constructs pdf-lib normalises differently — verify the result renders correctly before relying on it for archival.
Producer / ModDate changed
ExpectedThe save updates document metadata, so the Producer string and modification date reflect the conversion, not the original tool that authored the old PDF. That's normal for a re-serialization. Scrub or set metadata afterward if your workflow tracks it.
File exceeds the tier size or page cap
400 limitOld documents can still be large scans. Free tier caps at 2 MB / 50 pages, Pro at 50 MB / 500 pages, Pro+Media at 500 MB / 2,000 pages, Developer at 2 GB / 10,000 pages. Upgrade your tier, or reduce the file first with PDF Compress (Lossless).
Expected the upgrade to enable transparency or layers
Not addedA higher version permits features like advanced transparency and optional content (layers), but version conversion doesn't add them to content that doesn't already use them. The visible content is identical — you only get the structural/serialization change, not new graphic capabilities.
Frequently asked questions
Can this tool save my PDF as version 2.0?
No. The Target version dropdown offers only 1.4, 1.5, 1.6, and 1.7 — the highest available is 1.7 (the ISO 32000-1 baseline). There is no PDF 2.0 (ISO 32000-2) output. If you specifically need 2.0 features such as associated files, the newer encryption schemes, or PDF/UA-2, use a desktop tool like Acrobat or a library that supports ISO 32000-2.
Does upgrading the version make my PDF accessible (tagged)?
No. A newer version *permits* tagged PDF, but bumping the version number doesn't create the structure tree that makes a document accessible. An untagged file stays untagged after upgrading. Accessibility tagging is a separate operation — use a dedicated tagging/PDF-UA tool, or the PDF to PDF/A pipeline for an archival pass.
Will upgrading add XMP metadata?
No. Version conversion doesn't synthesise XMP. The save actually rewrites the existing Producer and modification-date fields, so metadata changes but isn't enriched. To set or clean metadata, do it separately — PDF Metadata Scrubber removes identifying fields without otherwise altering the file.
Why would I upgrade an old PDF at all?
Two practical reasons. First, to re-serialize a 1.3/1.4 file into the compact object-stream + compressed-xref structure, which is usually a bit smaller. Second, because some strict modern toolchains and libraries prefer (or warn on anything below) the 1.7 baseline. If neither applies and the old file works, there's no need to upgrade — the version number isn't a quality score.
Does upgrading make the file bigger or smaller?
Upgrading from a pre-1.5 file (no object streams) to 1.7 typically makes it slightly smaller because the structure gets compressed. Upgrading a file that's already 1.5+ won't change size much. For meaningful reduction, use PDF Compress (Lossless) or strip unused glyphs with the Font Subsetter — version conversion isn't a size tool.
Will my text stay selectable after upgrading?
Yes. Upgrading re-serializes the page objects rather than re-rendering them, so text, fonts, and images are preserved and text stays selectable and searchable. It's a structural change, not a rasterisation.
What gets lost when I upgrade?
The same things any version change drops in this tool: interactive form fields (AcroForm), bookmarks/outlines, document JavaScript, and any existing digital signature; the output is also unencrypted. Page content is preserved. If you have a fillable form, flatten it first with PDF Flatten so the values become part of the page; re-sign with PDF Digital Signature after.
Is 1.7 widely supported?
Yes — PDF 1.7 is ISO 32000-1 and is the de-facto modern baseline that virtually every current reader, browser, and PDF library handles. It's the recommended target for general modernisation. Only go higher (2.0) if you specifically need ISO 32000-2 features, which this tool doesn't produce.
Can I add AES encryption as part of upgrading to 1.6+?
Not in this step. Targeting 1.6 or 1.7 makes the version capable of AES, but the converter outputs an unencrypted file. Apply encryption separately with PDF Password Protect after converting. Keep the order in mind: upgrade the version first, then protect, since converting strips encryption.
Is my document uploaded?
No. The upgrade runs entirely in your browser via pdf-lib — the file never leaves your device. Only an anonymous usage counter is recorded when you're signed in, and you can opt out in account settings.
Can I upgrade many old files at once?
The browser tool handles one file per run. For a bulk modernisation, the converter is available through the @jadapps/runner on a paid tier: fetch GET /api/v1/tools/pdf-version-converter, pair the runner once, and POST each file with { "version": "1.7" } to 127.0.0.1:9789/v1/tools/pdf-version-converter/run. Files are processed locally — nothing is uploaded.
How large a file can I upgrade?
It depends on your tier: free is 2 MB / 50 pages, Pro 50 MB / 500 pages, Pro+Media 500 MB / 2,000 pages, Developer 2 GB / 10,000 pages, beyond which browser memory is the limit. Large legacy scans may need compressing first with PDF Compress (Lossless).
Privacy first
All PDF processing runs locally in your browser using PDF-lib and pdf.js. No file is ever uploaded — only metadata counters are saved for signed-in dashboard stats.