Remote recording is now the default for most B2B podcasts. Your host might be in Chicago, your guest in London, and your editor somewhere else entirely. That distribution is fine -- as long as you build your production workflow around it from the start.
The challenge is not the distance. The challenge is that different recording environments, different microphones, different internet connections, and different room acoustics all land in the same episode. Without deliberate editing practices, the result sounds like exactly what it is: a patchwork of separate rooms taped together.
This guide covers the best practices for editing podcasts recorded in different locations so your final episode sounds like a single, professional production -- regardless of where each speaker sat.
The single biggest thing you can do to improve the quality of a remotely edited podcast is ensure every participant records a local audio file.
Platforms like Riverside.fm, SquadCast, and Zencastr are built for this. Each speaker records directly to their own device, and the platform uploads those individual tracks after the session ends. What you get is a clean, lossless WAV file for each participant -- not a compressed, glitch-prone stream.
The difference in audio quality between a double-ended local recording and a single mixed recording from a video call is substantial. Audio pulled directly from a Zoom or Google Meet call carries compression artifacts, echo from acoustic feedback, and whatever background noise the platform's noise suppression missed. A local .WAV file from a dedicated platform gives you clean material to work with.
If local recording is not possible for a particular guest -- they are calling in from a phone, using an unfamiliar setup, or simply not tech-comfortable -- record the cleanest version of their audio you can get and treat it separately from the host track. Never mix the two signals before editing.
Editors waste significant time hunting for files when producers do not establish a clear folder structure. Before your editor opens a single track, deliver files in a predictable format.
A reliable convention for multi-location episodes:
EpisodeName_EP###/
raw/
host-firstname-lastname.wav
guest-firstname-lastname.wav
backup-mix.mp3 (if applicable)
assets/
intro.wav
outro.wav
notes/
show-notes-draft.txt
timestamp-notes.txtTimestamps matter more for remote recordings than studio recordings. Because each file is recorded independently, cuts happen at different points in each track. If your host or producer took notes during the session marking the approximate time of a fumble, a tangent to cut, or a key quote to keep, that information saves the editor 20 to 30 minutes of review time per episode.
When you import separate tracks into your editing software, they are not automatically aligned. A guest who started speaking 11 seconds after you launched the recording will have 11 seconds of silence at the top of their file. If you do not account for this before cutting, every edit will be slightly off.
The two common alignment methods:
Manual clap sync. At the start of each recording session, have every participant clap clearly on camera or say a sharp word simultaneously. In the waveform view, that clap shows up as a sharp transient spike on every track. Drag the tracks until those spikes are vertically aligned, and every subsequent word is in sync.
Automated sync tools. Software like Adobe Audition, Logic Pro, and Descript includes automated multi-track alignment. Audition's "Remix" and "Align" features are particularly fast for this. iZotope RX has a "Dialogue Match" module that can align and match room tone simultaneously.
Once tracks are aligned, work in a non-destructive editing environment. Keep your original files untouched and make all cuts on a separate layer or project session so you can return to the raw material if needed.
This is where most amateur remote podcast editors fall short. They apply noise reduction to the entire mix instead of treating each track individually.
Your host might be in a home office with minor HVAC noise. Your guest might be in a live-end room with noticeable reverb. If you apply the same noise reduction profile to both, you will overcorrect one and undercorrect the other.
Process each track independently through these steps:
1. Remove background noise. In Audacity, capture a noise profile from a moment of silence on each track, then apply noise reduction at a conservative setting (10-15 dB of reduction is usually sufficient; more risks audio artifacts). iZotope RX's Spectral Repair and De-noise tools are more precise for problem recordings.
2. Reduce room reverb. A guest in a reverberant room (bare walls, hardwood floors, large space) will sound noticeably hollow compared to a host in a treated space. iZotope RX's De-reverb plugin and Accusonus ERA Bundle's Reverb Remover address this well. You will not fully fix a terrible room, but you can minimize the difference.
3. Normalize and level-match. The host and guest should land at roughly the same perceived loudness before compression. A target of around -20 to -23 LUFS for each raw track before processing gives you enough headroom to work with.
For a deeper breakdown of the full editing workflow, see the podcast editing and post-production guide.
After cleaning, every voice needs compression and EQ applied to its own track. The goal is to smooth out volume inconsistencies (guests who get louder when excited or quieter when thinking) and shape the tonal character of each voice so they blend naturally.
Compression settings for speech: A ratio of 3:1 or 4:1 with a medium attack (5-10ms) and a slightly faster release (50-80ms) works for most voices. You want to catch the loudest peaks without squashing the natural dynamics of speech.
EQ for clarity: Roll off everything below 80 Hz on voice tracks -- it is almost always low-frequency room rumble rather than useful vocal information. A slight boost around 3-5 kHz adds presence and intelligibility. If a voice sounds boomy, cut a narrow band around 200-300 Hz.
Work with reference headphones or studio monitors, not laptop speakers. Consumer laptop speakers exaggerate mid-range and hide low-end problems.
Technical cleanup is only half of podcast editing. The structural pass -- deciding what stays and what goes -- is what separates a good episode from a great one.
For remote recordings specifically, watch for:
Internet-caused glitches. Even with local recording, guests sometimes experience connection hiccups that affect their monitoring and cause them to re-state a sentence. If the first attempt was clean in their local file, keep it and remove the re-statement.
Latency-driven interruptions. When recording across time zones and internet connections, guests often talk over each other simply because they cannot hear each other in real time. These overlapping moments can sound natural if left in or distracting if left in awkwardly. Listen through them and decide case by case.
Verbal padding specific to remote settings. "Can you hear me okay?" and "I think we had a bit of a delay there" are common in remote recordings and rarely add value once the episode is edited.
Cut for a listener who was not in the room. They do not know what was a technical hiccup and what was intentional -- but they will feel the difference in pacing.
With all individual tracks cleaned, compressed, and edited, the final mix combines them into a single stereo (or mono) file.
Loudness standard: The Podcast Loudness Standard targets -16 LUFS for stereo and -19 LUFS for mono, as specified by most major platforms including Apple Podcasts and Spotify. Export at these levels using a loudness normalization tool (included in most DAWs or available as a free plugin like YouLean Loudness Meter).
File format: MP3 at 128 kbps mono or 192 kbps stereo is the standard for podcast distribution. Some shows upload WAV files for hosting platforms that handle compression, but check your hosting platform's recommendations.
True peak limiting: Apply a true peak limiter set to -1.0 dBTP before export. This prevents clipping on playback across different devices and media players.
Managing remote recording files, track alignment, per-voice processing, structural editing, and proper mastering is a time-intensive production workflow. For in-house teams producing two or more episodes per month, the editing workload alone typically runs 3 to 6 hours per episode.
A B2B podcast production service handles all of this for you -- file collection, alignment, noise removal, structural editing, and final export -- so your team focuses on content and guests, not audio files.
Podsicle Media works specifically with B2B brands producing company podcasts. If your team is spending more time editing than planning episodes, that is a sign the workflow is due for a change.
Talk to the Podsicle Media team about done-for-you editing.
Follow this sequence consistently and your remote-recorded episodes will match the quality of studio recordings -- often surpassing them because local .WAV files captured at the source are cleaner than most studio setups that rely on shared microphones and room acoustics.
For details on the tools best suited to each step, see the best audio editing software comparison. For options at no cost, see free audio editing software options.
