Why your PDF's fonts look wrong on someone else's computer

You build a document, it looks great, you export it to PDF and send it off. Then someone replies that it looks broken on their end: the font is different, the spacing is off, a heading wrapped onto two lines, the whole thing shifted. You open your copy again and it’s still perfect. So what happened?

Almost always, it’s fonts. And once you know why, the fix is quick.

The font isn’t always inside the file

Here’s the thing most people assume but that isn’t always true: a PDF doesn’t necessarily contain the fonts it uses. Sometimes it just contains a reference, a note that says “render this text in Some Font.” When you open that PDF, your computer looks for Some Font among the fonts installed on your machine. If it’s there, great, the document looks right. If it isn’t, the reader substitutes a different font, and that’s when everything shifts.

On your computer the document looks perfect because you have the font, it was probably installed by the software you used. On a machine that doesn’t have it, the reader makes a guess, and the substitute is rarely the same width or shape. Text reflows, spacing breaks, the careful layout falls apart.

This is why a PDF made with a fancy or unusual font is most at risk. Common system fonts tend to exist everywhere. A specialty font you downloaded? The person opening your file almost certainly doesn’t have it.

The fix: embed the fonts

The solution is to make the PDF carry its fonts inside itself. That’s called embedding. When fonts are embedded, the file doesn’t ask the other computer for anything, it brings its own. Wherever it’s opened, it uses the exact fonts you chose, and the layout holds.

A properly embedded PDF looks the same on a phone, a ten-year-old office PC, and a printer at a copy shop, because none of them have to supply a font. The file already has everything.

How to fix a PDF with font problems in your browser

If you’ve got a PDF that’s rendering wrong elsewhere, the cleanest way to lock its fonts in is to convert it to PDF/A, the archival format, which requires fonts to be embedded by design. files.co can do this on your device:

1. Open the PDF to PDF/A tool and drop your file in.
2. Let it convert. Part of meeting the PDF/A standard is embedding the fonts, so the tool pulls them into the file.
3. Download the fixed PDF. This copy carries its own fonts. Send it and it’ll look the same on the other end.

It’s the same move whether you’re fixing a one-off or just want to be sure an important document travels well.

Check before you send

A good habit for anything where layout matters, a contract, a CV, a designed report: don’t trust that it looks right just because it looks right to you. You’re the one person guaranteed to have the fonts. Open the PDF’s properties in your reader and look for the font information; many readers will tell you which fonts are embedded and which aren’t. If something important isn’t embedded, fix it before it goes out.

Why doing it locally is the right call

The documents most likely to use a distinctive font, and most likely to matter if they break, are designed pieces: contracts, proposals, branded reports, a CV you spent hours on. Uploading those to a random “fix my PDF” site to embed a font means handing the whole document to a server you don’t control.

files.co does it in your browser. The PDF is read into memory on your machine, the fonts are embedded right there, and the result saves to your downloads. Nothing is uploaded, which you can confirm with DevTools (F12) on the Network tab, or just by doing it offline.

So if a PDF keeps arriving broken, it’s almost certainly the fonts, and the fix is to make the file carry its own. Convert it once, send the embedded copy, and it’ll look the way you built it, everywhere.