Reaper Custom Actions: Complete Guide to Macros and Workflow Automation

Reaper's Actions system is the single most powerful customization feature in any DAW on the market. While other DAWs give you a fixed set of keyboard shortcuts, Reaper lets you chain any combination of its thousands of built-in commands into custom macros, bind them to any key or toolbar button, and fundamentally reshape how the software works. At $60 for a personal license, you get a level of automation that competitors charge hundreds more for and still cannot match.

For beat battle producers, custom actions are not optional. They are the difference between a five-click operation and a single keypress. When you have 30 seconds of playback time in an Audeobox battle, every fraction of a second you save in your workflow translates directly into more creative time with your music.

What Are Actions in Reaper?

An Action in Reaper is any discrete operation the software can perform. Opening a window, splitting an Item, toggling a track's mute state, inserting an FX, adjusting the grid size, rendering your project: every single one of these is an Action with a unique command ID. Reaper ships with over 3,000 built-in Actions, and every one of them can be triggered by a keyboard shortcut, a toolbar button, a MIDI controller message, or another Action.

A Custom Action is a macro that chains multiple Actions together into a single command. When you run the Custom Action, Reaper executes each step in sequence. You can consolidate five, ten, or fifty individual operations into one keypress.

This architecture means Reaper is not just a DAW. It is a programmable production environment. No other DAW at any price point offers this depth of workflow customization out of the box.

Navigating the Actions List

The Actions List is your command center. Open it with ? on both Windows and Mac, or navigate to Actions > Show action list from the menu bar. The window that opens contains every Action available in Reaper, organized by section.

Understanding Sections

The dropdown at the top left of the Actions List controls which context you are working in:

• Main - Actions that work in the main arrange view and globally across Reaper
• Main (alt recording) - Actions specific to alternative recording modes
• MIDI Editor - Actions that only trigger when the MIDI Editor is focused
• MIDI Event List Editor - Actions for the event list view
• Media Explorer - Actions for Reaper's built-in media browser

This section system is what makes Reaper's shortcuts context-aware. You can bind the same key to different actions depending on which window is active. For example, G could toggle the grid in the arrange view and toggle snap in the MIDI Editor without any conflict.

Searching for Actions

Type any keyword into the Filter field to search. Reaper searches both action names and command IDs. If you know what you want to do but not what the action is called, describe it in natural terms. Searching "split" shows you every split-related action. Searching "render" shows rendering options. The search is fast even across thousands of actions.

Creating Your First Custom Action

Let us build a practical Custom Action: a one-key command that selects all Items on the current track, splits them at the edit cursor, and deletes the right side. This is a trim-to-cursor macro that is invaluable for quickly cutting beats down to battle length.

1. Open the Actions List with ? (Windows and Mac).
2. Click the New action button at the bottom of the window and select New custom action from the dropdown.
3. The Custom Action editor opens with two panels. The left panel is the filter/search for all available Actions. The right panel is your Custom Action sequence, currently empty.
4. In the left panel filter, type "select all items on selected tracks" and double-click the matching action to add it to your sequence.
5. Next, search for "split items at edit cursor" and double-click it to add it as the second step.
6. Search for "unselect all items" and add it as step three.
7. Search for "select all items to right of edit cursor on selected tracks" and add it.
8. Finally, search for "remove items" and add it as the last step.
9. Name your Custom Action at the top of the editor. Call it something descriptive like "Trim track to cursor - delete right."
10. Click OK to save the Custom Action.

Your new Custom Action now appears in the Actions List. To assign a keyboard shortcut, select it in the list and click the Add button in the Shortcuts section. Press the key combination you want to assign, then click OK. The shortcut is now live.

Building Battle Macros

Here are five Custom Actions that every battle producer should have in their Reaper setup. Each one eliminates multiple clicks from operations you perform constantly under time pressure.

Quick Render to Desktop

This macro renders your project to a WAV file on your desktop with zero dialog interaction:

1. Action: File: Set render bounds to time selection
2. Action: File: Render project, using the most recent render settings, auto-close render dialog

Set your render settings once (WAV, 44.1kHz, 16-bit, desktop output folder) and this macro reuses them every time. One key press and your battle beat is rendered.

Instant Freeze and Unfreeze

Freezing tracks reduces CPU load by rendering FX Chain processing to audio. Chain these two as separate Custom Actions:

Freeze: Track: Freeze to stereo (render pre-fader, save/remove items and FX)

