Most Flatpak trouble starts before the first app installs. You add Flathub, search for an app and get “No matches found”, or the install dies with “Flatpak system operation Deploy not allowed for user” because you ran it over SSH without sudo and polkit refused it. This Flatpak cheat sheet puts the commands you need on one page, then explains the handful of behaviours that catch people out, each with the real error text so you can match it to your terminal.
You’ll find remotes, installs, updates and rollbacks, permission overrides, runtime cleanup, Flathub verification, and the common errors with their fixes. If you’re still deciding between formats, our Snap vs Flatpak vs AppImage comparison covers that first. I went through every command again in November 2026 on Fedora 45 (Flatpak 1.18) and Ubuntu 26.04 LTS (Flatpak 1.16), and they still hold. The whole sheet is also a free one-page PDF.
Use the Flatpak cheat sheet tables
Every row below ran on one of the two lab machines. Commands with sudo change the system installation in /var/lib/flatpak, and commands with --user change your own copy in ~/.local/share/flatpak. Pick one per machine and stick with it, because most of the confusing errors further down come from mixing the two. A desktop you use alone works well with system installs, since GNOME Software uses them too, while a shared box where you lack admin rights is the case for --user. When a command is missing from this sheet entirely, the tldr command examples guide shows how to install tldr and pull community example pages for it.
Remotes
| Command | What it does |
|---|---|
flatpak remotes --show-details | List remotes with URL, options and filter |
sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo | Add Flathub for all users |
flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo | Add Flathub for your account only |
flatpak remotes --show-disabled --columns=name,options | Include disabled remotes in the list |
sudo flatpak remote-modify --disable flathub-verified | Turn a remote off without deleting it |
sudo flatpak remote-modify --enable flathub-verified | Turn it back on |
sudo flatpak remote-delete flathub-verified | Remove a system remote |
flatpak remote-delete --user flathub | Remove a user remote |
Search and install
| Command | What it does |
|---|---|
sudo flatpak update --appstream | Download the app catalog that search reads |
flatpak search flatseal | Search names and descriptions |
flatpak search --columns=application,version,branch,remotes calculator | Search, showing app ID, version, branch and remote |
sudo flatpak install -y flathub com.github.tchx84.Flatseal | Install system-wide by full app ID |
flatpak install --user -y flathub org.gnome.Calculator | Install for your account, no sudo |
flatpak remote-ls flathub --runtime --columns=application,branch | List runtimes and branches on a remote |
flatpak remote-info --log flathub org.gnome.Calculator | Show remote version and commit history |
Run and inspect
| Command | What it does |
|---|---|
flatpak list --app --columns=application,version,origin | Installed apps only |
flatpak list --columns=application,branch,installation,size | Apps and runtimes with sizes |
flatpak info org.gnome.Calculator | Version, runtime, commit, installation |
flatpak info --show-location com.github.tchx84.Flatseal | Where the app lives on disk |
flatpak run org.gnome.Calculator | Start an app |
flatpak run --command=sh org.gnome.Calculator | Open a shell inside the sandbox |
flatpak ps | Running sandboxed instances |
flatpak --installations | Paths of the system installations |
flatpak history | Every pull, deploy and uninstall with dates, read from the systemd journal, so it reaches back only as far as the journal keeps entries |
Update, roll back and hold
| Command | What it does |
|---|---|
sudo flatpak update -y | Update every system app and runtime |
flatpak update --user -y | Update your user installation |
flatpak remote-ls --updates | Show pending updates without applying them |
flatpak update --user --commit=0032886e3396c2e0cb107d453d600301c8090241d3fef31ca3f688510dba0e43 org.gnome.Calculator | Move an app to an older commit |
flatpak mask --user org.gnome.Calculator | Stop updates for one app |
flatpak mask --user | List masked apps |
flatpak mask --user --remove org.gnome.Calculator | Allow updates again |
Permissions and overrides
| Command | What it does |
|---|---|
flatpak info --show-permissions org.gnome.Calculator | Permissions the app ships with |
flatpak override --user --filesystem=~/Documents:ro org.gnome.Calculator | Grant read-only access to one folder |
flatpak override --user --unshare=network org.gnome.Calculator | Cut the app off the network |
flatpak override --user --nofilesystem=host | Revoke filesystem=host grants for every app |
flatpak override --user --nofilesystem=host:reset com.github.tchx84.Flatseal | Drop every file grant the app ships with |
flatpak override --user --show org.gnome.Calculator | Show your overrides for one app |
flatpak override --user --reset org.gnome.Calculator | Drop all overrides for one app |
sudo flatpak override --nofilesystem=home org.gnome.Calculator | System override for all users |
flatpak run --filesystem=~/Downloads org.gnome.Calculator | One-off grant for this run only |
Runtimes and disk cleanup
| Command | What it does |
|---|---|
flatpak uninstall --user -y com.github.tchx84.Flatseal | Remove an app, keep its data |
flatpak uninstall --user -y --delete-data org.gnome.Calculator | Remove an app and its ~/.var/app data |
sudo flatpak uninstall --unused -y | Remove system runtimes no app needs |
flatpak uninstall --user --unused -y | Same for your user installation |
flatpak pin --user | List pinned runtimes that cleanup skips |
flatpak pin --user --remove runtime/org.freedesktop.Platform/x86_64/23.08 | Unpin so cleanup can remove it |
sudo flatpak repair | Verify objects and prune the repo |
du -sh ~/.local/share/flatpak | Real disk use of the user installation |
Flathub verification
| Command | What it does |
|---|---|
curl -s https://flathub.org/api/v2/verification/com.github.tchx84.Flatseal/status | Ask Flathub whether an app is verified |
sudo flatpak remote-add --if-not-exists --subset=verified flathub-verified https://dl.flathub.org/repo/flathub.flatpakrepo | Add a remote that holds only verified apps |
flatpak remotes --columns=name,subset,url | Show which remote uses a subset |
flatpak remote-ls --app flathub-verified | List what the verified remote offers |
The sections below walk through the same commands with the output both machines printed, starting from a system that has no Flatpak at all. Read them in order the first time, because each one builds on the remote and the apps from the step before. After that you can live in the tables and only come back down here when an error shows up that you do not recognise.
Install Flatpak and add Flathub
Fedora Workstation ships Flatpak already, but the Fedora 45 Cloud image I tested on didn’t have it, and neither did Ubuntu 26.04. On Fedora, install the package with dnf. If you’re setting up a fresh desktop, our list of things to do after installing Fedora 45 covers Flatpak alongside codecs and drivers:
sudo dnf -y install flatpak
On Ubuntu the package comes from the universe repository, which was already enabled on the 26.04 cloud image I used:
sudo apt-get update
sudo apt-get install -y flatpak
Confirm the version afterwards. Fedora 45 had 1.18.4 and Ubuntu 26.04 had 1.16.6, and both behaved the same for everything on this page, so you don’t need a newer build from a PPA or COPR to follow along. The version also tells you which page of the upstream Flatpak command reference matches your system:
flatpak --version
The Fedora machine printed this. Notice that flatpak remotes printed nothing on either box at this point, because a fresh install has no remote at all:
Flatpak 1.18.4
With the package in place, the next job is giving Flatpak somewhere to install apps from, and the two distros go about that differently.
Add Flathub on Ubuntu, then refresh the catalog
Flathub is the remote almost everyone wants. Add it system-wide with sudo so every account on the machine can use the same apps and runtimes. The --if-not-exists flag makes the command safe to rerun in a script:
sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
The next step is the one that trips people up. Right after adding the remote, flatpak search found nothing, not even Flatseal, because search reads a local copy of the Flathub catalog and that copy did not exist yet. Installs worked fine by app ID in the meantime, so the remote itself was healthy. One flatpak update --appstream fixed search:

