Episode 45 weighs 65 MB. A hundred simultaneous downloads—the shared host throttles, WordPress slows, the host sends a "bandwidth exceeded" email. A podcast is not an HTML page: large files streamed or downloaded repeatedly by listening apps. Same server as the blog means sharing an elevator with pallets of bricks.
A podcast combines an RSS feed, audio files (MP3 or Opus), and metadata. The site presents episode notes; audio can live elsewhere—and should, once audience exceeds a few hundred listens per month. Confusing the two consumption patterns (light web requests vs gigabytes of audio) leads to billing surprises and brochure sites slowed by show success.
Good architecture does not require an expensive platform from episode one. It requires separating what scales in requests from what scales in gigabytes—before growth forces an emergency migration.
Audio hosting options
| Option | Advantages | Limits |
|---|---|---|
| Same web host | Simple, one account | Bandwidth, heavy backups |
| Object storage + CDN | Predictable GB cost, scale | More technical RSS setup |
| Podcast platform (Anchor, Acast, etc.) | Little infra to manage, stats | Partial dependency, limited branding |
| Pro podcast host (Buzzsprout, Transistor) | RSS, analytics, support | Monthly subscription |
Same web host suits launch: a few dozen listens, files in /wp-content/uploads/, RSS from a plugin. Once the show takes off, bandwidth becomes the main cost—not PHP CPU.
Object storage + CDN (S3, Scaleway Object Storage, OVH Object Storage) offers predictable cost per gigabyte transferred. The RSS <enclosure url="..."> tag points to CDN, not WordPress. See choosing a cloud region to place the bucket near your audience.
Recommended architecture: separate site and audio
A healthy architecture rests on four distinct blocks:
- Site—WordPress, static site, or headless CMS for episode pages and notes.
- Audio—object bucket with CDN, or dedicated podcast host depending on budget and skills.
- RSS—stable URL;
<enclosure>points to CDN or platform, never/wp-content/uploads/in production. - Stats—podcast platform or prefix analytics (Podsights, etc.); Apache logs alone undercount listens via third-party apps.
Opus or AAC reduces bandwidth vs 128 kbps MP3—test compatibility with major listening apps before switching. Perceived quality matters, but a file half the size also halves transfer cost.
Bandwidth: orders of magnitude before deciding
1000 listens × 50 MB ≈ 50 GB transfer per episode. Ten popular episodes = 500 GB/month—well outside standard shared quota. Calculate before "putting everything on the site":
| Monthly audience | Episode size | Estimated transfer |
|---|---|---|
| 500 listens | 40 MB | 20 GB/episode |
| 2000 listens | 50 MB | 100 GB/episode |
| 10,000 listens | 60 MB | 600 GB/episode |
For heavy video, logic is identical; podcast stays lighter than 4K video but far heavier than an optimized CSS page or image. Compare object storage and CDN in the directory before committing to a single web host.
The peak: podcast scales in gigabytes — site in requests
"Unlimited hosting" marketing does not mean the same thing as your RSS feed. A brochure site consumes requests; a podcast consumes gigabytes. Mixing both on shared hosting bets your audience stays modest—a bet many lose.
Decide and move forward without blind spots
Before publishing the next episode:
- Estimate monthly transfer (expected listens × average episode size)—round up if launching a promotion campaign.
- Separate
<enclosure>URL from WordPress hosting once you expect more than 100 GB/month transfer. - Try a free platform as proof of concept, then plan RSS migration if audience exceeds expected threshold.
- Monitor web host quota—alert at 80% of cap avoids cutoff mid-episode release.
Frequently asked questions
Can I host my podcast on web hosting?
Yes for small audience: MP3 and RSS on same domain suffice at launch. As downloads grow, bandwidth and cost explode—a CDN or podcast host becomes cost-effective before first billed overage.
Difference vs Spotify for Podcasters or Anchor?
Free platforms hosting audio and RSS, with stats and sometimes monetization. Less total control, migration possible via RSS redirect. Ideal to start without managing infrastructure—plan exit if show grows.
CDN mandatory?
Recommended beyond a few hundred listens per month. Same logic as heavy Jamstack assets: large files, long cache, predictable cost per gigabyte.
Same domain or subdomain?
Website here (WordPress or static); audio often on CDN or feed subdomain (feeds.domain.tld). Separating avoids audio downloads slowing the brochure site.
If your podcast grows, the question is no longer "where to put the MP3"—it is "who pays for the gigabytes." The answer is rarely: the same shared host as the blog.