Convert Jupyter Notebook to Python Script

Drag & drop your .ipynb file here, or click to browse

Converts to Python on secure servers · first daily conversion free · no signup

Your first conversion each day is free. A $2.99 one-time Day Pass unlocks 24 hours and ends by itself.

Convert Jupyter notebooks (.ipynb) to Python scripts (.py) instantly. Extract code cells, remove outputs, and create clean Python files for production deployment.

By ChangeThisFile Team · Last updated: March 2026

Quick Answer

ChangeThisFile converts a Jupyter Notebook to a Python script in seconds. It extracts code cells in notebook order and removes stored outputs and execution metadata. The current route processes the file on a secure server using encrypted transfer, then automatically deletes it after conversion. Free with no signup.

First daily conversion free No signup required Encrypted transfer · Async jobs kept up to 24h Queued when needed Updated July 2026

Jupyter Notebook vs Python: Format Comparison

Key differences between the two formats

Feature	IPYNB	PY
Type	Source format	Output format
Human-readable	Depends on contents	Depends on contents
Tooling support	Format-specific	Format-specific
Best for	Working with IPYNB	Working with PY

When to Convert

Common scenarios where this conversion is useful

Production Deployment

Convert research notebooks to production-ready Python scripts for deployment in containers, serverless functions, or scheduled jobs.

CI/CD Pipeline Integration

Extract Python code for automated testing, linting, and continuous integration workflows that require standard .py files.

Code Collaboration

Share clean Python code with team members who don't use Jupyter, or integrate notebook logic into larger Python applications.

Version Control Optimization

Create Git-friendly Python files that show clear code changes without notebook metadata and output noise.

Library Development

Extract functions and classes from exploratory notebooks to create reusable Python modules and packages.

Who Uses This Conversion

Tailored guidance for different workflows

Developers

Convert {'NAME': 'IPYNB', 'FULL_NAME': 'JUPYTER NOTEBOOK', 'DESCRIPTION': 'INTERACTIVE COMPUTING DOCUMENT CONTAINING CODE, MARKDOWN, AND OUTPUT CELLS', 'EXTENSIONS': ['.IPYNB'], 'MIME_TYPE': 'APPLICATION/X-IPYNB+JSON'} config files to {'NAME': 'PY', 'FULL_NAME': 'PYTHON SCRIPT', 'DESCRIPTION': 'PLAIN TEXT FILE CONTAINING EXECUTABLE PYTHON CODE', 'EXTENSIONS': ['.PY'], 'MIME_TYPE': 'TEXT/X-PYTHON'} for compatibility with different tools or frameworks
Transform {'NAME': 'IPYNB', 'FULL_NAME': 'JUPYTER NOTEBOOK', 'DESCRIPTION': 'INTERACTIVE COMPUTING DOCUMENT CONTAINING CODE, MARKDOWN, AND OUTPUT CELLS', 'EXTENSIONS': ['.IPYNB'], 'MIME_TYPE': 'APPLICATION/X-IPYNB+JSON'} API responses to {'NAME': 'PY', 'FULL_NAME': 'PYTHON SCRIPT', 'DESCRIPTION': 'PLAIN TEXT FILE CONTAINING EXECUTABLE PYTHON CODE', 'EXTENSIONS': ['.PY'], 'MIME_TYPE': 'TEXT/X-PYTHON'} for debugging, logging, or documentation

Validate the converted {'NAME': 'PY', 'FULL_NAME': 'PYTHON SCRIPT', 'DESCRIPTION': 'PLAIN TEXT FILE CONTAINING EXECUTABLE PYTHON CODE', 'EXTENSIONS': ['.PY'], 'MIME_TYPE': 'TEXT/X-PYTHON'} output with a linter to catch any structural issues from the conversion

Watch for data type coercion (e.g., numbers becoming strings) when converting between {'NAME': 'IPYNB', 'FULL_NAME': 'JUPYTER NOTEBOOK', 'DESCRIPTION': 'INTERACTIVE COMPUTING DOCUMENT CONTAINING CODE, MARKDOWN, AND OUTPUT CELLS', 'EXTENSIONS': ['.IPYNB'], 'MIME_TYPE': 'APPLICATION/X-IPYNB+JSON'} and {'NAME': 'PY', 'FULL_NAME': 'PYTHON SCRIPT', 'DESCRIPTION': 'PLAIN TEXT FILE CONTAINING EXECUTABLE PYTHON CODE', 'EXTENSIONS': ['.PY'], 'MIME_TYPE': 'TEXT/X-PYTHON'}

