PDF to Word

How to convert a PDF to Word

Two reliable ways to do it, and an honest explanation of why the result sometimes arrives broken.

Converting a PDF to Word is a two-minute job that works beautifully most of the time and then, on one document in a handful, produces something unusable: text you cannot click into, a table that behaves like a picture, an extra blank page in the middle of chapter three.

That inconsistency is not bad luck, and it is not a sign that you picked the wrong tool. It comes from the file format itself. Understanding the reason takes about four minutes and it will save you from fighting documents that were never going to convert cleanly.

What a PDF actually stores

Here is the single fact that explains almost every PDF to Word problem: a PDF records where marks go on a page, not what those marks mean.

When you look at a PDF you see headings, paragraphs, a table, a footnote. The file contains none of those things. It contains instructions along the lines of "draw the characters Quarterly in 14pt Helvetica starting at coordinate 72, 690", followed by several hundred more instructions just like it. There is no paragraph object. There is no sentence. There is nothing recording that one run of text is a heading and the next is body copy, or that these nine pieces of text belong to a table, or even which piece of text a reader is supposed to encounter first.

A page as it appears, next to the same page as the PDF file stores it On the left, a rendered page showing a heading, three lines of body text and a table. On the right, the same page shown as the file stores it: each piece of text is an independently positioned run with its own coordinates, and the table is four separate drawn lines with nine unrelated text runs sitting near them. Nothing records paragraphs, reading order or cells. What you see What the file stores Heading, paragraph, table x 72 y 690 run 3 runs. no paragraph joining them. 8 drawn lines. 9 text runs. 0 cells. Positions only. No structure.
The root of the problemBoth sides describe the same page. The left is what a reader perceives. The right is everything the file actually contains: independently positioned runs of text, and lines that were drawn near them. The grouping into paragraphs, the reading order and the table cells exist only in the reader's head.

This is by design. PDF was created to make a document look identical everywhere, on any screen and any printer, forever. Throwing away structure and keeping only exact positions is exactly how it achieves that. The format is doing its job well. It is simply the opposite of what Word needs.

Word is a format built around meaning. It stores a paragraph as a paragraph, a table as a grid of cells with relationships between them, a heading as a heading. That is what lets text rewrap when you type, and lets you drag a column wider and have the whole table respond.

Converting a PDF to Word is not a translation between two formats that hold the same information. It is a reconstruction. The converter reads a set of positions and works backwards to a guess about what the author originally meant.

When the guess is right, you get a document you can genuinely edit. When it is wrong, you get something that still looks correct and behaves like a photograph.

Every remaining section of this article is a consequence of that one sentence.

Check your PDF first

Before choosing a method, find out which kind of PDF you have. It takes five seconds and it determines everything that follows.

Open the PDF in any viewer and try to select a sentence by dragging your cursor across it.

Words highlight

Born-digital

The PDF was exported from a real document, and genuine text is inside it. Everything in this article applies. Conversion will work, and the quality of the result depends on how cleanly the original was laid out.

Nothing highlights

Scanned

The page is a photograph. There is no text in the file to convert, so it has to be recognised from the picture first. That is optical character recognition, and it is a different job with different failure modes.

If your document is a scan, the methods below will still open it, but Word in particular will hand you an image sitting in a document rather than editable text. Read converting a scanned PDF to Word instead, which covers what OCR can and cannot do.

One more thing worth checking while you are here: if the PDF is a filled-in form, expect a harder time than the layout suggests. Form field values are stored separately from the page they appear on, and a converter has to merge two different layers to produce something sensible. A blank form usually converts more predictably than the same form with answers typed into it.

Converting with Microsoft Word

Word has been able to open PDFs directly since Word 2013, and it is the most direct route if you already have it. There is no separate converter to install and nothing is uploaded anywhere.

Opening a PDF in Word

  1. In Word, go to File, then Open, then Browse.
  2. Set the file type filter to All Files or PDF Files, otherwise the PDF will not be listed.
  3. Select the PDF and click Open. Word displays a notice explaining that it is about to convert the PDF into an editable document, and that the result may not look exactly like the original. Click OK.
  4. Wait while Word rebuilds the document. A long or graphics-heavy file takes noticeably longer than a plain one.
  5. Go to File, then Save As, and choose Word Document (.docx).

Do not skip step 5. Until you save, the open document is still associated with the original .pdf filename, which is how people end up believing their edits vanished. Saving as .docx keeps the editable version separate from the PDF you started with.

That notice Word shows in step 3 is not boilerplate. It is the software telling you, accurately, that it is about to make inferences. Word for Mac works the same way through the same menu path.

Converting with Google Docs

Google Docs converts PDFs from any browser, on any operating system, at no cost. It is the usual answer for anyone without a Word licence, and it is the practical route on a Mac, a Chromebook or a Linux machine.

