REAPER batch export: map regions to the files you need

A project has several regions, but the delivery brief does not require every track from every region. Perhaps the introduction needs a complete mix while an interview excerpt needs both a voice-only file and a reference mix. Write those combinations down before starting a large render.
REAPER’s feature overview describes its Region Render Matrix as a way to choose particular tracks within particular regions. That makes it useful for a selective delivery map. A matrix full of selections is not automatically the same thing as the editor’s requested file list.
Make each intended combination explicit
Start with the recipient’s requirement. Give every intended file a row containing the region, the source or mix to include, the intended filename and the purpose of that file.
Here is a hypothetical brief, not a rendered project:
| Region | Required content | Purpose |
|---|---|---|
| Introduction | Master mix | Complete reference |
| Answer | Voice track | Separate editing source |
| Answer | Master mix | Reference for the same excerpt |
This brief describes three intended deliverables. It does not ask for every possible region-and-track combination. Keep intentionally omitted combinations visible in your notes so that a missing selection can be distinguished from a deliberate omission.
The blank region delivery map provides one row per intended file. It is a planning ledger, not a REAPER project, render preset or script that changes your session.
Inspect the matrix in the matching guide
Geoffrey Francis’s REAPER 7.85 User Guide, section 21.10 on printed pages 419–420, explains the matrix with region columns and track choices. Its example distinguishes individual selected tracks, an unselected region and a region selected for a master mix. The guide also shows that All tracks includes the folder track in its example.
Inspect your actual project instead of assuming that a folder is merely an organisational heading or that naming a region selects its content. Record which row and region define each intended output. If the matrix and your written brief disagree, resolve that before rendering the full set.
The guide identifies the matrix, Region/Marker Manager and Render to File dialog as related views. It also distinguishes region render sources with and without the master path. Preserve the chosen source in the record rather than describing every file loosely as a “stem.” Agree which processing the recipient expects; a filename cannot settle that question.

Review naming and output options together
Section 21.10 describes using project, region and track wildcards in filenames. Martin Parker’s 2017 region-rendering tutorial also connects meaningful region and track names with exported filenames. Treat that older tutorial as workflow context, and use the versioned guide for the current controls.
Check the actual proposed names before writing files. A recipient should be able to distinguish the voice-only excerpt from its reference mix and distinguish a replacement from an earlier delivery. Keep names free of private interview details where those details are unnecessary.
Record channel count, format, source, bounds and any postprocessing. A three-row brief is a statement of what you want, not a guarantee of the file count under every output configuration. Review the dialog’s expected outputs, including any additional formats or channel-splitting choices, against the brief.
Verify content, not just the folder count
Use a preserved project and a separate review destination for an initial small comparison. Choose representative combinations that would reveal an incorrect source or boundary. Open the resulting files independently and check the intended content, opening, ending and channel layout.
Keep creator checks separate from recipient acceptance. If two apparently different names contain the same material, retain that discrepancy in the ledger. Change the specific mismatched choice and make a separately identified attempt rather than overwriting the only evidence of what happened.
If the recipient needs the editable session and its source media, use the REAPER project-handoff guide as well. Rendered listening files and a self-contained editable project are different deliverables.
We read the cited documentation and tutorial text. We did not open REAPER, change a matrix, play audio, render a batch or test the recipient’s system. No measured export, compatibility or time-saving result is supplied.
The cited reference passages were reviewed on 13 November 2026.