Fedora Linux receives a new major release approximately every six months. A major-release upgrade allows you to move from one Fedora version to the next without reinstalling the operating system from scratch.
For example, a system running Fedora 43 can be upgraded to Fedora 44 using Fedora’s built-in system-upgrade mechanism.
This guide explains how to upgrade Fedora from the command line using DNF System Upgrade.
The procedure is intended for standard Fedora Linux installations using DNF, such as Fedora Workstation and Fedora Server. Fedora Atomic desktops such as Silverblue and Kinoite use rpm-ostree and follow a different upgrade procedure.
Current example: Fedora Linux 44 was released on April 28, 2026. The release number in the commands below should be changed to the Fedora version you actually want to install.
Before You Upgrade
A Fedora system upgrade changes a large portion of the operating system. Although Fedora’s upgrade mechanism is designed to perform the process safely, back up important data before starting.
At minimum, make sure that important documents, photographs, configuration files and other irreplaceable data are backed up.
It is also a good idea to make sure you have:
- A stable Internet connection
- Sufficient free disk space
- A working power supply, particularly on laptops
- A current backup
- A recovery option such as a Fedora Workstation Live USB
Fedora’s documentation specifically recommends backing up important data before a system-wide upgrade because every major system change carries some risk.
Check Your Current Fedora Version
Before starting, check which Fedora release you are currently running:
cat /etc/fedora-release
You can also use:
rpm -E %fedora
For example, you may see:
Fedora release 43 (Forty Three)
The number is the important part.
If you are running Fedora 43 and want Fedora 44, the target release is:
44
Step 1: Fully Update Your Current Fedora Installation
Before performing a major-release upgrade, bring your current Fedora installation completely up to date.
Run:
sudo dnf upgrade --refresh
This refreshes repository metadata and installs the latest available packages for your current Fedora release.
Fedora’s upgrade documentation specifically recommends updating the existing system before beginning the release upgrade.
After the update completes, reboot the system:
sudo reboot
Rebooting is particularly advisable if the update installed a new kernel or other core system components.
Step 2: Check That DNF System Upgrade Is Available
The traditional Fedora procedure required installing:
dnf-plugin-system-upgrade
That distinction has changed with modern Fedora releases.
DNF5 includes the system-upgrade functionality directly, so a separate system-upgrade plugin is generally no longer required on current Fedora systems. Fedora documentation notes that dnf system-upgrade is embedded into DNF5, while the separate dnf-plugin-system-upgrade package applies to DNF4.
Check that the command is available:
dnf system-upgrade --help
You should see commands such as:
download
reboot
clean
log
status
Fedora 44’s DNF5 package includes the system-upgrade functionality.
What About Older Fedora Versions?
If you are following this tutorial on an older Fedora installation that still uses DNF4, you may need to install the traditional plugin:
sudo dnf install dnf-plugin-system-upgrade
You can then use the same dnf system-upgrade workflow.
This is why older Fedora tutorials often contain a separate plugin-installation step.
Step 3: Download the Packages for the New Fedora Release
This is the main preparation step.
For example, to upgrade to Fedora 44:
sudo dnf system-upgrade download --refresh --releasever=44
Replace 44 with the target Fedora release.
For example:
sudo dnf system-upgrade download --refresh --releasever=43
would prepare an upgrade to Fedora 43.
The --releasever parameter tells DNF which Fedora release you want to upgrade to.
Fedora’s current documentation continues to use this command for major-version upgrades.
What Does This Command Do?
The command does not immediately replace your running operating system.
Instead, it:
- Refreshes the repository metadata.
- Resolves the packages required for the new Fedora release.
- Checks dependencies.
- Downloads the packages.
- Prepares the upgrade transaction for the offline upgrade stage.
The actual system-wide package replacement happens after the subsequent reboot.
What Is --refresh?
The --refresh option tells DNF to obtain fresh repository metadata before resolving the upgrade.
This is useful for a release upgrade because you want DNF to work with current repository information rather than stale metadata.
The command therefore becomes:
sudo dnf system-upgrade download --refresh --releasever=44
What If DNF Reports Dependency Problems?
Sometimes DNF cannot resolve the upgrade because of packages that conflict with packages in the new Fedora release.
In that situation, the upgrade command may report that it cannot complete the transaction.
A commonly used option is:
--allowerasing
For example:
sudo dnf system-upgrade download --refresh --releasever=44 --allowerasing
This permits DNF to remove packages when necessary to resolve the upgrade transaction.
Fedora’s documentation and longstanding upgrade guidance describe --allowerasing as a way to deal with packages that prevent dependency resolution.
Should You Always Use --allowerasing?
No.
Do not automatically add --allowerasing simply because it appears in an older tutorial.
First try the normal command:
sudo dnf system-upgrade download --refresh --releasever=44
If DNF reports dependency conflicts that require packages to be removed, read the proposed transaction carefully.
Then decide whether:
--allowerasing
is appropriate.
The option can remove packages that are blocking the upgrade, which is useful, but it should not be treated as a harmless switch.
What About Packages That Are Not Available in the New Release?
This is another area where older Fedora tutorials can be misleading.
A package installed on your current Fedora release may have been:
- Renamed
- Replaced
- Merged into another package
- Removed from Fedora
- Dropped because its upstream project was discontinued
- No longer maintained for the new Fedora release
If DNF reports that a package is unavailable or obsolete, that does not automatically mean that the upgrade has failed.
Read the transaction carefully.
In some cases, the correct solution is simply to allow the obsolete package to be removed.
In other cases, especially with manually installed or third-party software, you may need to investigate the package separately.
Third-Party Repositories Can Cause Problems
One of the most common causes of Fedora upgrade problems is software installed from third-party repositories.
Examples include:
- RPM Fusion
- COPR repositories
- Vendor-specific repositories
- Manually configured package repositories
- Proprietary software repositories
These repositories are not controlled by the Fedora Project.
A repository that works perfectly on Fedora 43 may not yet provide compatible packages for Fedora 44.
This can result in dependency conflicts.
Fedora’s upgrade guidance specifically warns that third-party repositories may need to be disabled when they interfere with the release upgrade.
Before using --allowerasing, look carefully at the packages that DNF says are causing the problem.
Do not blindly remove important applications merely to force the transaction to complete.
Fedora GPG Keys and Repository Verification
During the download process, DNF may ask you to import or confirm repository signing keys.
For example, you may see a prompt asking whether you want to import a Fedora or repository GPG key.
Do not simply approve every key prompt without reading it.
For Fedora’s official repositories, verify that the key is the expected Fedora signing key.
For third-party repositories, verify the key with the repository provider before accepting it.
Repository signing keys are part of Fedora’s package-security model, so they should be treated as security-sensitive information.
Step 4: Reboot Into the Fedora Upgrade
After the download transaction finishes successfully, start the offline upgrade:
sudo dnf system-upgrade reboot
Fedora will reboot and enter the system-upgrade environment.
The previously downloaded packages will then be installed.
The computer may reboot again when the process is finished.
Fedora’s documented procedure uses this same dnf system-upgrade reboot command.
What Happens During the Reboot?
The important thing to understand is that the upgrade is not performed while you continue using your normal desktop session.
The system first prepares the transaction while Fedora is running normally.
You then reboot.
During the upgrade reboot, Fedora enters a special offline/system-update environment and installs the downloaded packages before starting the upgraded operating system.
Therefore, do not interrupt the computer during this stage.
Do not switch it off simply because the screen appears unchanged for several minutes.
Large upgrades can take a while depending on:
- Number of installed packages
- CPU speed
- Storage performance
- Number of repositories
- Amount of data downloaded
- Disk encryption
- Hardware configuration
This is a good time to step away from the computer and have a coffee.
Step 5: Verify the New Fedora Version
Once the upgrade has completed and you are back at the desktop, verify the Fedora version:
cat /etc/fedora-release
You should now see something similar to:
Fedora release 44 (Forty Four)
You can also run:
rpm -E %fedora
which should return:
44
Finally, make sure the system is fully updated:
sudo dnf upgrade --refresh
Step 6: Check for Problems After the Upgrade
Most users can simply start using their upgraded Fedora installation.
Nevertheless, it is worth checking a few basic things.
Test:
- Network connectivity
- Wi-Fi
- Bluetooth
- Sound
- Graphics
- Printers and scanners
- External drives
- Important applications
If you use development tools, databases, virtual machines or other server software, check those services as well.
You can look for failed system services with:
systemctl --failed
Ideally, this should report:
0 loaded units listed.
You can also examine the system journal for errors if something appears to be malfunctioning.
What If the Upgrade Fails?
Do not immediately attempt to start over with a second upgrade.
First determine where the failure occurred.
The system-upgrade plugin provides log-related commands, including:
sudo dnf system-upgrade log
and:
sudo dnf system-upgrade status
The available commands depend on your DNF version, but current Fedora DNF5 provides system-upgrade status and log functionality.
If the problem involves a third-party repository, temporarily disabling that repository may allow the transaction to resolve.
If the downloaded transaction needs to be discarded, the system-upgrade functionality also provides:
sudo dnf system-upgrade clean
This removes the stored system-upgrade transaction so that you can prepare the upgrade again.
What If the System Will Not Boot?
If a major upgrade results in a boot problem, use your Fedora recovery options rather than repeatedly rebooting and changing packages blindly.
A Fedora Workstation Live USB can provide a useful recovery environment.
It can be used to:
- Inspect the filesystem
- Access important files
- Examine logs
- Repair configuration problems
- Back up data
- Investigate the failed installation
This is one reason Fedora recommends preparing recovery media before major system upgrades.
Do Not Use This Method for Fedora Silverblue or Kinoite
This guide is for conventional Fedora installations using DNF.
It is not the appropriate procedure for Fedora’s image-based Atomic desktops, including:
- Fedora Silverblue
- Fedora Kinoite
- Fedora Sway Atomic
- Fedora Budgie Atomic
- Other Fedora Atomic variants
These systems use rpm-ostree and have a different upgrade mechanism.
For example, Silverblue uses commands such as:
rpm-ostree upgrade
and release rebasing through rpm-ostree. Fedora’s documentation specifically distinguishes rpm-ostree-based systems from the DNF system-upgrade method.
If you are running an Atomic Fedora edition, follow the documentation for that edition instead.
Can You Skip Fedora Releases?
It is generally best to upgrade Fedora one major release at a time rather than attempting to jump across several unsupported releases.
For example:
Fedora 42 → Fedora 43 → Fedora 44
is preferable to trying to jump directly from a much older release to Fedora 44.
In particular, if your installation is several releases behind, first check the Fedora release lifecycle and supported upgrade paths before proceeding.
An extremely old installation may be better served by a fresh installation after backing up your data.
Graphical Upgrade Using GNOME Software
Fedora Workstation users can also use the graphical GNOME Software application when a new Fedora release is offered.
Fedora’s release announcement notes that an existing system can be upgraded through GNOME Software or through the terminal using dnf system-upgrade.
The graphical method is easier for users who do not want to use the terminal.
The terminal method remains valuable because it provides more visible information about dependency resolution, repositories and errors.
For troubleshooting, command-line output can be especially useful.
Complete Command-Line Procedure
For a current Fedora system using DNF5, the basic procedure is:
1. Update the current system
sudo dnf upgrade --refresh
2. Reboot
sudo reboot
3. Download the new Fedora release
For Fedora 44:
sudo dnf system-upgrade download --refresh --releasever=44
If DNF reports dependency conflicts that require packages to be removed:
sudo dnf system-upgrade download --refresh --releasever=44 --allowerasing
4. Reboot into the upgrade
sudo dnf system-upgrade reboot
5. Verify the installation
cat /etc/fedora-release
6. Apply any remaining updates
sudo dnf upgrade --refresh
That is the complete basic workflow.
Why Older Fedora Upgrade Tutorials Look Different
If you have followed older Fedora tutorials, you may notice commands such as:
sudo dnf install dnf-plugin-system-upgrade
This is not necessarily wrong—it reflects the older DNF4 implementation.
Modern Fedora uses DNF5, where system-upgrade functionality is integrated into DNF itself. Fedora’s documentation explicitly describes dnf system-upgrade as embedded in DNF5, while the separate dnf-plugin-system-upgrade package applies to DNF4.
This means that a current tutorial should not blindly copy a Fedora 33-era procedure.
The underlying upgrade concept remains similar, but the package-management implementation has evolved.
Frequently Asked Questions
Will upgrading Fedora delete my personal files?
A normal DNF system upgrade is intended to upgrade the operating system without deleting your personal files.
Nevertheless, always maintain a backup before performing a major-release upgrade.
Do I have to reinstall Fedora?
No.
The DNF system-upgrade mechanism is specifically designed to upgrade an existing Fedora installation to a new major release without performing a clean installation.
How long does a Fedora upgrade take?
There is no single fixed duration.
The download and installation time depends on your Internet connection, storage, hardware and the number of packages installed.
The preparation stage can be performed while you continue using the system, but the final offline installation requires a reboot.
Should I use --allowerasing?
Only when dependency resolution requires it.
Try the upgrade without it first.
If DNF identifies packages preventing the transaction and proposes removing them, inspect the proposed changes before accepting --allowerasing.
What happens to third-party applications?
That depends on how they are packaged.
Software from repositories that support the new Fedora release may continue to work normally.
Software from repositories that have not yet been updated may cause dependency conflicts or may require reinstallation after the upgrade.
Can I upgrade from Fedora 43 to Fedora 44?
Yes. Fedora 44 is the current stable Fedora release as of this guide’s 2026 update.
The command is:
sudo dnf system-upgrade download --refresh --releasever=44
Is the dnf-plugin-system-upgrade package still needed?
On current DNF5-based Fedora installations, generally no. System upgrade is integrated into DNF5.
It remains relevant for systems still using DNF4.
Conclusion
Upgrading Fedora to a new major release does not normally require a complete reinstallation.
For a conventional Fedora installation, the process is:
sudo dnf upgrade --refresh
sudo reboot
sudo dnf system-upgrade download --refresh --releasever=44
sudo dnf system-upgrade reboot
After the reboot and upgrade process completes, verify the installed version:
cat /etc/fedora-release
and update once more:
sudo dnf upgrade --refresh
The most important precautions are to back up important data, keep the existing Fedora installation fully updated, pay attention to third-party repositories, and read dependency-removal proposals before using --allowerasing.
The older Fedora 33-era procedure remains recognizable, but modern Fedora has moved from the separate DNF4 upgrade plugin to DNF5’s integrated system-upgrade functionality.
For Fedora 44, released April 28, 2026, the DNF system-upgrade method remains an officially supported way to upgrade an existing Fedora installation.
Official References
Fedora Linux 44 release announcement
https://fedoramagazine.org/announcing-fedora-linux-44/
Fedora DNF system upgrade documentation
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/
DNF system-upgrade documentation
https://dnf-plugins-core.readthedocs.io/en/latest/system-upgrade.html
Fedora Workstation 44 changes
https://fedoramagazine.org/whats-new-fedora-workstation-44/
Fedora Project — DNF System Upgrade
https://fedoraproject.org/wiki/DNF_system_upgrade