If search ever returns “No matches found” for an app you know is on Flathub, refresh the catalog before you suspect the remote. For a deeper look at how Flatpak fits next to Snap and APT on this release, see our Snap, Flatpak and APT guide for Ubuntu 26.04.
Add Flathub on Fedora the Fedora way
Fedora ships its own Flathub definition in the fedora-flathub-remote package and turns it on through the “third-party repositories” switch that GNOME Software also offers. You can flip it from a terminal:
sudo dnf -y install fedora-flathub-remote
sudo fedora-third-party enable
The remote shows up marked filtered, which used to mean Fedora only let a short allowlist of Flathub apps through. On Fedora 45 the filter file is effectively empty, so you get the full catalog:

That single # Unfiltered line means you don’t need to delete and re-add the remote to see every app, which older Fedora guides still tell you to do. Our step-by-step Flatpak and Flathub setup for Fedora covers the GNOME Software side if you prefer clicking.
Whichever distro you’re on, a quick check before your first install saves most of the errors in the last section:
- You can see
flathubinflatpak remotes, and its options column sayssystemoruserthe way you expect. - You get results from
flatpak searchfor an app you know is on Flathub. - You know whether you’ll use
sudo(system) or--useron this machine, and you use it every time.
If any of those three is not true, fix it now. It is much easier than untangling apps that ended up split across two installations.
Install and run Flatpak apps
Always install by the full app ID, such as com.github.tchx84.Flatseal. A short name like flatseal fails outright in a script (the error is in the last section). The system install on Ubuntu pulled the GNOME 50 runtime, the GL drivers and codecs before the app itself:
sudo flatpak install -y --noninteractive flathub com.github.tchx84.Flatseal
Six refs came down for one 1.4 MB app, and the whole job took 54 seconds on a cloud VM. Your first install is always the slow one, because the runtime is the heavy part, and later apps built on the same GNOME 50 base reuse it and download only themselves:
Installing runtime/org.freedesktop.Platform.GL.default/x86_64/25.08
Installing runtime/org.freedesktop.Platform.GL.default/x86_64/25.08-extra
Installing runtime/org.freedesktop.Platform.codecs-extra/x86_64/25.08-extra
Installing runtime/org.gnome.Platform.Locale/x86_64/50
Installing runtime/org.gnome.Platform/x86_64/50
Installing app/com.github.tchx84.Flatseal/x86_64/stable
real 0m54.308s
The Fedora box got a user installation instead, which needs no sudo and keeps everything under your home directory. That suits a shared machine where you don’t have admin rights, or a laptop where you want apps to follow your account. A user install needs its own Flathub remote, so add one with --user first, then install two apps in one go:
flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
flatpak install --user -y flathub org.gnome.Calculator com.github.tchx84.Flatseal
The list afterwards is the best argument for cleaning up regularly. Two apps totalling 6.5 MB brought in two different GNOME runtimes at 1.1 GB each, because Calculator targets GNOME 51 and Flatseal still targets GNOME 50:

