Debian GNU/Linux is an operating system assembled and maintained by a community, with a package system that connects installation, updates, and long-term administration. A good Debian installation begins with a supported release, compatible hardware, and a recovery plan you understand.
As checked on September 5, 2026, Debian’s stable release is Debian 13, trixie. Use the Debian release overview to confirm the current release before downloading. Point releases refresh installation media; an existing installation normally receives their package changes through its configured repositories.
Choose a release according to the work
For a first installation or a machine with an important daily job, stable is a sensible starting point. “Stable” describes a release and change policy; it does not promise that every application is the newest upstream version or that every workload is trouble-free.
On a small screen, scroll the table sideways to read all columns.
| Choice | Typical reason to choose it | Responsibility to understand |
|---|---|---|
| Stable | A supported, officially released system with a relatively predictable package base. | Track security updates, support coverage, and the eventual next-release upgrade. |
| Testing | Help test the next stable release or work with newer packages. | Be prepared for package transitions and a different security-update situation. |
| Unstable (sid) | Participate close to active Debian development. | Investigate breakage and follow development notices; this is not a routine shortcut to a newer desktop. |
Debian’s security FAQ explains why testing does not receive the same timely security handling as stable. Check coverage for important packages and architectures rather than inferring it from a distribution’s overall support dates. Mixing stable, testing, and third-party repositories to obtain one package can change far more of the system than expected.
Check the whole machine before choosing an image
Identify the CPU architecture and exact hardware model. The amd64 image serves supported 64-bit x86 PCs, including many Intel systems; the name does not mean AMD-only. ARM devices need the appropriate architecture and a supported boot path. Use the matching Debian installation manual for architecture-specific instructions.
Check networking, graphics, storage controllers, docks, audio, and suspend/resume. A successful boot is only the first test of a laptop. Some devices need firmware packages, and very new hardware may need support beyond what your chosen installation image contains. Have a working network alternative or the required firmware available before relying on a wireless-only installation.
Copy important files to independent storage and open several restored files to verify the copy. Record the existing disk layout and boot mode, and keep recovery credentials for any encrypted operating system you intend to retain. A backup on another partition of the same drive does not protect against erasing that drive.
For a first experiment, a virtual machine avoids repartitioning the everyday computer. It teaches package and service administration, though it cannot validate the real machine’s wireless adapter, battery behavior, or graphics compatibility.
Choose media and make the disk decision deliberately
A network-install image downloads much of the chosen software during installation; plan for a reliable connection. A live image is useful for trying a desktop before committing. Neither approach removes the need to verify that the image is authentic. Debian’s image-verification instructions distinguish checking a downloaded file’s checksum from authenticating the signed checksum list. A matching hash from an untrusted source is not proof of origin.
Write the image to the intended removable device using the installation guide’s procedure. Confirm the destination by its size and model, because writing an image replaces that device’s existing contents. Boot in the mode you intend to use, then review the installer’s proposed changes before committing them.
Fictional installation choice: a dedicated learning laptop can use a simple guided layout on its selected internal drive after its files are backed up. A machine that must retain another operating system needs a separate space and boot plan. The two situations should not use the same “erase disk” instructions.
Encryption protects stored data under defined conditions, especially when a device is powered off. Plan how the machine will be unlocked and how recovery material will be kept. It does not replace backups or prevent an already-unlocked application from reading data it is allowed to access. Select only the desktop and services you need initially; additional packages can be added later.
Learn what is installed and review changes
These read-only commands answer three different questions. The distribution release, running kernel, and package architecture are related but distinct.
cat /etc/os-release
uname -r
dpkg --print-architectureUse the distribution’s package tools for software supplied by Debian. Refresh package information, read the proposed upgrade, and investigate unexpected removals before accepting changes. Record third-party repositories and their purpose. Software installed outside the package system needs its own update and provenance plan.
Schedule security updates, reboots when needed, and checks that important services still work. Automatic updates can reduce delay, but they do not remove the need to monitor failures, disk space, or restart requirements. Keep enough free storage for package downloads and system maintenance. Investigate growing logs before a full filesystem becomes an outage.
Download a Debian installation and maintenance checklist (plain text). It records the release, hardware checks, backup verification, disk choice, and post-install tests.
Treat a release upgrade as a planned change
Read the Debian 13 upgrade instructions before moving from Debian 12. They address preparation, package state, repository changes, and the upgrade sequence. Do not apply instructions for one release transition to a much older installation without checking the supported path.
Test a representative copy when practical, back up configuration and application data, and ensure you have a console or recovery route if networking stops. Keep a record of package sources and services. A package downgrade is not a general rollback plan: configuration formats and application data may already have changed. Verify login, networking, storage mounts, application behavior, and backups after the upgrade before calling it complete.