How to organise podcast files and media assets: a folder-based workflow

Every podcast generates an astonishing amount of stuff.

One interview can easily produce several raw recording streams, an edited final, a video version, a transcript, show notes, cover art, clips, guest headshots, a bio and a stack of social images. Multiply that by fifty episodes and you have hundreds of files — and if they live wherever they happened to land, every publishing day starts with a treasure hunt.

This guide shows you how to run it by hand, using the system that actually matches how episodes get made: stage folders that an episode moves through — from raw recording, to the editor, to prep, to published. It works with any storage you already use — a local drive, Dropbox, Google Drive or OneDrive.

Why you can't organise by episode number

Most "organise your podcast" advice says to start every file name with the episode number. It sounds tidy, and it falls apart on day one — because when the interview finishes, the episode number doesn't exist yet.

Recording order isn't publishing order. Episodes get held back, reshuffled, split in two or dropped entirely. The number is one of the last things an episode gets, so a system that needs it up front forces you to guess and rename later.

The fix: key everything on the guest name (or the topic, for solo episodes). That's the one identifier you have from the moment the recording stops, and it never changes.

Step 1: One home, and only one

Before any structure, make one decision: everything lives in one place. Not "recordings on your drive, the final in the editor's Dropbox, artwork in email, the transcript in Docs". One shared root folder that you, your editor and anyone else on the show all work inside.

• Use cloud storage, because the whole point is handing folders between people — you to the editor, the editor back to you.
• The editor works inside the system and delivers into it. No email attachments, no "which version did I send you?"
• If a file isn't in the root folder, it doesn't exist. The system dies from exceptions.

Step 2: Interview done — name the streams and hand off to the editor

A remote interview usually ends with multiple files: your track, the guest's track, maybe separate video streams and a backup recording. Deal with them immediately, while you still remember what they are:

The editor does all their work in that folder and, when they're done, exports the finished episode into it as the Final — e.g. jane-smith-final.wav. If revisions happen, the new export is final-v2; the highest version wins.

Step 3: Edit done — move the folder to prep and build the episode

When the Final lands, you don't copy files out — you move the entire folder into your prep/ stage folder. This is the moment the recording becomes an episode, so this is where you build its proper structure:

• Move the edit files into edit/. They've done their job. Keep them (they're irreplaceable), but get them out of your sight.
• Move the Final into media/. This is now the working directory for the episode.
• Create everything else in the same directory as the Final: the transcript, show notes, title options, chapter list and covers all live in media/, right next to the file they came from.
• Cut social clips into media/clips/. Clips multiply fast — a folder of their own keeps them together without burying the Final, and on promo day everything you post comes from one place.

That last rule is the one that saves you on publishing day. Everything you need to publish — the audio, the words, the artwork — is in one directory, not scattered across a docs app, a design tool and three downloads folders. Publishing becomes: open the folder, work through it top to bottom. (What actually needs producing at this stage is covered in the after-the-edit checklist and the show notes tutorial.)

Step 4: Publish — number it now, then move it out

Only when the episode is scheduled does it finally get its number. Prefix the folder — ep042-jane-smith — publish from it, and move the whole thing into your published/ stage folder. Done episodes leave the pipeline; you stop touching them.

So the root of the system is just the pipeline, left to right:

Your status board is just the file browser: what's in edit/ is with the editor, what's in prep/ is yours to finish, and the moves between stages are the handoffs. One glance, full pipeline.

Step 5: Guests get their own folders — once

Guest assets are the most re-requested files in podcasting. The first time a guest sends a headshot, bio and links, file them in guests/jane-smith/ and reference them from every episode they appear in. Repeat guests cost you nothing, and a season-later "best of" episode becomes an afternoon instead of an email campaign.

Step 6: Back it up and be ruthless about clutter

• Raw streams and Finals are irreplaceable — make sure your storage keeps version history or a second copy. Everything else can be regenerated at a pinch.
• Once an episode has been live for a month, its folder in published/ is an archive. Resist reorganising it.
• Never let the only copy of anything live on one laptop — especially not the editor's.

Where the folder system breaks down

Run this honestly and it will serve you well — for a while. But it has structural limits worth knowing in advance:

• You are the conveyor belt. Every stage transition is you moving folders, renaming files and telling the next person it's their turn. Miss a move and the pipeline silently stalls.
• It stores files, not knowledge. Folders can't tell you which episode discussed pricing or find a quote — the moment you need to search inside episodes, you're scrubbing audio again. That problem needs a searchable back catalogue.
• Nothing is actually connected. The transcript doesn't know its episode, the guest folder doesn't link to their episodes, and "which episodes is Jane in?" means remembering, not asking.
• Publishing still leaves the system. The folder holds the assets, but notes still get pasted into your host, posts into each platform, emails into another tool. The tabs multiply again on the way out.

Where PodMule fits

PodMule is this workflow without the conveyor-belt job. Every episode gets one organised home automatically — audio, video, covers and files in a single media library — and the transcript, show notes, titles, chapters and social posts are generated from the Final and attached to the episode they belong to, not filed near it.

Guests are real records linked to their episodes rather than folders you cross-reference by hand, pipeline status is visible without moving anything, and the whole catalogue is searchable by what was actually said.

Build the folder pipeline today — it genuinely works. And when you're ready to stop being the person who moves the folders, join the PodMule early-access list.