Updated September 27, 2026 · By Ryan Bold
To get a useful first result in RetroArch, install one copy of the frontend, add one core and start something that does not need a separate commercial game file. This guide uses the official Flatpak route on Linux and the standalone 2048 core.
A core supplies the program or emulation engine. Some cores need additional content and firmware; 2048 lets you check the interface and controls without introducing those dependencies. This walkthrough is based on the current project documentation, checked September 8, 2026. It is not a claim that every distribution or controller was physically tested.
1. Prepare a single installation route
Use a supported Linux desktop with Flatpak installed. If the flatpak command is missing, complete the setup instructions for your distribution first, including any required logout or restart. A work-managed computer may require an administrator’s approved software source.
Do not add a second RetroArch installation just because an existing package has a different menu. Check which copy you already use and preserve its settings and saves before changing installation methods. The steps below intentionally use a per-user Flatpak installation.
2. Install and identify the Flatpak
Libretro documents the official Flatpak installation route. Run these commands in a terminal as your normal user. If you want a safe command-line practice exercise first, use the Linux command walkthrough.
flatpak --version
flatpak remotes --user --columns=name,url
flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
flatpak install --user flathub org.libretro.RetroArch
flatpak info --user org.libretro.RetroArch
flatpak run org.libretro.RetroArch
If a remote named flathub already exists, confirm that its URL belongs to Flathub before installing. The --if-not-exists option does not replace an existing remote with that name. Inspect the proposed application, runtime downloads and permissions before accepting the installation prompt.
Record the version reported by flatpak info. If the launch fails, keep the terminal message; changing a video driver or adding a PPA is not a useful first response to a package download error. Flatpak’s command guide explains the user and system installation scopes.
3. Install the 2048 core and start it
- In RetroArch’s main menu, open Online Updater, then Core Downloader.
- Select the entry containing 2048 and wait for its download to complete.
- Return to the main menu and choose Load Core, then 2048.
- Choose Start Core. A numbered-tile game board should appear; this core does not require a separate ROM file.
The core installation guide covers the downloader, and the 2048 core documentation describes starting the game without loading external content. If 2048 is already installed, begin with Load Core.
If Core Downloader is absent, first confirm that you launched the Flatpak identified in step 2. In that build, check Settings → User Interface → Menu Item Visibility → Show Core Downloader. Distribution packages can supply cores through a different mechanism. Check the documentation for that build rather than mixing installations or downloading a random core archive.
4. Check input and save-state recovery
Use one keyboard or controller. Try the directional inputs and watch whether the board changes. A move that cannot slide or merge any tile may leave the board unchanged, so test more than one direction before deciding input is broken.
Before playing, find the menu-toggle binding under Settings → Input → Hotkeys so you can return to RetroArch’s menu. The official controls guide documents the keyboard bindings. On a stock keyboard configuration, F1 normally opens the menu. If you changed the binding, use your configured key.
- Make a few moves and note the tile arrangement.
- Open the Quick Menu, select an unused state slot and choose Save State.
- Resume the game and make a move that visibly changes the board.
- Open the Quick Menu again and choose Load State from the same slot. Compare the board with your note.
Use a disposable game for this check. Loading a state replaces the running state with the saved one. The 2048 core supports states, but that does not establish compatibility between different cores or future versions. Keep normal save files and state files distinct when backing up other games.
When the first test fails
| Failure | Next useful check |
|---|---|
| RetroArch never opens | Read the Flatpak launch error and verify the application ID and installation scope. |
| RetroArch opens but 2048 is missing | Check the downloader result and which RetroArch installation is running. |
| The board appears but does not respond | Check the selected input device and bindings before changing graphics settings. |
| A saved state cannot be restored | Confirm the core, state slot and save location; do not overwrite your only useful save to investigate. |
Change one setting at a time and record the observation. This first test exercises display, input and a state operation; it is not an audio test or a performance benchmark for console emulation.
Updates and other games
Close RetroArch before backing up saves and configuration. Update this same installation with flatpak update --user org.libretro.RetroArch, reviewing the proposed changes. If you remove it, flatpak uninstall --user org.libretro.RetroArch targets the application; do not add data-deletion options unless you have separately decided to remove its saved data.
For another system, read that core’s supported formats and firmware requirements. Use content and firmware you are authorized to use. Installing an emulator does not supply permission to copy a commercial game, and downloading a BIOS pack is not proof of a licence.
Revision note, September 8, 2026: replaced the broad distribution overview with one Flatpak workflow, a named standalone core and an observable state-recovery exercise.