Podcast and Spoken-Word Audio

How to split one long recording into several podcast episodes in REAPER

Published November 10, 2026 · Updated November 10, 2026

Quick answer

If you recorded several episodes in one sitting, you usually do not need to cut the file apart or build a project per episode. Do the cleanup that applies to the whole session once, then make one named region per episode and render them all in one pass: in File › Render... set Source to Master mix, Bounds to Project regions, put $region in the file name, and normalize each file separately. You get one file per episode, named after its region. Make the regions after your structural cuts, not before, and check each file before you upload it.

Batch recording is a common way to save time: set up once, record two, three or four episodes back to back, and stop. Some podcasting guides suggest saying a clear spoken marker between episodes, such as a pause and the next episode's title, precisely so the session is easy to split later. The splitting is where people get stuck. The usual workarounds are rendering a time selection over and over, or copying chunks into new projects, and both mean re-entering the same export settings every time.

REAPER has a cleaner route built in. Regions are named stretches of the timeline, and the render dialog can render every region as its own file in one go. It is a small amount of setup that pays back every time you batch record.

One project or one per episode?

Start by deciding whether the episodes should stay together. Both are reasonable; they suit different situations.

Keep one project with regions whenSplit into separate projects when
The episodes share the same people, mics and room, so the same cleanup suits all of themEach episode needs very different processing, or a different guest joined partway through
The editing is light to moderateEach episode needs heavy editing that you want to keep separate, or different people will edit different episodes
You want to render everything with identical settingsYou will publish weeks apart and want to revisit one episode without opening the others

If you go separate, the simplest method is to finish the shared cleanup, then save copies of the project under new names (File › Save project as...) and delete everything outside one episode in each copy. The rest of this article covers the one-project route, which is usually less work.

Step by step in REAPER

1

Do the shared work over the whole session first

Anything that applies to every episode, such as noise reduction, EQ, compression and matching host and guest levels, goes on the tracks once and covers every episode. That is the main saving of keeping one project.

2

Make your structural cuts before you make regions

Remove false starts, long breaks between episodes and tangents first. If you cut with ripple editing on all tracks, everything later in the timeline moves left. Since REAPER v7.62 there is a separate setting for whether ripple editing all tracks also moves regions and markers, reachable by right-clicking the ripple button on the toolbar. The simplest way to avoid surprises is to create regions last, once the cuts are done. The cutting itself is covered in how to cut a long podcast interview down to length.

3

Make one region per episode

Drag a time selection from the start of the first episode to its end, then press Shift+R (or right-click and choose Create region from selection). Hold Shift and double-click the region's icon on the ruler to name it. Repeat for each episode. Include whatever lead-in and tail you want in the final file, such as a second of room tone at each end, because the region edges are exactly where each file will start and stop.

4

Name regions the way you want the files named

The region name becomes the file name in the next step, so use something you will recognise later, such as ep041-guest-name. Keep to letters, numbers and hyphens. If you already have many items, regions or markers to rename, batch renaming in REAPER saves time.

5

Check the episodes in the Region/Marker Manager

Open View › Region/Marker Manager. Every episode should be listed with a sensible start, end and length. Gaps between regions are fine, since they simply will not be rendered. Two regions that overlap by accident will both include the overlap, so fix that here. You can edit a region's start, end or name by double-clicking the value.

6

Put the intro and outro inside every region

A region only renders what sits inside its stretch of the timeline. If each episode needs the theme music, copy the intro and outro items into each region. Do this after the spoken edit is locked, then set up ducking under the voice if you use it.

7

Render all the regions at once

Open File › Render.... Set Source to Master mix and Bounds to Project regions. In the file name box, type $region, or $project-$region if you want the show name in front. Choose your format and settings as you would for one episode; podcast export settings in REAPER covers the choices. Then open Postprocess... and normalize to your loudness target with each file separately selected, adding a true peak brickwall limit if you want one. The render button should now show a file count matching your number of episodes.

8

Check every file before you upload