Don’t add up the size column to estimate disk use. Flatpak deduplicates files between refs, so du -sh ~/.local/share/flatpak is the honest number, and it read 3.1 GB at this point. The info subcommand tells you which runtime an app is tied to and which commit you’re on, which matters when you roll back later:
flatpak info org.gnome.Calculator
Look for the Installation, Runtime and Commit lines:
Calculator - Perform arithmetic, scientific or financial calculations
ID: org.gnome.Calculator
Ref: app/org.gnome.Calculator/x86_64/stable
Arch: x86_64
Branch: stable
Version: 51.1
License: GPL-3.0-or-later
Origin: flathub
Collection: org.flathub.Stable
Installation: user
Installed Size: 5.1 MB
Runtime: org.gnome.Platform/x86_64/51
Sdk: org.gnome.Sdk/x86_64/51
Commit: 00516a24d410ad62ed3e955fa5deb5af221ab6b181ed5549103f3670d10d2fca
Parent: 0032886e3396c2e0cb107d453d600301c8090241d3fef31ca3f688510dba0e43
Subject: Merge pull request #55 from flathub/update-master-db2c4e6 (6d83df014422)
Date: 2026-10-12 11:33:26 +0000
To see what an app sees, open a shell inside its sandbox. This is the quickest way to test a permission change without a desktop session, and the sandbox reports the GNOME runtime as its operating system, not Fedora:
flatpak run --command=sh org.gnome.Calculator -c "cat /etc/os-release | head -3; ls ~ | head; id -un"
Your username carries into the sandbox, but the host’s operating system does not, so a library bug you see here belongs to the runtime and not to Fedora:
NAME="GNOME"
VERSION="51 (Flatpak runtime)"
VERSION_ID="51"
lorna
A plain flatpak run org.gnome.Calculator over SSH exits with “Failed to open display”, which is expected on a machine with no graphical session. It does not mean the install is broken, so don’t reinstall over it. Run GUI apps from the desktop, and keep --command=sh for poking around remotely.
Update, roll back and hold an app
A plain flatpak update updates apps and runtimes together and refreshes the catalog at the end. The shorthand “sudo for system, –user for yours” is only half right here: with no flag it covers both the system installation and your user one, so add --user or --system when you want to touch only one of them. On this test machine the apps lived in the user installation:
flatpak update --user -y
Everything was current on the day of the test. If you see a long list here instead, read it before you confirm, because a runtime jump such as GNOME 50 to 51 can be a gigabyte on a slow connection:
Looking for updatesβ¦
Nothing to update.
Updating appstream data for user remote flathub
When an update breaks an app, you can go back to an earlier build because Flathub keeps the commit history. List it with remote-info --log and copy the commit you want:
flatpak remote-info --user --log flathub org.gnome.Calculator
Each entry has a commit hash, the merge subject and a date. The newest one is what you have now, and the one below it was the previous release:
Commit: 00516a24d410ad62ed3e955fa5deb5af221ab6b181ed5549103f3670d10d2fca
Subject: Merge pull request #55 from flathub/update-master-db2c4e6 (6d83df014422)
Date: 2026-10-12 11:33:26 +0000
History:
Commit: 0032886e3396c2e0cb107d453d600301c8090241d3fef31ca3f688510dba0e43
Subject: Merge pull request #54 from user1-github/patch-1 (d05528e9ce1a)
Date: 2026-09-18 10:31:20 +0000
Pass that hash to --commit to downgrade, then mask the app so the next routine update doesn’t undo your fix. A masked app is skipped silently, so the following flatpak update reported nothing to update even though 51.1 was available:

