✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.

Most Linux updates are a one-way door: once the package manager finishes, the old system is gone, and a broken driver means an evening of repair work. Bazzite is built the other way round. Because the whole operating system ships as a single image, yesterday’s working system still exists on your disk after today’s update lands, and two operations — rollback and rebase — move you between system images without touching your games, saves or settings.

A companion article on this site explains immutable distros as a concept; this guide is the procedure that concept promises. It covers how deployments are stored, rolling back a bad update step by step, pinning a known-good deployment, and rebasing onto a different variant — deck, desktop, GNOME, KDE or NVIDIA — plus what survives each move.

As an Amazon Associate, we earn from qualifying purchases.

Quick answer

Rollback is Bazzite’s undo button for a bad update: reboot, pick the previous deployment in the boot menu, and your last working system returns with your games and files untouched. Rebase is the bigger move — it swaps your whole system image for another Bazzite variant, such as deck or NVIDIA, while keeping your home directory.

How Bazzite Deployments Work

Bazzite is an atomic, image-based system built on Fedora Atomic and managed by rpm-ostree: instead of updating packages in place, each update downloads a new system image and stages it as a separate deployment beside the current one. Your files are never part of that image: home directory, game libraries and variable system state live outside the read-only root, so swapping deployments never moves them.

At any moment your disk normally holds two deployments: the current one and the previous one. Both appear as entries in the boot menu, newest first. Booting the older entry is a complete return to that day’s system — kernel, drivers, desktop and all — because each deployment is a self-contained snapshot of the operating system rather than a pile of packages to unpick. Software installed with rpm-ostree layering sits on top of a deployment and is recorded per deployment, which matters for both operations below.

How to Roll Back a Bad Update

Rollback is the fix for the classic failure: an update lands, you reboot, and something is wrong — a black screen, a broken controller, a desktop that will not start — and the recovery takes one reboot.

  1. Restart the machine and open the boot menu. On most installs the GRUB menu appears briefly at startup; if yours stays hidden, Bazzite’s ujust tooling can set it to appear at every boot — worth enabling before you ever need it.
  2. Select the second entry, the previous deployment; entries are labelled with image and version, so you can confirm the older one.
  3. Boot it and check the fault is gone. If the system works, you are done for now: the machine keeps booting the deployment you chose.
  4. To make it permanent rather than a one-off boot choice, open a terminal in the rolled-back system and run rpm-ostree rollback. This swaps the deployment order so the older image becomes the default and the bad update is queued for removal.
  5. Wait before updating again: the faulty image went to every Bazzite user, a corrected build normally follows, and updating days later usually skips the broken release.

One limitation matters: Bazzite keeps only the current and previous deployments by default, so you can step back exactly one update unless you pin. If one deployment is the build you trust — say, the last one where your handheld’s sleep and controller behaviour were perfect — pin it while booted into it with the ostree admin pin command. A pinned deployment survives cleanup indefinitely and stays in the boot menu as a permanent escape hatch, at the cost of the disk space the image occupies.

How to Rebase to Another Bazzite Variant

Rebase is rollback’s bigger sibling: instead of stepping back to an older build of the same image, it swaps your system onto a different Bazzite image while keeping your home directory, and it is the supported way to change variants without reinstalling. The usual reasons are changing hardware — a drive moved into a machine with an NVIDIA card — or changing your mind about form factor, turning a desktop install into a deck-style living-room box.

  1. Check where you are. The rpm-ostree status command shows your current image name and version; note it down, because it is also your way back.
  2. Pick the target image by its name. The desktop image is called bazzite, the handheld and living-room image is bazzite-deck, GNOME editions add a gnome suffix, and NVIDIA cards use the nvidia images — the open kernel module build for GTX 16-series and RTX cards, or the standard NVIDIA build for older hardware. Match the desktop environment you already run.
  3. Run the rebase with the signed image reference: rpm-ostree rebase followed by the signed container image address for your target, which the Bazzite documentation lists for every variant. The new image downloads beside your current one, like a large update.
  4. Reboot and choose the new deployment, which is now the default. Your home directory, Steam library, Flatpaks and saves are exactly where you left them.
  5. Check your layered packages: they are re-applied on the new image, and if one cannot be satisfied there, the rebase reports it rather than breaking the system — removing that layer and re-running the command is the documented fix.

Two cautions from the project’s documentation deserve emphasis. Switching desktop environments by rebase works, but both desktops leave configuration in your home directory, and the mixture can produce odd theming and settings behaviour; the same-desktop switch is the clean path. And a rebase is not a backup: it protects the system image, not your data, so anything irreplaceable still deserves its own copy elsewhere.

What Survives a Rollback or Rebase

The short version: everything that is yours survives, and everything that is the system’s is replaced. Your home directory — documents, screenshots, shader caches and the save files stored inside it — is untouched by both operations, as are game libraries on separate drives or partitions and every Flatpak you installed.

The differences sit in the layered packages. A rollback returns you to that older deployment’s exact layer set, so a package layered yesterday is absent in last week’s image and returns when you boot forward again. A rebase carries your layer list onto the new image and re-applies it. In both cases nothing is silently deleted: layers are part of the deployment record, and the status command shows exactly what each deployment contains before you boot it.

