Why does my PDF look different in different readers?

A PDF should look identical everywhere, and when it does not the cause is almost always one of a few things: fonts that were not embedded (so a reader substitutes a different typeface and the text shifts), live transparency effects that older engines render incorrectly, or features from a newer PDF version that a legacy reader ignores. Browsers, mobile apps, Apple Preview, Acrobat, and various third-party readers each implement the spec slightly differently and with different completeness, so anything non-standard exposes the gaps. Compatibility is mostly about removing those variables — embedding fonts, flattening effects, and sticking to widely supported features — so there is nothing left for a reader to interpret differently.

What does embedding fonts do and why does it matter most?

Embedding stores the actual font data inside the PDF, so every reader draws the text with the exact typeface and metrics you designed with. Without embedding, a reader that lacks your font substitutes a fallback, which changes character widths and can reflow lines, break alignment, and ruin a layout — the single most common compatibility failure. Subsetting (embedding only the glyphs actually used) keeps the file small while guaranteeing fidelity. Embedding fonts is the highest-impact compatibility step: it fixes the most frequent and most visible problem, and it is a prerequisite for archival standards like PDF/A.

Should I flatten the PDF for compatibility?

Flattening helps in two specific cases. Flattening transparency merges layered, semi-transparent artwork into a plain composite, which older rendering engines display correctly where they would otherwise show halos or black boxes. Flattening a form merges filled field values into the page so they display even in readers that do not support interactive forms, and it locks the content. Flatten when the document is final and you want maximum portability; keep an unflattened master if you still need to edit the artwork or the form. Do not flatten a working template — flatten a copy meant for distribution.

What is PDF/A and should I use it?

PDF/A is an ISO archival profile of PDF designed for long-term, reliable reproduction. It enforces exactly the compatibility rules that matter: fonts must be embedded, transparency and external dependencies are restricted, multimedia and JavaScript are prohibited, and the file declares its standard so any reader knows the baseline. Converting to PDF/A is a strong way to maximise compatibility, because it strips the very features that cause cross-reader inconsistency. Use it for anything you need to be readable years from now or across unknown software — records, contracts, published documents. The trade-off is you lose interactive features, which is the point.

Do I need to worry about PDF version numbers?

Sometimes. Each PDF version (1.4, 1.5, 1.7, 2.0) added features; a reader built for an older version may ignore or mishandle features from a newer one. For maximum reach — legacy enterprise software, older devices, government systems — saving to a widely supported version (1.4–1.7 is very safe) or to PDF/A avoids surprises. For ordinary modern audiences this rarely matters, since current readers handle recent versions. The practical rule: if you know your audience uses old or unusual software, target an older version or PDF/A; otherwise embed fonts and flatten, and the version is seldom the problem.

How do I check whether a PDF is actually compatible before sending it?

Verify rather than assume. Check that all fonts are embedded (a font-embedding check lists any that are not), confirm the PDF/A status if you converted, and validate PDF/A compliance if that is your target. Then do the practical test: open the file in a different reader than you created it in — ideally a browser and a phone as well as a desktop app — and confirm the fonts, layout, and images look right and any forms behave as expected. The combination of an automated check plus opening it in a couple of unrelated viewers catches almost every real-world compatibility problem.

Is it safe to run these compatibility fixes with an online tool?

If the document is confidential, prefer a tool that processes files locally. ScoutMyTool performs font-embedding checks, flattening, and PDF/A conversion entirely in your browser tab, so the file never leaves your machine. For anything you would not publish openly, confirm the tool does not upload before using it, or use an offline desktop tool.

6 min read

How to make a PDF compatible with all PDF readers

By ScoutMyTool Editorial Team · Last updated: 2026-05-21

I sent a beautifully laid-out PDF to a client once and got back a screenshot where every heading had turned into Times New Roman and the spacing had collapsed — on their machine, in their reader, my fonts simply were not there. The file was fine; it was not self-contained. That is the whole game with PDF compatibility: a PDF is supposed to look identical everywhere, and when it does not, it is because the file relied on something the reader did not have or did not support. This guide is the practical checklist for making a PDF that opens and looks right in every reader — embedding fonts, flattening the risky bits, avoiding exotic features, and using PDF/A when you need a guaranteed baseline.

What breaks compatibility — and the fix

Almost every cross-reader problem comes from a short list of causes. Here is each symptom and the fix that removes it.

Issue	Symptom	Fix
Non-embedded fonts	Text reflows or shows wrong typeface	Embed (subset) all fonts
Live transparency	Halos or black boxes in old readers	Flatten transparency
Interactive form fields	Fields blank or unfillable in some apps	Flatten the form when final
Newer PDF version	Features ignored in legacy software	Save to an older version / PDF/A
Exotic compression (JBIG2/JPXDecode)	Images fail to render	Re-encode with widely supported filters
Embedded multimedia / JS	Ignored or blocked; security flags	Remove or link externally instead
No declared standard	Inconsistent across viewers	Convert to PDF/A for a known baseline

Step by step — a compatibility pass