Because a mask is silent, it’s easy to forget one and run an old build for months. Check flatpak mask --user every so often, and when the upstream fix lands, remove the mask and update:
flatpak mask --user --remove org.gnome.Calculator
flatpak update --user -y org.gnome.Calculator
The app came straight back to version 51.1 on the newest commit, so the round trip leaves nothing behind. You can use the same pattern for a runtime that breaks an app, since runtimes have commit logs too, but downgrading a runtime affects every app built on it, so try the app first.
Override Flatpak permissions
Every app ships with a set of permissions its packager chose, and flatpak override lets you tighten or loosen them without waiting for a new build. Start by reading what the app asks for:
flatpak info --show-permissions org.gnome.Calculator
Calculator has network access (for currency rates) and no file access at all. That’s a sensible default, because a file you open through a file dialog still reaches the app through the desktop portal, so most apps never need a broad home folder grant:
[Context]
shared=ipc;network;
sockets=fallback-x11;wayland;
devices=dri;
The first attempt here granted read-only access to the documents folder with the xdg-documents shortcut and removed network access in the same command. The network part worked, but the app still couldn’t see ~/Documents/notes.txt. The shortcut resolves through ~/.config/user-dirs.dirs, and that file only exists after a desktop login has created it, so on a server or a fresh account it points nowhere. A literal path works everywhere:

The sandbox printed the file contents and then refused the write with “Read-only file system”, which is exactly what :ro promises. Look at the override list too: --nofilesystem=xdg-documents replaced the earlier xdg-documents:ro grant with a !xdg-documents deny entry, while the new ~/Documents:ro path was added alongside it. Entries for different paths pile up like that, and the clean way to drop all of them for an app is a reset:
flatpak override --user --reset org.gnome.Calculator
Before you start overriding, it helps to know where each kind of override lives and who it affects:
- You can keep an override to your account with
--user, which writes a file under~/.local/share/flatpak/overrides/. - You can apply one to every user with
sudo flatpak override, which writes to/var/lib/flatpak/overrides/. - You can leave out the app ID to set a global rule, such as
--nofilesystem=hostfor every app, which only revokes full host access and leaves narrower grants likexdg-downloadin place. - You can add
:reset, as in--nofilesystem=host:reset, to drop every file grant an app ships with, which is the real lockdown. - You can test a permission for one launch with
flatpak run --filesystem=~/Downloads, and nothing is saved.
The one-off run flag is the safe way to experiment, because a wrong guess disappears when the app exits. The difference between the two forms showed when both were applied to Flatseal alone, which ships read-only access to /var/lib/flatpak/app: after --nofilesystem=host it could still list that folder, and only after --nofilesystem=host:reset did the sandbox answer “No such file or directory”. If you’d rather click than type, Flatseal edits the same per-user override files in ~/.local/share/flatpak/overrides, so your --user changes show up there too.
Clean up old runtimes and reclaim disk
Uninstalling an app never removes the runtime it used, which is why Flatpak disk use creeps up over a year of updates. To show the whole cycle, an end-of-life runtime went onto the Fedora box on purpose. Flatpak warns you on install, and you’ll see the same “Info” lines during updates when an app you rely on still targets an old base:
flatpak install --user -y flathub org.freedesktop.Platform//23.08
The message names the runtime and branch, and tells you nothing will patch it any more:
Info: org.freedesktop.Platform is end-of-life, with reason: org.freedesktop.Platform 23.08 is no longer receiving fixes and security updates. Please update to a supported runtime version.
With Flatseal removed, the GNOME 50 runtime was orphaned. The cleanup command found it and four related refs, but it skipped the 23.08 runtime and said why. Any runtime you install by name, as happened here, gets pinned automatically, and pinned runtimes survive --unused:

