Get a PDF into a Google Doc

A survey appendix due with the application

Dasa is finishing a grant application in Google Docs on Sunday night. The funder wants the methodology appendix alongside the text, and the appendix exists only as survey-results-2026.pdf, six pages of tables her colleague exported last month. The portal takes one document, and the deadline is midnight.

She needs pages the reviewers can read without leaving the application, which points at pictures of the pages pasted under her final paragraph. Had the funder wanted the raw file instead, a link would have done. The reader decides the route, so this guide starts from the reader and works back to the clicks.

Three routes, three different readers

There is no fourth option hiding in a submenu. Workers who promise an embedded PDF inside a Google Doc are describing one of these three under a grander name, and each comes with its own way of disappointing the reader.

Match the row to your reader before touching any menu. Most failures on this page come from picking the route first, usually pictures, and discovering its cost after the document has been sent.

Link the file from Drive

Upload the PDF to Drive and paste its link where the reference belongs. Docs turns the pasted address into a chip carrying the file name, which the reader opens to reach the PDF itself. The document stays light, the PDF stays searchable, and nothing about the file changes.

Prefer this route for material the reader keeps: terms, a signed lease, a full report, a certificate. Dasa would have linked survey-results-2026.pdf had the funder asked for the appendix as a file rather than as reading inside the application. The chip points at the genuine article instead of a picture of it.

Sharing decides who actually opens it

A chip is a pointer, not a permission. When the file stays restricted, every reader outside your account meets a request access screen instead of the PDF, which is the most reported failure of the link route. Open the sharing settings on the file in Drive and set them to match the audience of the document before you send anything.

Think twice about link access for sensitive files. Anyone holding the document can forward the chip along with it, so a contract or a medical letter deserves named readers rather than an open link. And never trash the Drive file afterwards: the chip points at that exact file, so deleting it breaks every copy of the document at once.

Render the pages as pictures

When the pages must be read without leaving the document, turn them into images and insert those. PDF to images renders the pages you name in the tab, in JPG or PNG, with a resolution of 96, 150 or 300 dots per inch, and packs two or more into a zip you unpack before inserting.

1. Open PDF to images and choose the PDF.
2. Name the pages with the page picker, for example 2-3 for a two page appendix, and pick JPG for scans or PNG for tables and type.
3. Pick 150 dots per inch for screen reading, 96 for a light draft, 300 only when the document will be printed.
4. Download the pictures, unzip the bundle when several pages were rendered, and insert each with the Insert menu, Image, then Upload from computer.
5. Read the inserted pages at normal zoom and confirm the smallest figures stay legible.

The inserted pages read well and search for nothing. Their text is now dots, invisible to find in page and to screen readers, which is why this route suits an appendix of a few pages and never a forty page report. Match the resolution to the source too: a 150 dot scan rendered at 300 gains weight without gaining a single readable letter.

Open with Docs rebuilds the file as text

Drive can hand a PDF to Docs, which rebuilds it as an editable document. On a clean, single column text file the words arrive in good shape. On anything with tables, columns or a designed layout, the converter guesses the structure and usually guesses wrong, leaving a repair job longer than retyping.

Scanned pages go through text recognition on the way in, with the accuracy that implies. Numbers deserve a check by eye, every one of them, because a misread total looks exactly like a correct one. Treat the converted file as a draft that quotes the PDF, never as the PDF itself, and keep the original around for comparison.

Ways this goes wrong

The most common is the restricted link: a carefully written application pointing at a file nobody can open. Test every chip in a private window, or ask one recipient to open it before the batch goes out.

Next comes the forty page picture gallery. Inserting a whole report as images bloats the document, slows every open, and buries unsearchable text under an hour of scrolling. Past three or four pages, link the file instead.

Then the trusted conversion: a table-heavy PDF opened with Docs, skimmed, and sent on with its columns quietly shuffled. And the oversized insert, pages rendered at 300 dots per inch for a document nobody will print, which loads slowly on every phone it reaches. Each of these takes longer to fix after sending than the right route would have taken before.

When Docs is the wrong home for the PDF

Some readers need the document, not a document about the document. When the layout must print exactly, when a signature or a stamp has to stay verifiable, or when the file itself is the deliverable, send the PDF next to the Docs link instead of forcing it inside. A short line saying what the attachment holds beats any workaround.

Word users get a real fourth option: Word can hold a PDF as an embedded object, which the Word embedding guide covers step by step. And when the job runs the other way, several Docs exports that must become one file, export each to PDF and join them with Merge PDF; the document joining guide shows how page numbering survives that trip.