A PDF has no paragraphs — a text extractor has to guess where they are
A PDF doesn't store 'paragraphs' the way Word does. Internally, a PDF page is a sequence of positioned text-drawing instructions: this string of characters goes at this x,y coordinate. There's no structural tag saying 'this run of text is one paragraph' — that concept only exists in the mind of whoever laid out the original document. Extracting text means walking through those positioned instructions with pdf.js and reconstructing something readable from coordinates and line breaks.
This tool preserves that reconstruction as separate paragraph elements in the output .docx — but it's working from position data, not real document structure, which is the root of every limitation below. A PDF that has tables, multi-column layouts, or precisely positioned captions gives an extractor much less to go on than a simple single-column text document.
What survives conversion vs. what doesn't
| Element | Preserved | Why |
|---|---|---|
| Plain text content | Yes | Directly extracted from the PDF's text layer |
| Paragraph breaks | Yes, as separate `<w:p>` elements | Reconstructed from line-position data |
| Fonts, bold, italic | No | Only plain text is extracted, not styling |
| Tables | No | Table structure isn't part of a plain-text layer |
| Images | No | Only text is extracted |
| Multi-column layout | No | Reading order across columns isn't reliably inferable from positions alone |
| Scanned page text | No | Scans are images with no text layer to extract from |
Converting a PDF to Word
Drop a PDF onto the zone.
Click Convert to .docx — text is extracted and packaged as a Word file.
Open the .docx in Word, Google Docs, or LibreOffice.
Why the .docx file is deliberately minimal
The .docx format is a ZIP archive of XML files describing styles, layout, sections, and more — a full implementation is a large undertaking. This tool generates only the minimum XML structure Word actually requires to open a file: paragraphs as individual `<w:p>` elements, no styles beyond plain default text. That keeps the tool lightweight and fast, but it also means you're trading fidelity for simplicity — the output is meant as an editable text starting point, not a visual replica of the original PDF.
Checking whether your PDF is even a good candidate
Before converting, it's worth checking whether your PDF has a real text layer at all. Try selecting text in the PDF with your cursor in any PDF viewer — if you can select and copy individual words, there's a text layer to extract from. If clicking and dragging just highlights the whole page as one image, or nothing selects at all, the PDF is scanned and this tool has nothing to extract; you'd need an OCR step first to generate a text layer before conversion could work.
Common mistakes
Running a scanned PDF through this expecting text output — scanned pages are images with no text layer, so there's nothing to extract.
Expecting tables to come through as tables — table structure isn't part of a plain-text extraction; expect the cell contents to appear as a jumble of text in reading order instead.
Assuming the .docx will visually match the PDF — this conversion targets editable plain text, not layout fidelity.
Converting a heavily multi-column PDF (like a two-column academic paper) and expecting correct reading order — column-crossing text can come out interleaved incorrectly since positions alone don't reliably indicate column boundaries.
When this tool is the right fit
Pulling the text out of a single-column report or letter so you can edit it in Word without retyping from scratch.
Getting a rough editable draft from a PDF contract to revise the wording, accepting that formatting will need to be reapplied.
Quickly grabbing text content from a PDF for reuse elsewhere, where paragraph breaks matter but styling doesn't.
Converting simple single-column documents (memos, plain letters, text-heavy PDFs) where there's little layout complexity to lose.
Frequently asked questions
Q: Does it preserve formatting?
A: No — only plain text is extracted. Tables, images, fonts, and layout are not preserved. For faithful conversion, you'd need a dedicated layout-aware engine.
Q: Why a minimal .docx?
A: The .docx format is complex, so this tool generates only the minimum XML needed for Word to open the file, with paragraphs preserved as separate `<w:p>` elements.
Q: Will scanned PDFs work?
A: No — scanned PDFs are images with no text layer to extract from. You'd need to run OCR on the file first to generate extractable text.
Q: Is my PDF uploaded?
A: No. Extraction and .docx packaging both happen entirely in your browser.
Q: If I just want the plain text without a .docx wrapper, is there a simpler option?
A: Yes — if you don't need a Word file at all, PDF to Text or Extract Text from PDF skip the .docx packaging step entirely.
Q: What if I need the reverse — turning a Word document into a PDF?
A: That's a different conversion direction with different constraints; see Word to PDF.
Convert your PDF now
Extract editable text with the PDF to Word tool. Just need the raw text? Try PDF to Text or Extract Text from PDF. Need a structured, markdown-style output instead? Check PDF to Markdown.
