Where Are Saved Effects Files Stored in REAPER?

If you've been building up a collection of custom effect chains, EQ presets, or plugin settings in REAPER and suddenly can't locate them, you're not alone. REAPER's file structure is flexible by design — which means your saved effects files could be sitting in a few different places depending on how your installation is configured and what type of effect data you saved.

What REAPER Actually Saves When You Save an Effect

Before hunting for files, it helps to know what REAPER stores and in what format. There are several distinct types of "saved effects" in REAPER:

• FX Presets — Parameter snapshots saved directly within a plugin instance
• FX Chains — Groups of chained plugins saved as .RfxChain files
• Track Templates — Full track configurations including FX chains, saved as .RTrackTemplate files
• VST/Plugin State Files — Some plugins save their own preset files in their own folders

Each of these has a different default save location, which is why the answer isn't always a single folder.

The Default REAPER Resource Path 📁

REAPER stores most user-generated data — including effect-related files — in what it calls the Resource Path. This is the master folder for your REAPER configuration.

To find your exact Resource Path, open REAPER and go to:

Options → Show REAPER resource path in Explorer/Finder

This opens the folder directly. On most systems, the default locations are:

Everything described below lives inside this resource path unless you've customized it.

Where FX Chain Files Are Stored

FX Chains are some of the most commonly saved effect files. When you right-click a plugin chain in REAPER and choose "Save FX Chain," REAPER saves a .RfxChain file to:

You can also create subfolders inside the FXChains directory to organize by instrument type, project style, or workflow — and REAPER will reflect that folder structure in its browser.

Where FX Presets Live

FX Presets are slightly different. These are individual parameter snapshots for a specific plugin. REAPER saves them in:

Preset files typically carry the .ini extension and are named after the plugin they belong to. This means all your saved EQ curves, compressor settings, and reverb configurations for a given plugin are bundled into a single .ini file per plugin.

Track Templates and FX Together

If you saved an entire track — including its full FX chain — as a Track Template, those files are stored in:

Track templates use the .RTrackTemplate format and are a common way to carry complete signal chains (including effect settings) between projects.

Portable vs. Standard Installation 🔧

This is where things get more variable. REAPER supports a portable installation mode, where the entire resource path is kept in the same folder as the REAPER executable rather than the default system location. This is popular for users who run REAPER from a USB drive or want a fully self-contained setup.

If you're running a portable install, your FX chains, presets, and templates will be in subfolders right alongside reaper.exe (Windows) or the REAPER app bundle — not in AppData or Library.

How to tell which mode you're in: The "Show REAPER resource path" option in the Options menu will always point you to the correct location regardless of installation type.

Third-Party Plugin Presets Are a Separate Case

Not all effect presets are controlled by REAPER. Many VST, AU, and VST3 plugins manage their own preset systems and store files in entirely different locations — typically inside the plugin vendor's own folder structure under AppData, Documents, or the plugin's installation directory.

If you saved a preset within the plugin's own interface (not through REAPER's FX chain system), look in:

• The plugin manufacturer's dedicated preset folder
• Your Documents folder under a plugin-named subfolder
• A custom path set inside the plugin's settings

This is especially common with virtual instruments, sample-based effects, and more feature-rich processors that ship with their own preset managers.

Variables That Affect Where Your Files End Up

Several factors determine exactly where any given effect file is stored on your system:

• Installation type — standard system install vs. portable install
• Operating system — Windows, macOS, and Linux each use different base paths
• What you saved — FX chain vs. preset vs. track template vs. plugin-native preset
• Custom resource path — REAPER allows you to manually redirect the resource path in preferences
• Plugin behavior — third-party plugins may override REAPER's file handling entirely

A user running a portable REAPER setup on Linux who primarily uses native REAPER effects will have a very different file structure compared to someone running a standard Windows install with heavy use of third-party plugins that manage their own preset libraries.

Knowing which category your saved effect falls into — and whether your install is standard or portable — is the part only you can determine from where you're sitting.