Short version: Gmail, Chrome, Edge, and Mac Preview don't always display a PDF exactly as the real file. Missing fonts, layout shifts, and files created via older tools can look perfect on your screen and broken on the recipient's. Simple protocol: always open in Adobe Reader before sending, and if in doubt - convert to PDF/A which is guaranteed to be consistent.
"It Looks Fine on My End" - The Most Common PDF Sending Mistake
It happens constantly: "I sent the contract, the recipient said lines were missing." "I uploaded my resume, the employer said the cover letter was cut off." "I sent a 5-page proposal, the client saw 4 pages."
The common mistake is checking the file only in your own viewer, seeing it looks fine, and sending. But your viewer is not the recipient's viewer.
Table of Contents
- Why the same file looks different
- When it happens most often
- Pre-send check protocol
- When the recipient is already complaining
Why the Same File Looks Different to Two People
Fonts Not Embedded in the File
The most common cause. When creating a PDF, fonts sometimes aren't included in the file - the file "assumes" the recipient's computer has the same font.
When it doesn't, their computer finds a similar font and uses it. Different font = different spacing = lines shift = text falls outside a text box or off the page.
Result: You see 3 lines in a paragraph; the recipient sees 3 lines plus half a line that's cut off.
Different Viewer = Different Rendering Rules
PDF contains precise instructions for where to place every character. But every application that displays PDF translates those instructions slightly differently - how to round fractions of millimeters, how to display images, where page boundaries fall.
Gmail, Chrome, Mac Preview, Adobe Reader, Edge - each renders slightly differently. Most of the time the difference is invisible. With some files, it's obvious.
Gmail Preview - A Simplified Version
Gmail doesn't show the actual PDF. It converts it to a simplified image for display inside the browser. Convenient for quick reading. Not reliable for accuracy checking.
If the file contains non-standard fonts, complex layers, or precise layouts - Gmail will approximate them in its own way, not yours.
Export from Google Docs / Canva / "Print to PDF"
Each of these methods produces a slightly different PDF. Google Docs export embeds fonts but not always correctly. "Print to PDF" on Mac differs from "Print to PDF" on Windows. Canva exports PDFs that look perfect in the web version, but sometimes with unembedded fonts.
When It Happens Most Often
Files exported from Google Docs - especially with non-default fonts.
Files from Canva - looks perfect in editing, sometimes breaks in an external viewer.
Old documents - created in older versions of Word, OpenOffice, or WordPerfect.
Files passed through multiple conversions - "Print to PDF" → edit → "Print to PDF" again. Each pass adds some degradation.
Documents with purchased fonts - if you used a font you bought separately, it's likely not embedded.
Large files sent via WhatsApp - WhatsApp sometimes compresses large PDFs in ways that corrupt them.
Pre-Send Check Protocol - 3 Minutes
Step 1 - Save the Final File Locally
Don't check directly from the cloud. Save to disk. This is the file you're sending.
Step 2 - Open in Adobe Acrobat Reader
Adobe Reader (free) is the standard. If it looks right here - great. If it's already broken here - there's a problem with the file itself.
Check:
- All text is correct, nothing cut off
- All images display
- No extra blank pages at the end
- Page numbers are correct
Step 3 - Open in Chrome
Drag the file into a Chrome browser window. Chrome uses a simpler PDF viewer. If you see a difference from Adobe Reader - the file has compatibility issues.
Step 4 - Fix If Needed
See a difference? Options:
If made in Word: File > Save as PDF > make sure "Embed fonts" is checked in options.
If made in Google Docs: File > Download > PDF Document. Usually better than "Print."
If you're unsure of the source: Run it through the PDF/A converter on PDF File. It ensures fonts are embedded and layout is consistent across viewers.
When the Recipient Is Already Complaining
"Lines are missing / text is cut off"
Almost certainly unembedded fonts. Resave the original source with font embedding and send a new version.
"The file won't open at all"
Could be several causes. Most common: partial download - have the recipient download again, fresh. If it still fails, the file itself may be corrupt.
"The background is black / colors are inverted"
Dark mode issue in some viewers. The recipient needs to turn off dark mode in their PDF viewer. Or you send a version created with an explicit white background.
"Graphs / tables aren't displaying"
If graphs were inserted as embedded objects (Excel embed) rather than images, they may depend on the source application. Convert all graphs to images (PNG) before inserting into PDF.
"Looks fine on my end but recipient says it's not"
Ask the recipient to send a screenshot of what they see. That identifies the problem precisely. Then send a file that's been through the PDF/A converter - this usually resolves compatibility issues.
The Reliable Fallback - PDF/A
PDF/A is a PDF format that requires embedded fonts, self-contained layout, and cross-viewer consistency. Every PDF/A file looks the same on every computer, every viewer, every operating system.
If you're sending something important - a contract, a large proposal, a resume - it's worth converting it to PDF/A before sending. Takes seconds, the file looks identical, but it's much more reliable.
Summary
Checking a PDF only in your own viewer before sending is like tasting food only with your own tongue - it will always taste fine to you. The recipient may experience it differently.
Three things that will save you confusion:
- Open the final file in Adobe Reader before sending
- If anything looks different from expected - fix before sending
- For important documents - convert to PDF/A. One step, a few seconds, and peace of mind.
Want to convert to PDF/A now?
With full Hebrew support
Frequently Asked Questions
Why does a PDF look fine on my computer but broken on the recipient's?
Because every PDF viewer renders slightly differently. Gmail uses a simplified preview. Mac and Windows have different default viewers. Adobe Reader is the standard, but not everyone has it. The fix: create files in a way that ensures consistent display everywhere - specifically, make sure fonts are embedded.
The recipient said lines were missing - what happened?
Most likely: fonts that weren't embedded in the file. When the recipient's computer didn't find the original font, it substituted a similar one. Different font = different spacing = lines shifted = text falling off the page. Fix: resave the file with embedded fonts, or convert it through a tool that guarantees font embedding.
Is Gmail's preview the same as the actual file?
No. Gmail converts the PDF into a simplified image-like preview for quick viewing inside the browser. It's not the actual file. If there's any doubt, download the file and open it separately - don't rely on Gmail's inline preview.
Which viewer is the 'correct' one to check with?
Adobe Acrobat Reader (free) is closest to the official PDF standard. If it looks right in Adobe Reader, it will likely look right for most recipients. Chrome and Edge are generally fine. Mac Preview is usually fine. But Gmail's inline viewer is the least reliable.
The recipient claims the content is different from what I see. Is that possible?
Layout differences - yes, definitely possible. Actual content changes - not unless someone modified the file after sending. A PDF doesn't change itself. What does happen: layouts that shift between viewers, font substitutions, images displayed at different sizes.
How do I verify a PDF will look right before sending?
Open it in Adobe Acrobat Reader (free). Then open it in Chrome. If it looks consistent in both - good. If there's a difference between them, the file has compatibility issues. Fix before sending.
I sent a PDF on WhatsApp and the recipient said a page was missing. What happened?
WhatsApp sometimes compresses large PDF files in ways that corrupt them. Resend as a regular file attachment (not an image). Also, WhatsApp's built-in PDF viewer is limited and sometimes doesn't render the final pages.