Podcast Hosting

Podcast hosting where the feed never goes down.

For a podcast the most-requested URL is not a page. It is the feed, polled relentlessly by apps that never read a word of your site.

Feed answered from cacheRange-request audioRelease-day polling absorbed
Feed cachingRange requestsEdge mediaLarge storageDaily backups24/7 support
Built for listeners

The feed is the product.

Everything a podcast site does at scale happens at two URLs: the RSS feed and the audio file.

A feed polled by thousands of apps

Podcast clients re-fetch your feed on a schedule whether or not anything changed. Answered from cache with correct validators, most of those requests never wake WordPress at all.

Cached feedConditional requests

Audio that streams, not downloads

Episodes are served with range requests, so a player fetches the part it needs and can seek without pulling the whole file. Nothing occupies a PHP worker while somebody listens.

Range requestsEdge-served

Release day handled at the edge

A new episode brings a burst as apps notice at once. That burst hits the edge cache rather than the origin, so publishing is uneventful.

Storage that grows with the back catalogue

A weekly show is a few gigabytes a year and never shrinks. Storage is part of the plan and can be topped up without moving anything.

Show notes recoverable

The audio may live elsewhere, but the episode posts, transcripts and artwork live here — and are in the daily backup.

Distribution

Apps are your biggest audience.

Most of your traffic is software rather than people: clients polling a feed on a timer. It is the cheapest traffic to serve correctly and the most expensive to serve badly.

  • Feed answered from cache and revalidated cheaply
  • Audio streamed with seek support
  • Storage sized for the back catalogue
  • Release-day polling absorbed at the edge
RSS feed
Cached, revalidated
hit
Episode audio
Range-request enabled
streaming
Back catalogue
Stored and served
182 eps
New episode
Propagating to apps
publishing
Delivery

One feed, thousands of pollers.

Podcast traffic is repetitive by design, which makes it almost entirely cacheable — provided the feed sends the headers that let a client skip the download.

Edge
delivery in 14 regions
Range
requests for audio
NVMe
storage for the catalogue
MagicWP30 ms
Typical shared host480 ms
Origin without edge cache190 ms

Illustrative comparison of a feed request. Your numbers depend on episode count and feed size.

Configuration

What we change for podcasts

Two URLs carry almost all the load, and both are static between publishes.

SettingWhat we doWhy
Feed cachingCached with validators, purged on publishPodcast clients poll on a timer regardless of changes, and a correctly validated feed answers most of those without rendering anything.
Audio deliveryRange requests, served from the edgeWithout range support a player cannot seek, and every listen ties up a worker for the length of the episode.
StorageSized for a growing back catalogueArchives only ever get bigger, and a show that has to delete old episodes has a hosting problem rather than an editorial one.
Publish purgeFeed and episode page onlyA release should invalidate the two things that changed, not discard every warm cache entry on the site.
ArtworkOptimised on uploadCover art is delivered large to directories and small to players, from one original.
Plans

Simple, transparent pricing.

Every plan includes free migration, daily backups, SSL and 24/7 support.

MonthlyYearly 2 months free
Starter
For personal sites, blogs, and portfolios.
$20/mo
  • 1 WordPress site
  • 10 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Support tickets
Start free trial
Pro★ Most popular
For growing businesses and busy stores.
$80/mo
  • 5 WordPress sites
  • 50 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Priority support tickets
Start free trial
Enterprise
For agencies and high-traffic platforms.
$250/mo
  • 20 WordPress sites
  • 200 GB NVMe disk
  • Free SSL
  • Daily backups
  • One-click deployment
  • Dedicated support
Start free trial
FAQ

Questions, answered.

Should I host the audio files here?
You can, and storage is part of your plan. Many shows use a dedicated podcast host for analytics and keep the site here — both work, and the edge cache serves either.
Why is my feed slow when the site is fine?
The feed is usually the least cached URL on a podcast site and the most requested. If every poll renders it from scratch, thousands of apps are regenerating it for no reason.
What happens on release day?
Apps notice at roughly the same time, which is a burst rather than a ramp. It is served from the edge, so the origin sees a fraction of it.
Can listeners skip ahead in an episode?
Yes, that is what range requests are for. Without them a player has to download from the start, which is why seeking feels broken on some hosts.

Publish without watching the dashboard.

Bring the show across — migration is free, back catalogue included.