A .docx file is a ZIP archive, not a document format
Under the hood, a .docx file is a ZIP archive containing a set of XML files — styles.xml for formatting rules, document.xml for the actual content, plus files for images, fonts references, and more. Opening a .docx 'properly' means parsing all of that XML and reconstructing styles, tables, and layout from it, which is a substantial undertaking.
This tool takes a narrower path: it unzips the .docx entirely in the browser using JSZip, reads just word/document.xml, strips the XML tags, and keeps paragraph breaks. What's left is the raw text content with none of the formatting instructions that lived alongside it. For .txt and .md files there's no unzipping step needed — they're already plain text — but the same principle applies: content in, formatting stays out.
What each input format gives you
| Input format | What's extracted | What's lost |
|---|---|---|
| .docx | Paragraph text from document.xml | Styles, tables, images, fonts, headers/footers |
| .txt | Full text content | Nothing to lose — already plain text |
| .md | Raw text including markdown syntax | Rendered formatting (the `bold`, `#` symbols stay as literal characters) |
| legacy .doc | Not supported | Requires a binary parser this tool doesn't include |
Converting a document to PDF
Drop a .docx, .txt, or .md file onto the zone.
Click Convert to PDF — the text is extracted and rendered to A4 pages with word-wrapped paragraphs.
The PDF downloads instantly.
Why Markdown files come out looking odd
Markdown is plain text with formatting conventions layered on top — asterisks for bold, pound signs for headings — meant to be interpreted by a Markdown renderer. Since this tool extracts raw text rather than rendering Markdown syntax, a heading written as `## Section Title` will appear in the PDF exactly as those literal characters, not as a larger, bolded heading. This is expected behavior for a plain-text extractor, not a bug: it treats Markdown source the same as any other text file, syntax and all.
Getting readable output from a word-wrapped PDF
Because layout is generated fresh rather than copied from the source, paragraph breaks are the one structural element that reliably carries over — the tool explicitly preserves them when reading document.xml, then re-wraps each paragraph's text to fit A4 page width. What doesn't carry over is anything relying on visual formatting to convey structure: a document that used bold text or larger fonts (rather than actual headings or explicit line breaks) to distinguish sections will read as one undifferentiated block of body text in the output.
Common mistakes
Uploading a legacy .doc file and expecting it to work — the binary .doc format needs a different parser than this tool includes; save or export as .docx first.
Converting a table-heavy .docx and expecting the table to render as a table — table structure lives in styles/layout XML this tool doesn't parse, so cell contents come out as plain sequential text.
Assuming a Markdown file will render its formatting — the tool extracts literal text, so Markdown syntax characters appear as-is rather than being interpreted.
Reaching for this tool when visual fidelity to the original document matters — for that, a native 'Save as PDF' from Word or LibreOffice is the right tool, not a plain-text extractor.
When this tool is genuinely the right fit
Turning a plain-text draft or notes file into a shareable PDF without installing anything.
Converting a simple .docx letter or memo, with no tables or embedded images, into PDF for archiving.
Getting Markdown source content into a portable PDF for reading, when preserving the rendered formatting isn't required.
Quickly producing a PDF from text content pulled from another tool, as a lightweight last step in a workflow.
Frequently asked questions
Q: Why is the formatting lost?
A: This tool extracts plain text only — no styles, tables, images, or fonts. For faithful Word-to-PDF conversion, use LibreOffice or Word's built-in 'Save as PDF' feature instead.
Q: How does .docx extraction work?
A: .docx files are ZIP archives containing XML. The tool unzips in-browser, reads word/document.xml, strips the tags, and keeps paragraph breaks.
Q: Is my document uploaded?
A: No. Unzipping and PDF generation both happen locally, using JSZip and pdf-lib.
Q: Does it support .doc (legacy) files?
A: No — the binary .doc format requires a different parser. Convert the file to .docx first, then use this tool.
Q: My PDF came out as one long page of text with no section breaks — why?
A: If the original document used bold text or font size changes (rather than actual paragraph breaks) to separate sections, that visual distinction doesn't carry over, since only paragraph breaks are preserved during extraction.
Q: I need to go the other direction — PDF back to an editable document. Can I?
A: Yes, see PDF to Word for the reverse conversion, with the same plain-text trade-offs.
Convert your file now
Turn your document into a PDF with the Word to PDF tool. Need the reverse direction? Try PDF to Word. Converting images instead? Use Images to PDF, or for styled web content, see HTML to PDF. Combining multiple results into one file? Merge PDF can do that.
