Word to PDF
Online

When you'd want to convert Word to PDF

Most of the time it's because the recipient asked for it specifically. Job applications, research submissions, government forms, expense reports — they all want PDF, not Word. The reason is that PDF is the format that looks the same on every machine. A .docx that looks fine on your laptop can shift its layout on the recipient's machine if they have different fonts installed, a different version of Word, or open it in something other than Word at all (Google Docs, Pages, LibreOffice). Sending a PDF removes that risk: the recipient sees exactly what you saw.

The other common reason is finality. A document sent as PDF is one you don't expect them to edit further. The cover letter is final, the proposal is final, the report is what it is. Sending the .docx invites changes; sending the PDF says "this is the version".

What goes in, what comes out

The tool accepts .docx files (the modern Word format used since Word 2007). Older .doc files are not supported — Word's binary format from before 2007 is too different from the modern XML-based format to render reliably in the browser. If you have a .doc file, open it in Word, Google Docs, or LibreOffice and save it as .docx first, then convert here.

The output is a PDF that looks like your document. Headings, paragraphs, tables, images, lists, headers, footers, page numbers all come through. What's worth knowing about the result:

• The output is image-based — text isn't selectable. The tool renders each page of your document into the browser as HTML, takes a picture of it, and saves the PDF as a sequence of those pictures. That's the only way to guarantee fidelity (so a picture of your document is what gets stored). The trade-off is that recipients can't copy text out of the PDF or run search on it. For a CV or a final report this is usually fine — the document is meant to be read, not extracted from. If text-selectability matters (legal filings, academic papers indexed for search), use Word's own "Save as PDF" if you have it, or a different conversion tool.
• Fonts may not match exactly. Word documents reference fonts by name (Calibri, Cambria, Arial). The browser may not have those fonts installed; this tool substitutes metrically-compatible alternatives from Google Fonts (so a line of Calibri text takes about the same width and height as it would in real Calibri). The result looks very close, but a graphic designer would notice. For day-to-day documents the substitution is invisible.
• Comments and tracked changes are flattened. If your .docx has unresolved tracked changes or comments in the margins, the PDF shows them as-is. Accept the changes and resolve the comments in Word before converting if you don't want them in the output.

What's preserved, what isn't

What does come through cleanly:

• Heading styles, body text, paragraph spacing, lists.
• Tables with their content, borders, and shading.
• Embedded images (photos, charts copied from Excel, screenshots).
• Headers, footers, page numbers, footnotes.
• Page size and orientation (A4, Letter, landscape).

What may not survive perfectly:

• Complex layouts — multi-column documents, sidebars with floating images, callouts. The tool handles them but the result may be slightly different from Word's exact rendering.
• Form fields — interactive form fields (checkboxes, dropdowns) become flat content. The form is still readable, just not interactive.
• Macros and embedded objects — macros don't run, embedded Excel sheets are converted to their visible representation, embedded videos become still placeholders.
• Hyperlinks — the URL text comes through and is visible, but it isn't clickable in the PDF (since the PDF is image-based).

Practical notes

1. Long documents take longer. A 200-page document needs to be rendered and captured page by page, which takes minutes on a typical laptop. Be patient on the first run — the tool isn't stuck, it's just working through the pages.
2. For a smaller PDF, run the result through compress-pdf after conversion. PDFs from Word documents with lots of images can come out larger than necessary.
3. To go the other direction (PDF back to Word), see pdf-to-word. Note that the round-trip Word → PDF → Word loses the original Word formatting completely — the second Word file would be a Word document built from the image PDF, which is very different from the original .docx.
4. If you need to sign the document, do it after converting: convert here first, then add your signature with sign-pdf on the resulting PDF.

What happens to your file

The .docx you drop in is read into your browser's memory. It's parsed and rendered locally — the conversion engine runs in your browser, not on a server. The resulting PDF is offered to you as a download; nothing is uploaded, nothing is stored on a server, no copy of your document is kept anywhere. You can verify it: open DevTools, watch the Network tab while you convert, and you'll see only the initial page load and (if you have analytics enabled) anonymous pings — never your document content.