Home / Guides / Record system audio in Reaper

How to Record System Audio in Reaper

Reaper doesn't ship with a built-in way to record system audio — whatever's playing through Spotify, YouTube, Zoom, your browser, or any other app — into a project. This guide walks through a clean six-step workflow using AudioRoute Capture: no aggregate device, no virtual driver wiring, no Audio MIDI Setup. Works on both Mac and Windows.

Updated May 2026 macOS 14.5+ or Windows 10+ Reaper 6.x+ ~5 minutes

Why this is hard by default

Reaper can record audio from any input device — an audio interface, a USB microphone, a built-in mic. But "system audio" isn't a single device. Your OS routes whatever's playing through whatever output you've selected (built-in speakers, headphones, audio interface, AirPlay), and there's no built-in "system output as input" device to pick.

The conventional workarounds all treat system audio as a routing problem — they install a virtual audio device that pretends to be a speaker, then you redirect your system output to it. On Mac that means BlackHole + an aggregate device in Audio MIDI Setup so you can still hear what's being routed. On Windows it's VB-Cable or VoiceMeeter with similar manual wiring. Both work, but they hijack your output routing and break the moment you change devices.

AudioRoute takes a different approach. Instead of rerouting your output through a virtual device, it quietly observes whatever your system is already playing. Your speakers, headphones, or audio interface keep working exactly as they did, and AudioRoute simply gets a parallel copy of the audio to deliver into Reaper. No aggregate device, no rerouting, no driver tweaking. More on how it works under the hood if you're curious.

Reaper is one of the friendlier DAWs for this workflow because it doesn't filter plugins by AU/VST type the way some hosts do — AudioRoute Capture shows up in the standard VST3 instrument list and goes on any track you like. The whole flow is six clicks.

What you'll need

• macOS 14.5 (Sonoma) or later, or Windows 10 (build 20348) or later.
• Reaper 6.x or later — this guide was written using Reaper 7.73 on macOS, but the workflow is identical on Windows and on older versions.
• AudioRoute — the free 14-day trial is enough to try the whole workflow. €29 lifetime license once you're sold.

Once AudioRoute is installed, Reaper will pick up AudioRoute Capture on its next plugin scan. If it doesn't appear, force a rescan in Reaper → Settings → Plug-ins → VST → Re-scan.

Step 1
Add a new track

Open your Reaper project, or start a new one. Click the + button at the top of the track list (or use Track menu → Insert new track, shortcut Cmd/Ctrl+T). An empty track appears.

Step 2
Open the track's FX chain

On the new track's header, find the FX button (small grey button just to the right of the Mute/Solo buttons). Click it.

Step 3
Add AudioRoute Capture

The Add FX to Track 1 dialog opens. In the filter box at the top, type audio — the list narrows to AudioRoute entries. Click VST3i: AudioRoute Capture (AudioRoute), then click Add.

If it's not in the list, your VST3 scan probably hasn't picked it up yet. Go to Reaper → Settings → Plug-ins → VST and click Re-scan, then reopen the Add FX dialog.

Step 4
Enable Output to DAW

The AudioRoute Capture plugin window opens. The first time you load it, you'll see an "⚠ Output to DAW is muted" warning with a big blue Enable Output to DAW button. This is intentional — the plugin starts in a safe state on first launch so it can't accidentally create a feedback loop before you've finished setting up your routing. The meters above are already moving, which confirms the daemon is capturing system audio; it's just not yet being passed through to the DAW track.

Click Enable Output to DAW. The warning disappears, the status flips to a green ✓ Output to DAW, and the plugin starts sending captured audio into the track.

You'll also see a checkbox labeled "Always enable (I'll use Sends Only)". Leave it unticked for now — tick it later only once you've set up Sends Only routing (covered in Common gotchas below). It's there to bypass the safety mute on future loads, which only makes sense after you've eliminated the feedback path the safety mute exists to prevent.

Step 5
Arm the track for recording

Close the FX window. On the track header, click the red record-arm circle (left side of the track controls). It lights up red when armed, and the track meter starts following the audio flowing through AudioRoute Capture.

Step 6
Hit global Record

Press the global Record button in the Reaper transport (large red circle, top-centre), or use the shortcut Cmd/Ctrl+R. The captured audio is recorded onto the armed track as a normal audio item — the same kind of item you'd get from recording a microphone or audio interface input. Edit it, glue it, render it, drop it into any project.

That's the whole setup. The first time it feels like a lot of clicks; every project after that takes about ten seconds because the AudioRoute plugin and the routing both persist in saved Reaper templates.

Common gotchas

Recorded file is silent even though meters were moving

By default Reaper records the track's input, not its FX output. If your record-armed track has its input set to a real audio interface (or no input at all) and you forgot to switch it, the recording will be silent regardless of what the AudioRoute plugin is doing.

Fix: right-click the track's record-arm button and choose Record: output → Record: output (stereo). The track will now record whatever the FX chain outputs — which is exactly what we want here. (Reaper sometimes sets this automatically when you add an instrument FX; this gotcha exists for the case where it doesn't.)

Feedback loops during recording

If you hear a feedback howl or runaway oscillation while recording, here's what's happening: the captured audio is being played back through your output (speakers or headphones), AudioRoute picks it up again, and the signal loops.

The cleanest fix is to stop sending the captured signal to your output at all. On the track holding AudioRoute Capture, click the small speaker icon next to the record-arm to toggle monitor off — the track still records, but it no longer plays back through your master out, so AudioRoute can't pick its own signal up again.

As an alternative, if the routing tweak feels fiddly, wear headphones during recording. Less surgical but often quick enough to get a clean take.

What does the "Mute Output" button in the plugin do?

The Mute Output toggle inside the AudioRoute Capture plugin window stops the plugin from sending audio to the DAW entirely. It exists for scenarios where you only want to use AudioRoute's standalone tray recorder (or its virtual input device, on macOS) and don't need the DAW path active.

My recording sounds quiet (or too loud)

The plugin passes audio through at unity gain by default. Check the Gain slider in the plugin window — it should be at 0.0 dB unless you've adjusted it. The L/R meter levels you see in the plugin are exactly what'll be written to disk on the track. If you need to attenuate or boost, do it with the Gain slider in the plugin (before recording) or as a fader move on the track during playback.

Shortcut: skip Reaper, capture straight to WAV

If your goal is just "I need a WAV file of what's playing on my system" and you don't need DAW editing, AudioRoute can do that directly from the tray app. No Reaper project, no FX chain, no record-arming.

Click the AudioRoute icon in your menu bar (macOS) or system tray (Windows) → Start Recording. It captures to ~/Music/AudioRoute/ by default (configurable in preferences) at your chosen sample rate and bit depth. Click Stop Recording when done. The file is ready to drop into anything that opens a WAV.

Same plugin under the hood, zero DAW setup. Useful for quick one-offs — capturing a snippet of a lecture, grabbing a sample from YouTube, recording a Zoom call without setting up a session.