DOCX to PDF

Convert your DOCX files to PDF, right here in your browser.

Free
Private
No limits
No upload

... or drop files here

Files never leave your device

Add a DOCX file to convert.

Frequently asked questions

What is actually inside a DOCX file?

A .docx file is not one document but a ZIP archive of XML parts — one for the text, others for styles, images and relationships. Rename it to .zip and you can open it up and look.

Are my files uploaded to a server?

No. Your DOCX file is read and the PDF is built entirely inside your browser, so nothing ever leaves your device.

Can I convert several files at once?

Yes. Add as many DOCX files as you like and download the PDFs one by one, or all together as a ZIP archive.

Will the layout look exactly like the original?

The text, headings, lists and tables carry over and are laid out onto clean A4 pages. This is a content-faithful conversion rather than a pixel-perfect copy of the original formatting.

Is there a file size or file count limit?

No. Everything runs on your own device, so the only practical limit is how much memory your browser has available.

Do I need to install anything?

No. There is nothing to install and no account to create — the converter runs in any modern browser, on desktop and mobile alike.

Will my PDF look exactly like my Word document?

No, and it is worth being direct about that. Your text, heading structure and table data come across; the page design does not. Doing a pixel-exact job means running Word's layout engine, which exists on your computer and not in a browser tab. If the visual design is the point, use File → Save as PDF in Word. If getting the content into a fixed, shareable file is the point, this does that without uploading anything.

Why can't I convert a .doc file?

Because .doc is a completely different, binary format from before 2007 — not an older version of .docx but a different thing entirely, and one that realistically only Word and LibreOffice read correctly. Open it in either, or in Google Docs, and save as .docx first. A converter that accepted .doc and quietly produced garbage would be worse than one that tells you up front.

Do the images in my Word document come through?

No. Images are stored as separate files inside the .docx archive and positioned by Word's anchoring and text-wrapping rules; reproducing those faithfully is a large job, and getting them approximately right puts pictures in the wrong places. The converter carries the text, headings and tables and leaves images out rather than guessing.

Is my document uploaded to a server?

No. The archive is unzipped and parsed inside your browser tab, and the PDF is assembled there too. Nothing is transmitted, which also means confidential contracts, HR files and drafts under NDA never leave your machine — and that there is no queue and no file-size ceiling beyond your own available memory.

Can I convert several documents at once?

Yes. Add as many as you like and each is converted to its own PDF, keeping its original name. They are processed one after another on your device, so a large batch is limited by your machine rather than by a per-account quota.

What happens to tracked changes?

Tracked insertions come through as ordinary text, because that is exactly how they are stored in the document XML, and deletions and comments are dropped. Accept or reject the changes in Word first if the final PDF needs to reflect a decision either way.

A .docx file is not a document in the way it looks on screen. It is a ZIP archive, and inside it `word/document.xml` holds the text as a sequence of paragraphs, each tagged with the name of a style — "Heading1", "Title", "BodyText" — rather than with any appearance of its own. What that style looks like lives in a second file, `styles.xml`, and what it looks like *on your machine* depends on fonts Word expects to find installed rather than fonts carried inside the document.

That last detail is the reason a Word file opens differently on a colleague's laptop, and the reason converting to PDF is worth doing at all. A PDF fixes the result. This converter reads the paragraph list and the style names out of `document.xml`, then lays that content out fresh on A4 pages with a consistent typeface, so the file you send is the file they see.

What it does not do is photograph your Word layout. There is no Word engine in your browser to ask for one, so the output is a clean, readable rebuild of the document's content and structure — not a pixel copy of the page you were looking at in Word.

How to convert Word to PDF

Add your .docx files
Drop them in or choose them. You can queue several at once; each becomes its own PDF, named after the original. Only .docx is accepted — see the note below on the older .doc format.
Check the list
Files appear in the order you added them, and any you picked by mistake can be removed before you start. Nothing has been read yet at this point beyond the name.
Convert
The archive is unzipped in the page, `document.xml` is parsed, and the paragraphs are laid out onto A4. A long document takes a moment; the work is happening on your own processor rather than in a queue behind other people's files.
Download
Save each PDF, or take them all at once. Your .docx files are never modified and never uploaded — they are read in the browser tab and nothing is sent anywhere.

