Skip to content

The libretro folder

Alongside your games sits a second tree, libretro/. RetroXR owns this one: the core downloader fills it in, and you rarely need to open it.

It is worth knowing what is in it, because it is where a stubborn BIOS problem or a corrupted core option actually lives.

Platform Location
Windows %USERPROFILE%\retroxr\libretro
Linux / macOS ~/retroxr/libretro
Quest internal app storage — reachable as libretro/ in the web file manager

On Quest this folder is not next to your games. Your games live in external storage where you can copy files freely; libretro/ is in the app’s own private storage. The web file manager shows both under one root, which is the only place you will see them side by side.

libretro/
cores/ the emulator cores themselves
system/ BIOS and firmware, one folder per core
core_assets/ asset packs some cores need
core_options/ your per-core settings
save/ battery saves
temp/ scratch space
cores_manifest.json what is downloadable, and what you have
core_defaults.json which core each system launches with
firmware_state.json which BIOS files are present

One file per emulator. These arrive through CORES → Download and there is no reason to put them here by hand — a core dropped in manually will not be registered in the manifest.

This is the one you may legitimately need to open. Cores look for their BIOS and firmware here, in a folder named after the core. The PlayStation’s scph5500.bin and friends, the Dreamcast’s boot ROM, the DS firmware — all of it lands under system/.

The BIOS page is the friendlier route: it tells you which files a system wants, by exact name, and where they go.

Your settings for each core, written when you change something in CORES → Manager. If a core is behaving strangely and you want a clean slate, resetting its options from the Manager rewrites the file for you — safer than editing it.

Battery saves — the in-game saves a cartridge would have kept on its own chip. See game saves and backups.

Scratch space. RetroXR copies a core here before running it, so one machine’s core cannot tread on another’s. Nothing in here is worth keeping.

In rough order of what to try:

  1. Reset the core’s options in CORES → Manager. Most odd behavior is a setting.
  2. Check its BIOS in CORES → BIOS / Extras. A missing required file usually shows as a machine that powers on and does nothing.
  3. Re-download the core. It replaces the file in cores/.
  4. Try a different core for that system, if one exists.