The questions most often asked by Fireside customers
Yes, Fireside supports importing from Libsyn, Feedpress, SoundCloud, Squarespace, and from any iTunes-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, iTunes, 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:
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:
mono, 64kb/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.
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.
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.
Absolutely! Just enter your custom domain into Fireside, and create a CNAME in your DNS pointing your root domain (e.g.
example.com), usually abbreviated as
hosted.fireside.fm. (note the trailing
.). Make sure to use the same URL in both places — if you enter
example.com as the CNAME in your DNS, make sure to enter
example.com as your Custom Domain in Fireside. See the image below for an example:
If you'd like for
www.example.com to also work, you'll need to setup a 301 redirect (sometimes called a "forward") at your DNS provider to redirect
www.example.com to your base domain,
If your DNS host won't allow you to map a CNAME as the root domain, we suggest using a CNAME that maps
hosted.fireside.fm. instead and entering
www.example.com as your custom domain in Fireside. You'd then setup URL Forwarding from the base domain to
www. See the image below for an example:
Although adding a custom domain in Fireside is instantaneous, it may take up to 24 hours for your new CNAME record to start working, depending on your DNS provider's settings.
Yes. There's a bookmarklet that lets you add links with one click.