Publié
Why a PDF Looks Different on Every Device
Open the same PDF on a laptop, a phone, and a browser tab, and the type doesn't always match — a heading shifts to a different face, spacing tightens, line breaks land somewhere else. That's rarely a bug. It's what happens when a PDF's fonts were never embedded, and each device quietly substitutes something it already has installed. Here's what embedding actually does, why some PDFs skip it, and how to tell an ordinary substitution from a real problem.
What it is
A PDF is supposed to look the same no matter where you open it. That's the entire premise — a fixed-layout, device-independent document meant to travel intact from the machine that made it to whatever machine opens it next. That promise only holds if the file actually carries everything it needs to render itself, and fonts are part of that bargain. A font can be embedded — its own data packed inside the PDF — or unembedded, where the file just names a typeface and trusts the device opening it happens to have the same one installed. When that trust doesn't pay off, the device fills the gap on its own. That's the moment a PDF starts to look different depending on where you open it. It's a close cousin of reflowable vs. fixed-layout files: one is about whether a page's layout can move at all, this is about whether the letterforms sitting on that layout stay exactly what the author chose.
Why it matters
When a font isn't embedded, the viewer doesn't leave a blank space. It reaches for something already installed on that device and uses it instead. What's installed varies from device to device, so the substitute your phone picks isn't necessarily the one your laptop picks — and neither one is promised to resemble the original. This isn't only cosmetic. A substitute rarely has identical letter widths and spacing to the original font, so lines can break in different places, paragraphs run longer or shorter, and a page that ended cleanly in one typeface spills onto the next in another. Even PDF's own list of "standard" typefaces — Times, Courier, Helvetica, a few others most readers are expected to have — was never a guarantee written into the specification itself. Expected isn't present. In the least forgiving cases, a viewer that can't find anything close enough shows blank boxes or the wrong characters entirely — not a slightly different typeface, but no typeface at all.
Where you'll see it
This shows up in specific, recognizable places: a PDF exported years ago from a layout tool using a licensed display font nobody thought to embed. A scanned form retyped with an unusual character set. A contract built in design software that isn't installed on whatever device is now trying to read it. Different apps expose the same gap differently, too — a browser's built-in PDF viewer implements only part of the full specification, so the identical file can render a little differently in a browser tab than it does in a dedicated reader on the same device. It's the same idea behind why the reading font you choose changes the experience — except here, nobody chose anything. A device simply ran out of the typeface it was told to use and picked its own replacement. Worth remembering: this is a rendering problem, not a content problem. The words on the page are exactly what they were. Only their shape and spacing are up for negotiation.
How Margina handles it
Margina reads the document as it is — no silent re-typesetting, no swapping in a "close enough" font behind your back that changes what the page actually looks like. If a PDF you've sent yourself does have unembedded fonts, expect the same kind of visual variation you'd see anywhere else. That's a property of the file, not something an app can quietly fix without changing what you were sent in the first place. What Margina can promise is consistency on your end: a dense academic PDF you're reading on your phone renders the same way today as it did yesterday, on the same device, because nothing about the file — or the fonts it's asking for — has changed between sessions.
Frequently Asked Questions
How do I know if a PDF has its fonts embedded?
Most desktop PDF readers let you check document properties or font information, and it'll list every font used in the file along with a tag — "Embedded," "Embedded Subset," or neither. No embedded tag means the device you're viewing it on is showing you a substitute, not the original typeface.
Does font embedding make a PDF file bigger?
A little, but usually not by much. Most well-made PDFs embed only a subset of a typeface — the specific characters actually used in the document — rather than the entire font file, which keeps the size increase modest.
Why does the same PDF look fine on my laptop but wrong on my phone?
Each device substitutes from its own installed set of fonts when a PDF's fonts aren't embedded. Your laptop and your phone don't necessarily carry the same fonts, so the substitute each one reaches for can differ.
Can I fix a PDF that's missing embedded fonts myself?
Sometimes. Most PDF creation tools — including "print to PDF" and standard export dialogs — have a setting to embed fonts, which you can re-run if you still have the original document. If all you have is the finished PDF, the more reliable fix is asking whoever made it for a version with the fonts embedded.
Conclusion
A PDF that looks slightly different from one device to the next almost always comes down to one thing: fonts that were never embedded in the file to begin with. The format was built to travel intact, but that only holds if everything it needs travels with it. Next time a document looks a little off somewhere new, check for embedded fonts before assuming anything is actually broken.