If you are trying to make sense of Parrot Linux versions, this page walks through every major release line, from the first 1.0 images to the current Parrot 7.4, and explains what changed along the way. Each era of Parrot OS maps to a different Debian base, a different default desktop and a different idea of what the distribution should be. Knowing that history helps you read old forum answers correctly, understand why some tutorials no longer work, and decide whether your installed system is still worth upgrading in place or should be reinstalled.
This site is an independent guide and is not run by the Parrot project. Where exact release dates matter, follow the links to the archived release notes on this site, which carry the original announcement text, or check the official Parrot website.
How to check which Parrot Linux version you are running
Before reading about the history, confirm what you have in front of you. Parrot ships a standard os-release file, so these commands work on every edition:
cat /etc/os-release
lsb_release -a
uname -rThe first command prints the Parrot version and its codename. The second shows the Debian-compatible release information. The third prints the kernel version, which is useful because Parrot often ships a newer kernel than the Debian release it is based on.
You can also check the version of the metapackage that defines the system:
apt policy parrot-coreIf your version is older than the current 7.x line, read the guide on how to update and upgrade Parrot Linux safely before doing anything else.
Parrot Linux versions at a glance
| Release line | Debian base | Default desktop | Defining change |
|---|---|---|---|
| 1.x | Debian 7 era | MATE | First public images, security-focused live system |
| 2.x | Debian 8 era | MATE | Installer and persistence matured, AnonSurf became a core feature |
| 3.x | Debian testing (Stretch) | MATE | Move to a rolling Debian testing base, Home edition appears |
| 4.x | Debian testing (Buster/Bullseye) | MATE | Long rolling period, Docker images, Pi builds, many 4.x point releases |
| 5.x | Debian 11 (Bullseye) | MATE | Return to a stable Debian base, Architect and HTB editions |
| 6.x | Debian 12 (Bookworm) | MATE | Refreshed tooling, improved installer, Pi 5 support |
| 7.x | Debian 13 (Trixie) | KDE Plasma 6 | New default desktop, Linux 7.x kernel, codename Echo |
The table is a simplification. Parrot has used Debian testing snapshots at some points and frozen stable releases at others, so the exact package set for a given point release can only be confirmed from that release’s notes.
Parrot 1.x and 2.x: the early live-system years
The first Parrot images were built as a security-oriented live distribution with MATE as the desktop. The idea was a lightweight system that booted from USB, included a curated set of penetration-testing tools, and offered built-in anonymisation through Tor. The 1.x line established the identity that Parrot still has today: Debian underneath, a tool collection on top, and privacy utilities that are not an afterthought.
The 2.x line continued on the Debian 8 generation. This is where the installer became reliable enough for permanent installations rather than only live use, and where the project began splitting its audience into people who wanted a full security toolkit and people who simply wanted a hardened daily-driver desktop. Very little from this era is still relevant to a modern install; if you find a tutorial that mentions Parrot 2.x, treat the commands with suspicion because package names and repository layouts have changed several times since.
Parrot 3.x: moving to a rolling Debian testing base
With the 3.x series Parrot switched to tracking Debian testing, which at the time was the Stretch development branch. The 3.x point releases came frequently and introduced a lot of the structure you still see: separate Security and Home flavours, the first ARM builds, and the mirror network that the project still relies on. The archived notes for Parrot 3.5, Parrot 3.8 and Parrot 3.11 on this site show how quickly the desktop and tool set evolved during that period.
Two things from the 3.x era still trip people up today. First, the repository structure was reorganised more than once, so sources.list entries copied from a 3.x guide will not work on a modern system. Second, a few releases had upgrade problems that required manual intervention, which is why the project started recommending its own parrot-upgrade wrapper instead of a plain apt dist-upgrade.
Parrot 4.x: the long rolling period
The 4.x line is the longest-lived series in Parrot’s history. It started around the Debian Buster development cycle and kept rolling through the Bullseye cycle, with point releases from 4.0 all the way to 4.11. Because the base kept moving, a Parrot 4.3 system and a Parrot 4.11 system could be very different under the hood even though they shared a major version number.
Important additions during 4.x included:
- Official Docker images, so the tool set could be pulled into a container instead of a full install. See the Docker images for Parrot OS page.
- Raspberry Pi and other ARM builds becoming a regular part of each release.
- AppArmor and Firejail sandboxing enabled by default for many desktop applications.
- The 4.11 release, which was the last of the line and the one most people upgraded from when 5.0 arrived.
If you still have a 4.x install, do not try to upgrade it in place to 7.x. The jump spans three Debian generations and the supported path is a clean reinstall.
Parrot 5.x: back to a stable Debian base
Parrot 5.0 marked a deliberate change of philosophy. Instead of chasing Debian testing, the project rebased on Debian 11 Bullseye, a released stable version, and committed to a long-term-support style of maintenance for the 5.x line. The Parrot 5.0 press release on this site covers the reasoning; in short, security professionals wanted predictability more than bleeding-edge packages.
The 5.x era also introduced two editions that are still part of the line-up:
- The Architect edition, a minimal installer that lets you pick your desktop and tool set during setup. This site has a separate Architect edition install walkthrough.
- The Hack The Box edition, a build tuned for HTB labs and shipped in cooperation with that platform.
Point releases 5.1, 5.2 and 5.3 followed with kernel refreshes and tool updates. The 5.3 release notes describe the final state of the line before the 6.0 rebase.
Parrot 6.x: Debian 12 and a refreshed toolkit
Parrot 6.0 rebased the distribution on Debian 12 Bookworm. The visible changes were a newer MATE desktop, an updated installer, a cleaned-up tool menu and better out-of-the-box support for newer hardware, including the Raspberry Pi 5. Under the hood, the project also reorganised how it packages and signs its own repositories, which is why some third-party guides from the 5.x era produce GPG errors on 6.x.
The 6.x point releases, from 6.0 through 6.4, were mostly maintenance updates: kernel bumps, tool refreshes and fixes to the installer and to AnonSurf. If you installed Parrot in the 6.x era and have kept it updated, your system is one supported upgrade away from the current 7.x line.
Parrot 7.x: KDE Plasma, Debian 13 and the Echo codename
The 7.x series is the current generation. Parrot 7.0 "Echo" rebased on Debian 13 Trixie and made the biggest desktop change in the project’s history: KDE Plasma 6 replaced MATE as the default environment. MATE did not disappear; it is available as a spin alongside LXQt and Enlightenment, and this site compares them in Parrot Linux desktop environments compared.
The 7.x point releases have arrived at a steady pace:
- Parrot 7.1 and 7.2 stabilised the Plasma desktop and fixed early upgrade issues.
- Parrot 7.3 brought another round of tool and kernel updates.
- Parrot 7.4, released on 3 October 2026, is the current version at the time of writing. It ships a Linux 7.1 kernel on the Debian 13 base and is available in Home, Security, Cloud, Architect, Hack The Box and Raspberry Pi editions.
For a 7.x system, keeping up to date is simple: run sudo parrot-upgrade regularly and you will move from one point release to the next without reinstalling.
Which Parrot Linux version should you install today?
Unless you have a specific reason to run something older, install the current 7.4 image. Older ISOs are still mirrored, but their package repositories eventually stop receiving updates, and installing an old version only to upgrade it immediately wastes time and bandwidth. The Parrot Linux download guide explains which edition fits which use case, and Home vs Security edition goes deeper on that choice.
The one exception is hardware with an unsupported kernel. If a brand-new laptop refuses to boot the 7.4 kernel, it is usually better to wait for the next point release than to go back to a 6.x image whose drivers are even older.
Reading old tutorials across Parrot Linux versions
A lot of search results for Parrot problems date from the 3.x and 4.x eras. A few rules of thumb when you hit one:
- Ignore any
sources.listlines it tells you to add. Repository paths have changed; use the official mirror list on the mirrors network page instead. - Replace
apt-get upgradeorapt dist-upgradewithparrot-upgrade. - Menu paths that reference the MATE panel will not match the Plasma layout on 7.x.
- Tools that were removed from the default install can usually still be installed from the repository with
apt install.
FAQ: Parrot Linux versions
Does Parrot Linux use a rolling release model?
Not any more. The 3.x and 4.x lines followed Debian testing and rolled continuously. Since 5.0, each major version is tied to a stable Debian release and receives point releases on top. Within a major version, parrot-upgrade moves you forward; between major versions a reinstall is sometimes the cleaner option.
Can I upgrade directly from Parrot 5 or 6 to Parrot 7?
A 6.x system that is fully updated can usually be taken to 7.x with parrot-upgrade, but back up first and read the upgrade guide on this site. From 5.x or older, do a fresh install of 7.4.
How do I find the exact release date of an old version?
Open the archived release notes linked throughout this article. Each one preserves the original announcement, so the publication date on the post is the reliable reference rather than anything summarised here.