Free PDF to Word Converter

Convert PDF files to editable Word DOCX documents instantly. Extract text content and create a document you can edit. Your files never leave your device.

Your files never leave your device
Drop PDF file here or click to browse

Supports PDF · up to 50 MB

Converting PDF...

Conversion Complete

Your Word document is ready to download.

How It Works

  1. Upload PDF: Drop or select a single PDF file to convert to Word.
  2. Configure Options: Choose font, page breaks, and page number settings.
  3. Convert to Word: Click "Convert to Word" to process the PDF and extract text.
  4. Download DOCX: Download your converted Word document and edit it as needed.

Why Convert PDF to Word?

Converting PDF files to Word documents gives you an editable format that you can easily modify, format, and reuse. Word documents are more flexible than PDFs, allowing you to add comments, change fonts, reorganize content, or incorporate the text into larger documents. This is particularly useful for contracts, reports, research papers, and any document you need to edit or customize.

Features

Frequently Asked Questions

Does this preserve the original PDF layout?

This tool extracts text content and creates a basic Word document. Complex layouts, columns, images, and formatting from the original PDF may not be perfectly preserved. For documents where layout is critical, you may want to manually adjust the Word document after conversion.

Can I edit the converted Word document?

Yes. The output DOCX file is fully editable in Microsoft Word, Google Docs, LibreOffice, and other compatible applications. You can add, remove, or modify any text, and apply your own formatting.

What about images and graphics in the PDF?

This tool extracts text content only. Images, graphics, and diagrams in the PDF are not included in the converted Word document. For documents with significant visual content, you may need to manually add images back into the Word file.

Can I convert scanned PDFs?

No. This tool works with PDFs that contain selectable text. Scanned PDFs (image-based PDFs) do not contain extractable text and would require OCR (Optical Character Recognition). Use an OCR tool first to extract text from scanned documents.

What's the file size limit?

Files up to 50 MB are supported. Larger files may work depending on your browser's available memory, but conversion will be slower.

Can I convert password-protected PDFs?

Yes, if the PDF is protected with a user password (not an owner password). You would need to remove the password first using another tool, then convert with this tool.

Is my PDF uploaded to a server?

No. All conversion happens locally in your browser using PDF.js and the docx library. Your PDF never leaves your device, ensuring complete privacy and security.

Can I convert on mobile devices?

Yes. This tool works on desktop, tablet, and mobile browsers. Just tap to select a PDF file and the conversion will process on your device.

What is a PDF to Word converter?

A PDF to Word converter takes a PDF file and produces a Microsoft Word DOCX file with the same text content laid out so you can edit it in Word, Google Docs, LibreOffice or any DOCX-compatible application. The output is a brand new editable document; the original PDF stays on your disk untouched. The Word file is structured into paragraphs and runs of formatted text, which is fundamentally different from a PDF's flat stream of positioned glyphs.

PDF was designed as a final-format file in 1993, optimized for faithful display and print rather than editing. Word documents are the opposite: structured, editable, and built for reflow. Converting between them is therefore a guess-the-original-intent problem rather than a mechanical translation. The converter walks the PDF's content stream, groups glyphs into words and lines, and tries to reconstruct paragraph breaks and font runs. For straight prose this works well; for tables, columns and complex layouts the reconstruction is imperfect by definition.