Opening a PDF in Google Docs

  1. Upload the PDF to Google Drive by dragging it into a Drive window.
  2. Right-click the uploaded file and choose Open with, then Google Docs.
  3. Wait for the converted document to open in a new tab.
  4. To get a Word file out of it, choose File, then Download, then Microsoft Word (.docx).

Layout is simplified quite aggressively. Google Docs prioritises getting editable text out over reproducing the page. Multi-column layouts frequently arrive as a single column, and precise positioning is generally not preserved. When the text matters more than the layout, that is a feature. When you needed the layout, it is not.

One genuine advantage: Google Docs runs optical character recognition automatically when the PDF turns out to be a scan, so it will produce editable text from a scanned document where Word will not.

The tradeoff is that your document is uploaded to Google Drive to be converted, which leads directly to the next section.

Online converters and confidential files

Search for a PDF to Word converter and you will find a great many web-based services. They are convenient, they need nothing installed, and for a lot of documents they are entirely reasonable.

The question worth asking before using one is not about conversion quality. It is about what happens to the file.

An online converter works by uploading your document to a server you do not control, processing it there and holding the result until you download it. For a restaurant menu or a public brochure that is irrelevant. For these, it is worth pausing over:

Retention policies vary and are not always easy to find. Some services delete uploads within the hour, others are considerably vaguer. If a document falls into one of the categories above, the safe assumption is that uploading it counts as disclosing it, and the decision should be made on that basis rather than on convenience.

Word running on your own computer does not transmit the document anywhere, which is worth remembering when the file is sensitive.

Why the result looks wrong

When a conversion disappoints, it is almost always one of three specific failures. Each one is the reconstruction guess going wrong in a particular way, and each one has a tell you can check for.

Text that will not flow

The most disorienting outcome is a document that looks perfect and refuses to behave. You click into a paragraph, type a word, and instead of the text rewrapping, it overflows or vanishes. Delete a line above and nothing below moves up.

What happened is that the converter could not confidently group the positioned text runs into paragraphs, so it fell back on the option that always looks right: it pinned each block of text into a fixed frame at the exact coordinates the PDF specified. A frame preserves appearance perfectly. It also freezes it.

Flowing text compared with pinned text after an edit On the left, flowing text: inserting a word pushes the following words along and the paragraph rewraps onto an extra line. On the right, pinned text: the same insertion overflows the fixed frame because the frame cannot grow or rewrap, and the text below stays exactly where it was. Flowing Pinned before after inserting a word Text rewraps. The paragraph grows. before after inserting a word overflows the frame Frame cannot grow. Text spills.
How to recognise itClick into a line of text and watch the ribbon. If Word switches to Shape Format or Drawing Tools, that text is sitting in a frame rather than in the body of the document. Turning on the paragraph mark button also helps: flowing paragraphs show a paragraph mark at the end of each one, frames do not.

A converter that pins everything will produce a document that is visually flawless and effectively read-only. A converter that flows everything will produce a document you can edit freely that may not match the original page layout. Neither choice is wrong in general, and both are wrong for somebody.

Tables and pictures of tables

Ask what a PDF stores for a table and the answer is unsettling: nothing that identifies it as a table. There are some lines that were drawn, and some text that was placed near those lines. No cell, no row, no column, no record connecting any piece of text to any region.

So a converter has to look at the drawn lines, look at where the text sits, and infer the grid. When it succeeds you get a real Word table: click in a cell and it behaves like a cell, drag a boundary and the column resizes. When it fails you get the lines redrawn as shapes with text boxes floating over them. On screen the two are indistinguishable. The difference appears the moment you try to add a row.

A reconstructed Word table compared with redrawn lines and floating text On the left, a real Word table where cells are connected, so widening a column moves the boundary and its content together. On the right, the same appearance built from independent drawn lines and separate floating text boxes, where dragging a boundary moves only that one line and leaves the text behind. Reconstructed as a table Redrawn as a picture Drag the boundary. The column resizes and its text reflows with it. Drag the boundary. One line moves. The text stays where it was.
How to recognise itClick inside what should be a cell. A real table puts Table Design and Layout tabs in the ribbon and shows row and column handles on hover. If instead you select a text box, or the whole block selects as one object, the table was redrawn rather than rebuilt.

Borderless tables are the hardest case of all, because the drawn lines a converter relies on are simply not there. Column alignment has to be inferred purely from where text sits, and a column of right-aligned figures next to a column of left-aligned labels can look, positionally, a lot like one wide column.

A page count that changes

Converted documents routinely arrive one or two pages longer than the original, or with a blank page wedged into the middle. This one is not really a bug.

