Android RetroArch backup tutorial / 2026-08-02

Back up and restore one RetroArch core setup on Android

Preserve the base config, core options, overrides, remaps, saves, and states as separate layers before an Android update.

10 minute tutorialCurrent RetroArch for Android; package storage and export access vary by distribution

Back up and restore one RetroArch core setup on Android

Record RetroArch and core versions, close content through the menu, and copy the configured Config, Remap, Saves, and Save States directories through Android's supported file picker. Restore into the same versions first, then verify each layer separately before upgrading.

Do this in order

  1. 01

    Record the RetroArch package and version, core name and revision, content identity, and every displayed directory path.

  2. 02

    Quit content and RetroArch from their menus so configuration and save writes finish.

  3. 03

    Copy the base configuration plus Config and Remap directories using a location Android has granted to the app or file picker.

  4. 04

    Copy Saves and Save States separately; label states with the exact core revision and content hash.

  5. 05

    Restore to the same package and versions first, reload one authorized title, and verify options, override, remap, native save, and state independently.

  6. 06

    Only then update one layer; keep the original backup until a cold relaunch and native-save test pass.

Decision and diagnostic table

LayerTypical dataRestore risk
Base/config overrideFrontend settings and scoped CFGNarrower override may win
Core optionsCore-specific OPT valuesOption names can change
RemapRetroPad-to-core mappingController enumeration can differ
Save/stateNative progress / snapshotStates are more version-sensitive

Copy configured directories, not guessed paths

Android packages can use private, shared, or user-selected storage. RetroArch's Directory screen is the evidence for the active location.

Restore layers one at a time

A working native save does not prove a state is compatible, and a loaded remap does not prove an override was restored. Test each artifact by the behavior it owns.

Same-version restore comes first

A same-version rehearsal separates backup completeness from migration compatibility. It also gives a reversible baseline before any app or core update.

First-party sources

Related guides