Feeder Icon

Feeder Support


These are some frequently asked questions about Feeder. You can also find comprehensive help files in the application by choosing Help > Feeder Help from the main menu.





Email Support

If you can't find an answer in the FAQs, you can also send questions to


You can follow and tweet @feederapp.


I own an older version of Feeder, do I need to pay?

Feeder 3 is a major new version and a new license is required, but whether or how much you need to pay depends on when you purchased the earlier version:

  • If you purchased Feeder 2 after the launch of macOS 10.10 Yosemite on October 16, 2014, you qualify for a free upgrade whether or not you purchased directly from Reinvented Software or the Mac App Store.
  • If you purchased Feeder 2 before October 16, 2014, you qualify for a half-price discount of $24.99.
  • There are no upgrade discounts for Feeder 1.x users.


How can I upgrade to Feeder 3?

If you purchased Feeder 2 from the Mac App Store, you can only upgrade through Feeder 3 from this site and need Feeder 2 installed on your Mac from the Mac App Store. When Feeder 3 launches it'll show an alert about the trial period, click Upgrade and follow the instructions. If you do not see an Upgrade button, please get in touch.

Feeder 3 Trial version upgrade panel

If you purchased Feeder 2 directly from Reinvented Software, you can either upgrade by clicking the Upgrade button you see in the trial version, or through the Reinvented Software store:

You will now be shown whether you qualify for a free upgrade or shown the upgrade discount for the new version.


Why doesn't Feeder accept my registration code?

Make sure the code is for the correct version of Feeder. If you purchased the code for a version earlier than 3.0, you can either download that version again from the bottom of the Feeder downloads page or get a new code for Feeder 3. See I own an older version of Feeder, do I need to pay? for more information.

Codes that have been refunded will not work. If you are sure the code was purchased for Feeder 3 and are still having problems, please get in touch.


Can I open my Feeder library in version 2 after opening version 3?

Yes, but any changes you make in Feeder 3 will not be reflected in version 2, and vice versa.


Feeder shows the message "Cannot cd to directory", "Server denied you to change to the given directory" or "No such file" when publishing.

Usually this happens because a path for the feed or server is incorrect. To correct this problem:

  • Open the Servers window by choosing Window > Servers from the menu.
  • Select the server you are using to publish.
  • Clear everything out of the Site Folder field and click the Choose button next to it.
  • Choose the folder where your web site's files are kept. This is usually called "public_html", "htdocs", "yourdomain.com" or similar.
  • Close the Servers window.

The next thing to check is that your feed is set to upload to the correct directory.

  • Select the feed in the sidebar.
  • Choose File > Publish from the menu.
  • Click the Settings button.
  • Clear everything out of the Path field and click the Choose button next to it.
  • Choose the folder where you want to store your feed.
  • Click Continue, then click Publish.

If you need any more help, please get in touch.


How can I track subscribers to my feed?

To track people who've subscribed to your feed, you will need to use a third-party service. Here are some:

Feeder provides support for adding redirects to URLs if necessary, including specific support for Podtrac redirects. See the Help files for more information.

Apple also provides statistics for podcasts listed in its apps on Podcasts Connect.

Feeder has built-in ping services that can tell services such as the above to update after your feed has been published. To use those:

  • Choose View > Show Settings from the menu.
  • Select Pings.
  • Check the services you wish to ping after publishing.


After upgrading to Feeder 3, I get the validation error "No iTunes subcategory chosen".

iTunes now requires that if a category has subcategories, that one of those are chosen instead of just the parent category. To make your feed valid:

  • Choose View > Show Feed from the menu.
  • Select "iTunes Podcasting"
  • In the Store Categories section, click the + button below the list of categories.
  • Choose an appropriate subcategory for each parent category shown in the list above that has no subcategory.

Note that iTunes makes the first category/subcategory the primary one in iTunes. You can rearrange the categories using the up / down buttons below the list.


I've updated my podcast but changes don't appear in the iTunes Store.

The iTunes Store checks for updates to your podcast on its own schedule, and it could take 24 hours for your changes to appear. However, subscribers should see updates the next time they refresh their podcasts. If you subscribe to your feed from the iTunes Store and can see the changes, there is nothing you need to do.

If not, check the status of your podcast in Podcasts Connect.


Where can I get help with my podcast in the iTunes Store?

If you are having problems with your podcast in the iTunes Store and your feed is valid according to the FeedValidator, then you may be able to find answers on the Apple site:


Why does FeedValidator validate my feed but give the warning 'Your feed appears to be encoded as "utf-8", but your server is reporting "US-ASCII" '?

XML files such as the RSS files created by Feeder state the text encoding at the top of the file, like this:

<?xml version="1.0" encoding="utf-8"?>

This is correct - XML files created by Feeder are encoded as UTF-8. However, when a newsreader or browser contacts your server to get a file, the server returns a MIME type, which the web server determines by checking the file's extension against a configuration file. If not found, the web server will default the type to something like "text/text", which suggests a default encoding of US-ASCII.

For RSS feeds created by Feeder, the correct MIME type to return is either "application/xml" for a file with a .xml extension, or "application/rss+xml" for a file with a .rss extension. Having either of these MIME types returned will tell the newsreader or web browser to determine the text encoding from the processing instruction in the file rather than the MIME type.

The solution to this problem is to configure your web server to return the correct MIME type. With Apache this can be done using AddType. Contact your system administrator if you are not able to change this yourself.

In practice, newsreader applications tend to ignore the MIME type when determining text encoding, preferring to check the processing instruction in the XML, if at all.

This is also discussed on FeedValidator's help pages.