
REAPER can expose recording controls through its Web browser interface, letting a phone or tablet control the computer's session from the microphone position. Select that control-surface mode, apply its settings and use the exact Access URL shown. The selected HTML interface determines which commands are available; this is not evidence that the phone itself records the microphone.
Key Takeaways
- Configure the web interface as a REAPER control surface.
- Use the displayed Access URL rather than guessing an address.
- Check recording, track arming and monitoring separately before a real take.
Choose the control page
On the REAPER computer, open the project and Preferences > Control/OSC/web. Choose Add, then Web browser interface in the control-surface mode selector.
Section 15.31 of the 7.81 manual uses basic.html for a simple interface and suggests index.html for a graphical alternative. A different page can expose a different task set. Choose according to the controls required for the session, rather than its appearance alone.
Click Apply Settings and retain the exact Access URL displayed by that setup. This guide has not enabled a server or connected a device.
Verify control from the microphone position
Open the displayed URL in the phone or tablet browser. The documented basic interface offers play, stop, record and abort-record buttons. Its track list provides arming, monitoring and mute controls; opening an individual track exposes additional controls such as solo and volume.
Before an important voice-over, rehearse a disposable take. Confirm the intended computer input and armed track, start recording remotely, speak a test phrase and stop deliberately. Inspect the recording on the computer. A responsive button proves less than an actual correctly captured take.
The narration replacement guide addresses matching a new performance to surrounding speech. Remote transport control does not settle that acoustic requirement.
Keep connection choices explicit
The manual notes that Windows port and firewall settings can affect access. Confirm the actual configured port and local access conditions instead of disabling protections indiscriminately.
Its optional Use rc.reaper.fm choice records the local IP and supplies a persistent redirect when that IP changes. Treat that as a separate connection choice, not a requirement inferred from this procedure. No public-access configuration is prescribed here.
Inspect the captured result
Confirm that the new item contains the complete intended performance and that monitoring did not enter the recording unexpectedly. Remote operation does not define a bounded replacement interval: Audacity's continuing Punch and Roll behavior is a separate recording contract.
Accept the setup only after the available controls and captured material match the session's intended scope.
Related tasks
- How Do I Record One Replacement Sentence That Does Not Sound Pasted In?
- Why Did Audacity Punch and Roll Replace Everything After My Selection?
Sources and scope
- REAPER User Guide 7.81: Section15.31: Preferences Control/OSC/web > Add > Web browser interface; basic.html versus index.html affects controls; Apply Settings gives exact Access URL; basic transport and track arm/monitor/mute controls; optional rc.reaper.fm stores local IP and redirects.
Guidance based on the verified official REAPER 7.81 manual, read on October 23, 2026. The recording, processing and device comparisons described here are proposed checks; no remote connection, listening result or performance measurement has been performed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Mak Cézar / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.