A PDF page is a fixed canvas: content was placed onto it at set coordinates and it cannot move. A Word page is the opposite. It is simply however much text happens to fit before the text runs out of room, which means that once the text is flowing again, every small difference compounds down the document.

Font substitution is the usual culprit. If the PDF was set in a typeface that is not installed on your machine, the converter picks the closest available match. A replacement that is fractionally wider changes where every single line breaks, which changes where every paragraph ends, which eventually pushes a line onto a new page. From there the whole document shifts.

The other frequent cause is a converter turning the fixed spacing at the bottom of a PDF page into an explicit page break in Word. Do that on every page and any text that has reflowed shorter leaves a blank page behind it. If your converted document has stray empty pages, turn on paragraph marks and look for manual page breaks. Removing them usually resolves it.

What survives and what does not

Given all of the above, it is possible to predict fairly reliably how a given document will convert before you start.

Usually converts cleanly

  • Single-column text documents: letters, reports, essays, manuscripts
  • PDFs exported directly from Word in the first place, which often carry structural hints the converter can read
  • Documents using widely installed fonts, where nothing has to be substituted
  • Simple tables with visible ruled lines and one line of text per cell
  • Straightforward numbered and bulleted lists

Converts, but expect to do some repair

  • Multi-column layouts, where reading order has to be inferred from position
  • Documents with sidebars, pull quotes or text wrapped around images
  • Tables without ruled lines, or with cells spanning several columns
  • Headers, footers and footnotes, which are frequently converted into ordinary body text
  • Anything set in an unusual or embedded typeface

Rarely converts to something you would want to edit

  • Scanned documents without an OCR step: there is no text in the file to recover
  • Design-led layouts such as brochures, magazine spreads and annual report pages
  • Technical drawings, charts and diagrams, which are vector artwork rather than text
  • Filled-in forms, where field values live on a separate layer from the page
  • Documents in a script the converter cannot map back to characters correctly

If your document is in the third group, converting it is often slower than rebuilding the parts you need by hand. Recognising that early is worth more than any amount of tool selection.

Common questions

In Microsoft Word 2013 or later, go to File, then Open, then Browse, and select the PDF. Word shows a notice saying it will convert the PDF into an editable Word document, then rebuilds it. Save the result with File, then Save As, and choose Word Document (.docx). Google Docs is the free alternative: upload the PDF to Google Drive, right-click it, choose Open with Google Docs, then download it as .docx.

A PDF stores the position of marks on a page, not the meaning of those marks. It has no concept of a paragraph, a sentence, a reading order or a table, so every converter has to infer that structure from where things sit. When the inference is right the document is genuinely editable. When it is wrong you get text in fixed frames, tables that behave like drawings, and unexpected page breaks.

The converter most likely placed the text in fixed frames rather than flowing paragraphs. Text in a frame does not rewrap when you type, and deleting a line above it does not move it up. Click a line of text and watch the ribbon: if Word switches to Shape Format or Drawing Tools, the text is in a frame rather than in the body of the document. Editing a PDF in Word covers how to get out of that state.

A scanned PDF holds a photograph of a page with no text inside it, so it needs optical character recognition first. Google Docs runs OCR automatically when you open a PDF from Google Drive. Microsoft Word does not perform OCR on a scan and will typically place the page into the document as an image. See converting a scanned PDF to Word.

Word for Mac opens PDFs through the same File, then Open path as the Windows version. macOS has no built-in PDF to Word conversion: Preview can view and export PDFs but cannot produce an editable Word file, and Pages cannot open a PDF as editable text. Google Docs works from any browser on macOS and is the usual free route.

A PDF page is a fixed canvas. A Word page is whatever the text fills after it reflows. Once text is flowing again, small differences in font metrics, line spacing or margins accumulate down the document, and a line that no longer fits pushes everything after it along. Font substitution is the most common trigger, because a replacement font that is slightly wider changes where every line breaks.

It depends on whether the table was reconstructed or merely redrawn. A PDF does not store a table, only the lines that were drawn and the text placed near them, with no record of which text belongs to which cell. A converter that rebuilds those relationships gives you a real Word table. One that does not gives you line drawings with text floating on top, which looks correct until you try to edit a cell. Borderless tables are hardest, because there are no drawn lines to work from.

An online converter uploads your document to a server you do not control, where it is processed and stored at least temporarily. For public material that is fine. For a contract, a medical record, a privileged client file or anything carrying personal data, the upload itself is the exposure, independent of how good the conversion is. Check the retention policy first, or use software that runs on your own machine.

No. Opening a PDF in Word or Google Docs reads the file and builds a new document from it, leaving the original untouched. The one thing to watch is that Word keeps the original filename until you save, so use Save As and pick Word Document (.docx) to keep the two files clearly distinct.