If cleanup keeps leaving a runtime behind, check flatpak pin before anything else. Pins are easy to collect without noticing, because some app instructions tell you to install a runtime by hand first, and that runtime then stays forever. Unpin it and run the cleanup again:
flatpak pin --user --remove runtime/org.freedesktop.Platform/x86_64/23.08
flatpak uninstall --user --unused -y
App data is the other thing uninstall leaves behind. Settings and caches live in ~/.var/app/<app-id> and stay there after a normal uninstall, in case you reinstall. Add --delete-data when you’re done with an app for good:
flatpak uninstall --user -y --delete-data org.gnome.Calculator
flatpak uninstall --user --unused -y
The user installation on Fedora shrank like this, measured with du -sh after each step of that cleanup:
| Step | Disk used |
|---|---|
| Two apps, two GNOME runtimes, one EOL runtime | 4.2 GB |
After removing Flatseal and running --unused | 2.8 GB |
| After unpinning 23.08 and cleaning again | 1.8 GB |
| After removing Calculator with its data | 110 MB |
Nearly all of that space was runtimes, not apps. The two apps themselves never weighed more than 6.5 MB together, so when a disk usage tool points at ~/.local/share/flatpak or /var/lib/flatpak, the cleanup commands above are the answer, not deleting apps you still use. If a broken download or a full disk ever leaves the installation in a bad state, sudo flatpak repair verifies every object and prunes what nothing references. On Ubuntu it verified all 13 refs in the local repository and pruned it without complaint.
Check Flathub verification before you install
A verified app on Flathub is one whose developer proved they own the app ID, according to Flathub’s verification documentation. It tells you who publishes the package. It doesn’t mean anyone audited the code, and plenty of popular apps are community packages that can’t be verified at all. You can check the status without a browser, through the same API the website uses:
curl -s https://flathub.org/api/v2/verification/com.github.tchx84.Flatseal/status
Flatseal is verified through its developer’s GitHub account. Spotify returned "verified":false the same day, because it’s packaged by the community rather than by Spotify:
{"verified":true,"timestamp":"1675765033","method":"login_provider","login_provider":"github","login_name":"tchx84"}
The same information is already on your disk after flatpak update --appstream, as custom keys in the Flathub catalog. This loop pulls the verification lines for several apps at once, which is handy when you audit a machine offline:
for app in com.github.tchx84.Flatseal org.gnome.Calculator com.spotify.Client org.videolan.VLC; do echo "== $app"; zcat /var/lib/flatpak/appstream/flathub/x86_64/active/appstream.xml.gz | awk -v id="<id>$app</id>" 'index($0,id){f=1} f&&/verification::(verified|method|website|login_name)/{print} f&&/<\/component>/{exit}' | sed 's/^ *//'; done
Apps with no lines under their name aren’t verified. GNOME Calculator shows a second method, verification by website, which is how organisations like GNOME prove ownership:
== com.github.tchx84.Flatseal
<value key="flathub::verification::verified">true</value>
<value key="flathub::verification::method">login_provider</value>
<value key="flathub::verification::login_name">tchx84</value>
== org.gnome.Calculator
<value key="flathub::verification::verified">true</value>
<value key="flathub::verification::method">website</value>
<value key="flathub::verification::website">gnome.org</value>
== com.spotify.Client
== org.videolan.VLC
To enforce it rather than check it, add a second remote with --subset=verified. That remote only offers verified apps, and installing anything else from it fails. On the test day it listed 2,239 apps against 3,527 on full Flathub, so roughly a third of the catalog drops out, VLC among them:

