libretro / libretro/RetroArch

Feature request: Global base directory for configs, ROMs, saves and assets (NAS/network support)

Open
#18,522 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Feature Description

I would like to request a feature that allows RetroArch to work using a single global base directory pointing to a NAS or network share (SMB).

The idea is to define one base/root directory, and RetroArch would automatically resolve all internal folders relative to it.


Example (SMB / NAS)

Base directory: //192.168.15.150/RetroArch

RetroArch would internally resolve:

  • ROMs → //192.168.15.150/RetroArch/roms
  • Saves (SRAM) → //192.168.15.150/RetroArch/saves
  • Save States → //192.168.15.150/RetroArch/states
  • Thumbnails / Images → //192.168.15.150/RetroArch/thumbnails

Use Case

This would greatly improve support for:

  • NAS-based emulation libraries
  • Multi-device environments (Android, Linux, Windows, TV boxes)
  • Centralized backups and portability
  • Users who want all RetroArch data stored on shared/network storage

Currently, each directory must be configured individually, which becomes difficult and error-prone when using SMB paths, especially on Android.


Expected Behavior
  • A single setting such as "Base Directory" or "User Data Root"
  • All other directories inherit from this base by default
  • Advanced users can override individual directories if needed

Platforms Affected
  • Android (SMB paths are especially painful to configure)
  • Linux
  • Windows
  • Any platform using network-mounted storage

Additional Notes

This feature would make RetroArch significantly easier to use in modern NAS-based setups and multi-device environments.

Thank you for your work on RetroArch.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is identified in the issue. Start by locating RetroArch’s existing directory settings and path-resolution code, then trace how Android, Linux, and Windows handle network paths. Done means one base directory supplies defaults for the listed folders while individual overrides continue to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.