Notebook to Markdown,plain and portable.

Use the converter at the top of this page: choose or drop in your .ipynb file and the browser builds a Markdown document — markdown cells as-is, code cells fenced with the kernel language, outputs embedded. Then download the .md file. No upload, no install, no terminal.

Run jupyter nbconvert --to markdown notebook.ipynb. nbconvert writes a .md file next to your notebook and a folder of extracted images. This page embeds images as data URLs instead, so you get one portable file — useful for wikis that dislike asset folders.

Stream text, JSON and execute_result outputs become fenced blocks under the code. HTML output tables are converted to real GFM tables, images are embedded as base64 data URLs, and tracebacks are kept as plain text with the error name.

Markdown is the format your tools already edit: it diffs cleanly in git, renders on GitHub and in Obsidian, and can be pasted into most documentation systems. Choose HTML for a shareable page and PDF for printing; choose Markdown when the text will keep changing.

The Jupyter extension in VS Code exports HTML, Python scripts and .ipynb files — not Markdown, so vscode ipynb to markdown has no built-in answer. Drop the notebook into this page instead: the .md it produces renders the same in VS Code's Markdown preview.

In Colab use File → Download → .ipynb to save the notebook locally, then convert that file here. Colab has no direct Markdown export; the downloaded notebook converts exactly like any other .ipynb file — headings, code, plots and all.

Yes — image outputs are embedded as base64 data URLs inside the .md, and GitHub renders those directly in the file preview. That also means the file is larger than an nbconvert export with a separate image folder; the trade-off is one portable file versus many small ones.

Formulas export as their LaTeX source inside fenced blocks. Markdown has no universal math syntax — GitHub uses $$ delimiters, Obsidian its own — so the export keeps the formulas copy-pasteable rather than guessing a dialect.

nbconvert extracts images into an assets folder next to the .md; this converter inlines them as data URLs so the Markdown file is a single artifact. Both produce valid Markdown — pick nbconvert when you manage assets explicitly, this page when you want one file.

No. The file is read with the browser's File API, parsed as JSON and serialized inside the tab. You can disconnect from the network after the page loads and the conversion still works — which is also the practical proof that nothing is uploaded.

Not on this site — that direction is the job of Jupytext or the VS Code Python Interactive window, which read ```-fenced scripts back into notebooks. The fences this converter writes are the format those tools understand.

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 IPYNB to PDF, IPYNB to PY and IPYNB to HTML converters.