Selecting where you host your podcast media files is critical to the experience your audience will have with your podcast and your website.
WARNING: Do not host your media files (such as mp3 audio or mp4 video) on the same account as your website.
Web hosting is not designed to serve large files that will have sporadic downloading behavior. Podcasting by nature will cause download spikes that typically occur during the 1-3 days following the release of a new episode. These spikes also may occur when your podcast is featured on a website or iTunes.
The last thing you want is for your website to become unreachable. This happens all too often when podcasts are hosted directly on the website.
Think of your web server’s internet connection as a pipe that limits how much data can be transferred at any given point. The server’s internet connection, for the sake of example, may be 100Mbps. If you have a 60 minute mp3 file hosted on your server and 100 listeners try to download that podcast at the same time, your server will only be able to serve each media file at 1Mbps. With today’s internet speeds, the user downloading the podcast will perceive there is a problem due to the slow downloading. Furthermore, the other 99 downloads will choke your website from normal web traffic during the download spike. The end result is a negative impact on your media delivery and your website.
The best solution is to use a reputable podcast hosting service that utilizes a top-tier CDN (Content Delivery Network) service with podcasting best practices built-in.
Requirements for hosting podcast media files
When picking a podcast media host, make sure they support the following features.
- HTTP/1.1 compliant – Required for most applications including iTunes
- Byte serving and byte range request – Required by iTunes and many other portable devices and smartphones
- World class content delivery network – Guarantees fast delivery of media to your audience
- Audio/video content types – Critical for serving media to portable devices such as iPhone and Android
- All valid HTTP methods supported – All types of HTTP requests (e.g. HEAD, GET, etc.) must be supported to guarantee media delivery to portable devices and software such as Tunes.
- Default HTTP protocol – FTP (ftp://) and other non-HTTP protocols limit what applications and devices can download your media. Media should be served using the default (http://) protocol.
We recommend Blubrry’s Podcast Media Hosting.
Blubrry’s Podast Media Hosting uses their top-tier content delivery network (CDN) configured and optimized specifically for podcasting. CDN’s are designed to handle spikes in downloads and delivery performance by serving podcast media closest to where the request occurred. Blubrry’s CDN has over 50 dedicated data centers throughout the world. When podcasts are hosted by Blubrry, download spikes will not effect your website, your audience will be able to download your episodes as fast as their internet connection allows.
Blubrry’s Podcast Media Hosting also supports streaming for seamless playback on the web. Combined with web-based HTML5 player such as the players packaged with Blubrry PowerPress or Blubrry’s own Blubrry Player, episodes can be played nearly instantly without any negative effect to your website.
Blubrry Podcasting and its parent company was founded by podcasters in 2005. Blubrry is the only podcast hosting service that includes free support including by phone and video conferencing support. If you need to talk to an podcasting expert, Blubrry is ready to help you.
Where NOT to host your podcast media
In general, you should NOT host your podcast media on the following:
- services that are not fully HTTP/1.1 compliant
- archive.org – Not completely HTTP/1.1 compatible
- CloudFlare – Known podcast feed and Media Issues
- Incapsula – Known podcast feed and Media Issues
- Your own website – Performance issues
- DropBox – URLs constantly change, violates TOS
- Google Cloud Drive – URLs do not work in podcast apps, violates TOS
- Microsoft OneDrive – URLs do not work in podcast apps, violates TOS
- Google Docs – URLs do not work in podcast apps
- Microsoft SharePoint – URLs do not work in podcast apps,
- Microsoft Office online – URLs do not work in podcast apps
- Confluence – URLs do not work in podcast apps
- Box – URLs do not work in podcast apps
- Igloo – URLs do not work in podcast apps
Archive.org is not a good place to host podcasts.
Though it is a good idea to upload your podcast media to archive.org as a backup, it is not ideal for hosting your podcast for distribution. Archive.org is not set up as a content delivery network and the delivery of your media files is not guaranteed to be served with the necessary requirements for podcasting.
CloudFlare and Incapsula are not compatible with podcasting
Though CloudFlare and Incapsula may be excellent services for enhancing the performance of your website or to deal with a DDoS (denial of service) attack, they are not compatible with podcasting. These services are not intended to host large media files. Media files downloaded through CloudFlare or Incapsula typically prematurely fail during downloads, leading to applications such as Apple podcasts to only download and play the first portion of each episode. Depending on the security mode they are in they can also block valid requests such as HTTP HEAD requests that are common for podcast applications. It is typical with these services for podcast feeds to be inaccessible by some subscribers as well as by podcast directories, most notably Apple Podcasts directory.
Podcast feeds are also effected by these services. Depending on the security levels used in these services they can inadvertent block non web browser user agents, such as Apple podcasts’s “iTMS” user agent. iTMS is the user agent Apple uses for updating the iTunes podcast directory.
Your own website is a terrible place to host podcast media files
Of the many reasons it is a bad idea to host your media on the same server as your website, the primary reason due to media file size. Large media file downloads can cause your website to come to a crawl following the release of new episodes. Websites have a finite amount of bandwidth available which can lead to bottle necks at any given time causing your web pages to load slowly, typically on release days of your podcast episodes. Typically the bandwidth and resources needed to host a healthy podcast far exceed the demands of a normal web hosting provider, which is why there are companies like Blubrry Podcasting who specialize in using top-tier CDN networks in order to distribute podcast media across the world without issue.
Hosting services that are not HTTP/1.1 complaint
Believe it or not, there are many services that are not completely HTTP/1.1 compliant. If you are technology savvy, you can use tools do determine if a web service is complaint by testing for byte serving and HEAD request support. if your podcast hosting company does not support the HTTP/1.1 protocol including HEAD and byte range requests, find a new service immediately!
Cloud storage does not work with podcasting
Services such as DropBox, Cloud Drive and Microsoft OneDrive have specific terms of service that do not allow you to use the service for content distribution. These services may throttle download bandwidth, not fully support the HTTP/1.1 protocol and/or terminate your service for violating their terms of service. Furthermore, URLs that these services provide are not permanent, requiring you to update your podcast every few days with the latest valid URLs.
Document sharing services do not work with podcasting
Services such as Google Docs, Microsoft SharePoint, Microsoft Office online, Confluence, Box, and Igloo are designed for sharing documents and files within a web browser-based ecosystem. Such platforms are not designed to host podcast media files.