Notebook to Python script,in one drop.

Use the converter at the top of this page: choose or drop in your .ipynb file, and the browser turns it into a Python script with # %% cell markers — code cells unchanged, markdown as comments. Then download the .py file. No upload, no install and no terminal involved.

Run jupyter nbconvert --to script notebook.ipynb. nbconvert ships with Jupyter, so it needs no extra install, and it writes a notebook.py in the percent format next to your notebook. This page produces the same layout in the browser instead, without opening a terminal.

A .py file can only contain Python, so markdown cells become # comment lines between the cell markers. Headings, lists and notes survive as readable comments; only rendered images and LaTeX have no script form and are left out.

Yes — the code cells are copied unchanged in notebook order, so if the notebook ran top to bottom, the script does too. Two caveats: outputs are not carried over (re-run the script to regenerate them), and Jupyter magics like %matplotlib inline or shell lines like !pip install are not valid Python, so comment those out before running.

Both produce the same style of script, and nbconvert is the right tool inside a pipeline you already have. This converter runs in the browser instead: nothing is installed, nothing is uploaded, and it works on machines without Jupyter — for example when you received a notebook and only need the code.

Three common reasons: running the code somewhere without a kernel — a scheduler, a CI job, a server; reviewing changes as a plain-text git diff, which no notebook rendering gives you; and importing functions into another project. An .ipynb file stores outputs and metadata; a .py file is just code your tools already understand.

VS Code can export a notebook open in the editor: use the Jupyter extension's export command and choose Python Script, which writes the percent format. If the notebook is only a file (Colab, Kaggle, a download), drop it into this page instead — the script is the same either way.

In Colab use File → Download → .ipynb to save the notebook locally, then convert that file here. Colab has no direct .py export that keeps markdown; the downloaded notebook converts exactly like any other .ipynb file.

The classic Jupyter File menu offers downloads as .ipynb, .py, .html, .md and .pdf — the .py entry is the same conversion nbconvert does, and it comments markdown and writes cell markers. Notebook 7 and JupyterLab hide it behind the nbconvert route, which is why a browser converter is often the faster path.

Yes. The # %% markers in the script are the percent format that VS Code's Python Interactive and Jupytext both read: open the .py in VS Code and click “export” above a cell, or run jupytext --to ipynb script.py. The round trip is not pixel-perfect — markdown becomes comments and cannot be fully restored as markdown.

No. The file is read with the browser's File API, parsed as JSON and turned into a script 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.

Yes, with no account, no file-size gate and no watermark. Conversion runs on your own device, so there is no per-file cost to pass on — same as the site's IPYNB to PDF converter.