How Long Should a Podcast Episode Be, Really

Ayush Sharma28th June, 2026
A podcast timeline shown as an adjustable slider, with markers for short news, mid-length solo, and long-form interview lengths

There is no single ideal podcast episode length, and anyone who hands you one number is guessing. The right length is set by your format and your goal: daily news runs 5–12 minutes, a solo teaching episode 15–30, a conversational co-host show 35–60, a deep interview 60–120. Then your own audience's completion rate tells you the real ceiling.

The number you should chase is not a duration at all. It is the share of the episode people actually finish. A tight 22-minute episode that holds 70% of listeners beats a 75-minute one that loses half the room by the 30-minute mark. Below, you get a length-by-format table, a completion-rate test to find your show's ceiling, and the one habit that quietly kills more episodes than any runtime: padding to fill the time.

Why there is no magic number

The "perfect length" question has a stubborn answer: it depends on what the episode is doing. A news recap and a two-hour philosophy interview are not the same product, and treating them as if one ideal length covers both is how shows end up either too thin or bloated.

The audience supports a wide range. US podcast listening is at a record, about 158 million monthly listeners, 55% of the 12-and-up population, with roughly 115 million listening weekly (Edison Research, Infinite Dial 2025). People who choose to subscribe to a show about welding or venture capital are not allergic to length. They are allergic to wasted time. Length only becomes a problem when minutes stop earning their place.

So the planning question is not "how long should my podcast be." It is two questions: what format am I making, and what is this episode supposed to do for the listener. Answer those and the range narrows on its own.

Illustration depicting How Long Should a Podcast Episode Be, Really

Length by format and goal

Here is a working table. Treat these as starting ranges drawn from how the common formats actually behave, not as limits. Your goal sets where you land inside the range.

Format / goalTypical lengthWhy this range
Daily news / briefing5–12 minListened to on a commute; value is speed, not depth
Solo teaching / explainer15–30 minOne idea taught well; padding shows fast
Conversational / co-host35–60 minChemistry needs room; past ~60 min, tangents creep in
Deep interview60–120 minThe format people will sit for if the guest delivers
Narrative / storytelling25–45 minScripted and tight; every minute is built, not filled
Typical episode length ranges by format Daily news 5 to 12 minutes, solo teaching 15 to 30, conversational 35 to 60, narrative 25 to 45, deep interview 60 to 120 minutes. Length by format (start here, then test) Daily news5–12 min Solo teaching15–30 min Narrative25–45 min Conversational35–60 min Deep interview60–120 min Bar width is proportional to the upper bound of each range. Editorial rule of thumb (QuickReel), not a benchmark.
Length by format, a planning rule of thumb, not a fixed standard.

A few honest notes on this table. The ranges are an editorial framework, not a sourced statistic, there is no clean public dataset that maps optimal length to genre, partly because the biggest host, Spotify, shares no public benchmarks at all. So use the table to pick a starting point, then let your own data correct it. That is what the next section is for.

If you have not locked which format you are even making, do that first. The choice between solo, co-host, and interview determines your length range before any other decision, and it shapes how much you should script versus outline your prep.

The completion-rate test

The benchmarks above get you a starting length. Your audience sets the real one. Run this test once you have three or four episodes published: look at the average percentage of each episode that listeners actually consume, and let that number tell you whether to shorten or hold.

  1. Find your consumption number. Apple Podcasts Connect and Spotify for Creators both show average consumption, the share of the episode the typical listener gets through. YouTube shows the same as average percentage viewed.
  2. Read it against 60%. If your average consumption is comfortably above ~60%, your length is fine; the episode is earning its minutes. If it sits well below that, the episode is longer than your audience wants it to be.
  3. Find the drop-off point. Look at where the retention curve falls off a cliff. That timestamp is usually a tangent, a long intro, or a section that should have been cut. That is your ceiling, in minutes, for that format.
  4. Cut to the cliff, not to a number. Shorten by removing the weak section you just found, not by trimming evenly across the whole episode. Then publish three more and re-check.