Use the verified remote on machines you hand to other people, where you want a clear rule, and keep full Flathub on your own desktop where you can judge a community package yourself. Both remotes can sit side by side, and you choose per install by naming the remote. Each installed app remembers the remote it came from (the Origin line in flatpak info), and updates keep coming from that remote, so the choice you make at install time sticks.
Fix common Flatpak errors
Each error below appeared on one of the lab machines during this test, word for word. Most of them come down to the system and user installations being two separate worlds.
error: No remote refs found for βflathubβ
The remote you named doesn’t exist in the installation you’re using. It happened on Ubuntu before Flathub was added, and again on Fedora when flatpak install --user ran while Flathub existed only as a system remote. Run flatpak remotes, look at the options column for system or user, and add the remote to the installation you meant to use. Don’t add it to both unless you really want both, because that leads straight to the “multiple installations” prompt below.
Flatpak system operation Deploy not allowed for user
You tried a system-wide install without sudo, and polkit refused to approve it. Flatpak’s polkit rules let an admin (wheel or sudo group) install system-wide from a local desktop session, and other desktop users get a password dialog. An SSH session isn’t local, so polkit refuses instead. It failed over SSH on both lab machines, and on Fedora I also tried it with --noninteractive (which tells Flatpak not to ask at all) and from an interactive ssh -tt terminal. Every runtime failed in turn:

Put sudo in front of the install, or switch to --user with a user remote. The “GetRevokefsFd not allowed” lines are the same problem and go away with the same fix.
Remote βflathubβ found in multiple installations
Flathub exists both as a system remote and as a user remote, so Flatpak asks which one to use. In a script or a pipe there’s no one to answer, and it gives up:
Remote βflathubβ found in multiple installations:
1) system
2) user
Which do you want to use (0 to abort)? [0-2]: 0
error: No remote chosen to resolve βflathubβ which exists in multiple installations
Pass --user or --system explicitly, or delete the duplicate with flatpak remote-delete --user flathub if you don’t need both.
error: Invalid id flatseal: Names must contain at least 2 periods
Flatpak wants a full reverse-DNS app ID when you name a remote, and a short name is rejected before it ever reaches Flathub. That’s the same whether you pass -y or not. Find the ID with flatpak search (refresh the catalog first if search comes back empty) and use com.github.tchx84.Flatseal instead of flatseal.
error: No installed refs found for an app you know is installed
Running flatpak uninstall --user com.github.tchx84.Flatseal on Ubuntu failed this way because the app was a system install. Check the installation column in flatpak list --columns=application,installation and repeat the command with sudo or --user to match.
Can’t fetch summary from disabled remote βflathubβ
The remote is still configured but switched off, often by a “third-party repositories” toggle. The full line read “error: Unable to load summary from remote flathub: Can’t fetch summary from disabled remote βflathubβ”. Re-enable it with sudo flatpak remote-modify --enable flathub and the install goes through again.
error: Nothing matches org.videolan.VLC in remote flathub-verified
The app exists on Flathub, but it is not verified, so the verified subset remote does not carry it. That’s the subset doing its job rather than a broken remote. Install it from the full flathub remote if you’re happy with a community package, or pick a verified alternative.
Gtk-WARNING: Failed to open display
You started a graphical app from a shell with no display, usually SSH. The app is fine, so there’s nothing to reinstall or repair. Launch it from the desktop, or use flatpak run --command=sh when you only need to look inside its sandbox.
If you take one habit from this page, make it running sudo flatpak uninstall --unused (or the --user form) after big updates, and checking flatpak pin when it seems to miss something. For the package managers on either side of Flatpak, the DNF5 cheat sheet and the APT cheat sheet follow the same format, and every printable sheet we publish is collected on the cheat sheets hub.