Open the render folder and confirm you have one file per episode, with the names you expected. Play the first and last few seconds of each file, because a region edge set a second too early or late is the most common mistake and only shows up there.

Rendering only some of the episodes

Which regions the Project regions bound renders follows what is selected in the Region/Marker Manager or the Region Render Matrix (File › Region Render Matrix). To re-render just one episode after a fix, the quickest route is to right-click its region name on the ruler and choose Render region....

Why "each file separately" matters

REAPER's normalize options can treat files separately, match them to the loudest file, or treat them as if they play together. Episodes are heard one at a time, so each should hit the target on its own. A quieter episode normalized "as if they play together" would stay quieter than the rest. For choosing the target itself, see podcast loudness and the -16 LUFS question.

Separate files for each speaker or an editor

If someone else will edit an episode, or you want each voice as its own file, the Region Render Matrix lets you pick tracks per region. Each column is a region and each row a track: tick a track in a region's column and REAPER renders that track for that region, or tick Master mix for the full mix. Then render with Source set to Region render matrix. Use a backslash in the file name to make a folder per episode, for example $region\$track on Windows (a forward slash on Mac), so each episode's stems land together.

What this will not do

If it still goes wrong

  1. Only one file came out. Bounds is probably still set to Entire project or Time selection. Set it to Project regions, and check the regions are selected for rendering in the Region/Marker Manager.
  2. Every file has the same name, or a number instead of a name. The file name box is missing $region, or the regions were never named. Name them and render again.
  3. A file starts mid-word or ends early. That region's edge is off. Fix it in the Region/Marker Manager and re-render just that region.
  4. The regions no longer line up with the episodes. A ripple edit moved the audio but not the regions, or the other way round. Undo, check the ripple-all regions setting on the toolbar ripple button, or move the region edges to match.
  5. One episode is much louder or quieter than the rest. The normalize option was set to treat the files together rather than separately, or normalize was off. Change it and re-render.
  6. An episode has no intro music. The music items sit outside that region. Copy them in and re-render that region.
Takeaway

A batch-recorded session does not need to become several projects. Do the shared cleanup once, make your cuts, then make one named region per episode, with its intro and outro inside it. Render with Master mix, Project regions, $region in the file name and normalize each file separately, then listen to the start and end of every file before you upload.

Sources

  1. Cockos, Up and Running: A REAPER User Guide v7.85, November 2026, official HTML edition: 9.8 Creating and Using Regions (Shift+R, Create region from selection, Shift+double-click to name, Render region from the region's right-click menu); 9.9 Region/Marker Manager; 21.1.1 Wildcards; Render to File options (Bounds including Project regions, Presets, Postprocess normalize each file separately, to loudest file, or as if files play together, brickwall limit to Peak or True peak); 21.10 Rendering Regions and the Region Render Matrix, including the $project\$region-$track folder example. dlx.reaper.fm/userguide
  2. Cockos, REAPER changelog (whatsnew.txt), v7.62, February 28, 2026: setting for ripple-all to affect regions and markers, via action or by right-clicking the toolbar ripple button; v7.63 fix to the same behaviour. Current version at publication: v7.85, November 5, 2026. reaper.fm/whatsnew.txt
  3. Violet Recording Editorial Team, “How to Batch Record Podcast Episodes Fast”, June 2026: spoken marker between episodes to make splitting easier. violetrecording.com
  4. The Podcast Consultant, “Batch Recording Podcasts: Complete Time-Saving Guide”, updated October 2026: batch recording as a time-saving practice. thepodcastconsultant.com
  5. BassChat forum, “Dividing a track into separate songs in Reaper”: a user splitting one long recording into separate exports, with replies suggesting repeated time-selection renders. basschat.co.uk
  6. Adobe Community, “Separating two shows in Audition CC”, July 2017: keeping two shows from one session separate. community.adobe.com

Forum threads and podcasting guides are cited as evidence that the problem is common, not as technical proof. The REAPER steps follow the official user guide; menu wording can shift slightly between versions, so if a label differs on your screen, look for the closest match.