RetroDECK data and lifecycle

Scope

RetroDECK is a self-contained Flatpak integrating emulators, engines, ports, and management tools. Device support and component versions must be checked in current RetroDECK documentation.

Trust boundary

The Flatpak packages many upstream components inside one managed environment and accesses user-selected ROM, BIOS, save, screenshot, and removable-storage paths. Each included component still carries its own behavior and licensing requirements.

Supported installation

Install net.retrodeck.retrodeck through Discover/Flathub. Review supported devices, choose the data directory deliberately, and begin with one platform. Provide only legally obtained ROM/BIOS content.

Verification

Record RetroDECK/Flatpak version, device, data path, component/core, controller mapping, display mode, and test title. Verify launch and exit inside RetroDECK before adding external Steam integration.

Update

Update through Discover/Flatpak and read RetroDECK migration notes. Back up saves, states, and configuration before component or directory migrations; test a representative title after each major update.

Uninstall

Inventory the RetroDECK data tree, ROMs, BIOS, saves, states, screenshots, and Steam entries. Uninstall the Flatpak without data deletion first; remove data only after comparing the backup.

Rollback

Restore the recorded data/configuration tree or previous supported Flatpak commit through an appropriate Flatpak workflow, then verify the original test title. Do not mix rollback with save-format conversion.

Recommended use

Use RetroDECK when a self-contained, centrally updated emulation environment is preferable to separately managed emulators. Use EmuDeck when its orchestration and Steam-library workflow better fit your maintenance model.

Frequently asked questions

How is RetroDECK different from EmuDeck?
How is RetroDECK different from EmuDeck?
RetroDECK distributes a managed self-contained Flatpak environment, while EmuDeck orchestrates separately installed components. Their data and update boundaries differ.
Does uninstalling the Flatpak remove ROMs and saves?
Does uninstalling the Flatpak remove ROMs and saves?
Do not assume either outcome. Map the configured data directories and back them up before uninstalling, especially before using any delete-data option.

Sources

Version history

  • 2026-07-15: Phase 6 Flatpak boundary, data ownership, update, and rollback review.