Where Does RomM Store ROMs and Config?
Where RomM keeps its ROM library, resources, and config.yml in self-hosted installs.
Last updated
RomM organizes ROMs in a library folder plus a resources tree (covers, saves, states) and a config.yml beside the compose file. The database tracks it all; the folders hold the bytes.
Docker is the normal deploy, so host paths depend on your volume binds. The config file decides library roots, which means two installs rarely share literal paths. Read config.yml first on any unfamiliar box.
Where RomM stores this, by platform
/romm/library/
Library plus resources/ and config.yml; database alongside (sqlite file or separate container per setup). Persist all three volumes; exact names may vary by RomM version.
Frequently asked questions
Which RomM volumes must persist?
Mount persistent volumes for the library, resources, and database before first run (see the compose file). Without them, rescans and metadata vanish on container replace. Back up the database plus the library together.
How do I migrate a RomM install?
Copy config.yml, the library tree, and the database dump to the new host with matching RomM version. Rescan after the move so paths re-index. Exact internal names may vary by release; keep the compose file alongside.
Notice an outdated path? Let us know.