This tool uses pdf.js (Mozilla's JavaScript PDF renderer) to read each page and docx.js to build the output Word file, both running entirely in your browser. The file you upload never leaves your device. The output DOCX can be opened in Word, Google Docs, Pages, LibreOffice and every other modern word processor. The conversion focuses on text content and basic paragraph structure; tables, embedded images and complex multi-column layouts may need manual cleanup after the conversion.

What is inside the tool

A drop zone at the top accepts your PDF file. The 50 MB limit is a comfortable browser-memory ceiling; pdf.js handles larger files but conversion of very long documents slows down significantly. After upload, an info panel shows the filename, page count and file size so you can confirm the right document is queued. There are no extra options to fiddle with; the conversion is one-click.

Click Convert to Word and the tool walks every page of the PDF, extracts the text content using pdf.js, groups text by paragraphs (using vertical spacing and font changes as paragraph-break heuristics), and assembles a Word document using docx.js. The progress bar shows which page is being processed. A typical 10 to 20 page document converts in a few seconds; a 200 page document takes a minute or two depending on your machine.

When the conversion completes, a Download button appears. The downloaded DOCX file goes to your default downloads folder and opens directly in Microsoft Word, Google Docs (drag in or upload), LibreOffice Writer, Apple Pages, and any other DOCX-compatible editor. The file size of the output Word document is typically smaller than the original PDF because the Word format is more compact for text-heavy content.

History and background

PDF and Word as opposite design philosophies (1983 vs 1993)

Microsoft Word for MS-DOS was released in 1983 and for Macintosh in 1985, with the .doc binary format becoming the office editing standard. PDF (Acrobat 1.0) shipped a decade later in 1993 with the opposite design goal: a portable read-only final form, not an editing format. Word documents flow and reformat as you type; PDFs are frozen pages of positioned glyphs. The very design choices that make PDFs great for printing make them hostile to editing, which is what makes PDF-to-Word conversion an inherently lossy problem.

Acrobat 6 ships Save As Word (2003)

Adobe Acrobat 6 (released May 2003) was the first widely-used tool to offer PDF-to-Word conversion built in. The Save As Word Document feature in Acrobat Professional could produce a .doc file from any PDF with extractable text. The conversion was imperfect (Acrobat itself published lengthy disclaimers about layout reconstruction) but it established the user expectation that PDFs could become Word documents in one click. Later versions improved the quality, especially for table reconstruction in Acrobat 9 (2008).

Solid Documents and the specialist converters (2007)

Solid Documents released Solid PDF to Word in 2007 and quickly became the gold standard for desktop PDF-to-Word conversion, particularly for documents with complex tables and multi-column layouts. The company licensed its conversion engine to other vendors including Foxit and Nitro PDF. The specialist converters used layout-aware heuristics: detecting table boundaries, recognizing column flows, preserving font runs as character formatting. They cost money but produced noticeably better output than Acrobat or generic web converters for documents where layout reconstruction mattered.

Microsoft Word opens PDFs directly (2013)

Word 2013 (released January 2013) added the ability to open a PDF directly with File > Open. Word performed an internal PDF-to-Word conversion (Microsoft calls it PDF Reflow) and presented the result as an editable document. This was a major usability improvement: no separate converter required. The quality varies by document, much like every other converter. For text-heavy PDFs the result is usually good; for design-heavy PDFs Word warns the user that the reconstruction may not match the original.

Web converters and the SaaS wave (2013 onwards)

Smallpdf (2013), iLovePDF (2014) and PDF24 (older but expanded web service) made browser-based PDF-to-Word free and accessible. Their model required uploading the PDF to the vendor's server for processing, which raised privacy concerns for confidential documents. The convenience drove huge adoption: by 2020 these services collectively processed billions of conversions per year. The trade-off (privacy for convenience) is precisely what client-side browser tools like this one address.

Client-side conversion becomes viable (2019 onwards)

As pdf.js and docx.js matured, fully client-side PDF-to-Word conversion in the browser became practical. The user uploads nothing; the conversion happens in JavaScript on the user's machine. This is the path this tool follows. The output quality matches typical web converters for text-heavy documents; for layout-heavy documents the desktop specialists (Solid PDF to Word, Acrobat Pro) still produce somewhat better reconstruction, but the privacy trade-off favours browser-based conversion for any confidential document.

Practical workflows

Editing a PDF you do not have the source for

A vendor sends you a service agreement as a PDF without the Word source. You need to make tracked changes for your legal team to review. Convert to Word, edit with Track Changes in Word or Google Docs, share back with the vendor. The reconstruction may need a quick layout cleanup but the text is editable and your colleagues can use familiar review tools. This is the single most common reason to convert PDF to Word.

Migrating old PDFs back to editable archives

Many organizations have thousands of PDFs from decades past where the Word source has been lost or deleted. When a document needs updating (new policy, new fiscal year, new branding), converting back to Word is the first step. The output is rarely pixel-perfect but it gives you editable text to rebuild from. Pair with manual layout cleanup in Word for documents that will be re-published.

Translating a PDF to another language

Translation tools (Google Translate Documents, DeepL, professional translation memory tools like SDL Trados) work much better with Word documents than with PDFs. Convert to Word first, then run the translation, then optionally re-export to PDF after the translation is reviewed. The Word format also lets the translator track changes and add comments, which is critical for any review cycle.

Extracting and reformatting content for a new document

You want to use a section of a PDF report in a new presentation or memo. Convert to Word, copy the relevant paragraphs (now properly editable text), paste into the new document, and reformat in your target style. This is faster than copying directly from a PDF reader, which often introduces broken line breaks and lost formatting.

Updating a published form or template

An old PDF form (intake form, expense report template, application form) needs new fields, updated branding, or revised wording. Convert to Word, edit in Word with proper form fields (Developer tab in Word, or use Google Forms equivalent), then re-export as a PDF or distribute as Word. This works best for simple forms; complex AcroForms with calculations should be edited in a PDF form editor.

Pulling data from a PDF table

A financial report includes a table you need for analysis. Convert the PDF to Word, copy the table into Excel, clean up any cells that broke during conversion. For tables this is usually a starting point rather than a finished result; complex tables need manual cleanup. For pure data extraction (no need to preserve formatting), pdfplumber or tabula-py in Python often give cleaner results than going through Word.

Common pitfalls

Tables often break into separate text boxes

A PDF table is rendered as a grid of text fragments at specific x/y positions; there is no underlying table structure in most PDFs. The converter has to guess where the table boundaries are, which is harder than it sounds. Most converters produce tables as a series of text boxes or paragraph runs with tabs, not as proper Word tables. The fix is to recreate the table in Word manually after the conversion, or use Excel to clean up the data if you only need the values.

Multi-column layouts get scrambled

Academic papers, magazines, and newspapers typically use two or three columns per page. The converter sees each column as a stream of glyphs by x/y position and may interleave left and right columns into a single paragraph flow. The result reads as: first line of left column, first line of right column, second line of left column, and so on. For multi-column PDFs, copy column by column manually instead, or use a layout-aware Python library like pdfplumber that respects column boundaries.

Fonts get substituted

The PDF embeds specific fonts (sometimes obscure or custom) at specific point sizes. Word substitutes them with the nearest available font on your system. The result is the same content with different typography, which can break carefully designed documents. If your output document needs to match the PDF visually, manually re-apply the intended font in Word after conversion (or use a converter that explicitly preserves embedded fonts).

Form fields do not translate

PDF interactive forms (AcroForms or XFA forms) store field values separately from the static page content. The converter only sees the static page text, so form values are lost in conversion. If you need to convert a filled PDF form and keep the values, first extract them with a form-aware tool (pdftk, Adobe Acrobat Export Data, or Python pdfplumber's form-field API), then merge them into the Word document manually.

Mathematical equations come out garbled

Math is positioned using individual glyphs from special symbol fonts (Computer Modern, STIX). The converter reads the glyphs but loses the spatial relationships that make x squared different from x times 2. Inline equations come out as scrambled symbol sequences; display equations as disconnected runs of characters. For math-heavy PDFs, use a specialist math-aware tool (MathPix snip), or extract the equations as images for visual inclusion in the Word document.

Scanned PDFs produce empty Word documents

If a PDF was created from a scan, it contains an image of the page, not extractable text. The converter walks the content stream, finds no text operators, and produces an empty or nearly-empty Word document. Run the scan through OCR first (Tesseract, Adobe Acrobat Recognize Text, ABBYY FineReader) to add a text layer, then convert. If the source is purely a scan and you need an editable result, OCR is the unavoidable first step regardless of which conversion tool you use afterwards.

Privacy and data handling

The PDF you upload stays on your device throughout the conversion. pdf.js reads it into browser memory, docx.js assembles the output Word file, and the result downloads directly to your disk, all in JavaScript running on your machine. There is no upload step, no remote processing, and no telemetry about what document you converted. This matters because the documents you most want to convert privately (contracts, medical records, legal correspondence, financial statements) are exactly the documents you should never send to a third-party cloud converter.

Once the page is loaded, the tool works offline. You can disconnect from the internet, drop a PDF, run the conversion, and download the Word document without your data ever touching another machine. Cloud-based converters (Smallpdf, iLovePDF, Adobe Document Cloud) require uploading the PDF before processing; for confidential documents that is precisely the failure mode to avoid.

When not to use this tool

When you only need the text (use PDF to Text)

If your only goal is to extract text for searching, indexing, pasting elsewhere, or feeding to another tool, use the PDF to Text tool instead. It is simpler, faster, and avoids the overhead of building a Word document structure that you do not need. PDF to Word is for when you want an editable document; PDF to Text is for when you want the raw words.

For complex tables or data extraction (use specialised tools)

For documents that are primarily complex tables (financial reports, scientific data tables, parts catalogues), generic PDF to Word converters produce messy output. Use specialist tools: pdfplumber (Python library, free), tabula-py (Python, free), or Adobe Acrobat Pro's Table Extraction feature (paid). For one-off table extractions, Camelot (Python) and Excalibur (web UI for Camelot) are also options. Word documents store tables but the conversion to them is rarely table-faithful.

For scanned PDFs (run OCR first)

If your PDF is a scan of paper or a series of photos, there is no extractable text to convert. The Word document this tool produces would be empty. Run the PDF through OCR first: Tesseract (free command-line, excellent for English and Latin scripts), Adobe Acrobat Pro Recognize Text (paid, best layout retention), or ABBYY FineReader (paid, best for non-Latin scripts and complex documents). After OCR adds a text layer, this converter will work normally.

When pixel-perfect layout matters more than editability

If the document's exact visual layout is more important than being editable (legal exhibits, certified documents, technical drawings), do not convert to Word. The conversion will inevitably reflow text and substitute fonts, producing a document that no longer matches the original exactly. Keep the PDF as the authoritative version and only convert sections that genuinely need editing.

More questions

Why is the converted Word document different from the original PDF?

PDFs store positioned glyphs, not paragraph structure. The converter has to guess where paragraphs end, where columns flow, where tables start, which font is which. These guesses are correct most of the time for straight prose but get progressively worse for complex layouts. For documents where the conversion needs to be near-perfect, use a desktop tool with layout-aware conversion (Acrobat Pro, Solid PDF to Word, ABBYY FineReader) and expect to do some manual cleanup afterwards.

Will images from the PDF appear in the Word document?

This browser-based converter focuses on text and basic structure; embedded images may or may not survive the conversion depending on the PDF's complexity. For PDFs where images matter (photo books, presentations, illustrated reports), open the PDF in a viewer and extract the images separately, then insert them into the Word document manually. The PDF Extract Images tool on this site pulls every image from a PDF for this purpose.

Can the conversion go the other way, Word to PDF?

Yes, but use the dedicated Word to PDF tool for that direction. Word to PDF is the easy direction: Word already has a well-defined structure that maps cleanly to PDF. Every word processor (Word, Google Docs, LibreOffice, Pages) has built-in Export to PDF. The hard direction is PDF to Word because PDFs lack the structural information that Word relies on. Microsoft Word itself can open PDFs (File > Open in Word 2013 and later) using the same kind of reverse-engineering this tool does.

Does the tool support non-Latin scripts (Chinese, Arabic, Cyrillic)?

Yes, provided the source PDF has a proper ToUnicode font map for those characters (which any modern PDF does). The extracted text is Unicode and shows up correctly in the Word document. Right-to-left scripts like Arabic and Hebrew are produced in logical order; you may need to apply right-to-left paragraph formatting in Word for proper display. CJK (Chinese, Japanese, Korean) is fully supported.

What is the difference between DOC and DOCX?

DOC is the old Microsoft Word binary format (Word 97 to 2003). DOCX is the newer XML-based format introduced in Word 2007, standardized as ISO/IEC 29500 (Office Open XML) in 2008. DOCX is essentially a ZIP archive of XML files, which makes it open, parseable and well-supported by every modern word processor. This tool produces DOCX. If you specifically need DOC for compatibility with very old Word versions, save the DOCX as DOC from inside Word after the conversion.

How does this compare to opening the PDF directly in Word?

Microsoft Word 2013 and later can open PDFs directly using File > Open. The quality of Microsoft's built-in conversion is generally comparable to web converters for text-heavy documents and slightly better for layout-heavy documents (Microsoft has invested heavily in PDF Reflow). The advantage of this browser tool is privacy: nothing is uploaded, and the conversion runs on devices that may not have Word installed (Linux, Chromebook, mobile). Use whichever fits your workflow.

Related Tools