What this does

Drop in a .docx and it is laid out here, on your own machine, then written to PDF by your browser's print engine. Headings, tables, images, lists, headers and footers, and the document's own page size and margins all come through. The text in the result is real text — selectable, searchable and sharp at any zoom.

Nothing is uploaded. That matters more for Word files than for almost anything else people convert: contracts, CVs, references, medical letters and legal drafts are exactly what lands in this box, and every online converter that isn't doing the work locally has a copy of yours on a server.

How faithful is it?

Close, and honest about where it isn't. A Word document doesn't describe a page — it describes a stream of text whose appearance comes from a cascade of document defaults, named styles, numbering rules and direct formatting, all resolved at the moment of display. Resolving that cascade is what this does, and the result is usually indistinguishable from Word for the things documents are actually made of: paragraphs, headings, bold and italic, tables, bullet and numbered lists, images, page breaks and margins.

What can drift:

Fonts you have and the document expects. Word files reference fonts by name and rarely embed them. If a document asks for a font your device doesn't have, your browser substitutes the nearest match — exactly as Word does on a machine without it — and line breaks can land differently as a result.
Tracked changes and comments are not shown; the document is rendered as if all changes were accepted.
Fields that Word recalculates when it opens a file — page counts, cross-references, automatic dates — show the value last saved into the file.
Text boxes and floating shapes may sit differently, since their positioning rules are Word's own rather than the web's.

For anything where the exact layout is contractual, check the preview against the original before sending it. For the ordinary job of getting a readable, searchable PDF out of a Word file without handing the file to a stranger, it does the job.

Why the print window?

Because your browser contains a typesetter that writes proper PDFs, and nothing written in JavaScript comes close. The alternative approach — photographing the laid-out page onto a canvas and putting the picture in a PDF — produces a file with no selectable text that goes soft the moment it's printed. Handing the finished layout to the engine built for the job gives you real text and embedded fonts. Choose Save as PDF as the destination and that step is the conversion.

Is it private?

Yes. The document is unzipped, resolved and laid out by JavaScript inside this page, and printed by your own browser. It is never transmitted and never stored — there is no server on the other end to receive it. Images inside the document are turned into data held in the page rather than fetched, so nothing about the file reaches a third party either. Load the page, disconnect from the internet, and it still works.

Frequently asked questions

Can it open .doc?

No — the old binary .doc is a completely different format, and the tool will say so rather than failing obscurely. Open it in Word or LibreOffice and save as.docx first.

My document is password-protected.

Encrypted files can't be read without the password. Open it, save an unprotected copy, and convert that.

Why did the page count change?

Usually font substitution: slightly different metrics move the line breaks, which moves the page breaks. If it matters, install the font the document asks for, or set the paper size explicitly above.

Can I go the other way?

Yes — the PDF to Word tool extracts the text and structure of a PDF into an editable.docx.