PDF

Word to PDF · Desktop beta

Convert a DOCX file to PDF on your PC. Chrome/Edge 137+; large first-run download.

Runs in your browser · No file or text uploads

Preparing your tool…

ABOUT THIS TOOL

What Word to PDF · Desktop beta helps you do

Make a PDF from Word paragraphs, tables and page breaks without sending the document to a conversion server. This desktop beta uses a local LibreOffice engine and needs a capable PC.

How to use it

Select one DOCX file, up to 5 MiB.
Read the desktop and download requirements, acknowledge them, then choose Convert to PDF.
Wait for the engine download and conversion. Cancel stops the local engine.
Inspect the first-page previews and download the complete PDF. Compare important formatting with the original.

Input and output example

INPUT

Two-page DOCX with a title, table and Korean paragraph

OUTPUT

A PDF with two pages; review substituted fonts and table breaks

Supported formats and limits

Only DOCX; one file at a time, maximum 5 MiB. Legacy DOC/XLS/PPT, password-protected files and damaged packages are not supported.
Desktop Chrome or Edge 137+ with WebAssembly JSPI. Mobile devices and browsers without JSPI are not supported. A capable PC with at least 4 GB RAM is recommended.
The first run downloads a large engine and Korean font from this site. It can use around 1 GB of working memory. Browser cache settings determine whether another download is needed.
Macros, embedded OLE objects and externally linked resources are rejected. Font substitution and differences in charts, pagination or spreadsheet print settings can affect the PDF.
This beta does not convert PDFs back to Word, PowerPoint or Excel. It does not restore editable content from PDFs.

How the result is calculated

A pinned LibreOffice WebAssembly build imports the DOCX package and exports PDF locally. Document page setup controls pagination. Previews show up to the first three pages. No file content is uploaded.

Frequently asked questions

Is my Office file uploaded?

No. The browser downloads public engine and font assets, then works with your document in memory. The document, its filename and output are not included in engine requests.

Why is this a desktop beta?

The engine is much larger and more memory-intensive than the other tools and needs a recent Chromium browser. Real documents can expose font or layout differences; compare the result before using it.

Will every font and page break stay identical?

Exact layout is not guaranteed. Missing fonts are substituted and LibreOffice may paginate some elements differently.