REAPER Audio Workflows

REAPER keeps crashing or freezing? How to find the cause

By StudioRescue Editorial

Published September 24, 2026

Crashing is the one REAPER problem that stops everything. You cannot mix around it or EQ it away, and every crash costs you the take you were in the middle of. The good news is that repeat crashes are rarely mysterious. They are usually repeatable, and anything repeatable can be narrowed down.

The mistake almost everyone makes is changing several things at once: reinstalling REAPER, updating drivers, deleting plug-ins, and raising the buffer, all in one afternoon. If the crashing stops you still do not know why, so it comes back a month later. Change one thing at a time instead, in the order below.

First, describe the crash accurately

When it happens matters more than what the error box said. Before you change a setting, watch for one more crash and note the moment it happens.

The two-minute isolation test

REAPER's user guide documents three modifier keys you can hold while the program starts. Each one removes a whole category of suspect. Fully quit REAPER first, then hold the key down as you launch it and keep holding until the main window appears.

Write down which switch changed the behaviour. That single fact decides which of the next three sections you need, and you can skip the other two.

If it is a plug-in

This is the most common answer by a wide margin, and it is worth saying plainly: it is nearly always a third-party plug-in, not a stock one. The Rea-series plug-ins are built by the same people who build REAPER and are tested with every release.

Narrow it to one plug-in

If the crash happens during the scan, the last plug-in named on screen before the crash is your first suspect. Move that plug-in's file out of your VST folder to a temporary folder somewhere else, then let REAPER scan again normally. If the scan completes, you have found it. If you cannot tell which one, move half your third-party plug-ins out, scan, and keep halving until the crash follows one file.

That folder structure is worth understanding before you start moving files around, and it is covered in how to install VST plugins in REAPER, which also explains the re-scan REAPER needs after you change anything in those folders.

Let a suspect plug-in crash on its own

REAPER can run a plug-in outside its own process, so that if the plug-in dies it takes only itself down and REAPER survives. The user guide covers this under section 16.18, "Bridging and VST Plug-in Run Mode". There are two places to set it: a default for all plug-ins under Options › Preferences › Plug-ins › Compatibility, and a per-plug-in override by right-clicking the plug-in in the FX browser and choosing the run-as option.

The choice is between running the plug-in natively inside REAPER, running bridged plug-ins together in one shared external process, and giving one plug-in its own dedicated process. A dedicated process costs some CPU and memory, which is why it is not the default, but it is the setting that keeps one unstable plug-in from taking your session with it.

Then decide what to do about it

Once you know which plug-in it is, you have three honest options: update it, run it in its own process and accept the overhead, or stop using it. Check the developer's page for a version that names your operating system. A plug-in that has not been updated in several years is a plug-in you should expect to lose eventually.

If it is one project

When REAPER starts fine but one session kills it, work inwards rather than giving up on the file. In REAPER's Open Project dialog there is a checkbox labelled Open with FX offline (recovery mode). Tick it, and the project loads with every plug-in and instrument inactive, which is often enough to get a session open that crashed on every normal attempt. From there, bring tracks back online a few at a time until the crash returns. The last group you enabled contains the problem, and from there it is the plug-in process above.

If the project will not open at all, that is a different job, and a recoverable one more often than people expect. How to recover a lost or crashed REAPER project covers the backup files REAPER writes and where your recorded audio actually lives, which is on disk and usually intact.

If it is the audio device

Crashes and freezes that arrive during playback, especially after crackling or dropouts, usually point at the audio device rather than at a plug-in. Start by confirming REAPER is talking to the device you think it is, which is the first half of REAPER has no sound and how to fix it. Then raise the buffer size and watch whether the glitching goes before the crashing does.

If the machine is simply running out of headroom, the symptom set is different: the performance meter climbs, you hear stuttering, and a crash is the end of a process that started as a glitch. That is covered separately in how to fix high CPU usage in REAPER, and a buffer raised for stability has a cost while tracking that is explained in how to fix recording latency in REAPER.

Turn on the evidence before the next crash

You can make the next crash more informative than the last one.

• On Windows, REAPER's installer offers an option the user guide describes as "Configure Windows to save REAPER crash dumps. This option causes diagnostic information to be saved in the event of REAPER crashing." The guide also states that by default this option is set to off, so if you never ticked it, nothing is being saved. Re-run the installer over your existing install and enable it.
• On macOS, the system writes the report for you. Apple's Console app lists them under a Crash Reports category in the sidebar, and crash report names carry the .ips extension. Find the newest one named for REAPER after a crash.

Be realistic about what you will get. These files are written for developers, and most of a crash dump will mean nothing to you. What they are genuinely good for is spotting a plug-in's name or its file appearing near the top of the report, and for attaching to a bug report if you take the problem to the plug-in developer or the Cockos forum.

Protect your work while you are diagnosing

Do not run this whole process on the session you care about. Duplicate it, work on the copy, and make sure auto-save and timestamped backups are on before you do anything else. The settings and the recovery routine are in the crashed project recovery guide, and turning them on takes about a minute. It is the cheapest insurance in the whole program.

What this will not fix

Isolation tells you where the crash lives. It does not repair everything it finds.

• It will not fix failing hardware. If the machine also crashes outside REAPER, or under load in other programs, suspect memory, storage, overheating or power before you suspect any plug-in.
• It will not make an abandoned plug-in compatible. Running it in its own process can stop it killing REAPER, but a plug-in that has not been updated for your operating system may still refuse to work correctly.
• It will not recover the take you lost. Whatever was unsaved at the moment of the crash is a recovery question, not a crash-cause question.
• It will not tell you why in plain English. Crash dumps are diagnostic data, not explanations, and you should not expect one to name your problem in a sentence.
• It will not help much if the crash is not repeatable. A crash that happens once a fortnight with no pattern cannot be isolated by this method, because you cannot test a change against it.