Bazzite is a free, image-based Linux distribution built on Fedora Atomic that boots straight into a console-style gaming setup, and it is one of the easiest ways to move a gaming PC or handheld to Linux. It ships with Steam, GPU drivers, controller support, and a gaming-focused kernel already configured, and you can roll back a bad update from the boot menu. It is the right pick if you want Linux to behave like an appliance; it is the wrong pick if you plan to tinker with system packages every weekend.
Quick answer: Bazzite is a free Linux gaming operating system that you install from a downloadable image matched to your hardware, then manage mostly through Steam, Flatpak apps and automatic background updates. Pick the desktop, NVIDIA or handheld image first, install it on a drive you have backed up, and use Steam as your main launcher.
- Bazzite is published as several images, so the desktop, NVIDIA or handheld choice happens before you download.
- You can move between images later with a rebase command instead of reinstalling.
- Flatpak is the first choice for graphical apps; Distrobox covers command-line and developer tools.
- Format game drives as ext4 or Btrfs rather than NTFS to avoid Proton permission problems.
- Secure Boot can stay on if you enroll the project’s key when the firmware prompts you.
What “image-based” actually means for a gaming PC
Most desktop distros install thousands of loose packages into a writable system. Bazzite instead delivers the operating system as a single versioned image, in the same family as Fedora Silverblue and Kinoite. The root filesystem is read-only during normal use, and an update downloads a complete new image that becomes active on the next reboot. The previous image stays on disk as a fallback.
That design explains almost everything about how Bazzite feels:
- Updates are all-or-nothing. You either boot the new image or the old one, so a half-finished update cannot leave you with a broken graphics stack.
- Rollback is built in. The project documents rolling back to the previous deployment, or rebasing to an earlier Bazzite build from within roughly the last 90 days, without touching your personal files or game libraries.
- Apps live outside the base system. Desktop apps come from Flatpak, command-line tools can run in Distrobox containers, and games stay in your home directory or on a separate drive.
Which Bazzite image to download
Bazzite is published as several images rather than one ISO that does everything. Picking the wrong one is the most common first-day mistake, so match it to your hardware before downloading.
| Your hardware | Image to choose | Why |
|---|---|---|
| Desktop or laptop with an AMD or Intel GPU | Desktop image (KDE Plasma or GNOME) | Open-source Mesa drivers are part of the base image; nothing extra to load |
| Desktop or laptop with a GeForce GPU | NVIDIA desktop image | The proprietary driver is baked in and signed, so it works after install without compiling modules |
| Steam Deck, ROG Ally, Legion Go and similar handhelds | Deck image | Boots into a Steam Gaming Mode session with handheld-specific tweaks |
| Living-room PC driven by a controller | Deck/HTPC image | Same console-style boot, with no desktop needed to launch games |
| Developer who also games | Developer (DX) edition | Adds container and coding tools on top of the gaming base |
If you pick a desktop image and later want the console-style session, or the reverse, you can rebase to a different image with a single command rather than reinstalling. Your home directory carries over.
Console mode versus desktop mode
On the Deck-style images the machine boots into Steam’s full-screen interface running in a Gamescope session, the same compositor approach Valve uses on its own handheld. You launch games with a controller, adjust frame limits and scaling from a quick menu, and suspend like a console. A “Switch to Desktop” entry in the power menu drops you into a normal Plasma desktop for browsers, file management, and setup chores.
On a plain desktop image you boot to the desktop, but Steam, Lutris, and Heroic are available as launchers, and Steam’s Big Picture mode still works with a controller. Bazzite also bundles handheld support for ASUS, Lenovo, GPD, OneXPlayer, Ayn, and Ayaneo devices, including tools for button mapping and power profiles.
Installing it without regretting it
- Back up first. The installer can wipe the target disk, and a mistaken partition choice is permanent.
- Use a separate drive for Linux when you can. Windows updates are known to rewrite boot entries, and keeping each system on its own drive means one cannot damage the other’s bootloader.
- Disable Windows Fast Startup and BitLocker if dual booting. Fast Startup leaves NTFS partitions in a hibernated state that Linux will refuse to mount read-write, and BitLocker keys can trigger recovery prompts when firmware settings change.
- Flash the ISO to a USB stick with a tool that verifies the write. Corrupted installer media produces confusing mid-install errors that look like hardware faults.
- Decide on Secure Boot before you install. Bazzite supports Secure Boot through its own key, which you enroll once through the firmware’s key-management prompt. If you skip it, leave Secure Boot off and be aware that some games with strict anti-cheat will not run on Linux either way.
- Format game drives as ext4 or Btrfs, not NTFS. Proton stores Windows-style prefixes with permissions and symbolic links that NTFS handles poorly, which is a classic source of games that refuse to launch.
Updates, layering, and the habit that causes trouble
Bazzite checks for updates automatically and applies them in the background; the new image takes effect after a reboot. Flatpaks update on their own schedule. This is hands-off by design, but there is one behavior worth knowing: you can “layer” an extra system package onto the image. Layered packages are reapplied on every update, which slows updates and can block them entirely if a layered package conflicts with a new base image.
A sound order of preference when you need software:
- Flatpak for graphical apps.
- A Distrobox container for developer tools and anything that expects a traditional distro.
- The built-in ujust helper commands for common setup tasks such as extra tweaks and optional components.
- Layering a package only as a last resort, and removing it when you no longer need it.
Common failure modes and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Black screen or software rendering on a GeForce card | Installed the non-NVIDIA image | Rebase to the NVIDIA image of the same desktop |
| Game library on a second drive fails to launch games | Drive formatted as NTFS, or mounted without proper permissions | Reformat to ext4 or Btrfs and set the Steam library folder again |
| Update will not apply | A layered package conflicts with the new image | Remove the layered package, then update again |
| Boots to the wrong operating system after a Windows update | Windows rewrote the boot order | Reset the boot order in firmware, or boot Linux from the firmware menu |
| New image misbehaves after an update | Regression in the new build | Pick the previous deployment from the boot menu, or roll back from the terminal |
| Multiplayer game refuses to start | Anti-cheat not enabled for Linux | Check the game’s anti-cheat status before blaming the distro; Bazzite cannot change it |
Who should choose something else
Bazzite trades flexibility for stability. If you want to compile your own kernel, run an unusual desktop environment, or tweak system files directly, a traditional distribution such as Fedora Workstation, Arch-based options, or a gaming-tuned rolling distro will suit you better. If you only care about a handheld that behaves exactly like Valve’s own and you have a Steam Deck, SteamOS is the reference experience, while Bazzite is the alternative that extends the same idea to many other devices and to desktop PCs.
The remaining limit is not Bazzite’s: some competitive games block Linux with kernel-level anti-cheat, and no distribution can work around that. Check the games you care about first, then choose the operating system.
How do you set up Bazzite for gaming after installing it?
The first hour decides whether Bazzite feels like an appliance or a project. Work through this order and change one thing at a time.
- Finish updates first. Let the first update download and reboot before changing anything, so later problems are not blamed on a half-applied image.
- Confirm the graphics driver. Open the system information page and check that your actual GPU is listed, not a software renderer. A wrong-image mistake shows up here immediately.
- Launch two games. Try one native Linux title and one Proton title. If both run, your base setup is sound; if only one fails, the problem is that game, not the system.
- Add your game drive. Point Steam at the library folder and verify a game starts from it.
- Check the controller in both modes. On handheld or living-room images, test buttons and any back paddles in Gaming Mode and on the desktop.
- Set display options. Confirm resolution, refresh rate and scaling on your actual screen or TV before tuning frame limits.
- Try suspend and resume. On handhelds and living-room machines, make sure waking from sleep works before you rely on it.
Common mistakes are layering packages on day one, changing several settings at once, and skipping reboots after updates. Note each change you make so you can undo it if something breaks.
More quick answers
What should I do when one game will not launch? Start by changing the compatibility tool for that game in its Steam properties and trying another Proton version, since a newer or older release often fixes a single title. Then look for community reports about launch options that game needs. If it still fails, confirm its anti-cheat supports Linux before changing any system settings.
How do I add Epic, GOG or other non-Steam games? Install a launcher such as Heroic or Lutris as a Flatpak from the included app store, sign in, and install your games there. To start them from Gaming Mode, add the launcher or game to your Steam library as a non-Steam game. Confirm the launcher’s current setup notes, because options can change between releases.
What is ujust and when should I use it? ujust is a helper command that runs maintained setup recipes included with Bazzite, such as optional tweaks and extra components. Type ujust on its own in a terminal to see what your image offers, and read each recipe’s description before running it. Prefer these recipes over hand-editing system files, because they are built to work with the read-only base.
Will my Steam games and saves survive a reinstall? Games kept in a separate library on an ext4 or Btrfs drive can usually be added back in Steam after a reinstall, and Steam Cloud saves return when you sign in. Local-only saves live in your home directory, so back that up first. Confirm each game’s cloud sync before you wipe anything.
Frequently Asked Questions
Is Bazzite good for beginners?
Yes, because the defaults are already tuned for gaming and a bad update can be undone from the boot menu. The learning curve appears when you want to install system-level software, since the read-only base pushes you toward Flatpak and containers. Beginners who stay within those tools rarely run into trouble.
Can I dual boot Bazzite with Windows?
You can, and the safest approach is installing each system on its own drive so neither can overwrite the other’s bootloader. Turn off Windows Fast Startup first, and keep shared game storage on a filesystem Linux handles well rather than NTFS.
Does Bazzite work with NVIDIA graphics cards?
Yes. Bazzite offers dedicated NVIDIA images with the proprietary driver included, so you do not need to compile anything after installing. Choose that image at download time, and check whether your GPU generation is still covered by current drivers, since very old cards use an older driver branch.
Will Bazzite run every Windows game?
No. Most single-player titles run through Proton, but games that depend on kernel-level anti-cheat usually will not. Check the anti-cheat status and community compatibility reports for each game you care about before switching.
How do I undo a bad update?
Restart and choose the previous deployment from the boot menu, or roll back from the terminal. Because the previous image is kept on disk, your files and settings stay untouched while you wait for a fixed build.






