How to convert Word to PDF
- Add your
.docxfile. It stays on your device — nothing is sent anywhere yet. - The first time, YUQUE tells you it needs to download a local Office engine (about 57 MB) and waits for you to continue.
- The document is printed to pages in a separate local tab. Keep that tab open until it finishes.
- The pages appear in the workspace, where you can reorder or remove them before exporting.
- Export as PDF — or as PNG, JPEG or WebP if you want images instead.
What happens to the layout
The document is rendered the way it would be printed: paragraphs, images, tables, headers and footers, page breaks and page size all follow the document's own print layout. Because the rendering engine is not Microsoft Word, line breaks and font substitutions can differ slightly, and rare or heavily embedded objects may be flattened. For ordinary reports, letters and CVs the result reads the same; for a document with unusual macros-driven layout or exotic embedded content, check the pages before you send them.
Text, links and fonts
Body text usually stays selectable in the exported PDF, and ordinary hyperlinks are often preserved — both are best-effort rather than guaranteed, so treat them as a bonus rather than a contract. Common multilingual documents, including Chinese and Vietnamese text, render with a bundled font instead of falling back to empty boxes.
The first use downloads an engine
The first Office import downloads a local Office processing engine — about 57 MB — into your browser. YUQUE shows that before anything starts downloading, and nothing is fetched until you choose to continue. Later imports reuse the cached engine and are much faster. If your browser clears its cache, the engine is downloaded again.
Your document stays on your device
Your document is processed on your own device. It is not uploaded, there is no server-side copy and no conversion queue. The one thing that does travel over the network is the Office engine itself, which is downloaded from YUQUE the first time you use this — so this is "your file stays here", not "nothing is downloaded".
Desktop browsers are recommended
Office conversion is built for desktop browsers. The local engine reserves about a gigabyte of memory, which desktop Chrome and Edge handle comfortably; phones and tablets often do not, and Safari cannot run this engine at all today. Everything else in the workspace — PDF, images, DjVu, TIFF — works the same on any device.
Limitations
Only .docx is accepted — the older .doc format and macro-enabled .docm are not supported yet. Macros are never executed. Tracked changes and comments are rendered as the document would print them, which usually means they are not shown. Content that a Word document pulls from the network is not fetched.
Frequently asked questions
Does it keep my fonts?
If the font is a common one it will look the same. If the document uses a font that is not available to the local engine, a substitute is used, which can shift line breaks slightly. Embedding the font in the .docx before converting gives the most faithful result.
What about headers, footers and page numbers?
They are part of the print layout, so they are rendered into the pages. Fields such as page numbers are printed with the value the document would show when printed.
Is my file uploaded?
No. The conversion happens in your browser tab, so the document never leaves your device. The Office engine is downloaded from YUQUE the first time you use it; your file is not sent anywhere at any point.
Why is the first conversion slower?
Because the local Office engine has to be downloaded and started. On a desktop connection the whole first import — download, engine start and conversion — usually takes under ten seconds. After that the engine is cached and a small document is typically ready in a couple of seconds.
Can I cancel?
Yes. Cancel stops the import before any page is added. Once cancelling is accepted, no pages from that import will appear in the workspace, and the temporary copy of your document is deleted.