Average podcast downloads per episode calculator
8 episodes with 12,500 downloads between them average 1,562.5 downloads per episode. Use the same set of episodes and the same time window for both numbers so the benchmark holds up with sponsors. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Total downloads
- 12,500
- Episode count
- 8
- Average downloads per episode
- 1,562.5
Average podcast downloads per episode turns a cumulative download total into a comparable episode-level figure. Enter the downloads recorded across a defined set of episodes and the number of episodes represented by that total. The calculator divides the total by the count and returns the exact arithmetic average. It is useful for reporting, sponsor conversations, release comparisons, and routine audience tracking, provided both inputs cover the same shows, time window, and measurement rules.
Choose a consistent total and episode set
Start with a download total that belongs to a clearly defined group of episodes. The episode count must describe that same group: if the total covers twelve published episodes, enter twelve, not the full number in the podcast archive. Consistency matters because an average can look precise while combining incompatible periods.
For example, downloads collected during the first thirty days after release should not be mixed with lifetime downloads for older episodes unless that difference is intentional and disclosed. Decide whether trailers, bonus releases, reruns, or private-feed episodes belong in the analysis, then apply the decision to both fields. Use the unrounded total supplied by your analytics provider when possible.
The calculator accepts zero total downloads, which correctly produces an average of zero when at least one episode is present. It rejects a zero episode count because division by zero does not describe a meaningful per-episode audience. Recording the reporting window beside the result makes later comparisons easier to interpret and reproduce.
Understand the calculation and its limits
The calculation is total downloads divided by episode count. If eight episodes received 12,500 downloads together, the average is 1,562.5 downloads per episode. A fractional result is valid even though an individual download is a whole event: the fraction represents an average distributed across the episode set, not a partial listener action.
This arithmetic mean gives every episode equal weight and is most informative when episodes had comparable time to accumulate downloads. One unusually popular release can pull the mean upward, while a new episode with only a day of data can pull it downward. For a fuller performance review, consider looking at the median and the distribution of episode totals alongside this result.
Also confirm how your analytics source defines a download, filters bots, and handles repeated requests. The calculator performs arithmetic on the values provided; it does not reconcile definitions across hosting providers, remove outliers, estimate listeners, or claim that downloads equal unique people.
Use the result in reporting and planning
A per-episode average creates a compact benchmark for tracking a show over time. Calculate it for comparable release cohorts, such as each quarter's episodes measured thirty days after publication, and you can see whether typical reach is changing without letting a larger publishing schedule inflate the total. When sharing the number with sponsors or colleagues, include the episode count, collection window, and source so the figure remains auditable.
The returned object repeats both inputs beside the average for that purpose. Avoid presenting the result as a guaranteed audience for the next episode: topic, guest, promotion, seasonality, and distribution changes can all affect performance. For forecasting, treat the average as one historical reference and combine it with recent episode-level results.
Because the operation is deterministic, identical valid inputs always produce the same result.
What you can do with it
Prepare a sponsor benchmark
Convert a clearly defined campaign or release cohort total into a per-episode figure that can be shared with its measurement window.
Compare publishing periods
Normalize quarterly download totals by the number of episodes published so different release schedules can be compared more fairly.
Automate audience reporting
Add a deterministic average to a dashboard or recurring report using totals and counts already produced by podcast analytics.
FAQ
Can total downloads be zero?
Yes. A zero total with a positive episode count produces an average of zero downloads per episode.
Can the result contain a decimal?
Yes. The arithmetic average may be fractional even though each recorded download is a whole event.
Does this calculate unique listeners?
No. It averages the download total you provide and does not convert downloads into people or reconcile analytics-provider definitions.
Should I include trailers and bonus episodes?
Decide once and apply it to both numbers. If the total includes trailers, bonus releases or reruns, count them as episodes too; if you leave them out of the count, take their downloads out of the total as well.
Why can one episode distort the average?
Because every episode carries equal weight. One unusually popular release pulls the average up, while a brand-new episode with a single day of data pulls it down. Compare episodes measured over the same number of days after release.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/biz/podcast-download-per-episode-avg \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"total_downloads":12500,"episode_count":8}'const res = await fetch("https://api.kit.forhosting.com/biz/podcast-download-per-episode-avg", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"total_downloads": 12500,
"episode_count": 8
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/biz/podcast-download-per-episode-avg",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"total_downloads": 12500,
"episode_count": 8
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/biz/podcast-download-per-episode-avg", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"total_downloads":12500,"episode_count":8}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"total_downloads":12500,"episode_count":8}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/biz/podcast-download-per-episode-avg", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"total_downloads": 12500,
"episode_count": 8
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "biz.podcast_download_per_episode_avg",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Use the result in reporting and planning
Browser use is convenient for an occasional calculation, while the API costs $0.002 per request and fits recurring dashboards or reporting workflows.
Technical questions
What formula does the calculator use?
It divides total_downloads by episode_count and returns the result as average_downloads_per_episode.
What happens if the episode count is zero?
The request returns an invalid_input error because a per-episode average cannot be calculated with zero episodes.