REAPER Audio Workflows

Plugins missing after opening a REAPER project on another computer? Here is the fix

By StudioRescue Editorial

Published October 28, 2026 · Updated October 28, 2026

This is the classic laptop-to-desktop problem. You record on one machine, copy the session to another to mix, and REAPER greets you with a message about missing items. The vocal sounds dry, the drum bus has no glue, a synth track is silent. It feels like the project broke. It did not. It is just running on a computer that does not have all the same tools installed.

If your audio items are also showing OFFLINE, that is a separate problem with a separate fix, covered in REAPER says media offline? How to get your audio back. This article is about the FX.

Why this happens

A REAPER project file records which plugins sit on which tracks, in what order, and with what settings. It does not contain the plugins themselves. Those are installed separately on each computer. When the project opens somewhere a plugin is not installed, there is nothing for REAPER to load.

The official REAPER User Guide describes exactly this case. If an FX used in a project has been deleted or moved since the project was saved, REAPER shows a message about missing items when you open it. The project still loads, and the FX "will still be listed in the track FX chain but it will not be available."

REAPER's own stock plugins, the ones that start with "Rea" such as ReaEQ and ReaComp, plus the JS effects, come with REAPER. They are on every computer that has REAPER installed, so they are almost never the ones that go missing.

Before you touch anything

StudioRescue's understanding, which the user guide does not spell out, is that REAPER keeps each missing plugin's saved settings with its entry in the project file. That is why, once the same plugin is installed and the project is reopened, it normally comes back as you left it. Test this on your copy before relying on it. If you delete the entry and insert a fresh instance later, you start that plugin from its defaults.

Step 1: make a list of what is missing

Do not rely on memory or on the pop-up alone. Two places in REAPER show you what the project uses:

• The FX chain on each track. Open the FX window on any track that sounds wrong. The missing plugin is still listed by name. Note the prefix in front of the name too, such as VST:, VST3: or CLAP:, because that tells you which format the project expects.
• The Project Media/FX Bay. Open it from View › Project Media/FX Bay and go to the FX page. The user guide describes this page as listing the FX plug-ins used in the project, so it gives you the whole list in one place instead of track by track.

Write down each plugin, its format, and which tracks use it. Do not forget item FX and the master track.

Step 2: install the same plugins on this computer

For each missing plugin, install it on the new machine and make sure REAPER can see it. The order that works:

If a plugin crashes REAPER on the new computer

Sometimes a plugin is installed but will not run properly on the second machine, often because of a version difference. If the project crashes or freezes on open, use REAPER's recovery option. In the File › Open project dialog, tick Open with FX offline (recovery mode). The user guide explains that this opens the file with all FX set offline, so you can bring them back online one at a time and find the one causing trouble.

More general crash causes are covered in REAPER keeps crashing or freezing.

If you cannot install the plugin

Maybe it was a trial, it only exists for the other operating system, or you have run out of licence activations. You have three honest options:

• Print the sound on the original computer. Go back to the machine that has the plugin and freeze the track or apply the FX to the audio (both explained below). The audio then plays on any computer, plugin or not.
• Replace it with something you do have. Remove the missing entry and insert an equivalent, often a stock REAPER plugin. The user guide lists this as one of the two remedies. The Project Bay can also replace an FX throughout the project from its FX page. You will be setting the new plugin by ear, so expect it to sound different.
• Leave it and carry on. If the missing plugin was a small polish move, you can mix without it and decide later. Keep the entry in place so you can restore it on the original machine.

Move the next session without this problem

Do these on the original computer before copying a project anywhere, especially if the other machine is not yours or does not have the same plugins.

1. Copy all the media with the project

Use File › Save Project As and tick the option to copy all media into project directory. That puts every audio file in one folder with the project, so nothing points to a drive the other computer does not have. It does not copy plugins, which is why the next steps exist.

2. Freeze the tracks that rely on plugins the other machine lacks

Right-click the track, open the Render/freeze tracks menu and choose a Freeze command. The user guide explains that freezing replaces the track's contents with a single rendered audio item with the online FX applied, removes those FX from the chain, and that Unfreeze tracks restores the FX chain as it was. The frozen audio plays anywhere. To change those settings later, you unfreeze on a computer that has the plugin.

3. Or apply the FX to the item

For a single item, Apply track/take FX to items as new take renders the processed sound as a new take on the item. The original take stays on the item, so you can switch back to it.

4. Lean on stock plugins for anything that travels

Anything built only from REAPER's stock plugins opens the same on every computer with REAPER installed. If you move between machines often, building your everyday chains from stock plugins and saving them as FX chains removes most of this problem. How to save and reuse chains is in how to save FX chains and track templates in REAPER.

5. Sending to someone else? Send stems

If another person is mixing, do not expect their plugin collection to match yours. Render each track to audio and send those files with clear names. The handoff process is in how to prepare vocals for a mixing engineer in REAPER.

What this will not fix

• It will not make a plugin run on a system it was not built for. If the developer does not make a version for that operating system or processor, no REAPER setting changes that.
• It will not get around licensing. A plugin that is not authorised on this computer may load in demo mode, stay silent, or not load at all, depending on the developer.
• It will not make a replacement plugin sound identical. Settings do not transfer between different plugins, even ones that do the same job.
• It will not fix offline audio. Missing media is a different problem with its own fix, linked at the top.