✅ Updated Nov 2026
Affiliate Disclosure: As an Amazon Associate, we earn from qualifying purchases. Links marked "Check on Amazon" are affiliate links — learn more.
⭐ Key Takeaways
Quick answer: Our top pick is WD_BLACK SN850X 2TB NVMe SSD, with Samsung T9 Portable SSD 2TB as a strong alternative.

A Linux gaming PC accumulates front ends the way it accumulates distros: Steam for most of the library, Heroic for Epic and GOG, Lutris for everything awkward, Bottles for the odd Windows tool, itch for indie games, RetroArch for the retro shelf. Each keeps its own list, its own art and its own idea of what you own, and none shows the whole collection in one place.

Cartridges is a small GNOME application built to fix exactly that fragmentation. It imports the games those launchers know about into a single searchable grid of cover art, without asking for a single account login, because it reads the data the source apps keep on your disk. This deep dive covers how importing works, where the covers come from, what the app does not do, and the maintenance status to know before adopting it.

As an Amazon Associate, we earn from qualifying purchases.

Quick answer

Cartridges is a GNOME app that imports installed games from Steam, Lutris, Heroic, Bottles, itch, Legendary, RetroArch, Flatpak and desktop entries into one searchable grid, fetching covers from SteamGridDB with your own free key. It launches games through their source apps and manages no Wine or runners itself. Note: its maintainer has paused active development.

What Cartridges is

Cartridges is an open source launcher written in Python with GTK4 and Libadwaita, the GNOME toolkit pairing, and it belongs to GNOME Circle, the curated collection of ecosystem apps. That shows in the design: a clean cover grid, adaptive windows that collapse on small screens, and preferences that follow GNOME conventions. It is distributed as a Flatpak through Flathub; the GNOME app catalogue lists version 2.13.1, from September 2025, as the newest release.

Developed by kra-mo, with code on Codeberg, its scope is narrow on purpose: a library and a launch surface, not a store, not an installer and not a compatibility layer.

The nine import sources, and how importing works

The import system is the heart of the app. Cartridges supports nine sources: Steam, Lutris, Heroic, Bottles, itch, Legendary, RetroArch, Flatpak and plain desktop entries. For each enabled source it reads the local data that application keeps on disk — Steam’s library folders and app manifests, Lutris’s local game database, Heroic’s library records, the itch app’s local files and so on — and builds one entry per game, recording title, developer, source and the launch command the source itself uses.

Because the data comes from your disk, importing needs no logins and works offline. The trade-off is that Cartridges can only show what the source apps know about on this machine: games installed locally, or at least registered in a source’s library. A Steam game you own but have never installed does not appear, because Steam’s local manifests do not list it.

Three details make the flow practical. First, extra Steam library folders on other drives are detected automatically. Second, if you keep a source in a non-standard location, preferences let you point Cartridges at custom install folders per source. Third, importing is configurable: it can run automatically at startup, it can remove entries whose games were uninstalled since the last import, and a completed import can be undone if needed. Imports occasionally pull in the source apps themselves — the Steam client, for instance — which is what the Hide feature below exists for.

Cover art from SteamGridDB

A unified grid only works if it looks like one library rather than nine, so Cartridges downloads cover art from SteamGridDB, the community artwork database, during and after import. To enable this you add a free SteamGridDB API key in the preferences, from your own SteamGridDB account; it stays on your machine. With a key set, imported games get portrait covers, animated covers are supported, and a high-quality image option trades bandwidth for sharper art. Covers can also be replaced with your own images, or re-fetched if a better one appears.

Art quality is community-dependent. Popular games have several covers to choose from; an obscure itch release may have none, and falls back to a plain tile until you supply art yourself. That unevenness is a coverage fact, not an import failure.

Searching, sorting, hiding and details

Day to day, the library runs on a small toolset. A search field filters by title as you type. A filter narrows the grid to a single source — the fastest way to answer “what do I actually have in Heroic?” Sorting runs by title, date added or last played, using timestamps recorded each time you launch something through it. Any entry can be hidden, removing it from the grid without deleting it: the standard fix for imported launchers, duplicates and tools you never launch.

A game’s details page lets you edit its title, developer and executable, add games manually for anything no source covers, and look the game up on external databases such as IGDB, ProtonDB and HowLongToBeat. A GNOME Shell search provider lets games be found and launched from the desktop’s own search, without opening the app.

How launching works, and what Cartridges does not do

When you press play, Cartridges runs the launch command recorded at import, handing control to the source: a Steam entry starts through Steam, a Lutris entry through Lutris, a Heroic entry through Heroic. Cartridges itself contains no Wine, no Proton management, no runner downloads, no prefix settings and no install scripts: it cannot install a game, repair one, or change how one runs.

That is the sharpest contrast with Lutris and Heroic. Lutris installs games with community scripts and pins Wine and Proton versions per title. Heroic manages your Epic, GOG and Amazon libraries, with its own Wine handling per game. Cartridges sits one level above both, treating them as sources. If a game needs a different runner, you change it in Lutris or Heroic; Cartridges launches whatever the source does. Players who want one app that also does the plumbing should stay with the managers.

The honest limits, including its maintenance status

Two limits matter. The first is dependence: because imports mirror the sources’ local data, a source that changes its file layout can break its importer until Cartridges catches up, and forgotten entries linger until a re-import cleans them out. The library is also local to one machine: no account, no cloud sync, no built-in way to mirror the collection to a second PC.

