REAPER Audio Workflows

REAPER project folder too big? How to clear out unused takes and media safely

Published November 8, 2026 · Updated November 8, 2026

Quick answer

REAPER keeps the audio file for everything you record, including takes you rejected and items you deleted from the timeline, so a project folder only ever grows. The fix is a cleanup in the right order: decide which takes you are keeping and remove the rest from the items, save, then run File › Clean current project directory and send the files it lists to the Recycle Bin rather than deleting them outright. Play the song through before you empty the bin. It is fully fixable, and nothing is lost if you keep the Recycle Bin step.

A song that started as a few vocal takes can end up as several gigabytes of WAV files. Forum threads asking about this go back to at least 2008, and the pattern is always the same: hundreds of files in the folder, most of them not used, and no idea which are safe to remove. One poster deleted the contents of a folder by hand and lost most of the project. That is the outcome to avoid.

The good news is that REAPER already knows which files the project uses. You just have to tell it which takes you no longer want first, because a take you rejected but left inside an item still counts as part of the project.

Why the folder keeps growing

What is taking spaceWhy it staysHow to clear it
Rejected takes from loop or overdub recordingThey are still takes inside an item, so they belong to the projectRemove them from the item first (Step 2)
Items you deleted from the timelineDeleting an item does not delete its file from diskClean current project directory (Step 4)
Takes you kept when you stopped recordingREAPER can save every recording automaticallyClean them out, and decide at the stop prompt next time
Backup files (.RPP-bak, timestamped backups)Your backup settings keep previous versionsUsually small, because project files are text. Check your backup settings
Peak files (.reapeaks)They store the waveform drawing for each fileLeave them. REAPER builds them again when needed

The user guide describes this directly: as a project evolves it accumulates rejected tracks, overdubs and deleted items that are no longer required, and the Clean command exists to remove them. On most vocal projects the first two rows are where the gigabytes are.

Before you start: protect yourself

Step 1: See what the project actually uses

Open View › Project Media/FX Bay and go to the Source Media page. The user guide says it lists each media file once and shows in the Usage column if a file is used more than once. The Media Items page lists only the items actually in use. This gives you a picture of what the song depends on before you remove anything, and it is the same place to look if something goes offline later.

Step 2: Decide on takes, then remove the ones you do not want

If you recorded several takes per item, finish your comp first. The method is in how to comp vocal takes in REAPER. Once you are sure which take you want in each item:

Both commands work on the project, not on the disk. The files are still in the folder afterwards. That is fine: they now no longer belong to the project, which is what lets Step 4 find them.

Not sure yet? Keep the takes

If you might want an alternative line later, leave that item alone. Crop to active take is a commitment. You can always clean again at the end of the song, and disk space is cheaper than a take you cannot sing again.

Step 3: Save the project

Press Ctrl+S. This makes the project file on disk match what you see before you clean, and it is the version you will reopen in Step 5 to check.

Step 4: Run Clean current project directory

Choose File › Clean current project directory. According to the user guide, the Project Directory Cleanup window shows the project folder name and lists the files that are in the project directory but do not belong to the current project. There is an Explore button if you want to look at the folder itself.

  1. Select the files. Click one, Ctrl+click to add more, or click the first and Shift+click the last to select a range.
  2. Choose to send them to the Recycle Bin. The guide notes you can either delete them permanently or send them to the Recycle Bin. Pick the bin.
  3. Click Remove Selected Files.

Look down the list before you remove anything. If you see a file you recognise as part of the finished song, stop and find out why it is listed. The usual reason is that it belongs to a different project in the same folder.

Step 5: Check, then empty the bin

Close the project and open it again. Play it from start to finish, or at least jump through every section. If any item shows as offline, restore that file from the Recycle Bin and follow how to fix media offline in REAPER. Only when everything plays should you empty the Recycle Bin. That is the moment the space is really freed.

When several projects share one folder

The guide describes the cleanup as comparing the folder against the current project. It does not say it checks other projects. One user reported in 2014 that files used by another project open in a second tab were left alone, but that is a single report, not documented behaviour. Assume that any file used only by a song that is not open will be listed, and that removing it will break that song. The REAPER Blog gives the same warning for the shared default media folder: if projects do not have their own folders, there is no way to know which file belongs to which project. The long-term fix is one folder per song, set up as shown in how to set up a new REAPER project before you record.

Stop it growing next time

What this cleanup will not do

The guide’s shortcuts are for Windows. On a Mac, Ctrl is usually Cmd and Alt is Option, and the Recycle Bin is the Trash.

Takeaway

A REAPER folder grows because REAPER never throws a recording away on its own. Finish your comp, remove the takes you do not want with Crop to active take, save, then run Clean current project directory and send what it lists to the Recycle Bin. Reopen the song and play it through before you empty the bin, and never run it on a folder that other songs share.

Sources

  1. Geoffrey Francis, Up and Running: A REAPER User Guide v7.85 (November 2026), official HTML edition: section 22.11 Project and File Management (projects accumulate rejected tracks, overdubs and deleted items; File, Clean current project directory lists files in the project directory not belonging to the current project; Explore button; delete permanently or send to the Recycle Bin; Remove Selected Files). dlx.reaper.fm/userguide/html
  2. Same guide: section 8.7 Take Menu Command Summary (Delete active take, X; Crop to active take, Alt Shift T, removes all non-active takes from selected items); section 12.6 The Project Media/FX Bay (Source Media lists each file once with a Usage column; Media Items lists only items in use); section 1.25 REAPER File Types (.RPP stored as text, .RPP-bak, .reapeaks); section 22.9.2 Peaks Generation; section 3.37 Preference Settings for Recording (prompt to save/delete/rename files when recording is stopped; if disabled, files are saved automatically); section 15.10 Keyboard Shortcuts for Recording (Stop save all and Stop DELETE all recorded media); section 22.3.1 Project Backups (all off on first install; timestamped backups to a Backups subdirectory). dlx.reaper.fm/userguide/html
  3. The REAPER Blog, “Clean Up The REAPER Media Folder” (September 2024): a shared media folder cleaned from over 570 files, and the warning that without separate project folders you cannot tell which media belongs to which project. reaper.blog
  4. HomeRecording.com forum, “Does Reaper clean up after itself?” (July 2008): a 50 GB folder, emptied by hand, and most of the project lost. homerecording.com
  5. HomeRecording.com forum, “Rookie file saving Q” (April to May 2020): a moderator recommending Clean current project directory, and a poster reporting over 300 unused WAV files in one project. homerecording.com
  6. Ultimate Metal forum, “Reaper: Clean Current Project Directory” (March 2014): a single user report that files used by a second open project were not removed. ultimatemetal.com
  7. The Fretboard forum, “Reaper media files and memory” (2014): freeing drive space from old project media. thefretboard.co.uk

Every source above was retrieved and checked on November 8, 2026. REAPER behavior is taken from the official user guide, read in its HTML edition; forum threads are used only as evidence that the problem is real. The statement that non-active takes still count as part of the project is our reading of the guide (the cleanup lists files not belonging to the project, and takes are part of items), not a sentence from it. We did not test these steps in REAPER for this article.