
Overview
Recording a remote guest with studio-quality audio is easier than you think once you understand the core problem: video call apps like Zoom and Teams compress audio aggressively for bandwidth. The solution is to record each person locally and combine the files in post.
What You Need
- A microphone for yourself (USB or XLR)
- A recording app: Audacity, GarageBand, or a dedicated tool like Riverside.fm
- A video call app for the conversation (Zoom, Meet, etc.)
- A DAW or editor for mixing the two tracks together
Steps
Understand why Zoom audio sounds bad
Zoom and Google Meet apply variable bitrate compression, noise suppression, and automatic gain control, all designed for intelligibility, not quality. The result is pumping, artefacts, and processing smear. Recording the Zoom call directly will always sound like a Zoom call.
Choose your recording method
Double-ender (free): Both host and guest record themselves locally and share the files after. Dedicated platform (paid): Tools like Riverside.fm record each person at full quality locally in the browser, then upload post-session. Use the double-ender for budget setups, a dedicated platform for consistent professional results.
Set up the double-ender
You run Zoom for the conversation while also recording in Audacity separately. Your guest does the same. They record their own voice locally while on the call. After the session, your guest sends you their audio file. You now have two clean, uncompressed tracks.
Brief your guest before the session
Most guests have never recorded themselves before. Send a simple pre-session checklist: record in a quiet room, use headphones during the call (prevents bleed), press record before joining the call, clap once at the start so you have a sync point. Keep it to five bullet points, long briefs don't get read.
Sync the audio tracks in post
Import both tracks into your DAW as separate lanes. Use the clap you recorded at the start: zoom in on both waveforms and drag them until the clap transients align. From that point they'll stay in sync for the whole interview. Delete the pre-clap sections.
Mix and export
Process each track independently. EQ, compress, and noise-reduce them separately before setting final levels. Export as a stereo mix or combine to mono for podcast delivery. Aim for −16 LUFS on the final export.
Pro Tips
- Tell guests to turn off their phone and close all browser tabs, notifications are the most common recording-ruiners.
- If your guest doesn't have a microphone, ask them to use AirPods with the mic rather than their laptop's built-in microphone.
- Always record a Zoom backup even when using a dedicated platform. It's your safety net if local recording fails.
- Use our Remote Recording Apps guide to compare platforms like Riverside.fm, Squadcast, and Zencastr.
Tested: whether a clap sync stays in sync for a whole interview
We tested step 5 on 2026-09-30 with FFmpeg 8.1.2 and numpy. Two recorders never run at exactly the same sample rate, so a synthetic five minute track with a sharp click every 30 seconds was copied and the copy was resampled to run 100 parts per million fast, a plausible difference between two consumer devices. The two were aligned on the first click, as the page says, and the offset between them was read at each later click by finding the peak. The offset was then corrected by resampling with the ratio measured from the drift.
| Point in the recording | Offset after aligning on the clap | After resampling by the measured ratio |
|---|---|---|
| The opening clap | 0.0 ms | 0.00 ms |
| 1.5 min after the clap | 9.4 ms | +0.00 ms |
| 3.0 min after the clap | 18.8 ms | +0.00 ms |
| 4.5 min after the clap | 28.1 ms | +0.00 ms |
The clap sync does not hold for a whole interview if the clocks differ. The offset grew at 0.10 ms per second, which is 104 ppm, and reached 28 ms at the last click, four and a half minutes in. At that rate a 60 minute interview drifts about 375 ms, about a third of a second. The page's "they'll stay in sync for the whole interview" is true only for short sessions, or when both files come from the same clock.
The fix is a resample. Applying the measured ratio to the second track left every click aligned with the first to well under a millisecond, 0.00 ms at the worst. In practice that means a second sync point at the end, as well as the start, and stretching the track between them. Some editors and platforms do this on import and this test does not say which. The prices and platform features in the Knowledge Base were not tested.
Reference. Measured 2026-09-30 with FFmpeg 8.1.2 and numpy on synthetic tracks. 100 ppm is an assumed clock difference (104 measured, because of rounding in the resample), real devices range widely, and a recording that is resampled by the platform or by the call software may not drift at all.
Knowledge Base
What You'll Learn
Record high-quality audio from remote guests via Zoom, Riverside, or SquadCast. Learn backup recording methods, audio routing, and how to ensure remote guests don't sound compressed or distant.
Remote Recording Platforms
- Riverside.fm: Cloud recording plus local recording backup. Host and guest each record locally at full quality. Free plan, then Pro at $29 a month, or $24 a month billed yearly.
- SquadCast: Now part of Descript and sold on Descript's plans. The free plan includes 1 recording hour per editor a month, then Hobbyist is $24 per person a month, or $16 billed yearly.
- Zoom: Local recording to your computer works on a free account in the desktop app. Cloud recording needs a paid Pro, Business or Enterprise plan. Call audio is compressed either way.
- WhatsApp: Avoid for professional podcasts. Audio quality is poor, no local recording option. Skype is no longer an option, as Microsoft retired it on 5 May 2025.
Setup Checklist
- Wired Ethernet connection (not WiFi). Reduces audio dropouts.
- Quiet room for guest. Ask them to avoid hard surfaces (desk, walls) behind them.
- Microphone positioned 6-8 inches from mouth.
- Test call 10 minutes before recording. Confirm audio levels and quality.
- Record locally on both sides (host and guest). Internet quality always dips slightly.
Audio Mixing
Remote audio usually needs aggressive noise reduction (traffic, HVAC). High-pass filter at 100 Hz helps. Don't over-EQ, keep natural. Local recordings are almost always higher quality than stream quality. Use those.
Contingency Plan
If video drops, have phone recording backup (iPhone Voice Memos, Android Recorder). Never lose an interview.
Where This Fits
A double-ender is one remote guest method, and Best Podcast Setup for Beginners places it in the full show setup.
Sources
Read 5 October 2026. Riverside's pricing page: Free at $0 and Pro at $29 a month or $24 billed yearly in US dollars, shown in euros to some regions. SquadCast's pricing page says SquadCast has joined Descript, with Hobbyist at $16 per person a month billed annually or $24 monthly. Zoom Support, Starting a computer recording (a Basic free account or above, desktop app) and Starting a cloud recording (a licensed Pro, Business or Enterprise user). Microsoft Support, "Skype is retiring in May 2025: What you need to know". Not checked: Zoom and Google Meet compression behaviour, including Zoom's Original sound option, WhatsApp's audio, and Zencastr.
FAQ
Q: Is Zoom good enough for a professional remote-recorded podcast?
A: Not ideal. Zoom's call audio is compressed noticeably, whichever way you record it. It's fine for a casual show, but if audio quality matters, use a platform with local recording (Riverside, SquadCast) instead.
Q: What's the single most important habit for remote recording reliability?
A: Always record locally on both ends, not just relying on the platform's cloud stream, internet quality dips are common and local recordings are almost always higher quality than what gets streamed.
Prices on this page were last checked in August 2026. Software and hardware pricing moves, so treat these as a guide and confirm before you buy.
Translate this page
- Español
- 简体中文
- हिन्दी
- العربية
- Português
- Français
- Deutsch
- 日本語
- Русский
- Bahasa Indonesia
- 한국어
- Italiano
- Türkçe
- Tiếng Việt
- Polski
- Nederlands
Machine translation provided by Google Translate, on Google’s servers. We do not check these translations and they will get technical terms wrong. The English page is the authoritative one. Following a link sends this page’s address to Google. Your browser may also offer to translate this page itself, which keeps the request on your device.