Verified podcast plays benchmarks: what you can compare

Verified podcast plays benchmarks do not exist as a published percentile table, and the timing explains why. The 30 second threshold that makes a play worth comparing was defined by the Alliance for Measurement in Podcasting and only reached Spotify's creator dashboard on June 11, 2026. Apple Podcasts and YouTube are not part of that group and apply their own rules. Nobody has a comparable dataset yet.

What you can build is a benchmark with visible boundaries: your own plays-to-downloads ratio inside a single platform, measured in a fixed window and tracked as a trailing median. That comparison holds up when someone asks how you got the number.

Why plays cannot be benchmarked across platforms yet

Each platform counts a play under its own rule, and the rules are far enough apart that the resulting numbers are different metrics wearing the same name.

The gap between "any press of play" and "at least 30 seconds" is not small. Every accidental tap, every pause and resume, and every three second sample lands in one column and not the other. A show with the same real audience on both platforms will report a larger Apple number, every time, with no growth involved.

Spotify's deduplication rule adds a second wrinkle. The same listener playing half an episode twice registers two plays, while the audience total treats a logged-in user as one person across your show's entire history. Plays and audience on the same screen are counted on different bases.

For the definitions themselves, verified podcast plays covers each platform's rule in detail.

The benchmark that does exist

Downloads remain the metric with real, dated, disclosed percentiles, which is why they stay the anchor for anything commercial.

Buzzsprout's platform stats for July 2026 put the median episode at 27 downloads in its first seven days, 97 at the top quarter, 409 at the top tenth, 1,010 at the top twentieth, and 4,579 at the top hundredth, across 112,701 active podcasts on that platform.

Those figures describe Buzzsprout-hosted shows in a seven day window under the IAB guidelines. They do not describe the whole market, and they count file requests rather than confirmed listens. They are still the only percentiles in podcasting with a stated population, a stated window, and a stated method. Our podcast downloads benchmarks breakdown covers how to place your show against them without reading a percentile as an average.

Build a plays benchmark from your own data

Five steps, run monthly.

Step 1: Pick one platform and stay in it. Spotify plays and Apple plays are separate series. Never add them, never average them, and never compare a figure from one against a figure from the other.

Step 2: Fix the window and the episode age. A 30 day window for show-level totals, and a fixed episode age such as 30 days for episode-level figures. Comparing a mature episode against a fresh one is the most common way these numbers get misread.

Step 3: Record your app mix from your host at the start of the window. Buzzsprout's July 2026 breakdown puts Apple Podcasts at 36.1 percent of downloads and Spotify at 26.5 percent, with web browsers at 14.2 percent. Your show's mix will differ, and it decides how much of your audience a platform's play count can possibly see.

Step 4: Calculate plays per download inside that platform. Use the download share your host attributes to that app as the denominator. A ratio near or above one suggests people are opening what arrives. A ratio well under one suggests episodes are being delivered and left unopened.

Step 5: Set your benchmark as the trailing median of your own last six comparable periods. That line controls for your genre, your cadence, your geography, and your app mix automatically, because it is built from your show.

Re-baseline whenever a platform changes its counting rule, and note the date you did it. Spotify's June 11, 2026 change is the clearest recent example of a threshold shift that moves every historical comparison.

Reading your ratio without over-reading it

Three things move the plays-to-downloads ratio without your audience changing at all.

Episode length moves it on the platforms with a duration threshold. A 30 second floor is a larger share of a 12 minute episode than of a 90 minute one, and the effect shows up most on short-format shows.

Automatic downloads move it in the other direction. Apps fetch new episodes for people who follow a show, so a growing following audience produces downloads that may never turn into plays for weeks. This is the same dynamic behind podcast listener churn, read from the delivery side.

Back catalogue traffic moves it whenever a new episode brings people to older ones. Fixing the episode age in step 2 is what keeps that out of your trend.

Pair the ratio with a depth metric before drawing conclusions. A strong plays figure with weak consumption rate means people open episodes and leave early, which is a different problem from episodes not being opened. The podcast analytics guide covers how the layers fit together.

What to tell a sponsor

Lead with downloads, because delivery is what sponsors buy and downloads are the only figure with a shared standard behind them. Use plays as supporting evidence about engagement on a named platform.

Quote plays with the platform, the threshold, and the window attached every time. "112,000 Spotify plays at the 30 second threshold, July 2026" is checkable. "112,000 plays" invites a question about method that no seller wants to be answering mid-pitch.

For pricing that sits on top of these numbers, podcast CPM benchmarks and how much to charge for podcast sponsorship cover the commercial side.

Anchor your plays to delivery you can prove

Play counts live inside each platform and only ever describe that platform's slice. The download data underneath them is what makes a ratio meaningful. Podder tracks IAB-compliant downloads, app mix, and audience geography through a prefix that works with most major hosting providers, including Buzzsprout, Transistor, Captivate, Podbean, and Castos. Start with Podder Analytics and build a benchmark from your own numbers.