Tools and Recommendations

REAPER vs Audacity for podcasting, and what Audacity 4 changed

By StudioRescue Editorial

Published October 17, 2026

Most “REAPER vs Audacity” comparisons you will find were written against Audacity 3 and have not been revisited. That matters right now, because Audacity 4.0.0 was published on 3 September 2026 and is a rebuild rather than an update. Some of what it changed is genuinely nice. Some of it is a list of features its own release notes describe as not yet available. Whether you should switch depends entirely on which of those lists your workflow sits in.

What Audacity 4.0 actually changed

Taking this from Audacity's own 4.0.0 release notes rather than from opinion. The new version is built on a new interface with high-DPI rendering, dockable panels, saved workspace layouts, a home screen, direct clip selection, multi-clip editing, clip grouping, a dedicated split tool, a draggable playhead, seeking without stopping playback, recording from any point on the timeline, ASIO in the official Windows builds and meters in the track headers. For a lot of podcast editing, that is an improvement.

The release notes also list features as not yet available in 4.0:

• Macro Manager and the scripting pipe. This is the one that caused the noise. If you had a saved macro that normalised, trimmed and exported a folder of files, it is not there.
• The Mixer.
• Play-at-speed, which transcribers and interview editors lean on.
• VAMP and LADSPA plugin hosting. Supported formats in 4.0 are VST3, Nyquist, LV2 on Linux and Audio Units on macOS.
• Time Tracks and Note/MIDI tracks, plus, in the release notes' own words, some exporting and rendering features, analyzers and effects.

Two things were removed rather than deferred: the separate Select, Envelope, Draw and Multi-tool modes, whose functions are now context-sensitive, and Sync-Lock, which the transition guide says has been replaced by ripple editing.

On Macros specifically, there is no published date for their return. An Audacity contributor stated on 10 September 2026 that macros are not in 4.0 and may be added to a future version, and the tracking issue is GitHub issue 9407, “Macro manager”. A forum user suggested 4.1 without citing a source, so treat that as a guess rather than a roadmap.

The three honest answers

There is no single verdict here, because the three groups of people asking this question need different things.

What REAPER gives a spoken-word editor

Four things, in rough order of how much difference they make to a podcast workflow.

1. Per-track effect chains that stay put

Each track carries its own FX chain, and you can reorder plugins by dragging them. You can save a chain and load it onto another track later, from the FX window's own save and load FX chain commands. The practical effect is that your voice processing lives on your voice track, your guest's lives on theirs, and neither is baked into the audio.

2. Reusable session templates

Track templates are saved and inserted from the Track menu. Build one session with your mic routing, your chain and your naming, save it, and every future episode starts there. If you want this set up properly, the walkthrough is in how to record a podcast in REAPER, and the chain and template mechanics are covered in how to save and reuse FX chains and track templates.

3. A real mixer and separate inputs

You assign each track's input by right-clicking its record arm button, so two mics land on two tracks and stay independent. That is the difference between being able to fix one person's level and having to fix the whole episode.

4. A stock batch file converter

REAPER ships a batch converter that takes a file list and applies conversion settings to all of it. It is the closest stock replacement for the Audacity macro that people lost, with the honest caveat below. The method is written up in how to batch convert and normalize a folder of audio files in REAPER.

What it costs

Audacity is free. Its own site says it “has always been and will always remain free for everyone”, and the current download is 4.0.1.

REAPER is not free, and the pricing is unusual enough to state exactly. As published on Cockos's purchase page today: $60 for the discounted license, $225 for the commercial license. You qualify for the discounted license if you are an individual using REAPER only for personal use, or if you are an individual or business using it commercially and your yearly gross revenue does not exceed USD $20,000, or if you are an educational or non-profit organization. Before you buy anything, “you get 60 days of evaluation free, with full functionality, and no strings attached”, and a new license includes free upgrades through REAPER version 8.99.

For most independent podcasters that is $60 once. It is still $60 more than Audacity, and that is the whole of the financial case you have to weigh.

What switching will not fix

This is the part the comparison pages skip.

• It will not make your recording sound better. Your mic, your room and your distance from the mic decide most of your sound. A different editor changes none of them.
• It will not rescue a bad take. Room echo, clipping and laptop-mic audio are the same problems in any program. If that is your issue, start with reducing background noise in a podcast recording instead of changing software.
• It will not give you your Audacity macros back. REAPER's batch converter works on files, so it covers convert, trim and level jobs on a folder. Repeating a sequence of edits inside a session is a different mechanism in REAPER, built from custom actions, and you will have to learn it rather than import it.
• It will not be faster in week one. REAPER has far more surface area and almost everything is configurable, which is a strength later and a cost at the start.
• It will not fix an accessibility problem by itself. If you use a screen reader or need high-contrast labels, test that before you commit, in either program. Neither one is a safe assumption.

If you decide to try REAPER, do these three first

1. Install your plugins and confirm they scan. Plugin format and scan-path problems are the most common first-day frustration. See how to install VST plugins in REAPER.
2. Build one session and save it as a track template. Do not start episode two from an empty project.
3. Set your delivery target before you render. Rendering is File then Render, and you can render the master mix or individual stems. For spoken word, pick your loudness target first: how to hit a podcast loudness target in REAPER.