The completion-rate test Publish, check average consumption, then if above sixty percent hold the length, if below sixty percent find the drop-off and cut that section. Let your audience set the ceiling Check avg. consumption Above ~60%? Length is fine, hold Below ~60%? Find the drop-off second Cut that section, re-test Consumption data from Apple Podcasts Connect, Spotify for Creators, and YouTube analytics.
The completion-rate test: a four-step loop you run on your own analytics.

The 60% line is a practical threshold, not a published standard, pick it as your own internal floor and adjust once you know your show. The point is to stop arguing about whether 30 or 45 minutes is "right" and let the people who already subscribe vote with their attention. A small caveat worth stating: consumption numbers across Apple, Spotify, and YouTube are measured differently, so compare each platform to itself over time rather than against the others.

Illustration for 'The real killer: filling the time'

The real killer: filling the time

The thing that ruins episode length is not the runtime on the file. It is the decision to fill a slot instead of finishing an idea. A host books a "one-hour show," runs out of substance at 38 minutes, and stretches the rest with throat-clearing, repeated points, and tangents nobody asked for. The clock got fed. The listener got bored.

Filling the time vs cutting to the idea Padding to fill a slot Cutting to the idea • Long, rambling intro • Same point made three times • Tangents to hit a runtime • Consumption drops mid-episode • Get to the point in 60 sec • Each minute adds something new • End when the idea ends • Higher completion, more clips
Length is a symptom. Padding is the disease.

Cut the other way. Decide what the episode is about, say it well, and end when it is done. A 24-minute episode that respects the listener's time is a feature, not a shortfall. This matters more than it used to: video is now the default way people meet new shows, 53% of new US weekly listeners say they prefer to watch a podcast, up from 30% in April 2022 (Backlinko). On video, padding is even more obvious than it is in audio, and it shows up directly in the retention graph.

There is a survival angle too. Nearly half of all podcasts never make it past their first three episodes Amplifi Media, and a steady weekly or biweekly cadence is what separates the shows that last from the ones that fade. Targeting a runtime you cannot sustain is a quiet way to burn out. A tight 25-minute show you can make every week beats a 90-minute marathon you abandon by episode four. If long episodes are your format, batch-recording several at once is the way to keep the cadence without the burnout.

A length-planning checklist

Before you hit record, run this. It takes two minutes and saves you from filling time.

  • Name the format. News, solo, conversational, interview, or narrative, pick one and take its range from the table.
  • Write the one-line goal. What should the listener know, feel, or do by the end. If you can't write it, the episode isn't ready.
  • Set a soft ceiling, not a target. "Up to 45 minutes," not "must be 60." A ceiling lets you stop early; a target makes you pad.
  • Plan the structure. A repeatable episode structure keeps you from rambling into the runtime.
  • Check consumption after three episodes. Run the completion-rate test and adjust your ceiling to what your audience actually finishes.

Frequently asked questions

How long should a podcast episode be for beginners? Aim short and finishable: 15–30 minutes for a solo or explainer show, up to about 45 for a conversation. A shorter episode you can publish consistently beats a long one you can't sustain, and a regular cadence is what separates shows that survive from the ones that fade, with nearly half never getting past three episodes Amplifi Media.

Do longer podcasts get more listeners? Not on their own. Length helps only when every minute earns its place; a long episode with a low completion rate loses people and signals nothing good to platforms. Deep interviews can run two hours when the guest delivers, but length is the result of substance, not a way to manufacture it.

What is the average podcast episode length? There is no reliable single average, and you should be skeptical of any figure presented as one, the dominant platforms share little public data, so the question is genuinely uncertain. Plan by format using the table above and verify against your own consumption analytics rather than chasing a market average.

How do I know if my episodes are too long? Check your average consumption in Apple Podcasts Connect, Spotify for Creators, or YouTube. If listeners are finishing well under ~60% of the episode, look for the timestamp where the retention curve drops and cut that section. Compare each platform to itself over time, since each measures consumption differently.

Pick your format, set a ceiling instead of a target, and let your completion rate move it. If you are still deciding the shape of your show, lock your core format and your episode structure first, those two choices set your length range long before the gear does, though a decent mic by budget tier is worth getting right early too.