Podcast Production File Workflow: Remote Recording, Editing, and Revision Cycles

The Modern Podcast File Flow

Podcasting has moved beyond a single person hitting record on their laptop. Today's shows often involve:

• Remote guests recorded in separate locations
• Multiple audio tracks captured simultaneously
• Dedicated editing and mixing
• Show notes, artwork, and metadata coordination
• Multiple platforms needing different formats

Each of these steps creates files that need to move between people. And those files are large.

Raw File Sizes: What You're Actually Dealing With

A typical episode recording setup involves multiple audio sources, all captured in lossless format for editing flexibility:

• Host: Professional USB mic or XLR into interface — mono WAV, 24-bit/48 kHz
• Guest (remote): Zoom/Skype call capture or Zencastr session — WAV, variable sample rate
• Guest (remote #2): Same as above
• Ambient/room tone: Background recording for room sound — stereo WAV

Here's what a typical episode looks like in raw files:

A typical twice-weekly podcast (2 hours per episode) generates 12 GB of raw files per week. Across a month, that's 48 GB of raw material. These files need to move from capture devices to your editor.

The Problem: Remote Recording Quality

Many podcasts use Zoom or Skype for remote guests. These services compress audio in real-time to save bandwidth. The result sounds fine for a video call, but for podcast production it's a problem.

Why Zoom/Skype Audio Isn't Good Enough

• Compressed to roughly 64 kbps per direction (equivalent to AM radio quality)
• Loses presence and clarity that professional podcast listeners expect
• Makes remote guests sound like they're in a tin can
• Can't be fixed in post-production — the data is already gone

That's why professional podcasts use dedicated remote recording services like Zencastr or Riverside. These capture the guest's audio locally at full quality (usually WAV, 24-bit/48 kHz or higher) while also recording the Zoom call as a backup. The host gets the uncompressed file afterward, not the compressed Zoom stream.

But now you have a new problem: those uncompressed files are large, and they need to move from the guest's computer (or the remote service) to your editor.

The Typical Podcast Workflow

Here's how files move through a modern podcast operation:

That's 5-6 file transfers minimum. Most podcasts do 2-3 revision rounds, doubling the transfers. A typical 2-hour episode moves 30-40 GB in total files before it's published.

Why Common Transfer Methods Break

Email

Even a single 10 GB file exceeds email attachment limits. Not viable.

Cloud Storage (Dropbox, Google Drive)

• Upload speed bottleneck: 10-50 Mbps typical ISP upload
• 10 GB file takes 2-4+ hours to upload
• Syncing wastes local storage (you don't want 100 GB of synced podcast files on your laptop)
• Revision cycles create version confusion ("which edit did I listen to?")
• Collaboration permissions get messy with freelance editors

Per-GB Services

• 10 GB per episode at $0.25/GB = $2.50 per episode (host → editor)
• 3 GB back (editor → producer) = $0.75
• 2-3 revision rounds × 3 GB = another $2.25
• Total per episode: $5-8 in transfer fees
• Weekly podcast: $20-32/week = $1,000-1,600/year in transfer fees alone

Zencastr / Riverside File Delivery

• Service hosts files for 2-3 weeks
• You download files (limited speed from their servers)
• No direct connection to your editor — you download, then re-upload
• Double the time, double the bandwidth

How P2P Changes the Workflow

Imagine your podcast editor had a persistent folder that you could access directly. You record, download your local files, and immediately add them to the shared folder. Your editor gets notified, downloads at full internet speed while you're still wrapping up. By the time you've done show notes, your editor is already editing.

Revision cycles become instant: editor returns updated file, you review, add notes, editor downloads revisions instantly, completes changes within hours instead of days.

Speed Comparison: 10 GB File

• Cloud storage upload: 20 Mbps upload, 6,700 seconds = 1.9 hours
• P2P direct: 300 Mbps connection, 267 seconds = 4.5 minutes
• Speedup: 25× faster

Cost Comparison: Weekly Podcast

• Per-GB service: $20-32/week = $1,040-1,664/year
• P2P (Handrive): Free
• Savings: $1,000+/year

Multi-Episode Workflows

If you batch-record episodes (common for efficiency), you might have 3-4 episodes waiting for editing at once. That's 30-40 GB of raw files, all needing to transfer to your editor.

With P2P, you drop all four episodes in the shared folder simultaneously. Your editor downloads them in parallel at full speed. With cloud storage, you'd be uploading for 6-8 hours straight, and the editor would be waiting.

Setting Up Your Team: Producer, Editor, Guests

Producer → Editor

Setup (one-time):

1. Both install Handrive (free, 2 minutes)
2. Create a shared folder on producer's machine: "Episodes for Editing"
3. Editor adds producer as contact, downloads updates when available

Ongoing:

1. Producer adds raw episode files to shared folder
2. Editor gets notification, downloads at full speed
3. Editor finishes edit, adds file to their share back to producer
4. Producer downloads, reviews, approves or requests changes

Guest → Producer (for remote recordings)

If a guest recorded locally and needs to send you their audio:

1. Set up a temporary Handrive share specifically for that guest
2. Guest installs app, downloads their recording, drops into shared folder
3. You download at full speed
4. Delete the share after the episode is published (cleanup)

Privacy for Unreleased Content

Podcast recordings contain:

• Sponsor announcements (not yet public)
• Guest announcements or news
• Conversations that could be taken out of context if leaked
• Personal stories you don't want on a server

Cloud transfer services store files on their infrastructure. Even with encryption in transit, files sit on servers controlled by others. Some platforms scan for copyright/illegal content. Some use data for AI training.

P2P transfer means files go directly from your device to your editor's device. No intermediate servers. No third party can intercept or archive your content.

Scale: Adding More Editors/Producers

If your show grows and you bring on a mastering engineer or additional editor:

• Create separate shares for each: "Mastering Queue", "Second Editor Reviews", etc.
• Add files once, distribute to multiple people simultaneously
• Each person downloads at their own speed, parallel transfers don't compete
• No per-GB fees, no matter how many people you're sending to

Monthly File Transfer Estimates

Typical twice-weekly podcast (4 episodes/month, 2 hours each):

• Raw recordings: 12 episodes/month × 6 GB = 72 GB down from Zencastr
• Transfer to editor: 72 GB
• Edited versions back: 12 episodes × 3 GB = 36 GB
• Revision files: 36 GB (2 rounds of changes)
• Total per month: 216 GB of file movement

With cloud storage at 20 Mbps upload: 360+ hours of uploading per month. Not feasible.

With per-GB service: 216 GB × $0.25 = $54/month = $648/year in transfer fees.

With P2P: Zero transfer fees. Same 216 GB moving 25× faster.