Data Analysts

Convert {'NAME': 'IPYNB', 'FULL_NAME': 'JUPYTER NOTEBOOK', 'DESCRIPTION': 'INTERACTIVE COMPUTING DOCUMENT CONTAINING CODE, MARKDOWN, AND OUTPUT CELLS', 'EXTENSIONS': ['.IPYNB'], 'MIME_TYPE': 'APPLICATION/X-IPYNB+JSON'} exports to {'NAME': 'PY', 'FULL_NAME': 'PYTHON SCRIPT', 'DESCRIPTION': 'PLAIN TEXT FILE CONTAINING EXECUTABLE PYTHON CODE', 'EXTENSIONS': ['.PY'], 'MIME_TYPE': 'TEXT/X-PYTHON'} for importing into spreadsheet software, databases, or BI tools
Transform {'NAME': 'IPYNB', 'FULL_NAME': 'JUPYTER NOTEBOOK', 'DESCRIPTION': 'INTERACTIVE COMPUTING DOCUMENT CONTAINING CODE, MARKDOWN, AND OUTPUT CELLS', 'EXTENSIONS': ['.IPYNB'], 'MIME_TYPE': 'APPLICATION/X-IPYNB+JSON'} datasets to {'NAME': 'PY', 'FULL_NAME': 'PYTHON SCRIPT', 'DESCRIPTION': 'PLAIN TEXT FILE CONTAINING EXECUTABLE PYTHON CODE', 'EXTENSIONS': ['.PY'], 'MIME_TYPE': 'TEXT/X-PYTHON'} for sharing with teammates who use different analysis tools

Check that column delimiters and quote escaping are handled correctly in the converted {'NAME': 'PY', 'FULL_NAME': 'PYTHON SCRIPT', 'DESCRIPTION': 'PLAIN TEXT FILE CONTAINING EXECUTABLE PYTHON CODE', 'EXTENSIONS': ['.PY'], 'MIME_TYPE': 'TEXT/X-PYTHON'} file

Preview the first few rows of the {'NAME': 'PY', 'FULL_NAME': 'PYTHON SCRIPT', 'DESCRIPTION': 'PLAIN TEXT FILE CONTAINING EXECUTABLE PYTHON CODE', 'EXTENSIONS': ['.PY'], 'MIME_TYPE': 'TEXT/X-PYTHON'} output to verify headers and data alignment

System Administrators

Convert {'NAME': 'IPYNB', 'FULL_NAME': 'JUPYTER NOTEBOOK', 'DESCRIPTION': 'INTERACTIVE COMPUTING DOCUMENT CONTAINING CODE, MARKDOWN, AND OUTPUT CELLS', 'EXTENSIONS': ['.IPYNB'], 'MIME_TYPE': 'APPLICATION/X-IPYNB+JSON'} configuration to {'NAME': 'PY', 'FULL_NAME': 'PYTHON SCRIPT', 'DESCRIPTION': 'PLAIN TEXT FILE CONTAINING EXECUTABLE PYTHON CODE', 'EXTENSIONS': ['.PY'], 'MIME_TYPE': 'TEXT/X-PYTHON'} when migrating between infrastructure tools or platforms
Transform {'NAME': 'IPYNB', 'FULL_NAME': 'JUPYTER NOTEBOOK', 'DESCRIPTION': 'INTERACTIVE COMPUTING DOCUMENT CONTAINING CODE, MARKDOWN, AND OUTPUT CELLS', 'EXTENSIONS': ['.IPYNB'], 'MIME_TYPE': 'APPLICATION/X-IPYNB+JSON'} log exports to {'NAME': 'PY', 'FULL_NAME': 'PYTHON SCRIPT', 'DESCRIPTION': 'PLAIN TEXT FILE CONTAINING EXECUTABLE PYTHON CODE', 'EXTENSIONS': ['.PY'], 'MIME_TYPE': 'TEXT/X-PYTHON'} for ingesting into monitoring or analysis systems

