How to organize your REAPER projects

Organizing REAPER projects comes down to four habits: keep every project under one top-level folder, always tick Create subdirectory for project when you save so each song owns its own directory, copy your media into that directory rather than referencing it from wherever it happened to land, and keep the backup files under control instead of letting them pile up beside your real work. REAPER is unusually good at the file-system side of this already, which is why the thing REAPER users actually run out of is not tidiness. It is a way to see what is in a hundred project folders without opening a hundred projects.

Why REAPER libraries go wrong

REAPER hands you more control over where things go than almost any other DAW, and that cuts both ways. Used deliberately, you end up with a genuinely clean tree: one folder per song, media inside it, everything portable. Used casually, you end up with the two classic REAPER messes.

The first is the flat dump. If Create subdirectory for project was not ticked when you saved, the project file and every recorded take land in whatever folder the dialog was pointing at, so a single directory ends up holding four songs and three hundred audio files with no obvious way to tell which belongs to which. The second is backup sprawl. REAPER's automatic backups are a genuinely excellent safety net, and left on defaults for a couple of years they leave a trail of near-identical files beside every project, so the folder listing is mostly noise and the real project file is somewhere in it.

1. One folder above everything

Whatever the structure below it, keep a single top-level folder that every project lives under. This is the boring step that makes every other step possible: one location can be searched, backed up and scanned as a set, where projects scattered across a desktop, a Downloads folder and two external drives cannot. REAPER's own project templates and its recent-projects list will happily point wherever you like, so there is nothing to fight.

2. Always create a subdirectory

When you save a new project, tick Create subdirectory for project. It costs nothing at the time and it is the single decision that makes a REAPER project portable, because the project and everything it recorded then live in one place you can move, zip, back up or hand to someone. Once that is a reflex, a whole class of "where did that take go" problems stops happening. If you record often, it is also worth checking Project Settings → Media so that new recordings are written into the project directory rather than a global scratch path.

3. Copy media in before you archive or send

Like every DAW, REAPER references media by its location on disk, so a project that points at files outside its own folder is one cleanup away from opening with gaps. The fix is built in: File → Save project as offers to copy all media into project directory, which gathers everything the project uses into one place. Do that for anything you are archiving, sending to a collaborator, or expect to reopen in a few years. If you want to go the other way and reclaim space, File → Clean current project directory will show you the media in the folder that the project no longer uses, which is a very satisfying button on an old song.

4. Decide what happens to backups

REAPER's backup behaviour lives in its preferences, and the two settings worth an opinion are how many backups to keep and whether they go beside the project or into a Backup subfolder. Putting them in a subfolder is the low-effort win: the safety net stays exactly as good, and your project folders stop being a wall of near-identical filenames. Keep the backups. Just stop looking at them.

5. Bounce anything worth remembering

A project file holds no audio you can hear without loading REAPER. Render a reference of every idea worth revisiting into a consistent renders or exports folder, named to match the project. This is what turns a back catalog into something you actually browse, because auditioning fifty ideas takes two minutes with renders and an afternoon without them.

6. The part that always rots

Steps one to five are habits, and habits mostly hold. What fails for everyone is the searchable list. Every .rpp file already knows its tempo, which plugins the tracks are running, and the exact REAPER version that saved it. All of it is sitting in plain text that nothing outside REAPER shows you, so answering "which of my projects are around 140 BPM, still unfinished and using that synth I am about to uninstall?" means opening projects one at a time.

What Saltado Sessions does for REAPER

Saltado Sessions scans wherever your projects live, reads what each .rpp already knows, and gives you one searchable, sortable, ratable library. REAPER projects are folder-grouped, the same way Ableton projects are, so a folder holding a project plus its media is one row, and several project files in one folder are shown as that project's files with the most recently modified one treated as the main version. Backup files and Backup folders are skipped, so a project that has been saved four hundred times is still one row.

Here is the honest full picture for .rpp files rather than a feature list that quietly assumes Ableton.

The plugin row is worth pausing on, because it is the one that surprises people. REAPER's project format is plain text and it names every VST and VST3 instance a project loads, so Sessions can show you which plugins each project actually uses, and the Library view can tell you how many projects depend on a given plugin before you uninstall it. Key is the honest no: the format stores no project-level key, so nothing can show you one that is not there, and you can type your own in, which is then treated as yours and never overwritten by a later scan. The deepest reads, meaning the per-sample list, missing-sample detection, the arrangement view and the browser-based compatibility checker, are built on Ableton's .als format and are not claimed for REAPER. Everything that does not depend on a session's internals works identically: ratings, statuses, tags, notes, search, collections, previews, loudness metering, backups, and the record of which labels heard which track.

Common questions

Do my REAPER backup files show up as extra projects?

No. REAPER writes its automatic backups with a different extension, and folders named Backup are skipped during a scan, so neither turns into a duplicate row beside the real project. You get one entry per project rather than one entry per save.

Does Saltado Sessions read the key of a REAPER project?

No, because the REAPER project format has no project-level key to read. Tempo is stored in the project header and is read for every project, and so is the list of VST and VST3 plugins your tracks use. You can type a key in yourself, which is then treated as yours and never overwritten by a later scan.

What if I keep several REAPER projects in one folder?

That folder is treated as one project, with the most recently modified project file as the main one, and the others listed as its files. This suits the common REAPER habit of keeping a mix version and an edit version of the same song side by side. If they are genuinely different songs, give each one its own subdirectory and they will list separately.

Will it move or change my REAPER projects?

Scanning is read only. The app reads your project files where they already sit and writes what it learns to its own local database, so a scan never renames, moves or rewrites anything. The actions that do touch disk, such as renaming a file or deleting one to the recycle bin, are buttons you press deliberately.

Working in more than one DAW? The same library holds all of them side by side. There is a companion guide to organizing Ableton Live projects, which goes deeper because the .als format gives up more, and one for FL Studio projects. You can also start from the overview if you want to see the whole app first.