Fable and Folly network closing: producer checklist

The Fable and Folly network closing takes effect on December 31, 2026, according to the network. Fable and Folly says it will help producers move to new hosting and advertising partners through the end of the year. Producers now need to confirm feed control, replacement hosting, episode GUIDs, and redirect timing before network access ends.

Fable and Folly's announcement attributes the decision to changes in the podcast industry, especially advertising, and the investment the company believes it would need to keep pace. The company says it grew from about 12 shows in 2020 to a historical roster of more than 200. That figure is self-reported and does not establish how many active shows currently need to move.

What the Fable and Folly network closing means

The network says the shows are heading to new homes and that it is connecting producers with hosting and advertising partners. It has not published a migration calendar for individual shows or guaranteed that every series will keep the same schedule, feed, or paid subscription offer.

Podnews reported the closure on October 5, 2026. The Fable and Folly homepage itself does not display an announcement date, so October 5 should be treated as the date of the Podnews report rather than the date of the network statement.

Fable and Folly has also paused Plus plans. Its homepage says subscribers should no longer be charged beginning October 6, 2026, while retaining access to shows still on the network through year-end. Subscribers should keep the confirmation and check their own billing record because the company's wording stops short of an unconditional billing guarantee.

Producers should confirm RSS control first

A hosting move depends on access to the old RSS feed. Ask Fable and Folly, in writing, who controls the current feed and who can configure its redirect. Record the old feed URL, the deadline for changes, the replacement contact, and the date the old account will become unavailable.

The RSS feed glossary explains why this file carries show and episode metadata to podcast directories. The enclosure URL glossary covers the episode-level address that points apps toward each audio file. Both need to work after the transition.

Choose the replacement host and import the show while the old feed remains accessible. Compare both feeds before redirecting. Apple's hosting-provider migration checklist tells producers to keep the show title, description, artwork, audio, season numbers, episode numbers, and episode GUIDs consistent.

GUIDs deserve a separate check. A GUID identifies an episode even when its title or media URL changes. Apple warns that changing GUIDs can create duplicate episodes and disrupt analytics. Compare a sample from the beginning, middle, and recent end of the catalog instead of checking only the latest release.

Arrange the redirect before the deadline

Ask the old host to return a permanent HTTP 301 redirect from the old feed to the new feed. Apple says a redirect performed through the old provider moves followers in Apple Podcasts and other podcast apps that read the feed. Editing the feed URL inside Apple Podcasts Connect is an Apple-only fallback when the old feed is inaccessible. It does not update other directories.

For self-hosted feeds, Apple's RSS feed URL guidance calls for both a 301 redirect and an <itunes:new-feed-url> tag. Apple says to maintain them for at least four weeks. That is Apple's migration guidance, not a promise from Fable and Folly about redirect availability, so producers should agree on duration before December 31.

After the redirect goes live:

1. Request the old feed and confirm that it resolves to the intended new feed.
2. Play an older episode and the newest episode through normal listening apps.
3. Check titles, artwork, dates, numbering, explicit labels, and episode order.
4. Look for duplicate episodes caused by changed GUIDs.
5. Confirm that the next release appears from the new host.
6. Record the cutover time in your analytics notes.

Host dashboards may count the change differently. Apple says its own Podcasts Analytics should remain consistent, while hosting dashboards can show atypical download patterns after a move. Use the podcast analytics audit to document the cutover and keep pre-move and post-move reporting definitions visible.

Producers need a transition record

Keep an operational copy of files and records you may need after the network closes. As a practical precaution, that can include raw audio, artwork, transcripts, current descriptions, publishing dates, analytics exports, advertising agreements, revenue records, paid-subscriber terms, and contact details for active campaigns. These backup steps are editorial recommendations rather than requirements stated in Apple's migration pages.

Advertising needs its own handoff. Identify which inserted campaigns remain active, who controls future insertion, where approvals live, and which party will issue final reports or invoices. Avoid assuming that a hosting introduction also transfers an advertising contract.

Listeners should follow each show's own website, newsletter, and social accounts for its confirmed destination. Fable and Folly says it will share links as producers settle into new homes. A directory listing that still plays today does not confirm that the feed has completed its move.

Producers should obtain written answers on feed ownership, redirect duration, hosting cutover, and advertising responsibilities while the network team is still available. Then test the public feed and released audio before calling the transition complete.

Start with Podder Analytics to create a fresh measurement record after the hosting move.