Bazzite editions, hardware support, updates, and rollback

Scope

Bazzite is a Fedora Atomic-based gaming distribution with desktop and controller-first image choices. This page is a selection gate; use the current Bazzite image picker for exact image names.

Image names, GPU paths, supported devices, branches, and rebase commands change. Never reuse an old rebase command without checking current Bazzite documentation and the target image.

Architecture and editions

ChoiceIntended sessionCore boundaryTypical fit
Desktop image
KDE/GNOME desktop
Does not imply Gaming Mode support
Desktop gaming and general use
Bazzite-Deck
Gamescope/Steam Gaming Mode first
Exact GPU and device must be supported
Handheld or living-room appliance
DX variant
Developer tooling layered on Bazzite
Not a separate handheld compatibility class
Development workstation

The image-based system uses Fedora Atomic deployment concepts. Applications commonly use Flatpak or containers; arbitrary host package layering is not the default operating model.

Hardware and GPU boundaries

Bazzite documents selected handhelds through its Handheld Wiki and uses Handheld Daemon (HHD) for controls and power integration on relevant non-Deck devices. The list is explicitly not proof that every booting device is supported. AMD, Intel, and NVIDIA images/sessions have different constraints; select by the current hardware guide.

Updates and rebasing

System updates create deployments. Rebasing changes the tracked image and can change desktop, GPU, or edition assumptions. Pin a known-good deployment before a risky change and record the deployment checksum.

Recommendation

Choose Bazzite-Deck for a named, supported handheld or compatible AMD couch system that needs controller-first Gaming Mode. Choose Bazzite Desktop for mixed desktop use or when the GPU/session is not supported by the Deck image. Stop if exact hardware, recovery access, or target image is uncertain.

Blockers

  • The exact handheld or GPU/session path is absent from current documentation.
  • Secure Boot, disk layout, encryption, dual boot, or firmware constraints are not understood.
  • Required controls, suspend, audio, HDR/VRR, docks, or update recovery are unverified.
  • The only recovery plan depends on the installed system still booting.

Verification

Before migration, record the exact image, branch, deployment checksum, hardware IDs, GPU driver path, firmware, session, HHD, controls, suspend cycles, update result, and a successful recovery-media boot.

Rollback

Use the currently documented deployment rollback path for an OS regression and keep a known-good deployment pinned when appropriate. Keep separate backups for user data. For a failed rebase or unbootable system, use tested external recovery media; reinstall only after preserving required data.

Frequently asked questions

Is Bazzite an unofficial SteamOS image?
Is Bazzite an unofficial SteamOS image?
No. Bazzite is its own Fedora Atomic-based Linux distribution. Bazzite-Deck provides a Steam Gaming Mode experience, but it is not Valve SteamOS.
Does image rollback also roll back personal data?
Does image rollback also roll back personal data?
Do not assume so. Deployment rollback changes the operating-system deployment; user data and application state need their own backup and restore plan.

Sources

Version history

  • 2026-07-15: Phase 4 publication with edition, hardware, rebase, blocker, and rollback gates.