If you’ve run into trouble, please take a look at these commonly asked questions to see if they address your issue. If not, please use the link in the section at the bottom to create a support ticket.
Please check our Service Health Website if you’re having trouble accessing Fireside or want to check to see if there is a system-wide problem.
Nothing will happen 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.
Here are several links to instructions for setting up a 301 Redirect for various hosts:
This can happen if the MP3 file is too large (over 100MB in size), or when another type of audio file (such as an AAC file) was used. The Fireside team of podcasters and engineers has done extensive testing to find the ideal balance between file size and audio quality. We support MP3 files, which have become the standard for podcasts, and are the most widely supported audio format. We 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.
Fireside updates your MP3 file's metadata from the data you enter for each episode (title, copyright, cover-art, etc.), but will not re-encode, up-convert, or down-convert your audio.
Setting up a custom domain with Fireside is easy, but configuring your DNS provider's settings can be tricky.
To add the custom domain in Fireside, enter it into the Custom Domain field on the Admin > Advanced Settings page. Then, create a CNAME on your DNS provider's website that points your root domain (e.g.
hosted.fireside.fm. (note the trailing
. at the end). 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 (taken from Namecheap.com):
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,
example.com (see the next section for an example).
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 for your custom domain in Fireside, as in this example (taken from Hover.com):
You will then need to setup URL Forwarding from the base domain to
www. This is an important step that people often forget or get confused about. See the image below (from Hover.com) for an example:
Adding a custom domain in Fireside is instantaneous, but it may take up to 24 hours for your new DNS provider to register the change, depending on their settings.
Please submit a support ticket and we will be happy to help you out!
Be sure to include your Podcast's Admin URL in the ticket or we will be unable to help you in a meaningful way. Screenshots are helpful, but without your Admin URL, we won't be able to help.