DOCX to PDF — Convert Word Documents to PDF Online, Processed Locally

Turning a Word document into a PDF is not a simple file-extension swap; it means re-laying the text onto fixed paper with chosen size, margins and orientation. Everything here runs locally in your browser: the document never leaves your device, and the page keeps working offline once it has loaded. Drop one file or a whole batch of .docx documents, set A4, Letter, Legal, A3 or A5 paper, pick portrait or landscape, tune all four margins or apply a preset, choose searchable text PDF or image-based PDF, then convert and download. Corrupt or password-protected files are caught with a clear message instead of crashing, and converted files can be packaged into a single ZIP. The comparison view shows the original document next to the finished PDF so you can check the result before saving. Before converting, you can read an HTML preview rebuilt from the document structure to confirm that headings, paragraphs and tables were recognised correctly. You set the file-size limit yourself, and files above it are rejected at the queue with a clear reason. Every file in the queue has its own progress and status, a single failure is skipped and written to the log, and when done you can download by original name or package everything in one click.

Drop Word documents here

or click to choose .docx files — batch supported

Accepts .docx (and .doc, see notes). Max file size 20 MB. Files are processed locally and never uploaded.

PDF settings

Paper sizeOrientation

Margins

TopRightBottomLeft

Output mode

Re-flows the document into real vector text — selectable, copyable, crisp at any zoom, with CJK drawn from an embedded font. Best for most documents.

Max file size

File queue

No files yet. Drop or choose Word documents to begin.

Compatibility & limits

Legacy binary .doc files are not parsed; save as .docx first.
Text mode draws with an embedded CJK sans; brand fonts and rare glyphs are substituted.
Multi-column layouts, text boxes, floating images, footnotes and headers/footers are simplified or flattened.
Tracked changes, comments and macros are not preserved.
Tables are drawn as simple text grids without merged-cell or nested complexity.
PDF/A is best-effort metadata only; full conformance is not guaranteed client-side.

This tool runs entirely in your browser and does not upload your files. Results depend on the source document's complexity; always review the comparison view before relying on the output. It is not a substitute for a certified archival or legal PDF workflow.

How to use

Drop .docx files onto the page or click to choose several at once. The tool checks the extension and the file size against the limit you set, and rejects files that are too large or have the wrong type with a clear note. You can add more files later and remove any single item from the queue.
Open the settings panel to choose paper size (A4, Letter, Legal, A3, A5), orientation (portrait or landscape) and margins. Pick a preset like Standard or Narrow, or set each of the four margins by hand. Then choose the output mode: searchable text PDF (recommended, text can be copied) or image-based PDF (the page becomes a picture, best for exact visual fidelity).
Press Convert all to run the queue. Each file is converted one after another; a single failure is skipped and reported in the log without stopping the rest. A progress bar shows overall completion, and when a file finishes its preview appears automatically.
Review the result in the comparison view, which places the original document on the left and the generated PDF on the right. Download a single file with the original document name, download everything as a ZIP, copy a link that stores your current settings, or export a text log of what succeeded and what failed.

Frequently asked questions

Are my documents uploaded to a server?

No. Reading, layout, rendering, preview and download all happen inside your browser. The original files and the finished PDF never leave your device, and the page keeps working offline once it has loaded. Only loading a file from a URL would involve a network fetch, which is not part of this tool.

What is the difference between searchable text PDF and image-based PDF?

Searchable text PDF draws the characters with real fonts, so you can select, copy and search the text; it is smaller and better for archives. Image-based PDF captures each page as a picture, preserving the exact visual appearance (fonts, spacing, any layout quirk) but the text is not selectable and the file is larger. Choose image mode when faithful appearance matters more than copyable text.

Can it convert old .doc files (not .docx)?

This tool reads the modern .docx format. Legacy binary .doc files from very old Word versions use a different structure and cannot be parsed here; open them in Word or a compatible editor and save as .docx first. The file picker accepts .doc for convenience, but conversion will report a clear error rather than fail silently.

Why might my PDF look slightly different from the original Word file?

Complex Word features such as multi-column layouts, text boxes, floating images, tracked changes, footnotes, headers and footers, and exact font matching are flattened or simplified during conversion. Searchable text mode draws with an embedded CJK sans plus the PDF base Latin fonts, so brand fonts and rare glyphs from the source are substituted. For pixel-exact output, use image mode, which captures the rendered page as a picture.

If I enable PDF/A, is the output a fully compliant archival PDF?

Not quite. When enabled, the tool writes metadata such as the title and creation date and declares a best-effort PDF/A intent, but full PDF/A conformance also requires embedding every font, attaching an ICC colour profile and forbidding transparency and external dependencies — conditions a browser-only environment cannot guarantee one by one. Treat it as a best-effort archival marker only; for contracts, invoices or files that must be kept for years, verify the result with a dedicated validator before archiving.

What is it

A PDF page is a fixed-size sheet measured in points, where one point is one seventy-second of an inch; A4 is 595 by 842 points. Unlike a Word file, which reflows to whatever screen it is opened on, a PDF freezes the layout: every paragraph, heading and table sits at an exact coordinate. The conversion therefore has two jobs. First, read the Word document and turn it into something the browser can lay out — here the library extracts the document's structure (headings, paragraphs, lists, tables, bold and italic) into HTML. Second, place that content onto PDF pages. In text mode the tool draws each character with a real font, so the result is selectable and copyable; in image mode the rendered page is captured as a picture, which preserves the exact visual look but makes the text non-selectable and the file larger. Margins define the rectangle available to the body text, and content taller than one page continues on the next, so larger paper and narrower margins usually mean fewer pages for the same document. The image-quality setting only changes the sampling scale in image mode; text mode always draws vector text and stays sharp at any zoom, which also explains why the two modes can differ so much in size. Both modes keep the document on your device; nothing is uploaded to a server.

Origin & history

The need to turn office documents into fixed-layout files is almost as old as graphical word processors. In the 1980s and 1990s Word used a proprietary binary .doc format; other programs could only read it through reverse engineering or vendor-supplied components, and conversion usually happened on a desktop machine with the same software installed. Adobe released PDF in 1993 with one clear goal: a file should keep the same layout on any machine and any system. PDF was gradually opened up afterwards and became ISO 32000 in 2008; PDF/A, aimed at long-term preservation, was defined by ISO 19005 in 2005 and set stricter requirements for font embedding, colour profiles and metadata. The turning point came around 2007. Microsoft changed the default format in Word 2007 to .docx, which is no longer proprietary binary but a ZIP package holding XML files, later standardised as ECMA-376 and ISO/IEC 29500. That step turned understanding Word from a job needing licensed components into parsing work anyone can implement: unpack the archive, read the XML, and you can extract paragraphs, styles, lists and tables. Open-source libraries that convert .docx into HTML appeared soon after, choosing to preserve semantic structure rather than fight over pixel positions, and this tool's parsing stage is built on exactly that route. The other thread is the browser growing up. The File API and Blob let a page directly read the file a user selects without uploading it first; Canvas lets a page capture a rendered result as a bitmap. Mozilla's pdf.js, started in 2011, proved that complex PDFs can be parsed and displayed inside a browser; libraries such as pdf-lib that followed made creating, writing and merging PDFs a purely front-end operation; and html2canvas and html-to-image filled in the last piece, capturing the DOM as an image. Put together, unpacking, parsing, laying out, generating a PDF, previewing it and downloading it could for the first time happen end to end without a server. This tool leaves paper, output mode and batch handling in the user's hands, and keeps the whole process local so the document never has to leave the browser.