Notebook to Word,a document anyone can open.

Use the converter at the top of this page: choose or drop in your .ipynb file and the browser assembles a real Word document — headings, shaded code blocks, lists and outputs. Download the .docx and open it in Word, Google Docs, LibreOffice or Pages. No upload, no install.

Yes. The converter writes the Open XML parts a Word document consists of — content types, package relationships, styles and the document body — and packages them as a ZIP in the browser. That is exactly what a .docx is, so no application treats it as a renamed text file.

The nbconvert DOCX exporter needs Pandoc installed and, depending on your configuration, a reference document and a LaTeX engine for the conversion. This page has no external dependency at all: the document is assembled in the tab, which also means nothing has to be uploaded to a server.

Yes. The package contains the parts a Word document needs, including a styles part that defines every paragraph style the body references. Word, Word Online, Google Docs, LibreOffice, Pages and WPS all open it as an ordinary document.

A figure has no text form, so image outputs become a short note naming where the figure sat instead of vanishing silently. For a document where the plots are rendered, use the IPYNB to PDF converter, which paginates the figures into the page.

LaTeX math appears as its source text — readable in the document but not typeset as equations. Rendering math in Word requires an OMML conversion pass that a browser-only export cannot do; the PDF converter typesets it properly.

Yes — it is an ordinary Word document. Headings, lists and code paragraphs are normal styled paragraphs, so you can retype prose, move sections, apply your own template, generate a table of contents from the headings, or add comments and tracked changes.

Code cells land in a paragraph style that pairs a monospace face with a light shaded background and an indent, so code is visually distinct from prose and its indentation is preserved. Syntax colours themselves are not applied — the goal is a readable document, not an IDE.

Yes by default: stream text, results and tracebacks follow their code cell as text paragraphs with a lighter style, so a printed document walks the same path the notebook ran. Turn outputs off and the document carries the code and prose only.

Yes. The file is read with the browser File API and the .docx parts are assembled inside the tab, so after the page loads you can disconnect the network and the conversion still works — which is also the practical proof that nothing was uploaded.

No. The notebook is parsed and the Word document written in the browser. No server is involved at any step, and closing the tab leaves nothing behind.

Yes, with no account, no file-size gate and no watermark. The conversion runs on your own device, so there is no per-file cost — same as the site's IPYNB to PDF, PY, HTML, Markdown, TXT and LaTeX converters.