basetools
PDF

Convert PDF to an editable Word (.docx) file

Rebuilds a PDF's text as an editable .docx document — paragraphs, heading hierarchy, bold and italic when detectable, and simple lists — without reproducing the original layout: columns, text boxes, and exact positioning aren't preserved.

This rebuilds the text with basic formatting — it's not an identical copy of the PDF. Columns, text boxes, exact element positioning, and images aren't preserved. The result is meant for editing the text content, not for getting the same visual layout as the original file.

Click to choose a PDF

Up to 50 MB, no password protection

Local processing: your file never leaves your computer.

  • Does:Rebuilds a PDF's text as an editable .docx document — paragraphs, heading hierarchy, bold and italic when detectable, and simple lists — without reproducing the original layout: columns, text boxes, and exact positioning aren't preserved.
  • Processes:Your PDF is processed entirely in your browser — nothing is uploaded to a server.

What this tool rebuilds, and what it doesn't try to do

A PDF is, by nature, a "digital printed page" format — every element sits at an exact position, designed for printing, not editing. A Word document is the opposite: built for rewriting, reorganizing, and formatting as flowing text. Converting from one to the other isn't a copy — it's a reconstruction, based on what can be identified with confidence in the PDF's text (paragraphs, headings, bold, italic, lists), and deliberately without trying to reproduce exact position, columns, or text boxes, something a Word document simply doesn't represent the same way a PDF does. Everything runs locally, in your browser, so the file you upload is never transmitted anywhere while it's being converted.

Where each paragraph comes from

The PDF's text is read item by item, along with the position of each chunk on the page. Items close together vertically form a line; lines close enough together, without a larger gap between them, form a paragraph — the same logic used by any tool on this site that needs to rebuild flowing text from a PDF. When a line ends with a word broken by a hyphen (common in text justified for print), the word is reassembled before it goes into the final paragraph.

How headings get identified

There's no explicit "this is a heading" marker inside a typical PDF — what exists is a larger font, used visually to make a section stand out. This tool calculates the most common font size in the document (the "body text") and compares every paragraph against that reference: a paragraph with a font much larger becomes a level-1 heading, a bit larger becomes level 2, and so on. It's a proportional estimate — it can get it wrong in a document with unusual font usage, or one that doesn't use font size to set sections apart at all.

Bold and italic: only when the PDF actually says so

Every font embedded in a PDF carries (sometimes) its own information about its style — whether it's a bold variant, an italic one, or neither. When that information is available clearly, the text comes out with the same style in the generated document. When it isn't — a font with a generic name, no clear style indication — the text comes out without bold or italic, instead of risking a guess that wasn't actually read from the file. That's the difference between "detected" and "invented," and this tool only does the first one.

Simple lists, without preserving the exact numbering style

A line that starts with a list marker — a bullet symbol (•, -, *) or a number (1., 2.) — is recognized as a list item and converted into a bulleted list in the generated document. The original marker's exact style (roman numerals, letters, a specific symbol) isn't preserved — every detected list item comes out with the same marker format in the result, a deliberate simplification to keep the conversion reliable instead of trying to recreate every possible list-style variation.

Why the honesty notice comes before you upload anything

The most common expectation when using a PDF-to-Word converter is to open the result and find a visual copy of the original — which this tool doesn't deliver, on purpose. That's why the notice about what isn't preserved shows up on screen before you even choose a file, not just after the result is ready or buried in an FAQ answer: whoever uses it decides with the right expectation from the start, not after already generating the document.

What this tool doesn't do

It doesn't reproduce columns, text boxes, tables as a visual grid, images, or the exact position of any element — only the text, rebuilt as paragraphs, headings, bold, italic, and simple lists. It doesn't recognize text inside an image (for that, this site has an OCR tool). It doesn't work with a password-protected PDF, which needs the protection removed first. And it doesn't guarantee that the detected heading hierarchy exactly matches what the original document's author intended — it's an estimate, worth checking carefully before treating the generated document as a final version for any use. Think of the result as a solid first draft to clean up in Word, not a finished, ready-to-ship file.

Frequently asked questions

Does the generated document look visually identical to the original PDF?

No, and this tool doesn't try to do that. It rebuilds the text CONTENT — paragraphs, headings, bold, italic, simple lists — as an editable .docx document. Columns, text boxes, the exact position of each element on the page, and images aren't preserved. The result is meant for editing the text, not for getting an identical copy of the layout.

How does the tool decide what counts as a heading?

By the font size of each paragraph relative to the most common size in the document (the "body text") — a paragraph with a font much larger than the body becomes a level-1 heading, a bit larger becomes level 2, and so on. It's a proportional estimate, not a reading of markup: a PDF doesn't declare "this is a heading" anywhere, so the classification can be wrong in documents with unusual font usage.

Why do bold and italic show up 'when detectable,' not always?

Because bold and italic information comes from the internal descriptor of the font used in the PDF, and not every PDF exposes that information clearly enough for automatic reading — some embed a font with a generic name, with no style indication. When it can't be determined confidently, the text comes out without bold or italic, instead of applying a guessed value.

Can this tool recognize text inside an image in the PDF?

No. It reads text that already exists as text inside the PDF (the layer extracted by pdf.js) — an image inside the PDF, even if it visually looks like text, isn't read. For that, this site has a dedicated optical character recognition (OCR) tool.

Is the extracted text sent to any server during conversion?

No. Reading the PDF and generating the .docx both happen entirely in your browser — the uploaded file is never transmitted to any server run by this site.

Related tools