Unfreeze: Track: Unfreeze tracks

Bind Freeze to Ctrl+F (Windows) / Cmd+F (Mac) and Unfreeze to Ctrl+Shift+F (Windows) / Cmd+Shift+F (Mac). When your session gets heavy during a battle, freeze non-essential tracks instantly.

Battle Export Prep

This chains multiple steps to prepare your project for battle submission:

1. Action: Time selection: Set start point (at project start)
2. Action: Move edit cursor to project start
3. Action: Go forward 30 seconds (using SWS extension action)
4. Action: Time selection: Set end point
5. Action: File: Render project, using the most recent render settings

Insert and Arm Track

Quickly adds a new track, arms it for recording, and opens the FX browser:

1. Action: Track: Insert new track at end of track list
2. Action: Track: Toggle record arm for selected tracks
3. Action: Track: Open FX browser for selected track

Duplicate Item with FX

Duplicates the selected Item along with all its take FX settings:

1. Action: Item: Copy items
2. Action: Move edit cursor forward one beat
3. Action: Item: Paste items/tracks

Toolbar Customization

Custom Actions become even more accessible when you place them on toolbars. Reaper supports multiple custom toolbars that you can dock anywhere in the interface.

Adding Actions to the Main Toolbar

1. Right-click any empty space on the main toolbar.
2. Select Customize toolbar from the context menu.
3. In the Customize dialog, click Add to insert a new button.
4. The Actions List opens. Find your Custom Action and select it.
5. Click Select to add it as a toolbar button.
6. Back in the Customize dialog, you can set a custom icon by right-clicking the new button entry and choosing Set icon.

Creating a Dedicated Battle Toolbar

Go to View > Toolbars > New toolbar to create a floating toolbar dedicated to your battle workflow. Add your battle prep, quick render, freeze, and export macros as buttons. Dock this toolbar at the top or bottom of Reaper's arrange view so your battle tools are always one click away.

Reaper supports up to 16 custom floating toolbars. Each one can be toggled on and off independently, so you can create context-specific toolbars for mixing, arranging, recording, and battling.

Advanced Action Techniques

Consolidating Actions with the SWS Extension

The SWS Extension is a free, open-source add-on that adds hundreds of additional Actions to Reaper. After installing SWS, your Actions List gains powerful commands for region management, track manipulation, envelope editing, and more. SWS is considered essential by most serious Reaper users and integrates seamlessly with Custom Actions.

Key SWS Actions for battle producers:

• SWS: Save current track selection and SWS: Restore saved track selection - Save and recall track selections within macros
• SWS/S&M: Set selected tracks to specific color - Visual organization in one step
• SWS: Move cursor forward by specified seconds - Precise cursor movement for battle timing

Cycle Actions

Cycle Actions are Custom Actions that toggle between different states. Each time you trigger the same shortcut, it advances to the next step in the cycle. This is perfect for toggling between two or three grid sizes, switching between snap modes, or cycling through monitor configurations.

To create a Cycle Action, click New action > New cycle action in the Actions List. Each step in the cycle runs when you trigger the action sequentially. Step 1 runs first, step 2 on the next trigger, and so on until it loops back to step 1.

Conditional Actions with ReaScript

When you need if/then logic, Custom Actions reach their limit and ReaScripts take over. A simple Lua script can check conditions before executing actions:

For example, a script that only renders if a time selection exists prevents accidental full-project renders. You write the logic in Lua, save it as a .lua file in your Reaper Scripts folder, and load it as an Action through the Actions List. It behaves exactly like a native Action and can be bound to shortcuts or toolbar buttons.

Sharing and Backing Up Actions

Your Custom Actions live in the reaper-kb.ini file inside your Reaper resource path. Find this path by going to Options > Show REAPER resource path in explorer/finder. Back up this file regularly. If you reinstall Reaper or move to a new machine, copying reaper-kb.ini to the new resource path restores all your custom shortcuts and actions.

To share individual Custom Actions with other producers, you can export them from the Actions List. Select the action, click Export, and save the .ReaperKeyMap file. The recipient imports it through the same dialog. This makes it easy to share battle-optimized configurations with your crew on Audeobox.

Consider version-controlling your Reaper configuration folder with Git. Every time you create a new Custom Action or modify your toolbar, commit the change. This gives you a history of your workflow evolution and makes it trivial to sync configurations across multiple machines.

Frequently Asked Questions