I’ve been spending a lot of time setting up RetroArch across different devices and kept running into the same issue:
Before you even get to cores/playlists, it’s hard to tell what’s actually in your ROM folder.
Especially with:
- mixed systems in one directory
- inconsistent naming
- duplicates
- zipped vs extracted ROMs
So I built a small Windows tool to help with that.
Main feature right now:
⚡ Quick Snapshot
Point it at a ROM folder and it instantly shows:
- detected systems
- file counts per system
- approximate sizes
No hashing, no playlist generation, no changes — just a quick way to understand your library before doing anything else.
After that it can:
- detect systems from file types/folder structure
- handle zipped ROMs
- auto-download DAT files for validation (No-Intro style)
- help organize libraries for cleaner setups
This is the first public build, so I’m mainly looking for feedback from people using RetroArch with larger libraries:
- does system detection match what RetroArch expects?
- does the snapshot help before building playlists?
- any edge cases I should account for?
Download:
https://github.com/cancruiser/RetroLibraryBuilder
Appreciate any feedback.