Debian Versions: Release History, Codenames, and Support Dates

When choosing a Debian release or checking an older server, the version number alone does not tell you whether it still receives security updates. Debian also uses codenames such as Trixie and Bookworm, along with labels such as stable and testing.

This guide lists Debian versions, codenames, and release dates, explains the different release channels, and shows how long each recent version receives support.

Current Debian Releases #

As of October 21, 2026, the current stable version is Debian 13 “Trixie”. It was released on August 9, 2025. The latest point release is Debian 13.7, published on September 12, 2026, according to the Trixie release information .

The table below shows the support status of recent releases. The free support column includes LTS; paid ELTS is a separate service with more limited coverage.

Debian 14 “Forky” is the next release and is currently in testing. It has no announced release date. Debian 15 will be called “Duke”.

If you are running Debian 11 or older, the free security updates have ended. The upgrade guides for Debian 11 to 12 and Debian 12 to 13 walk through moving one release at a time.

Full Debian Release History #

The table below lists Debian releases from 1.1 Buzz onward, using the dates in Debian’s release index . These are the initial release dates, not the dates of later point updates:

Before Buzz, Debian shipped releases such as 0.91 in early 1994 and 0.93R5 and 0.93R6 in 1995, without the codenames used today.

A new stable release arrives roughly every two years. Debian does not commit to a fixed release date; the release team freezes testing and works through release-critical bugs before publishing the next version.

Debian Codenames #

Debian codenames come from characters in the Toy Story films. The tradition started in 1996 with Buzz. For example, Bookworm is the green toy worm, and Trixie is the blue triceratops. Debian explains the names in its archive FAQ .

You also use the codename in APT sources to select a release’s repositories. For example, a Debian 13 system using the traditional /etc/apt/sources.list format may contain this entry:

deb http://deb.debian.org/debian trixie main

Systems that use the newer deb822 format keep the same codename in a Suites: trixie line under /etc/apt/sources.list.d/.

Changing repository codenames is one part of a release upgrade. Follow the target release’s upgrade instructions rather than changing the name and running an upgrade without preparation.

One codename never moves: sid, named after the boy next door who breaks toys, is the permanent name of the unstable distribution.

Stable, Testing, and Unstable #

Debian keeps several suites at the same time. A codename belongs to one release, while a suite name points to whichever release currently holds that role:

• stable - The current officially released version, Trixie. This is the usual choice for servers and desktops.
• oldstable - The previous stable release, Bookworm. It is currently maintained by the LTS team.
• oldoldstable - The release before that, currently Bullseye.
• testing - The next release in progress, Forky. Packages move here from unstable after meeting migration requirements, including checks for bugs and dependencies.
• unstable - Always sid. New package uploads land here first.
• experimental - A staging area for packages that are not ready for unstable. It is not a full distribution.

The difference matters in your APT sources. When Debian publishes a new release, stable starts pointing to that release. The codename trixie continues to point to Debian 13.

Using a codename keeps your sources on the same release until you choose to change them. A source named stable can start offering packages from the next release, but it does not perform a complete release upgrade for you. APT may ask you to confirm changed release information, and you still need to follow the upgrade procedure.

How Long Debian Releases Are Supported #

Debian separates regular security support, LTS, and ELTS. They cover different periods and do not guarantee updates for every package or architecture.

Regular security support comes from the Debian security team. It usually lasts about three years. Debian 13 has regular support until August 9, 2028; Debian 12’s regular support ended on July 11, 2026.

Long Term Support (LTS) extends the release’s lifetime to about five years. A separate team takes over from the security team. Updates are free, but package and architecture coverage is more limited. The Debian LTS project explains how this maintenance is organized.

For example, Debian 12 LTS runs until June 30, 2028, and covers i386, amd64, armhf, arm64, and ppc64el. If your system already has the correct Debian security repository enabled, you continue installing updates through APT. You do not need a paid subscription for LTS.

Extended LTS (ELTS) is a paid service from Freexian that extends selected releases to around ten years of support. It covers packages needed by subscribers, uses a separate repository, and has its own architecture restrictions. Check Freexian’s ELTS information before relying on the dates in the table for a particular system.

Version Numbering #

Debian 5.0 and 6.0 had a decimal major version (6.0), and point releases added a third number (6.0.10). Earlier releases marked point releases with a revision suffix, such as 4.0r9. Starting with Debian 7, the major version is a single integer and point releases increment the second number: 7.1, 7.2, and so on.

Point releases are not separate distributions. Debian 13.0 and 13.7 are both Trixie. A point release collects security updates and important bug fixes into updated installation media and packages, as explained in the Debian 13.7 announcement .

You do not need to reinstall from a newer image to get those fixes. An existing Debian 13 installation receives them through normal package updates. The point-release number alone does not prove that every available security update is installed.

Check Your Debian Version #

If you are looking up support dates for an existing system, first read /etc/debian_version:

cat /etc/debian_version

13.7

This example shows Debian 13.7. Your output depends on the installed base-files package. On development releases, you may see a value such as forky/sid instead of a point-release number.

For the codename as well as the number, use /etc/os-release:

grep -E '^(VERSION|VERSION_CODENAME)=' /etc/os-release

VERSION="13 (trixie)"
VERSION_CODENAME=trixie

Here, VERSION gives the major release and codename, while VERSION_CODENAME gives the name used in APT sources. Other methods, including lsb_release and hostnamectl, are covered in how to check your Debian version .

Conclusion #

When planning an upgrade, check both the release’s support deadline and the coverage for your packages and architecture. If you are choosing between distributions for a new system, see our Debian vs Ubuntu comparison .

About the authors

Dejan Panovski

Dejan Panovski is the founder of Linuxize, an RHCSA-certified Linux system administrator and DevOps engineer based in Skopje, Macedonia. Author of 1000+ Linux tutorials with 20+ years of experience turning complex Linux tasks into clear, reliable guides.

View author page