Dzielenie IPYNB

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.