The questions most often asked by Fireside customers
Yes, Fireside supports importing from Libsyn, Feedpress, SoundCloud, Squarespace, and from any Apple Podcasts-compatible RSS feed regardless of where you host it. You can import an unlimited number of episodes, too.
It's easy. Just enter the URL for your podcast's feed and we do the rest. We import all of your episodes, MP3 files, and associated metadata, and publish them to your Fireside while you sit back and enjoy your coffee.
No. In fact, nothing happens until you redirect your old feed to your new Fireside feed using a 301 Redirect. This means you can import your old podcast with complete confidence that nothing at all can go wrong. Once you're happy with your new setup, you can put the redirect in place to forward all of your subscribers to your podcast's new home.
Until you do that, none of your subscribers, Apple Podcasts, or any other app directories, services, or podcast clients will know about your new Fireside feed, so it's important to do once you've started posting new episodes to Fireside.
The answer varies depending on where you were hosting your podcast. Here are a few links to hosting services' instructions for redirecting your podcast to a new host:
If you tried to submit your Podcast to Apple Podcasts and it’s being rejected, the solution is often a simple one: Apple Podcasts requires that you have filled out the subtitle and description fields under Settings → Podcast, and that you have at least one published Episode in your RSS feed before it will accept your Podcast. If you don’t, it will be instantly rejected.
All Fireside Podcasts are guaranteed to have RSS feeds that are importable by third-party services, and delivered securely over SSL.
It can take 24-48 hours for a new Episode to appear in many third-party services, and unfortunately there’s no way for you to manually make the process go faster. But rest assured that if the Episode appears on your Podcast’s website, then it is available to everyone, including your subscribers.
Anecdotally, we’ve been told that the more popular a podcast is, the more frequently third-party services will poll your RSS feed. In other words, the more listeners you have subscribing through the third-party service, the more often it will check for new Episodes.
No, they do not! This is a common misunderstanding, and often leads to concern when a Fireside customer publishes a new Episode and it does not immediately appear in iTunes/Apple Podcasts. Here’s how the process works:
This is important, because it means that what appears in iTunes has no bearing on what a subscriber sees in their local iTunes or podcast client. In other words, it doesn’t matter how long it takes for your latest Episode to appear in the iTunes service. Everyone who is a subscriber to your RSS Feed will see the new Episode, because they are polling your RSS Feed directly.
Yes, they do. Although Fireside fully integrates with Spotify’s API to integrate their statistics, you will need to use Stitcher’s and Google Play’s services directly in order to get download counts from them, as they have not yet provided Fireside with access to their APIs as Spotify has. As soon as access is provided to us, we will integrate those platform’s metrics.
You can’t, but fortunately it doesn’t matter! Although it’s possible to roughly estimate a so-called “subscriber count”, the number of people who are polling your RSS Feed is constantly in flux and does not accurately represent a true listener count. So rather than provide our customers with highly innacurate data, Fireside provides Unique Download Counts for every episode. This is the same data that advertisers will ask for, as they understand that “subscriber counts” are meaningless when it comes to measuring a podcast audience. Unique Downloads are all that matters.
Fireside considers every download by a unique, individual human being as one download. We do not differentiate between a file that was downloaded by a Podcast client, a play on the website, a play on the iTunes service, a “stream” of an Episode, or any other kind of download that comes directly from your RSS Feed or the Fireside service.
We have done our very best to create smart algorithms to determine real versus false or incomplete downloads, and we are constantly working to improve and update these algorithms as new podcast clients are developed. Fireside metrics are IAB compliant.
Don't worry, all Fireside feeds are valid. Unfortunately, although Feed Validator is ancient, antiquated, fragile, and wrong, many people still seem to use it to check Podcast Feeds.
Fortunately, we have the podbase Podcast Validator, a modern and superior solution. Try validating your Fireside feed there for more accurate results.
Fireside recommends the following MP3 export settings, which are considered to be the industry standard:
mono, 64-96kb/s, 44.1k sample rate
These settings represent the perfect compromise between quality and file size, and is a widely accepted standard. Even multi-hour-long episodes with several hosts, sound effects, and music will come in below the 100MB mark using these settings.
For more information, please review Apple‘s file export guidelines.
We support MP3 files, which have become the standard, and are the most widely supported audio format. MP3 files must be 100MB or less in size, which is easily attainable by using our Recommended MP3 Export Settings.
Fireside will update your MP3 file's metadata from the episode (title, copyright, cover-art, etc.) for all files you upload or import, but will not re-encode, up-convert, or down-convert your audio.
Unfortunately, you cannot just add
https:// to the URL for a domain and expect it to work. Only websites which have SSL certificates can be served via
https://. Fireside itself has a SSL certificate, as does all of its subdomains (like yourpodcast.fireside.fm), so they are served securely via
https://. Just adding your custom domain to Fireside doesn’t create a SSL certificate for it.
Fortunately, we have developed a (free!) SSL certificate aquisition and integration feature for customers with custom domains. Just flip the toggle switch in your Domains section to turn it on.
Visit the Episode’s admin page to see the cause of the trouble, which should appear at the top of the page in a red alert box. The most common reason for MP3 files not being imported is due to file size. Fireside supports MP3 files that are 100MB or less in size. Once you have a replacement MP3 ready, you can manually upload it on the Episode’s admin page without having to re-create the Episode.
This usually happens when your previous Podcast hosting provider limits the number of Episodes in your feed. Because Fireside uses your previous RSS feed to import Episodes, the importer is limited to what’s made available by the provider.
Unfortunately, many providers are guilty of this behavior (including Libsyn, Squarespace, and others). There isn't an easy way to overcome this limitation, but it may be possible to change this setting within the admin of your previous hosting provider.
Some Fireside customers have reported success by switching all Episodes after 100 into Draft Mode, running the import, then switching them back to Published, flipping the next 100 to Draft, and running the import again to get the next 100, until all Episodes have been imported. Other customers have re-created the Episodes within Fireside manually.
Fireside websites are fully responsive and look great on Macs, PCs, and are automatically optimized for mobile devices. We are working on a gallery/discovery section, but until then, checkout one of our customer’s podcasts, Very Bad Wizards.
You can see screenshots of the administration dashboard and more on the Features page.
Try restarting your browser, or wait a bit. Our CDN caches your images, and it takes a few minutes for the cache to be purged.
If you saw an error such as
Error 503 Backend fetch failed or received a blank page after an attempted upload, this is typically due to connectivity issues somewhere between you and Fireside’s infrastructure. It might be due to a slower connection on your end, or just trouble somewhere in between.
Unfortunately, it is essentially impossible to determine where or why the issue has occured. Fortunately, this error usually resolves itself if you wait a short while, or try from a different location, so waiting and trying again later is your best action.
Absolutely! Setting up a custom domain with Fireside is easy, but configuring your DNS provider's settings can be tricky.
In the Domains section of your Podcast’s admin, you will find detailed instructions for many different registrars as well as general purpose instructions which can be used to help you setup your DNS records correctly.
You can delete a Podcast by visiting its Settings → Advanced page, and clicking the red Delete Podcast button.
Deleting a Podcast is irreversible, and will result in the removal and deletion of all episodes, MP3 files, hosts, cover art, header art, and all other associated content. Once a Podcast is deleted, there is no going back.
If you are switching to a new host, you can redirect your RSS feed from Fireside to the new host by visiting Settings → Advanced page and enabling that option. The redirect only works while your Fireside Podcast still exists, so you might want to wait to delete the Podcast. We recommend keeping the redirect (and Podcast) active for at least 30 to 60 days after you’ve switched.
Note: Deleting a Podcast is not the same as deleting your account. See the section on deleting your Account for more information.
You can cancel your Account (deleting all Podcasts and associated data) at any time. Just click the My Account link in the navbar, then click Subscription in the sidebar, and click the red Delete Your Account button.
This will delete all of your Podcasts and their associated data. Please see the section on deleting your Podcast for more information.
If you are still in your trial period, your credit card will not be charged.
Yes. There's a bookmarklet that lets you add links with one click. Watch the video below for a demo.