Python, Spyder, JupyterLab and the scientific stack — running from a folder.

Download — WinPython 2026-03

Released 22 August 2026, built entirely in GitHub Actions. 64-bit only. Every installer is a self-extracting 7-Zip archive: there is no setup wizard, it just unpacks a folder.

Python 3.13.15, 3.14.7 and 3.15.0rc1 · what changed · the exact version of every package is in the packages link on each build below.

All files: GitHub release · SourceForge · checksums for every file (MD5, SHA-1, SHA-256, blake2b) in md5_sha1.txt.

Which build should I take?

Two decisions, and only two: how much do you want preinstalled, and do you want the free-threaded interpreter. The suffix on the file name is just those two answers.

.exe and .7z / .zip hold identical content — the .exe is only a self-extracting archive, so use whichever your download policy allows.

The package set, without the 670 MB

Every WinPython build now publishes the exact package set it was made of, twice: as a pylock.toml (PEP 751) and as a hash-pinned requirements file. Both are a few hundred kilobytes, both pin every wheel by hash. If you already have a Python, you do not need our installer at all.

pip install --no-deps --require-hashes --no-warn-script-location ^
  -r https://raw.githubusercontent.com/winpython/winpython/17.12.20260522/WinPython/changelogs/requir.64-3_14_7_0slim.txt

pip install --no-deps --require-hashes --no-warn-script-location ^
  -r pylock.64-3_14_7_0slim.toml

pip download --dest C:\Wheelhouse --no-deps --require-hashes -r requir.64-3_14_7_0slim.txt
pip install --no-deps --no-index --find-links=C:\Wheelhouse --require-hashes -r requir.64-3_14_7_0slim.txt

This is what makes a WinPython release reproducible rather than merely downloadable, and it is the direction we are moving in: a build is now defined by its lock file, and the binary is one convenient way — not the only way — to obtain it. The 3.15 slim set above is the first that exists purely as a lock file.

Lock and requirement files for every build of the cycle, betas included, live in winpython/portable/cycle_2026_03. Want a different package set? Fork the repository, edit the requirements, and run the build workflow in your own GitHub Actions.

What WinPython is

A free, open-source, portable distribution of Python for Windows 10/11, aimed at scientific, data and educational work.

• Non-invasive

  Lives entirely in its own directory. No installer, no registry writes, no PATH surgery. Delete the folder and it is gone.

• Portable

  Move the folder to a local disk, a network share or a USB drive and it keeps working, along with most application settings.

• Side by side

  Install as many WinPythons as you want on one machine. Each is isolated and self-consistent, and they can be different Python versions.

• Yours to modify

  Add packages with pip or wppm, zip the folder, hand it to your students or your colleagues.

• Built in the open

  Every published build comes out of a GitHub Actions run you can read, fork and re-run yourself.

• Registered only if you ask

  Optionally associate .py files, add Edit with Spyder to the context menu, and declare WinPython as a standard Python distribution — see below.

Portable or not, the choice is yours

WinPython is a portable application, so by default it does not integrate into Windows Explorer. If you want that integration, the WinPython Control Panel or WPPM can register the distribution with Windows: file associations for .py and .pyc, Python icons in Explorer, Edit with IDLE / Edit with Spyder context menu entries, and an entry in the registry so standard Python installers can see it. That is exactly what the official Python installer does — so you can have it both ways.

Elsewhere