How to convert a pdf to version 1.4 for maximum compatibility
- Step 1Confirm 1.4 is really what the target needs — If a legacy reader rejects your file, it is almost always choking on the PDF 1.5+ compressed cross-reference / object streams rather than the version number alone. PDF 1.4 is the safest target because it forces the old serialization. If you only need 1.5 or 1.6, those keep object streams and are covered by the downgrade-for-old-readers guide.
- Step 2Open the version converter and drop your PDF — Load the document into the PDF Version Converter. Parsing and rewriting happen in your browser through pdf-lib — nothing is uploaded. The tool accepts a single PDF at a time.
- Step 3Choose PDF 1.4 in the Target version dropdown — The only control is one dropdown listing PDF 1.4, 1.5, 1.6, and 1.7 (it defaults to 1.7). Select PDF 1.4. Choosing 1.4 is the one setting that switches object streams off.
- Step 4Run the conversion — The tool copies every page into a new document, saves with
useObjectStreams: false, and patches the header bytes to%PDF-1.4. Selectable text, fonts, and images are preserved page-for-page. - Step 5Download and open in the legacy viewer — The output downloads as
<name>.version-converter.pdf. Open it in the exact reader or embedded component that rejected the original — that is the only test that proves compatibility. - Step 6Re-add anything the rebuild dropped — If the source had interactive form fields, bookmarks, or a digital signature, those do not survive the page-copy rebuild. Re-flatten or re-add as needed — for example, fill-and-flatten a form with PDF Flatten, or re-apply a signature with PDF Digital Signature.
What changes when you target PDF 1.4
PDF 1.4 is the only target that disables object streams; everything 1.4 can't represent is written in the older form instead.
| Aspect | At PDF 1.4 (this target) | Why |
|---|---|---|
| Cross-reference / object streams | OFF — plain xref table + trailer | 1.5 introduced compressed xref + object streams; a 1.4-only reader can't parse them. The tool sets useObjectStreams: false for 1.4. |
| File header | %PDF-1.4 | The header bytes are overwritten so version checks in validators and old readers read 1.4. |
| Page content, fonts, images | Preserved, text stays selectable | Pages are copied object-for-object; this is a re-serialization, not a re-render. |
| Interactive form fields (AcroForm) | Dropped | pdf-lib's page copy carries page-level objects, not the document AcroForm catalog. |
| Bookmarks / outlines, document JavaScript | Dropped | These are document-level structures outside the copied pages. |
| Encryption / password | Removed — output is unencrypted | The file is rebuilt as a fresh, unencrypted document (encrypted input is read with ignoreEncryption). |
| Producer / ModDate metadata | Rewritten on save | The save path updates document metadata, so Producer and modification date reflect the rebuild, not the original. |
PDF version → feature baseline (for choosing a target)
Why 1.4 is the widest-compatibility floor. Only 1.4, 1.5, 1.6, and 1.7 are offered by this tool.
| Version | Year / Acrobat | Notable structural feature | This tool |
|---|---|---|---|
| 1.4 | 2001 / Acrobat 5 | Transparency; no object streams; PDF/A-1 baseline | Object streams OFF |
| 1.5 | 2003 / Acrobat 6 | Object streams + compressed xref, optional content (layers) | Object streams ON |
| 1.6 | 2004 / Acrobat 7 | AES-128, OpenType embedding | Object streams ON |
| 1.7 | 2006 / Acrobat 8 (ISO 32000-1) | Tool default; broadest modern support | Object streams ON (default) |
| 2.0 | 2017 (ISO 32000-2) | Not offered by this tool | Use a desktop preflight tool |
Cookbook
What the tool actually produces when you target 1.4, including the cases where the result is not what people first expect.
A 1.7 report that an old embedded viewer rejected
The classic case: a text-and-image report saved at 1.7 with compressed xref won't open in a legacy embedded component. Targeting 1.4 rewrites the structure to the plain form.
Input header: %PDF-1.7 (compressed xref / object streams) Target: PDF 1.4 Output header: %PDF-1.4 Structure: plain xref table + trailer (object streams OFF) Text: still selectable Result: opens in the legacy viewer
Form PDF loses its fillable fields
A 1.7 PDF with interactive AcroForm fields, downgraded to 1.4. The page-copy rebuild does not carry the document AcroForm catalog, so the fields disappear.
Input: acroform with 12 text fields + 3 checkboxes (1.7) Target: PDF 1.4 Output: %PDF-1.4, fields GONE (field appearances/values not preserved) If you need the data baked into the page, flatten first: PDF Flatten → then PDF Version Converter (1.4)
Already 1.4 — but still rebuilt
Running a file that is already 1.4 through the tool is not a no-op. It is re-saved (plain xref retained) and the Producer/ModDate metadata is refreshed.
Input header: %PDF-1.4 Target: PDF 1.4 Output header: %PDF-1.4 (re-serialized, object streams OFF) Note: Producer + ModDate are rewritten on save
Encrypted input comes out unencrypted
The converter reads past encryption to rebuild the file. Because it builds a fresh document with no security handler, the 1.4 output has no password.
Input: AES-128 encrypted, %PDF-1.6 Target: PDF 1.4 Output: %PDF-1.4, NO encryption If you need it protected again, re-apply with PDF Password Protect.
On the path to PDF/A-1b
PDF/A-1b is built on the PDF 1.4 structure. Converting to 1.4 satisfies the version floor — but full PDF/A also needs embedded fonts and an output intent.
Goal: archival PDF/A-1b Step 1: PDF Version Converter → 1.4 (version baseline) Step 2: embed any non-embedded fonts (Font Subsetter) Step 3: PDF to PDF/A for the output-intent + tagging pass
Edge cases and what actually happens
Interactive form fields disappear after converting to 1.4
Dropped by designpdf-lib's page copy carries page-level objects, not the document AcroForm catalog, so fillable fields are not preserved. This is independent of the version target. If you need the entered data kept, fill and flatten the form with PDF Flatten before converting — flattening bakes field values into the page content, which the page-copy does carry.
Bookmarks / outlines are gone
Dropped by designDocument outlines (bookmarks) live in the document catalog, not on individual pages, so they are not preserved by the page-copy rebuild. There is no option to retain them in this tool — re-create bookmarks afterward in a desktop editor if they matter.
A digital signature is invalidated
InvalidatedRe-serializing the file changes its bytes, so any existing digital signature no longer validates (and the signature object itself is not carried through the rebuild). Convert first, then re-sign with PDF Digital Signature. You can confirm a signature's state before/after with PDF Signature Verify.
The PDF was encrypted
DecryptedThe converter reads the file with encryption ignored and rebuilds it without a security handler, so the 1.4 output is unencrypted regardless of the input's password. There is no password field on this tool. If protection is required on the result, re-apply it with PDF Password Protect.
Producer and modification date changed
ExpectedThe save step updates document metadata, so the Producer string and ModDate reflect the conversion rather than the original authoring tool. If you need clean metadata afterward, run PDF Metadata Scrubber.
PDF 1.4 layers / optional content lost
ExpectedOptional content groups (layers) arrived in PDF 1.5. They are not part of the 1.4 feature set, so a layered source converted to 1.4 loses its layer structure (the content typically flattens to a single visible layer). If layers matter, target 1.5 or higher instead via the downgrade guide.
File is over your tier's size or page cap
400 limitPDF tools cap at 2 MB / 50 pages on the free tier, 50 MB / 500 pages on Pro, and 500 MB / 2,000 pages on Pro+Media. A large scanned 1.7 PDF can exceed the free cap. Upgrade, or reduce the file first with PDF Compress (Lossless).
Converted to 1.4 but the old reader still complains
InvestigateThe header is 1.4 and object streams are off, so the structural blockers are gone. If a viewer still fails, the cause is usually a content feature (e.g. a JPXDecode / JPEG2000 image, which is a 1.5 feature) rather than the version flag. Re-encode such images, or rasterise the affected pages with the lossy compressor, then re-convert.
Output is a touch larger than the 1.7 original
ExpectedTurning object streams off removes the cross-reference/object-stream compression that 1.5+ files use, so a 1.4 file of the same content can be slightly larger. That is the cost of the older, more compatible serialization. If size is critical, compress after converting.
Tagged-PDF accessibility structure not guaranteed
Not preservedThe structure tree that makes a PDF accessible is a document-level feature outside the copied pages, so a tagged source is not guaranteed to stay tagged through the rebuild. For an accessibility-focused archival output, use the PDF to PDF/A pipeline instead of bare version conversion.
Frequently asked questions
Why does PDF 1.4 fix 'cannot open' errors when 1.5 doesn't?
Because the real blocker is usually not the version number — it's the compressed cross-reference table and object streams that PDF 1.5 introduced. A pre-1.5 reader can't parse those. Targeting 1.4 is the only setting in this tool that turns object streams off and writes the classic plain xref/trailer, which is exactly what an old reader expects. 1.5 and 1.6 keep object streams on, so they don't solve that particular failure.
Will my text stay selectable after converting to 1.4?
Yes. This is a re-serialization, not a rasteriser — pages are copied object-for-object, so text, embedded fonts, and images come through unchanged and text remains selectable and searchable. (If you want the opposite, flattening pages to images is what the lossy compressor does, not this tool.)
What gets removed when I downgrade to 1.4?
Anything that lives outside the copied pages: interactive form fields (the AcroForm catalog), bookmarks/outlines, document-level JavaScript, and any encryption (the output is always unencrypted). Page content, fonts, and images are preserved. Producer and modification-date metadata are also rewritten on save. If you need form data kept, flatten the form first.
Does converting to 1.4 change how the document looks?
For standard text-and-image documents, no — the visual content is identical. The one visible exception is optional content layers (a 1.5 feature): a layered document converted to 1.4 loses its layer structure, since layers aren't part of the 1.4 feature set. Everything else renders the same.
Is targeting 1.4 the same as 'Save As PDF 1.4' in Acrobat?
It achieves the same compatibility goal — a 1.4-header file with the older serialization — but it isn't byte-identical to Acrobat's output, and it doesn't do Acrobat's preflight conversions (e.g. it won't down-convert a JPEG2000 image or transparency for you). For content-feature down-conversion you still need a desktop preflight tool; for fixing the xref/object-stream structural blocker, this tool is enough.
Can I use this to make a PDF/A-1b file?
Not on its own. PDF/A-1b is built on the PDF 1.4 structure, so converting to 1.4 satisfies the version baseline — but PDF/A also requires all fonts embedded, an output intent (colour profile), no encryption, and no disallowed features. For the full archival pass, use PDF to PDF/A; embed fonts first with the Font Subsetter if needed.
Does the file get bigger at 1.4?
It can, slightly. PDF 1.5+ compresses the cross-reference table and packs objects into object streams; 1.4 can't, so the same content is written less compactly. The difference is usually small. If size matters, run PDF Compress (Lossless) after converting — it keeps text selectable.
My signed contract needs to be 1.4 — what's the order of operations?
Convert to 1.4 first, then sign. Re-serializing the file changes its bytes and invalidates any existing signature, and the signature object isn't carried through the rebuild anyway. Apply the signature last with PDF Digital Signature, and you can confirm the result with PDF Signature Verify.
Is my document uploaded anywhere?
No. The conversion runs entirely in your browser via pdf-lib — the PDF never leaves your device. Only an anonymous usage counter is recorded when you're signed in, and you can opt out in account settings. This matters for the legal, medical, and financial documents that legacy 1.4-only systems tend to handle.
Can the tool target PDF 2.0?
No. The Target version dropdown offers only 1.4, 1.5, 1.6, and 1.7. There is no 2.0 option. If you specifically need ISO 32000-2 (2.0) output, use a desktop tool such as Acrobat or a PDF library that supports it.
Can I convert several files to 1.4 at once?
The in-browser tool handles one PDF per run. For batch automation, the converter is also exposed through the @jadapps/runner on a paid tier: fetch the schema from GET /api/v1/tools/pdf-version-converter, pair the runner once, and POST each file with { "version": "1.4" } to 127.0.0.1:9789/v1/tools/pdf-version-converter/run. The runner processes files locally — nothing is uploaded.
How big a PDF can I convert?
It depends on your tier: free is capped at 2 MB and 50 pages, Pro at 50 MB and 500 pages, Pro+Media at 500 MB and 2,000 pages, and Developer at 2 GB and 10,000 pages. Beyond that it's bounded by browser memory. A large scanned document 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.