Convert a Word .docx to a printable PDF: mammoth turns the document into clean HTML and the print dialog saves it — images and tables included.
Conversion runs entirely on your device with mammoth and your browser's print engine. Your document never leaves it.
Drop a .docx here or click to browse — Word 2007+ format only
Conversion runs in two entirely local stages: the open-source mammoth library turns your .docx into semantic HTML inside the page, and your browser's own print engine turns that HTML into a PDF when you choose Save as PDF in the print dialog that opens.
@page rule. When you click the button, the frame is sent to window.print() — your browser's print engine (the same one behind Print on any web page) produces the PDF, and its page-break decisions are the real ones you get in the file.No — and that is the honest trade-off of a converter that never uploads your file. Word keeps its layout logic outside the text, and reproducing it exactly needs Microsoft's rendering engine, which server-side services run on their machines. Here, mammoth extracts the meaning of the document and your browser lays that out on A4 paper. Body text, headings, lists, tables and images come through well; exact pagination and Word-specific spacing will differ.
Yes. mammoth reads the pictures embedded in the .docx package and inlines them as base64 data URIs in the HTML, so the print engine draws them directly. The document's text boxes and floating image placements are not preserved — images land in the flow of the text near where they appeared. A file with many high-resolution scans gets correspondingly heavy.
Semantic formatting survives: headings become heading levels, bold and italic stay bold and italic, ordered and unordered lists stay lists, and plain tables are rendered as tables. What is simplified: merged cells, exotic borders, exact column widths — and anything carried by Word styles that mammoth cannot map to HTML meaning.
Headers and footers, footnotes, comments, tracked changes, text boxes, columns and multi-section layouts are dropped — they have no faithful representation in the semantic HTML this pipeline produces. Table of contents fields, embedded objects and macros also don't convert. For those, the file needs real Word or a LibreOffice-based service.
No. The .docx is unzipped and translated to HTML in your browser by mammoth, and the PDF is produced by your own browser's print engine. There is no upload step, no account, and no network request containing your document.
If you just finished with DOCX to PDF, the natural next steps are Signature Generator, PDF Merge & Split, PDF Text Extractor, or browse every tool in Privacy File Tools.