Step 1 / source
Choose the source
Drop one file here
Choose the modern word docx you want to turn into rendered page pdf.
Checking publication status...LOCAL DOCUMENT CONVERTER / WORD TO PDF
Render an unencrypted DOCX into a page-by-page PDF locally, keeping visible text, tables, images, headers, footers, and common Word layout. Legacy .doc files are not accepted.
Step 1 / source
Choose the modern word docx you want to turn into rendered page pdf.
Checking publication status...This operation runs with browser APIs. Nirmion receives catalogue requests, not the selected source bytes.
The converter creates a separately named output. It never writes back into the source file.
One unencrypted .docx file up to 15 MB, 2,000 package parts, 120 MB expanded data, and 120 rendered pages. Output is limited to 100 MB.
Plain-language method
The browser preflights the DOCX ZIP package, reconstructs its pages as HTML, waits for local fonts and embedded media, captures each visible page, and places those page images into a separate PDF. No document bytes are sent to Flask or MySQL.
Use .docx created by a current Word-compatible editor. Password-protected packages, legacy binary .doc, damaged relationships, and oversized expanded packages are rejected.
Start with standard quality. Use high only when small text needs extra sharpness and the device has enough memory.
The result ends in _nirmion_tools.pdf and keeps the rendered page appearance. Because pages are captured visually, text search, selection, links, comments, tracked-change controls, and accessibility structure may not carry into the PDF.
Useful when
Before converting
Know the boundary
Browser rendering is not Microsoft Word. Complex fields, macros, equations, SmartArt, unusual fonts, floating objects, and pagination can differ. Use Word or LibreOffice for legally controlled or pixel-exact output.
Quick answers
The conversion contract is deliberately explicit.
No. Convert .doc to .docx in an authorised desktop editor first.
Not reliably. This release captures rendered pages to preserve appearance, so treat the result as page images.
No. The renderer reads supported OOXML parts and does not execute VBA macros.