Back up the original {'NAME': 'IPYNB', 'FULL_NAME': 'JUPYTER NOTEBOOK', 'DESCRIPTION': 'INTERACTIVE COMPUTING DOCUMENT CONTAINING CODE, MARKDOWN, AND OUTPUT CELLS', 'EXTENSIONS': ['.IPYNB'], 'MIME_TYPE': 'APPLICATION/X-IPYNB+JSON'} config before converting, especially for production systems

Test the converted {'NAME': 'PY', 'FULL_NAME': 'PYTHON SCRIPT', 'DESCRIPTION': 'PLAIN TEXT FILE CONTAINING EXECUTABLE PYTHON CODE', 'EXTENSIONS': ['.PY'], 'MIME_TYPE': 'TEXT/X-PYTHON'} in a staging environment before deploying to production

How to Convert Jupyter Notebook to Python

1

Upload Your Jupyter Notebook

Select your .ipynb file using the file picker. It is uploaded over an encrypted connection for conversion.
2

Automatic Code Extraction

The server extracts code cells in notebook order, removes stored outputs and execution metadata, and prepares a clean .py file.
3

Download Python Script

Download the Python script for testing or version control. The server copy is automatically deleted after processing.

Automate this conversion

Convert Jupyter Notebook to Python via API

Integrate this conversion into your pipeline with 3 lines of code. Free tier: 25 conversions/month.

curl -X POST https://changethisfile.com/v1/convert \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "file=@input.ipynb" \
  -F "target=py" \
  -o output.py --fail

const form = new FormData();
form.append('file', fileInput.files[0]);
form.append('target', 'py');

const res = await fetch('https://changethisfile.com/v1/convert', {
  method: 'POST',
  headers: { 'Authorization': 'Bearer YOUR_API_KEY' },
  body: form
});
const blob = await res.blob(); // your converted Python file

Replace YOUR_API_KEY with your free key — no credit card needed.

Get a free API key

Frequently Asked Questions

What happens to markdown cells when converting to Python?

Markdown cells are converted to multi-line comments in the Python script, preserving your documentation while making it compatible with Python syntax.

Are cell outputs included in the converted Python file?

No, cell outputs (printed results, plots, tables) are removed during conversion. Only the executable code is preserved in the .py file.

Will my converted Python script run the same way as the notebook?

The code logic will be identical, but you may need to adjust import statements or file paths since notebooks and scripts have different execution contexts.

How are notebook magic commands handled in the conversion?

Jupyter magic commands (like %matplotlib inline or %%time) are preserved as comments since they're notebook-specific and won't work in standard Python.

Can I convert notebooks with multiple programming languages?

This converter is designed for Python notebooks. Cells in other languages (R, Scala, etc.) will be included but may not execute properly in a Python script.

Are execution counts and cell metadata preserved?

No, execution counts, cell IDs, and other notebook metadata are removed to create a clean Python script focused on the code content.

How does the converter handle notebook variables and state?

Variables and their relationships are preserved in the same order as the notebook cells, but the converted script won't retain any executed state from the notebook.

Can I convert password-protected or encrypted notebooks?

Standard .ipynb files aren't typically encrypted, but if your notebook has access restrictions, ensure you can open it normally before conversion.

Will imports and dependencies work the same way in the Python script?

Import statements are preserved exactly as written in the notebook. You may need to install the same packages in your Python environment to run the script.

How large notebooks can I convert?

The current server-side converter enforces the service upload limit. Notebook files are usually small after outputs are cleared; remove bulky stored outputs before converting an unusually large notebook.

Are function definitions and classes preserved correctly?

Yes, all function definitions, classes, and their proper indentation are maintained exactly as written in the notebook code cells.

Can I convert multiple notebooks at once?

Currently, the converter processes one notebook at a time. For batch conversion, you'll need to convert each .ipynb file separately.

Related Conversions

Related Tools

Free tools to edit, optimize, and manage your files.

Data Prettify Data Validate Merge CSV

Read our guides on file formats and conversion

Ready to convert your file?

Convert Jupyter Notebook to Python instantly — free, no signup required.

Start Converting