What changed for paid Substack podcasts on Spotify?
Substack updated its paid-podcast distribution guidance on September 2, 2026. A Substack podcaster can connect a paid feed to Spotify through Spotify Open Access so paying subscribers can listen in Spotify while Substack remains the subscription platform.
The integration can move listening access into an app subscribers may already use. It does not remove the creator’s feed-architecture decision. A show that is not yet listed on Spotify has a relatively direct setup path. A show that already has a public listing must decide whether the paid episodes belong in that existing listing or in a second, clearly differentiated paid feed.
Make that decision before pressing Sync. The safest operating sequence is Choose, Map, Connect, Route, and Verify. It treats the integration as a listener-access handoff, not as evidence that the show will gain discovery, subscribers, conversions, revenue, retention, or any other platform outcome.
Should you replace the public RSS feed or create a separate paid feed?
If the show already has a Spotify listing, Substack documents two options. The creator can replace the public RSS feed sent to Spotify with a feed that contains free and paid episodes, preserving the existing listing and followers. Or the creator can keep the public feed and create an additional paid feed with a distinct title.
A combined feed gives listeners one show page. Free listeners can see locked paid episodes, while subscribers can link their Substack account for access. A two-feed architecture preserves separate free and paid listings. Substack specifically points to dynamic ads or a high share of free previews as reasons a creator may prefer that separation, but both versions will appear in Spotify search and listings.
The choice is operational, not universal. Start with the membership promise and fulfillment boundary: what does a paying listener receive, which public episodes still need a stable home, and what must remain distinct? Then choose the smallest feed architecture that represents those promises without forcing listeners to guess which listing applies to them.
| Decision | Combined feed | Separate free and paid feeds |
|---|---|---|
| Spotify listing | Existing listing receives free and paid episodes | Both listings remain visible and need distinct names |
| Listener path | One page shows free episodes and locked paid access | Free listeners need a clear route to the paid listing |
| Operating burden | One listing and one primary route to verify | Two listings, links, episode relationships, and states to maintain |
Which Substack episode states will sync to Spotify?
Substack says syncing sends all current and future episodes in the feed to Spotify, with one stated exception: episodes restricted to founding members do not sync. It also says Spotify does not currently support free previews of episodes in this integration. Those boundaries should be visible in the access map before the creator promises that the Spotify version mirrors the Substack listening experience.
Map at least four states: free episode, paid episode, founding-member episode, and free preview. Record what exists on Substack, what is expected to appear on Spotify, which listener account state is required, and where an unsupported item should send the listener instead. Do not quietly convert a founding-only episode into a general paid episode or a free preview into a full free release just to simplify the map.
This is a different decision from audience-specific blocks inside one Substack post. That workflow governs which written block a subscription state sees. The feed map governs whether an audio episode can travel into Spotify at all and which listing or lock represents it.
- Free: confirm that the public episode appears in the intended Spotify listing.
- Paid: confirm that the episode appears with the intended access state and can be opened after account linking.
- Founding: keep a separate listener route because founding-member episodes are excluded from the sync.
- Free preview: keep a separate route or explanation because episode previews are not supported by this integration.
How do you connect the feed without creating a duplicate Spotify show?
Use one deliberate connection path. For a show that is not yet on Spotify, Substack provides a Sync to Spotify flow. For an existing listing that should become the combined feed, Substack provides a manual setup URL that the creator uses to replace the RSS feed in Spotify settings. For a separate paid feed, the creator uses the sync flow and then gives the new listing a title that distinguishes it from the public show.
The clearest failure warning in Substack’s guidance is about duplicate submission: after syncing through Substack, do not separately submit that RSS feed through Spotify for Creators as another show. Substack says that second submission creates an accidental duplicate. Before setup, record the existing Spotify show URL, current feed host, chosen destination, person making the change, and rollback path in the creator publishing source of truth.
Spotify says third-party paid podcasts must use a subscription platform integrated with Spotify. The subscription platform continues to manage the show and paid relationship. Availability, eligibility, supported partners, and the exact setup interface remain controlled by Spotify and Substack, so verify the current controls in both accounts rather than relying only on a saved checklist.
How should listeners be routed after the connection?
A correct connection can still produce a broken handoff if the public links point to the wrong listing. Substack tells creators to update the Spotify links shown on their podcast and episode pages after setup. In a one-feed architecture, that route should lead to the combined listing. In a two-feed architecture, the free and paid destinations need to remain distinguishable.
When two feeds remain, the paid title should clearly identify the subscriber version. Substack also documents a promotional banner that can link the free Spotify feed to the paid feed after at least one paid episode is uploaded. Treat that banner as a route, not a promise that a listener will subscribe or that Spotify will favor either listing.
Write the listener instruction from the starting state. A free listener needs to know which show page contains the public catalog and where paid access begins. An existing paid subscriber needs to know how to link the Substack account. A founding member or someone expecting a free preview needs an explicit fallback because those episode states are not supported in the sync.
When should a creator use Spotify Synced Feeds?
Spotify Synced Feeds can merge a separate free feed and paid feed into one episode list on Spotify, hide paired duplicates, and change what the show page displays according to subscriber access. Non-subscribers can see free episodes, locked bonus episodes, and paid-content prompts. Subscribers can see premium versions, bonus episodes, and free episodes that do not have a paid counterpart.
This is an optional layer for a two-feed architecture, not a reason to create two feeds by default. Spotify says both the free and paid podcasts must be claimed with the same Spotify account, the show must be hosted elsewhere, and setup and management happen on the web rather than the mobile app. Analytics and follower counts remain separate even when the display is synced.
Episode pairing also needs review. Spotify may approve high-certainty pairs automatically and send lower-certainty matches for manual approval. Similar titles can help matching, but the creator should inspect each pair, the subscriber benefit attached to it, and any unpaired episode before treating the combined display as complete.
What should you verify before announcing Spotify access?
Verify the result as more than one account state. Open the intended public or free listing as a non-subscriber and confirm the free catalog, locked episodes, show name, and route to paid access. Then use an eligible paid subscriber state to confirm account linking and playback. Check the founding-only and free-preview fallbacks separately because absence in Spotify can otherwise look like a publishing error.
If two feeds are active, search for the show and confirm that the titles make the listings distinguishable. If Synced Feeds is active, review pending and approved episode pairs from the web dashboard, then inspect both the free and subscriber show pages. Spotify notes that updates can take time, so record what was checked and when instead of declaring failure from one immediate refresh.
Finally, recheck every Substack-to-Spotify link and preserve the feed decision, access map, destination URLs, owner, and rollback notes. The handoff is complete when each intended listener state has a clear route and unsupported states have an honest fallback—not when the sync button reports success.
- Listing: the intended show exists, has the expected title, and is not duplicated by a second submission.
- Catalog: current free and paid episodes appear in the chosen architecture; excluded states are documented.
- Access: non-subscriber, paid-subscriber, founding-member, and preview expectations are checked separately.
- Pairing: Synced Feeds pairs, subscriber benefits, and unmatched episodes are reviewed when that feature is used.
- Routing: Substack pages, Spotify listings, banners, and listener instructions point to the intended destinations.
- Ownership: one person owns the next review and the rollback path if the architecture needs to change.