Embed every font. The highest-impact step. Check for non-embedded fonts with Font Embedding Check and embed/subset any that are missing — see embedding fonts.
Flatten transparency. Merge layered/semi-transparent artwork into a plain composite with Flatten Transparency so older engines render it correctly.
Flatten forms when final. If the document has interactive fields and is finished, flatten it with Flatten Form so values display in readers that do not support forms — see flattening a PDF. Keep an unflattened master.
Avoid exotic features. Re-encode images that use rare compression, and drop embedded multimedia or JavaScript (link to hosted media instead) — these are ignored or security-flagged by many readers.
Convert to PDF/A for a guaranteed baseline. For maximum portability or long-term reading, convert with PDF/A Converter — it enforces embedding and strips inconsistency-causing features. See PDF/A conversion.
Validate. Confirm the result with PDF/A Compliance Validator (or detect the PDF/A version) so you know the baseline you are shipping.
Open it in other readers. Test in a browser, a phone, and a desktop app — different from where you created it — and confirm fonts, layout, images, and any forms all behave. See PDF viewers.

Embedding fonts: the top compatibility fix.
Flatten a PDF: locking transparency and forms.
PDF/A conversion: a guaranteed-portable baseline.
Print-ready PDFs: a related fidelity checklist.
Best PDF viewers: where to test compatibility.
Font Embedding Check: find missing fonts in your browser.
All ScoutMyTool PDF tools: the full toolkit.

FAQ

Why does my PDF look different in different readers?: A PDF should look identical everywhere, and when it does not the cause is almost always one of a few things: fonts that were not embedded (so a reader substitutes a different typeface and the text shifts), live transparency effects that older engines render incorrectly, or features from a newer PDF version that a legacy reader ignores. Browsers, mobile apps, Apple Preview, Acrobat, and various third-party readers each implement the spec slightly differently and with different completeness, so anything non-standard exposes the gaps. Compatibility is mostly about removing those variables — embedding fonts, flattening effects, and sticking to widely supported features — so there is nothing left for a reader to interpret differently.
What does embedding fonts do and why does it matter most?: Embedding stores the actual font data inside the PDF, so every reader draws the text with the exact typeface and metrics you designed with. Without embedding, a reader that lacks your font substitutes a fallback, which changes character widths and can reflow lines, break alignment, and ruin a layout — the single most common compatibility failure. Subsetting (embedding only the glyphs actually used) keeps the file small while guaranteeing fidelity. Embedding fonts is the highest-impact compatibility step: it fixes the most frequent and most visible problem, and it is a prerequisite for archival standards like PDF/A.
Should I flatten the PDF for compatibility?: Flattening helps in two specific cases. Flattening transparency merges layered, semi-transparent artwork into a plain composite, which older rendering engines display correctly where they would otherwise show halos or black boxes. Flattening a form merges filled field values into the page so they display even in readers that do not support interactive forms, and it locks the content. Flatten when the document is final and you want maximum portability; keep an unflattened master if you still need to edit the artwork or the form. Do not flatten a working template — flatten a copy meant for distribution.
What is PDF/A and should I use it?: PDF/A is an ISO archival profile of PDF designed for long-term, reliable reproduction. It enforces exactly the compatibility rules that matter: fonts must be embedded, transparency and external dependencies are restricted, multimedia and JavaScript are prohibited, and the file declares its standard so any reader knows the baseline. Converting to PDF/A is a strong way to maximise compatibility, because it strips the very features that cause cross-reader inconsistency. Use it for anything you need to be readable years from now or across unknown software — records, contracts, published documents. The trade-off is you lose interactive features, which is the point.
Do I need to worry about PDF version numbers?: Sometimes. Each PDF version (1.4, 1.5, 1.7, 2.0) added features; a reader built for an older version may ignore or mishandle features from a newer one. For maximum reach — legacy enterprise software, older devices, government systems — saving to a widely supported version (1.4–1.7 is very safe) or to PDF/A avoids surprises. For ordinary modern audiences this rarely matters, since current readers handle recent versions. The practical rule: if you know your audience uses old or unusual software, target an older version or PDF/A; otherwise embed fonts and flatten, and the version is seldom the problem.
How do I check whether a PDF is actually compatible before sending it?: Verify rather than assume. Check that all fonts are embedded (a font-embedding check lists any that are not), confirm the PDF/A status if you converted, and validate PDF/A compliance if that is your target. Then do the practical test: open the file in a different reader than you created it in — ideally a browser and a phone as well as a desktop app — and confirm the fonts, layout, and images look right and any forms behave as expected. The combination of an automated check plus opening it in a couple of unrelated viewers catches almost every real-world compatibility problem.
Is it safe to run these compatibility fixes with an online tool?: If the document is confidential, prefer a tool that processes files locally. ScoutMyTool performs font-embedding checks, flattening, and PDF/A conversion entirely in your browser tab, so the file never leaves your machine. For anything you would not publish openly, confirm the tool does not upload before using it, or use an offline desktop tool.

Citations

Wikipedia — “PDF/A” (ISO 19005), the archival profile that enforces embedding and bans inconsistency-causing features. en.wikipedia.org/wiki/PDF/A
Wikipedia — “PDF” (ISO 32000), the format, its versions, and font embedding. en.wikipedia.org/wiki/PDF
Wikipedia — “History of the Portable Document Format,” on PDF version evolution and feature additions. en.wikipedia.org — PDF history

Make your PDF open right everywhere

Check font embedding, flatten the risky bits, and convert to PDF/A with ScoutMyTool’s in-browser tools — your file never leaves your machine while you make it universally compatible.

Open Font Embedding Check →