Why a PDF Prints Differently Than It Looks
Page scaling, the unprintable edge, fonts that were never embedded and flattened transparency all change a page on its way to paper.
Written against the Aug 8, 2026 release·what has changed since
The page looks right on screen. It comes out of the printer with the header clipped, the type fractionally too small, and a pale seam running through what should be a solid block of colour. Nothing changed between the two. What changed is that a printer has physical limits a screen does not.
Scaling: the few percent nobody asked for
Most print dialogs default to fitting the page to the printable area rather than printing it at true size. On a typical desktop printer that shrinks everything by a few percent. It is invisible on ordinary text and fatal on anything measured: a form that must line up with a pre-printed sheet, a label, a plan at a stated scale.
The control is named differently in every reader but always exists, usually as actual size or 100 percent. Set it before diagnosing anything else, because scaling explains a surprising share of print complaints.
The unprintable edge
A desktop printer cannot put ink at the very edge of the paper. The sheet is held by rollers, and a few millimetres all round are mechanically out of reach. A page that places text or a rule at the true edge loses it, and no setting recovers it, because the printer is not choosing to clip the page. It physically cannot reach.
This is why a document designed with no margin prints wrong on every printer you try. Keep content inside about ten millimetres. A design that must run to the edge needs a commercial printer and a trimmed larger sheet.
Fonts that were never in the file
A PDF can embed the fonts it uses, or it can name them and expect the reader to supply them. The second kind looks perfect on the machine that made it and wrong everywhere else: line breaks move, spacing opens up, and a table that fitted now runs onto a second page. Your printer is being honest. It is printing what the file actually says.
You can confirm it by opening the document on a different computer. If the layout shifts, the fonts are not embedded, and the fix belongs to whoever exported it. Nothing downstream can restore a typeface that was never included.
Transparency, and the faint seams
Drop shadows, soft edges and semi-transparent boxes are not something a printer understands directly. They are converted into flat opaque pieces first, and the boundaries between those pieces sometimes print as hairlines or slight shifts in tone across an area that looked smooth. It is an artefact of that conversion rather than damage to your file, and it often clears at a higher print resolution.
The one that is not about printing at all
A completed form that prints blank is a separate problem. Some readers print field values and some print only the page beneath them, a difference you cannot see until the paper appears. Flatten the form and the values are written into the page itself, so there is only one thing left to print.
Before you print fifty copies
- 1
Print one page
One sheet, on the actual paper, at actual size. A test page costs a few seconds and catches every fault on this list.
- 2
Measure something
Hold a ruler against a feature whose real size you know. If it comes up short, scaling is switched on.
- 3
Look at the margins
Anything within a centimetre of the paper edge is at risk on a desktop printer, whatever the preview shows.
- 4
Open it elsewhere
A layout that moves between computers is telling you the fonts were not embedded.
The short version
- Print at actual size before you diagnose anything else.
- A desktop printer cannot reach the paper edge, so keep a margin.
- A layout that moves between machines means fonts were not embedded.
- A filled form that prints blank wants flattening, not a printer setting.
Flatten PDF form fields
Bake current AcroForm values into the page before sharing a non-editable copy.
Was this article helpful?
Your answer stays in this browser. Nothing is sent to us. See how it works.
Keep reading
Reviewed and maintained by
Novus Stream Solutions Editorial Team
The Novus Stream Solutions Editorial Team maintains Novus PDF Studio's product documentation, tutorials and PDF explainers. The team checks product claims against the current browser-local implementation and tests, prefers primary specifications and vendor documentation, and corrects material errors openly. The byline identifies the responsible organization; it does not imply a named expert or professional adviser.
Privacy note: every tool mentioned in this article runs entirely in your browser. Nothing is uploaded or queued on a server. A PDF stays in the tab unless you explicitly use Save on this device, which stores that session in this browser without storing passwords. More on the how it works page.