Fedora is a free, community-developed Linux distribution sponsored by Red Hat, built on the RPM package format and the DNF package manager. In Linux fundamentals, it is known as a fast-moving, general-purpose distribution that ships recent upstream software on a roughly six-month release cycle and serves as the technical proving ground for Red Hat Enterprise Linux (RHEL).
Fedora began in 2003 as Fedora Core, when Red Hat split its free consumer product from its commercial enterprise line. It is governed by the Fedora Project, whose guiding principles of freedom, friends, features and first express a preference for free software and early adoption of new technology.
How Fedora is developed and released
Fedora follows a time-based release model: a new numbered version is targeted for each spring and autumn. Each release is supported until about four weeks after the release of the second following version, which gives roughly 13 months of updates. Users are therefore expected to upgrade about once a year, usually with an in-place system upgrade.
Development happens in Rawhide, the continuously updated development branch that receives new package versions first. Before each release, a branch is taken from Rawhide and stabilized through beta and release-candidate phases, with formal release criteria and blocker bug reviews deciding whether a version can ship.
Fedora is the upstream of CentOS Stream, which in turn is the upstream of RHEL. Features that mature in Fedora, such as a new compiler toolchain or a kernel subsystem, flow into enterprise releases years later. This position explains Fedora’s policy of staying close to upstream projects and avoiding heavy downstream patching.
Editions, spins and atomic variants
Fedora is published in several official editions aimed at different uses, plus community-maintained spins and labs. The table summarizes the main variants.
| Variant | Target use | Distinguishing trait |
|---|---|---|
| Workstation | Desktops and laptops | GNOME desktop with defaults kept close to upstream |
| Server | Traditional servers | Cockpit web console, minimal default installation |
| CoreOS | Container hosts and clusters | Automatic updates, image-based, provisioned with Ignition |
| IoT | Edge and embedded devices | Image-based system with rollback |
| Cloud | Virtual machines in public clouds | Cloud images with cloud-init |
| Spins | Alternative desktops | KDE Plasma, Xfce and other environments |
| Atomic desktops | Immutable desktop systems | Silverblue and Kinoite, built on rpm-ostree |
The atomic variants replace package-by-package updates with whole-system images that update atomically and can be rolled back at boot. Applications are installed mainly as Flatpak packages, and development tools run in Toolbx containers, which keeps the base system unchanged.
Technical defaults that define Fedora
Fedora often adopts new Linux technologies as default before most other distributions, which makes it a reference point for where the Linux desktop and server stack is heading.
| Area | Fedora default | Practical effect |
|---|---|---|
| Package management | RPM packages with DNF | Dependency resolution, history and rollback of transactions |
| Security | SELinux in enforcing mode | Mandatory access control for services out of the box |
| Filesystem | Btrfs on Workstation | Transparent compression, subvolumes and snapshots |
| Display | Wayland session | Modern graphics stack with better isolation |
| Audio | PipeWire | Unified audio and video stream handling |
| Init and services | systemd | Service management, logging through the journal |
| Firewall | firewalld | Zone-based firewall configuration |
Fedora also has a strict licensing policy: software in the main repositories must be free and open source. Codecs and drivers with patent or license restrictions, such as some proprietary graphics drivers, are obtained from third-party repositories, which is a frequent surprise for new users.
Fedora compared with other distributions
Fedora sits between long-term stable distributions and rolling releases. The comparison shows how it relates to its neighbors in Linux fundamentals.
| Distribution | Release model | Package system | Typical audience |
|---|---|---|---|
| Fedora | About every 6 months, 13-month support | RPM, DNF | Developers, enthusiasts, early adopters |
| RHEL | Major versions every few years, about 10-year support | RPM, DNF | Enterprises needing certified stability |
| Debian | Stable releases about every 2 years | DEB, APT | Conservative servers, derivative bases |
| Ubuntu | Every 6 months, LTS every 2 years | DEB, APT, Snap | Desktops, cloud images |
| Arch Linux | Rolling release | Pacman | Experienced users wanting full control |
Compared with Ubuntu, Fedora ships fewer proprietary components by default and keeps desktop software closer to upstream. Compared with Arch Linux, it offers tested point releases rather than continuous updates, which reduces the risk of breakage while still delivering recent versions.
Strengths, limitations and practical advice
Fedora suits users who want current kernels, compilers and desktop software in a polished, well-integrated system. Hardware support for new laptops and graphics chips is usually good because recent kernels arrive quickly.
- Short support window: production servers that cannot upgrade yearly are better served by RHEL-compatible or Debian-based systems.
- SELinux denials: disabling SELinux is a common but poor reaction; reading the denial and adjusting labels or booleans is the correct fix.
- Missing codecs: multimedia support often requires enabling a third-party repository.
- Skipping versions: upgrades are supported across at most two releases, so falling far behind complicates maintenance.
- Rawhide on daily systems: the development branch is meant for testing, not for primary workstations.
A sound routine is to apply updates weekly, read the release notes before each upgrade and keep a snapshot or backup of the home directory. On Btrfs installations, a snapshot taken before an upgrade allows a quick return to the previous state if a driver or application misbehaves. Administrators who need predictability can also wait a few weeks after a new release so that early bugs are fixed before they upgrade.
The simple explanation
Linux comes in many packaged versions, called distributions, each with its own style. Fedora is one of the best known. It is free, built by a large volunteer community with support from Red Hat, and it always offers fairly new software.
A useful comparison is a test kitchen for a restaurant chain. New recipes are tried and refined in Fedora first, and the best of them later appear in the chain’s more conservative business product. Fedora users get new ideas early, in exchange for upgrading about once a year.
How it is used in practice
A software developer working on container-based web services buys a new laptop with a recent processor and graphics chip. An older long-term-support distribution does not yet recognize the Wi-Fi adapter, while Fedora Workstation, with its recent kernel, supports every component after installation.
The developer uses DNF to install compilers and Podman, keeps SELinux in enforcing mode and works inside Toolbx containers for different project toolchains. Because the company deploys to RHEL servers, the same package tools and security model apply in development and production, which avoids surprises when software moves to the servers.
Once a year, the developer runs an in-place system upgrade that takes under an hour. The result is a workstation that stays current with very little maintenance and closely matches the enterprise target platform.