What comes across, and what doesn't

Paragraph text: Carried across in full, in document order, including text inside content controls — the bordered fields Word uses for templates and forms, which are a separate element in the XML and are easy to miss if a converter only walks top-level paragraphs.
Heading levels: Preserved as structure. A paragraph styled Heading1 through Heading9 is rendered as a heading, and a Title style as a title, so the document keeps its shape rather than flattening into one undifferentiated block of text.
Tables: Each row is written out as a line with its cells separated, set in a monospaced face so the columns line up down the page. You keep the data and the row-and-column relationship; you do not keep ruled borders or cell shading.
Images: Not carried over. Pictures in a .docx live as separate files inside the archive, referenced by relationship IDs, and placing them faithfully means reimplementing Word's anchoring and text-wrap rules. Rather than drop them in the wrong place, this converter leaves them out. A document whose point is its pictures is better exported from Word itself.
Fonts, colours and exact layout: Not reproduced. Output is set in a standard sans-serif at consistent sizes — 20pt for titles, 14pt for headings, 11pt for body text — with the page broken wherever the text runs out of room, not where Word broke it.
Tracked changes and comments: Not rendered. Tracked insertions appear as ordinary text because that is how they sit in the XML; deletions and comment bubbles are dropped. Accept or reject changes in Word before converting if the distinction matters.

Why .docx and not .doc

The two extensions look like versions of one format and are nothing of the sort. `.docx` has been the default since Word 2007 and is Office Open XML — a ZIP of XML parts, an open ECMA and ISO standard, and readable by any program willing to unzip it. `.doc` is the binary format that preceded it: a compound file with Word's internal structures written more or less straight to disk, undocumented for most of its life, and realistically parseable only by Word or by LibreOffice's long-refined importer.

Reimplementing that in a browser tab is not a reasonable proposition, and pretending to would mean shipping a converter that silently mangles old files. If you have a .doc, open it in Word, LibreOffice or Google Docs and save it as .docx first — every one of them does this correctly and for free.

The same reasoning explains the extension list on the picker. It accepts what the converter can genuinely read, rather than accepting everything and failing later.

Documents in other scripts

The standard PDF fonts cover Latin text and little else, so a document in Greek, Cyrillic, Arabic, Hebrew, Hindi, Thai, Chinese, Japanese or Korean would come out as a page of blank boxes if it were laid out the ordinary way.

When the text needs glyphs those fonts do not have, the converter switches approach: it draws each page using the fonts already installed on your device, which handle the full range including right-to-left scripts, and embeds the finished pages into the PDF. The result reads correctly and prints correctly. The trade-off is that text on those pages is an image, so it is not selectable or searchable — an honest consequence of not being able to ship a 20 MB CJK font to every visitor.

When the output looks wrong

A PDF containing only the filename means the parser found no text. Almost always the file is a .doc renamed to .docx, which the archive step rejects immediately because it is not a ZIP at all.

Missing sections usually means the content sits somewhere this converter does not read: text boxes, headers and footers, and footnotes live in their own parts of the archive rather than in the main document body.

A document that arrives much longer than expected is normally a table-heavy one. Wide tables consume vertical space quickly once each row is written as a text line, and a spreadsheet-shaped document is usually better served by Excel to PDF.

About the DOCX format

.docx is the word-processing format Microsoft introduced in 2007. It is published as an open specification under the name ECMA-376 / ISO/IEC 29500, so a file can be read without the program that wrote it.

A .docx file is not one document but a ZIP archive of XML parts — one for the text, others for styles, images and relationships. Rename it to .zip and you can open it up and look.

Files like this usually come out of Microsoft Word, Google Docs, and LibreOffice Writer.

What comes through

body text
heading levels
bulleted and numbered lists
table rows and columns
embedded images
reading order

What does not

the exact page design
tracked changes
comments
macros

Worth knowing

Because the format is an open, published one rather than a proprietary blob, a {ext} file can be read by LibreOffice, Google Docs, Apple's iWork apps and this page alike — none of them needs Microsoft Office installed to make sense of it.
Heading styles are read as structure rather than as big text, so the levels in the original become real headings rather than a guess based on font size.
This conversion is content-faithful, not pixel-faithful: text, heading levels and table columns survive, the original page design does not.

Information