Convert DOCX to PDF
Word to PDF, in your browser.
Drop your .docx file
or click to browse · max 50MB
or paste with ⌘V
Converting DOCX to PDF wraps your Word document in the universal cross-platform format. Our engine runs entirely in your browser tab — no server, no upload — and produces true vector PDFs with selectable, searchable text. PDF is what most workplaces, government portals, and printers expect when they ask for a document — JPGs and Word files often get rejected, PDFs are accepted everywhere.
When you'd use it
Submit forms and applications
Many job-application portals, tax filings, and contract systems insist on PDF. Converting your Word draft to PDF gives you something they'll accept on the first try.
Lock the formatting before sharing
Word docs render slightly differently on different machines depending on installed fonts. Converting to PDF freezes the layout, so what you see is exactly what your reader sees.
Email reliably across systems
PDFs pass through corporate email gateways more reliably than DOCX, which gets quarantined or re-converted by some scanners. PDF is the safe-bet attachment format.
How it works
-
Your file never leaves the browser.
-
Conversion runs locally via WebAssembly and Canvas.
-
Download. No account, no history.
Technical notes
Under the hood we run a battle-tested office document engine compiled to WebAssembly and executed inside a Web Worker in your browser tab. The conversion uses the same filter pipeline that Linux servers and CI systems have used for over a decade to convert Word documents to PDF — so output is a real vector PDF with embedded fonts and selectable text, not a rasterized image. The runtime (~52 MB compressed) downloads once on first use, then is cached by your browser. Subsequent conversions in the same session run in 0.1–2 seconds; only the first use of the engine has the one-time download cost. Open-source engine attribution and licenses are on the Credits page (linked from the footer).
Frequently asked
What happens to my DOCX files?
Nothing leaves your browser. The conversion runs locally on your device using WebAssembly and the Canvas API. No file is uploaded to a server — including ours.
Is the converted PDF identical to the original?
PDF preserves the input image exactly — embedJpg embeds your JPG bytes verbatim, embedPng embeds the PNG losslessly. The page size matches your image's pixel dimensions.
Is there a file size limit?
There is no hard cap, but very large files (hundreds of MB) may be slow on older devices because everything happens in your browser's memory.
Do you collect data on my file or my use?
Your file is invisible to us — it never leaves your browser. For aggregate page-view counts we use Cloudflare's server-side edge logs (no JavaScript beacon runs in your browser). We display Google AdSense ads on conversion result pages; the AdSense script loads on every page and may set advertising cookies after you accept the consent banner (Google Consent Mode v2 asks first). The ads see the page URL and standard browsing signals — they never see your file, because the file never leaves your device.
How does this compare to opening the file in Microsoft Word and saving as PDF?
Very close, but not pixel-identical. The engine renders ~95% of Word documents indistinguishably from Word itself. The remaining 5% are edge cases: fonts Word has installed that the bundled engine doesn't (we substitute with similar fonts — usually invisible, occasionally a bullet glyph differs), complex layout features like SmartArt diagrams or Word-specific embedded objects, and pixel-level font hinting differences. For standard business documents — letters, reports, tables, lists, headings, hyperlinks, colors — output is visually equivalent to Word's own PDF export.
Is the output really searchable and copy-pasteable?
Yes. The PDF contains true text (not an image of text), so you can select, copy, and search every word with Cmd+F or Ctrl+F in any PDF viewer. The fonts used by the document are embedded into the PDF itself, so the file looks the same on every device.
Where does my file go?
Nowhere. The entire conversion happens inside your browser tab. Your DOCX is never uploaded, never sent to any server, never seen by us. The engine binary downloads from a CDN on first use (so we don't bake a 50+ MB file into the page), but that download is just the conversion code — it doesn't carry any of your document's content.
Why does the first conversion take longer?
On the very first use, your browser downloads the conversion engine (~52 MB compressed). Expect 5–30 seconds depending on your connection. After that, the engine stays cached in your browser, and subsequent conversions in the same session take 0.1–2 seconds — usually faster than uploading the file would be.
How big is the resulting PDF?
Comparable to what Word or LibreOffice would produce for the same input — typically a few KB per page of text, plus the embedded font subsets and any images. A 5-page text-only document is usually 50–100 KB; a document with full-color photos might be 1–5 MB. Much smaller than a raster screenshot of the document would be.
What does NOT work?
Word-specific features like change tracking, embedded VBA macros, some SmartArt diagrams, and rare legacy formats may render simplified or be skipped. Very large documents (50+ pages with many images) may run into browser memory limits, especially on mobile Safari. If a document fails here it would also typically fail in any non-Microsoft converter — try simplifying the formatting in Word first.
Why not just use Word's built-in PDF export?
You should, when you can. Word's export is fastest if you already have Word open. This tool exists for the moments when you don't have Word handy — you're on a phone, a Chromebook, a borrowed laptop, a Linux machine — and you just need a real PDF right now without uploading your document anywhere.