- Top Pick: Samsung T9 Portable SSD 2TB
- Runner-up: WD_BLACK SN850X 2TB NVMe SSD
- Also consider: WD_BLACK P10 Game Drive 5TB
Install Steam, Heroic or Lutris as a Flatpak and everything seems fine — until you point the launcher at a second drive that never appears in its file picker, or plug in a controller the game insists is not connected. Nothing is broken. You have met the sandbox: a Flatpak app sees only the files, devices and services its package declares; everything else is invisible until you grant it. Flatseal is the tool built for that moment.
Flatseal is a graphical utility for reviewing and changing Flatpak permissions, app by app, without touching a terminal. Underneath the toggles it edits the same override files as the flatpak override command — a readable front end for Flatpak’s own permission layer. This deep dive covers the categories that matter for games, the three fixes Flatpak gamers need most, global versus per-app overrides, the terminal equivalents, and the honest limits of what a permission can repair.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
Flatseal is the graphical front end for Flatpak’s permission overrides: pick an app, and you can grant it a library drive, controller access or a save folder the sandbox hides by default. It writes the same override files as the flatpak override command, per app or globally, and every change needs an app restart.
What Flatseal actually changes
Every Flatpak ships with static permissions declared in its manifest: the network access, display sockets, device nodes and filesystem paths the developer asked for. Changing one in Flatseal does not edit the app — it writes a user-level override, a small key file in your per-user overrides folder, which Flatpak layers over the manifest at every launch. That is why changes survive app updates: the update replaces the package, not your overrides.
Three consequences follow. Changes are not live — permissions are read at launch, so the app must be fully restarted before a grant exists inside its sandbox. Changes are reversible: Flatseal marks every permission moved from its default, and reset deletes your overrides and restores the developer’s set. Flatseal also touches portal permissions — the one-off grants recorded when an app asks through a dialog — but the static side is where the gaming fixes live.
The permission categories, in gamer terms
Flatseal groups permissions the way Flatpak’s override format does. Most groups you will never touch; four solve nearly every gaming problem.
- Share covers network and inter-process communication. Multiplayer and store pages need the network toggle; switching it off is a genuine offline mode for a launcher you do not trust online.
- Sockets covers display and sound plumbing — the Wayland and X11 windowing sockets and the PulseAudio sound socket. Launchers ship with these on.
- Devices is the gaming-critical group: GPU acceleration, input devices, USB devices and the broad all-devices grant. A controller the sandbox cannot see is almost always a missing entry here.
- Filesystem controls which paths exist inside the sandbox: home, host, and a custom list of individual folders, each read-write or read-only. The invisible library drive is fixed here.
- Persistent lists home-relative paths an app may keep inside its own private data folder — why a sandboxed launcher’s saves live under its .var/app folder, not where a native install would put them.
- Features, Environment and Bus round out the list: Bluetooth, background running, multi-architecture support (older 32-bit Windows games under Proton can depend on it), environment variables and D-Bus names. Gamers rarely need them, but multi-arch is worth knowing when a legacy title refuses to start.
Case one: the library drive the launcher cannot see
The symptom is always the same: a second drive is mounted and full of games, yet Steam’s storage settings show only the internal drive and the file picker cannot browse to the mount point. The cause is the filesystem group — the launcher was granted its own data folder and a few declared paths, and a drive mounted at /mnt/games or under /run/media is not among them.
The fix takes a minute. In Flatseal, select the launcher, scroll to Filesystem, and under the custom paths list add the drive’s mount path — read-write for a library the launcher must install to, or with the read-only marker if the app only reads. Restart the launcher, then add the folder as a library location in its settings. (The file-chooser portal explains a common confusion: it lets an app open one file you pick in a dialog with no grant at all, while browsing a drive needs the override.)
Case two: the controller that is not there
A gamepad that works on the desktop and in native games but never appears inside a Flatpak launcher is a device-access problem: inside the sandbox, the controller’s device node has to be granted, and not every package declares it. Open the launcher in Flatseal and check Devices. The narrow grant is input devices, which covers gamepads; USB devices covers some dongles; all devices is the broad option that also sweeps in webcams and capture hardware. Grant the narrowest match, restart the app, and the pad should enumerate as it does anywhere else.
Note what this does not change: Steam Input and remapping still live inside Steam or the game, as on a native install — Flatseal only decides whether the device exists in the sandbox. If the controller is missing on the desktop too, the problem is on the host, and no toggle fixes it.
Case three: saves, mods and folders outside the sandbox
Sandboxed launchers keep their world in a private data folder, one per app, under .var/app in your home directory — saves landing there is the sandbox working as designed, and the Persistent group records which home-relative paths map into it. Trouble starts when something outside the app needs the same files: a mod manager, a backup tool, a second launcher sharing one mod folder. The answer is the library fix aimed at one folder: add it to the app’s custom paths, read-write for a tool that edits it, read-only for one that only reads. Resist granting the whole home directory instead — the sandbox stops meaning anything.
Global overrides vs per-app permissions
At the top of Flatseal’s app list sits an All Applications entry. Changes there are global overrides: they apply to every Flatpak you run, present and future — flatpak override with no app named. They suit a universal preference and little else, because the blast radius is your whole app collection: grant a library drive globally and every sandboxed app can read it.
The working rule is per-app by default: give the one launcher the one path or device it needs, leave the rest at manifest defaults, and keep global overrides for the rare setting you would defend for every app at once. Overrides stack — global first, then the app’s own — so a per-app reset never disturbs global choices.
The same fixes from the terminal
Flatseal and the command line write the same override files. Three commands cover most of it:
flatpak override --user --filesystem=/mnt/games com.valvesoftware.Steam
flatpak info --show-permissions com.valvesoftware.Steam
flatpak override --user --reset com.valvesoftware.Steam
The first grants a library drive to the Steam Flatpak at user level; the second prints the permissions an app will actually launch with, manifest and overrides combined; the third removes your overrides and returns the app to defaults — the terminal twin of Flatseal’s reset button. Device and socket grants follow the same pattern.
The honest limits
Flatseal cannot fix a badly packaged app. If a launcher is missing a runtime component or ships a broken build, an override may paper over the symptom, but the fix belongs to its maintainers. Nor can a permission repair things that were never permissions: an unmounted drive, a controller the host cannot see, or a driver mismatch between the runtime and your kernel.
The deeper limit is the trade itself: every grant weakens the sandbox by exactly its size. A single read-only folder is a small, deliberate hole; home access for every launcher is no sandbox at all; all-devices hands an app your camera and microphone along with your controller. Flatseal makes the trade visible and reversible — but it is yours to make, narrowly, per app.
Storage and input gear for a growing Flatpak library
Samsung T9 Portable SSD 2TB
The external library drive for a launcher granted exactly one extra path — fast over USB, small enough to move between desktop and dock.
Specs:
- Interface: USB-C, USB 3.2 Gen 2×2
- Maker-rated sequential reads up to 2,000 MB/s on a Gen 2×2 host; lesser ports cap it lower
- The 2TB model, MU-PG2T0B/AM; drop resistance maker-rated to 3 metres
WD_BLACK SN850X 2TB NVMe SSD
The internal option: a Gen4 NVMe drive that becomes the library Steam sees once its mount point is granted.
Specs:
- Interface: PCIe Gen4 NVMe, M.2 2280
- Maker-rated sequential reads up to 7,300 MB/s
- Model WDS200T2X0E, the heatsink-free version
WD_BLACK P10 Game Drive 5TB
Bulk spinning storage for the back catalogue, on a bus-powered drive a launcher can hold as a second library.
Specs:
- Portable 2.5-inch hard drive, bus-powered, USB 3.2 Gen 1
- Maker-rated speeds up to 140 MB/s; model WDBA3A0050BBK-WESN, 5TB
SanDisk 1TB Extreme microSDXC
For the Steam Deck side of a Flatpak library, where the card slot is the expansion path.
Specs:
- Format: microSDXC, UHS-I; A2 application performance class, U3 and V30 video classes
- Model SDSQXAV-1T00-GN6MA, 1TB capacity, SD adapter included
8BitDo Ultimate 2 Bluetooth Controller
The controller from case two: Bluetooth, a 2.4 GHz dongle and a wired mode, so whichever connection you grant, the hardware side is covered.
Specs:
- Connectivity: Bluetooth, 2.4 GHz wireless and wired USB-C
- TMR joysticks and Hall effect triggers, per the maker’s specification
- Model 80ND; charging dock included
How to choose
Match the fix to the symptom before touching a toggle. An invisible drive or folder is a Filesystem problem; a dead controller is a Devices problem; saves in an unexpected place are the private data folder explaining itself. Then grant narrowly: one app, not all applications; one path, not the home directory; read-only whenever the app only reads. Finally, restart the app and verify in its own settings — an unconfirmed grant is a hope with a toggle.
Who should skip this
Skip Flatseal if your launchers are native packages: with no sandbox there is nothing to override. Skip it, too, if your problem is a broken app rather than a hidden folder or device — permissions will not repair a bad build. And skip the global toggles if your instinct is to grant everything everywhere; the honest choice then is a native install, not a sandbox with every wall removed.
FAQ
Do Flatseal changes survive app updates?
Yes. Overrides are your files, stored separately from the package, and Flatpak applies them over whatever manifest the updated version ships. An update never deletes them — only a reset does that.
Why did nothing change after I toggled a permission?
Because the app was still running. Permissions are read at launch, so a launcher left open in the background keeps its old sandbox. Quit it, relaunch, and the new grants apply.
Is Flatseal just the flatpak override command with buttons?
Essentially, yes — both write the same override files. Flatseal earns its place with visibility: every permission in one list, changed values marked, and a reset button instead of flags to remember.
Final verdict
Flatseal is the missing control panel for the Flatpak gaming life: a small, honest tool that shows you what each launcher may touch and lets you amend the contract path by path, device by device. Learn the groups that matter — Share, Sockets, Devices, Filesystem — grant narrowly and per app, restart, and verify. Do that, and the sandbox stops being the reason a drive or a controller is missing, and goes back to being the reason you can trust the apps around your library.











