JupyTools.com
Available now.zip

Split IPYNB ZIP bundle

Slice a long notebook by Markdown headings or chunk size and grab every part in one ZIP for modular lessons or smaller reviews.

How it works

Cut one notebook into several

1

Upload one large .ipynb

Heading mode follows Markdown titles. Chunk mode slices every N cells.

2

Check later parts still run

Variables defined in early cells will not exist if a student opens only part 3. Add imports if needed.

3

Save the ZIP

Each part is a valid notebook. Processed for this request only.

Split Jupyter notebook online, break one.ipynb into multiple valid notebooks in your browser

When one notebook mixes a whole semester, this tool turns it into several valid .ipynb files you download in one ZIP. Each part opens independently in JupyterLab, VS Code, or Colab — useful when a file becomes impossible to review or when tickets need smaller attachments. No nbconvert or local Python stack required.

Students hit this when one giant file mixed every unit; teams split artifacts before attaching cells to different PRs. Choose rules that match your outline: split at Markdown headings (# for chapters, or # plus ## for sections), or slice every N cells for predictable chunk sizes. Filenames prefer the first heading in each slice when possible (for example 01-intro.ipynb), so the ZIP parts arrive already labeled for LMS upload.

Each exported notebook keeps kernelspec and language_info from the parent so runtime expectations stay consistent. Toggle execution hygiene—clear In [n] labels or renumber them inside each part—and pretty-printed JSON for readable archives. Remember that later parts may still depend on variables defined earlier; add setup cells or re-imports if students open slices in isolation. Saved outputs and embedded plots travel with the cells you grouped unless you stripped them beforehand. When heading mode returns a single part, add clearer Markdown titles or switch to a smaller chunk size so the ZIP actually contains multiple notebooks for graders.

Files are processed for this request only and are not stored afterward. Pair with our merger when you need round-trip experiments—split here, merge elsewhere. Use heading mode for teaching notebooks structured by titles; use chunk mode when LMS size caps or ticket workflows need evenly sized ZIP parts. Upload once, pick rules, preview any part, download notebook-split.zip.

How to split ipynb files online on this page

Step 01

Upload one notebook to split

Drop a long .ipynb to slice it by Markdown headings or cell chunks. No Jupyter install required.

Free IPYNB splitter online: drop a Jupyter notebook to slice it into multiple .ipynb parts and download as a ZIP

Step 02

Download the ZIP and preview parts

Get every split part as valid .ipynb files in one ZIP, then preview cells to confirm headings, code, and outputs look right.

Download a ZIP of split notebook parts and preview cells after splitting an .ipynb by headings or chunk size

Why split Jupyter notebooks here instead of nbconvert scripts

Split jupyter notebook online, headings or fixed chunks

Markdown-boundary mode respects # (and optionally ##) starts so split jupyter notebook into multiple files follows your outline; chunk mode splits every N cells when you need mechanical slices.

Split ipynb file with sensible filenames

Downloads name parts from the first heading in each slice (01-intro.ipynb) when possible, classic ipynb file splitter polish without manual renaming.

Execution counts per part

Optional clear or sequential In [1]… inside each export, helps graders after you split jupyter notebook online while outputs stay embedded.

Kernel metadata preserved

Each split notebook keeps kernelspec + language_info from the parent so JupyterLab and VS Code still open parts with the expected runtime.

Privacy-first split ipynb workflow

Split ipynb file logic uses secure server conversion, ideal when coursework cannot leave your laptop.

ZIP bundle download

One click grabs every .ipynb in notebook-split.zip (or a stem-based name) instead of dozens of separate saves.

FAQ

Frequently asked questions

Upload your .ipynb, choose heading-based or chunk-based splitting, then download the ZIP. That is split jupyter notebook online here, no account and no pip install required for the split itself.

Use this browser workflow: cells are grouped locally and exported with notebookToIpynb. Jupyter does not need to be installed, only a modern browser.

Yes, each slice carries the cells you grouped, including saved outputs and embedded images, unless you strip outputs elsewhere before splitting.

Each exported notebook is a full .ipynb with a subset of cells in document order, nbformat-valid JSON ready for JupyterLab or VS Code.

Heading mode needs Markdown boundaries: add # or ## titles, switch to H1+H2 depth, or use chunk mode with a smaller N.

No, it clones kernelspec metadata from the parent so each part still declares the same Python/R kernel name.

Yes, use our IPYNB Merger to queue the parts back into a single notebook when you need the inverse workflow.

No durable archive: split uses secure server conversion per our Privacy Policy — processed briefly and discarded.

Each entry is a full .ipynb with a subset of cells in document order. Filenames often derive from the first heading in that slice when heading mode finds boundaries.

Use headings when your notebook already has clear # / ## structure for lessons or chapters. Use every-N cells when you need evenly sized parts for tickets or LMS size caps.

Yes as notebooks, but later parts may depend on variables defined earlier. Add setup cells or re-import packages in each part if students open them in isolation.

That is a common use: produce smaller .ipynb files in a ZIP, then upload each lesson separately. Keep the original intact as your master copy.

Heading splits vs chunk splits

Heading mode is for teaching notebooks that already use Markdown titles as a table of contents. Each # (and optionally ##) becomes a new file named after that title. If heading mode returns a single part, the notebook does not have enough titles — add them, or switch to chunk mode.

Chunk mode ignores narrative structure. It is for LMS size caps and ticket attachments that only care about “no file larger than N cells.” Later parts will not see variables defined in earlier cells. Add imports or a short setup cell at the top of each part if students will open them in isolation.

Round-trip with the merger

Split here, send parts to different students, then merge the returned notebooks if you need one artifact again. The merger does not magically restore a shared kernel state. Treat each part as its own notebook.

If the parent file is already huge because of plots, strip or compress it before splitting. Otherwise every ZIP part still carries the same heavy outputs.

Try our other free tools