The second is development status. The project README carries a notice that Cartridges is no longer actively maintained, and that the most recent code sits on a rewrite branch the maintainer warns is unfinished. The released app still installs and works as described here, and its local design means it is unlikely to rot quickly — it depends on your files, not on a server. But new source formats will not be chased, so adopt it as a finished tool, not a project with a roadmap.

Gear that suits a unified library

WD_BLACK SN850X 2TB NVMe SSD

WD_BLACK SN850X 2TB NVMe SSD

WD_BLACK SN850X 2TB NVMe SSD

Check price on Amazon

A unified front end pays off most when the library lives in one fast place: this PCIe Gen4 drive keeps Steam, Heroic and Lutris libraries on a single volume, so imports from every source point at one disk.

Specs:
– Capacity: 2TB
– Form factor: M.2 2280
– Interface: PCIe Gen4 x4, NVMe
– Maker-rated sequential read: up to 7,300 MB/s
– Model: WDS200T2X0E

Samsung T9 Portable SSD 2TB

Samsung T9 Portable SSD 2TB

Samsung T9 Portable SSD 2TB

Check price on Amazon

For a library that moves between desktop and laptop, the T9 carries games on a USB drive; point each machine’s launchers at it and both see the same shelves. Its headline speed needs a USB 3.2 Gen 2×2 host, and it runs at the ceiling of lesser ports.

Specs:
– Capacity: 2TB
– Interface: USB 3.2 Gen 2×2
– Maker-rated sequential read: up to 2,000 MB/s on a Gen 2×2 host
– Model: MU-PG2T0B/AM

WD_BLACK P10 Game Drive 5TB

WD_BLACK P10 Game Drive 5TB

WD_BLACK P10 Game Drive 5TB

Check price on Amazon

The bulk shelf: a P10 holds the rarely played installs that would crowd an SSD, at hard-drive pace and capacity, and Cartridges organises slow storage exactly like fast storage, since it only reads what each source reports.

Specs:
– Capacity: 5TB
– Drive type: portable hard disk drive
– Interface: USB 3.2 Gen 1, Micro-B
– Maker-rated transfer speed: up to 130 MB/s
– Model: WDBA3A0050BBK-WESN

SanDisk 1TB Extreme microSDXC

SanDisk 1TB Extreme microSDXC

SanDisk 1TB Extreme microSDXC

Check price on Amazon

On a Steam Deck or handheld PC in desktop mode, this card is the usual expansion: a terabyte of microSD that Steam and RetroArch sources share, imported into the same grid as everything else.

Specs:
– Capacity: 1TB
– Format: microSDXC, UHS-I
– Maker-rated read speed: up to 190 MB/s with a compatible reader
– Model: SDSQXAV-1T00-GN6MA

8BitDo Ultimate 2 Bluetooth Controller

8BitDo Ultimate 2 Bluetooth Controller

8BitDo Ultimate 2 Bluetooth Controller

Check price on Amazon

One library deserves one controller. The Ultimate 2 covers the desktop over Bluetooth, its 2.4 GHz dongle or a cable, and its dock keeps it charged next to the machine whose whole collection sits behind a single grid.

Specs:
– Connectivity: Bluetooth, 2.4 GHz wireless, wired USB
– Joysticks: TMR
– Extras: charging dock, two remappable back buttons
– Model: 80ND

How to choose

Adopt Cartridges if your games span three or more of its sources and your frustration is finding and launching them, not configuring them. Install it from Flathub, add your SteamGridDB key before importing so covers arrive with the games, enable only the sources you use, run one import, then hide the launchers and duplicates it surfaces. Turn on automatic import at startup if you install games often; leave removal of uninstalled games off until you trust the flow, since it deletes entries. If you run a single-source library, the source’s client is your unified library, and Cartridges adds a layer without adding value.

Who should skip

Skip Cartridges if you need an app that installs games, manages Wine or Proton versions, or fixes broken titles — that is Lutris and Heroic territory, and Cartridges does none of it. Skip it if you dislike GTK apps that follow GNOME design language on a non-GNOME desktop. Skip it if the paused development status worries you and you prefer a launcher with active maintenance. And skip it if most of your library is uninstalled cloud purchases: Cartridges mirrors what is on the machine, not what a store account owns.

FAQ

Does Cartridges need my Steam or Epic password?

No. It never asks for store credentials, because it reads the local library data your launchers keep on disk. If a source app knows a game on this machine, Cartridges can import it; otherwise it stays invisible until the source does.

Why do some games have no cover art?

Covers come from SteamGridDB, a community database, and coverage of obscure or new games is uneven. You can wait for art to appear and re-fetch, or set your own image in the game’s details. A free SteamGridDB API key, added in preferences, is required for downloads.

A game launches with the wrong settings. Can Cartridges fix it?

No. Launch settings, runners and prefixes belong to the source app, so change them in Lutris, Heroic, Bottles or Steam and Cartridges will use the updated behaviour next launch. Cartridges records the command, not the configuration behind it.

Is Cartridges still being developed?

The released version on Flathub, 2.13.1, works as described, but the project README states the app is no longer actively maintained, with unfinished work on a rewrite branch. Adopt it as a finished utility rather than expecting new sources or features.

Final verdict

Cartridges does one job — gathering nine launchers’ scattered games into a single, good-looking, searchable GNOME library — and does it with restraint: no accounts, no store, no Wine plumbing, just your local data presented well. Its paused development and dependence on the source apps’ file formats are real caveats, but for a multi-launcher Linux desktop they are easy to accept. If your collection lives in several front ends, this is the front door it has been missing.

Explore Our Guides & Free Tools