Google Docs to PDF: Keep Formatting Intact (2026)
Google Docs' built-in "Download as PDF" usually works β until the doc contains a custom font, a wide table, or a long header that drifts onto the next page. This guide walks through three export paths, when to use each, and exact fixes for the most common formatting issues people run into when sending PDFs to clients, printers, or recruiters.
Method 1: Native "Download β PDF" (good enough for most docs)
For typical Latin-text documents with default Google fonts, this is the fastest path:
- Open the Google Doc.
- File β Download β PDF Document (.pdf).
- Save the file.
It works because Google renders the doc server-side with the exact same fonts it uses in the editor. Where it falls down: hidden CSS quirks in Drive-imported files, custom fonts via Extensis, and very wide tables that exceed the printable page width.
Method 2: Export β DOCX β in-browser converter (best fidelity)
If Method 1 produced shifted images, broken page breaks, or font substitutions, the most reliable workaround is to download as DOCX and convert that locally. Word fidelity is significantly higher in DOCX than in Google's PDF output.
- File β Download β Microsoft Word (.docx).
- Open our DOCX to PDF guide for the converter and tuning tips.
- Drop the file in. The conversion runs locally, embeds fonts, and respects DOCX page setup.
Surprising benefit: this also removes Google's tracking metadata from the file. The native PDF download embeds the Drive document ID, which some teams strip before sharing externally.
Method 3: Export β HTML / Markdown for editable web docs
For docs you intend to publish or restyle, export plain HTML or Markdown and convert that. You'll get a typographically cleaner PDF β especially for resumes, proposals, and meeting notes.
- File β Download β Web Page (.html, zipped) or use a Docs-to-Markdown add-on.
- For HTML: open to-pdf.com/html-to-pdf and drop in the file.
- For Markdown: open to-pdf.com/markdown-to-pdf and paste.
Fixing the most common Google Docs β PDF problems
Custom fonts swapping to Arial
If your doc uses a font added via an extension, the native PDF export silently falls back. Use Method 2 (DOCX β local converter) so the font is embedded directly in the document.
Wide tables clipping at the right margin
Google's PDF respects page width strictly. Either switch the page to landscape (File β Page setup β Orientation), reduce column widths in the doc, or export as DOCX and adjust margins in the local converter.
Images shifting up or down a page
Inline-positioned images respect the surrounding text flow. Float-positioned ("Wrap text" / "Break text") images sometimes jump to the next page after PDF export. Convert problem images to inline first (Image options β In line), then re-export.
Hyperlinks not clickable in PDF
Method 1 preserves clickable links. Some old "Print to PDF" workflows flatten them. If your PDF lost links, re-export with Method 1 or Method 2 β both produce real PDF link annotations.
Comments and suggestions visible in PDF
Before exporting, switch to Viewing mode (top-right dropdown). Suggestions are then rendered as accepted text, and comment threads are stripped from the export.
Multi-page resume looking cramped
Google Docs adds extra leading at the bottom of pages. For resumes specifically, a Markdown export gives you sharper control over line height and spacing β see how to create a resume PDF from Markdown.
Privacy considerations
The Method 1 native download routes through Google's servers (your data is already there, so no new exposure). Methods 2 and 3 use local browser-based converters β the file never leaves your device. If you've ever pasted client contracts into a free online "DOCX β PDF" site, the local route is the right upgrade.