How long a podcast episode takes to edit, measured on a Mac

24 September 2026 · 6 min read

Editing a podcast episode almost always takes longer than recording it, and by how much depends so heavily on the format, the audio and your own standards that anyone else’s rule of thumb tells you little about your show. The reliable answer comes from measuring a week: time in the audio editor, time listening back, time on notes and time uploading, divided by the episodes you shipped. That per-episode figure is what you plan a release schedule with, and what you price with if you edit for other people.

Why recording time is the wrong unit

Podcast work gets described in recorded hours because recording is the part with a clear start and end. An hour-long conversation is an hour on the calendar. Everything after it is harder to see: the first pass to cut false starts, leveling, noise cleanup, the listen-back, the second pass on the stretch where the guest’s connection dropped, the show notes, the chapter markers, the artwork, the upload, the scheduling.

That work happens in scattered sittings across several days, squeezed in around other things, which is exactly the kind of time memory drops. Ask a podcaster how long the edit took and you usually hear the length of the longest sitting.

The format changes everything as well. A solo episode recorded in one take in a quiet room edits very differently from a three-person interview recorded remotely on three different microphones. Your ratio belongs to your show, and it may differ between shows you make.

What each line on the receipt stands for

On a record kept by app name, a podcast week breaks into a handful of lines. Knowing what each one contains is most of the skill in reading it.

• The audio editor. GarageBand, Logic Pro or whichever editor you use: cutting, leveling, cleanup, music beds. If you record into the same app, the recording sessions sit in this line too, which matters for the arithmetic below.
• Listening back. Listen inside the editor and it is part of the editor line. Listen in QuickTime Player instead and it gets a line of its own. Listen on a phone during a walk and it is off the Mac, so it appears nowhere.
• Notes. Notes, TextEdit or a word processor: show notes, timestamps, the episode description, tidying a transcript.
• The browser. Uploading to your host, filling in episode details, scheduling the release, and the recording itself if you record remote guests through a browser.
• Mail and chat. Booking guests, sending them the link, the thank-you and the “it’s live” message.

A record of the frontmost app cannot tell whether you were at the keyboard. A long export or upload that runs while you make lunch may show up as editor or browser time. Note those stretches as they happen; one line each is enough.

Measuring a week, step by step

1. Pick a normal episode week. Not the live special, and not the guest who needed three rescheduled sessions.
2. Write the recording sessions down. Start and end times, from Calendar or from memory on the same day. You will subtract these from the editor line if you record into the editor.
3. Listen back in a separate app this week. Export a rough mix and play it in QuickTime Player, so listening gets its own line.
4. Keep a one-line log per day. “Tue: ep 48 first pass. Wed: ep 48 listen-back, notes. Thu: upload, 20 min export while away.”
5. Let the days record themselves. No timer at the start of each sitting, because a sitting that begins with “just fixing one cut” never gets one.
6. On Sunday, add it up. Editor line minus recording, plus listen-back, notes, the podcast share of the browser, and guest mail if you want the whole cost. Divide by the episodes you shipped.

Punchcard takes care of steps five and six. It notices which app is in front, by name only, and prints a receipt of each day at the closing time you set, with a week roll on Sunday. A weekly show lines up neatly with that roll: one week, one episode, one strip of paper that totals it. It has no projects or tags, so if you edit two shows in the same week, your one-line log is what separates them.

Turning a week into a per-episode figure

The number you end up with is useful in a few forms.

Hours per episode. The headline figure. Suppose the week roll shows 5 h 20 m in the editor, 1 h 10 m in QuickTime Player, 45 m in Notes and 35 m of podcast work in the browser, and your log says 1 h 15 m of the editor time was recording. The episode cost about six and a half hours beyond the recording itself. That is one invented week for illustration; yours will look different, which is the reason to measure.

Editing hours per recorded hour. Divide the post-recording hours by the recorded length. This is the ratio podcasters quote at each other, and now you have your own.

The split by phase. If listen-back is the biggest part after the edit itself, that is where time can come back: fewer full passes, or a rough pass at faster playback before the final one. If notes and upload are larger than you expected, a show-notes template and a fixed description format pay for themselves quickly.

One week gives you a figure. Three weeks give you a range you can trust. Keep the outlier (the episode with the terrible guest audio) labeled so it does not skew the average.

Planning and pricing with it

For a host, the per-episode figure sets the schedule more honestly than enthusiasm does. If an episode costs seven hours including recording and you have eight spare hours a week, a weekly show leaves one hour for everything else, including the week an episode goes wrong. That is the moment to consider an every-other-week schedule, or recording two episodes in one session and editing them back to back.

For a freelance editor, it is the basis of a per-episode price: hours per episode for each client’s format, times the rate you need, with the number of revision rounds named in the quote. The arithmetic is the same as for video, and how long a video edit actually takes covers it, including why revision rounds are the usual gap between quote and reality. For getting from a stack of receipts to a line on an invoice, see turning receipts into a simple invoice line.

Two cautions about what the receipts cannot know. They see apps, not episodes or clients. And they see nothing that happened away from the Mac: listening on a phone, planning questions on paper, guest research in a notebook. Add those by hand if they are a real part of your week.

Questions

Should recording time count as editing time?

No. Keep them apart. Recording scales with episode length; editing scales with length, audio quality and how polished you want the result. Mixing the two hides the part you can actually change.

I record and edit in the same app. Can the receipt separate them?

Not on its own. Punchcard records app names and time, not what you did inside an app. Your note of recording session times is what separates them.

How many episodes before I trust the figure?

Three of the same format is a reasonable start. A single week is far better than a guess, and it is still a sample of one.

Does an unattended export count as editing?

Only if you were doing something while it ran. A frontmost-app record may count it, so note long exports and uploads as they happen and take them out when you add up.