Gear That Pairs With This Workflow

None of this needs new hardware, but the machines and drives below pair naturally with the workflow: handhelds that run deck images, and fast storage that shortens image downloads.

ASUS ROG Ally X

The Ally X is the most common handheld rebase target: owners move it from Windows to the Bazzite deck image, and its storage makes keeping a pinned fallback deployment painless.

  • Chip: AMD Ryzen Z1 Extreme
  • Memory: 24GB LPDDR5X
  • Storage: 1TB PCIe SSD
  • Display: 7-inch 1080p, 120Hz
  • Battery: 80Wh

Valve Steam Deck OLED 512GB

Valve Steam Deck OLED 512GB

Valve Steam Deck OLED 512GB

Check price on Amazon

Valve’s machine uses the same image-based update philosophy, and it is also a supported Bazzite deck-image device for owners who want wider variant and desktop choices.

  • Storage: 512GB NVMe SSD
  • Memory: 16GB LPDDR5
  • Display: 7.4-inch HDR OLED, up to 90Hz
  • System: SteamOS, with Bazzite deck images supported

Samsung 990 PRO 2TB NVMe SSD

A Bazzite image is a multi-gigabyte download; a fast Gen4 drive shortens updates and rebases, and 2TB leaves room for a large library beside a pinned deployment.

  • Capacity: 2TB
  • Interface: PCIe Gen4, M.2 2280
  • Maker-stated read speed: up to 7,450 MB/s
  • Model: MZ-V9P2T0B/AM

WD Black SN850X 2TB NVMe SSD

A second high-speed option, suited to a desktop build where one drive holds the system images and the Steam library together.

  • Capacity: 2TB
  • Interface: PCIe Gen4, M.2 2280
  • Maker-stated read speed: up to 7,300 MB/s
  • Model: WDS200T2X0E

SanDisk Extreme PRO USB 3.2 Flash Drive 128GB

If a machine ever needs a clean reinstall — the one failure rollback cannot fix — a fast USB stick holding the Bazzite installer is the recovery path, and this one’s maker-stated speeds keep image writing quick.

  • Capacity: 128GB
  • Interface: USB 3.2 solid-state flash drive
  • Maker-stated read speed: up to 420 MB/s
  • Model: SDCZ880-128G-GAM46

How to choose

Match the operation to the problem. If the system worked yesterday and broke after an update, roll back — it is faster than any repair and loses nothing. If the system works but is the wrong shape for the machine — a desktop image on a handheld, a non-NVIDIA image after a GPU swap — rebase to the matching variant. Experimenting? Pin your current deployment first, so the experiment always has a way home. And if both deployments show the same fault, the problem is not the image: suspect the hardware, the drive or your own configuration.

Who should skip this

Skip this guide if you run a traditional, mutable Linux distribution — nothing here applies, because there are no deployments to roll back to. Steam Deck owners happy on stock SteamOS can skip it too: Valve runs its own A/B image system with its own recovery route, and these commands are Bazzite-specific. And if the machine will not power on or the drive is failing, fix the hardware first — no image operation helps a disk that cannot be read.

FAQ

Does rolling back delete my games or saves?

No. Games, saves, Flatpaks and your home directory live outside the system deployments, so a rollback changes only the operating system. The exception is layered packages: a layer added after the older deployment is absent while you are booted into it.

How many old deployments does Bazzite keep?

Two by default: the current deployment and the one before it — exactly one step back. Pinning a deployment with the ostree admin pin command exempts it from cleanup, so a pinned known-good image stays in your boot menu as long as it stays pinned.

Can I rebase from KDE Plasma to GNOME?

Yes, but the Bazzite documentation treats desktop switches as the messy case: both environments keep settings in your home directory, and the leftovers can clash. Rebasing between variants that share your current desktop — desktop to deck, or to an NVIDIA image — is the clean, recommended path.

Will a rebase remove my layered packages?

No. Your layer list is carried over and re-applied onto the new image. If a layered package cannot be installed on the target image, the rebase stops with an error naming it rather than producing a broken system; remove that layer and run the rebase again.

Final verdict

Rollback and rebase are the practical half of Bazzite’s immutable design: rollback turns a bad update into a thirty-second detour through the boot menu, and rebase turns switching deck, desktop or NVIDIA variants into a download instead of a reinstall. Learn the boot menu and pin the deployment you trust, and the safety net stops being a marketing claim and becomes how you run the machine.

ASUS ROG Ally X (RC72LA)

ASUS ROG Ally X (RC72LA)

Check price on Amazon

Samsung 990 PRO 2TB NVMe SSD (MZ-V9P2T0B/AM)

Samsung 990 PRO 2TB NVMe SSD (MZ-V9P2T0B/AM)

Check price on Amazon

WD Black SN850X 2TB NVMe SSD (WDS200T2X0E)

WD Black SN850X 2TB NVMe SSD (WDS200T2X0E)

Check price on Amazon

SanDisk Extreme PRO USB 3.2 Flash Drive 128GB (SDCZ880-128G-GAM46)

SanDisk Extreme PRO USB 3.2 Flash Drive 128GB (SDCZ880-128G-GAM46)

Check price on Amazon

Explore Our Guides & Free Tools