Podcast Hosting Account After Death: Preserve The Show And Feed
A podcast hosting account after death can become a surprisingly urgent digital-estate problem. The public show may still look healthy in listening apps, even while the credit card paying for its host is about to expire, its domain is nearing renewal, advertising money is accumulating in an inaccessible account, and nobody knows where the original audio files live.
The podcast is rarely contained in one place. Its host stores or serves episodes and generates the RSS feed. Apple Podcasts, Spotify, and other directories read that feed or maintain separate platform records. A registrar controls the domain. Cloud drives may hold master recordings. Advertising, subscriptions, donations, and sponsors create separate payment and contract obligations. Email and social accounts connect the show to listeners.
The safest response is therefore not to start changing passwords or deleting profiles. First map the system, preserve its assets, establish authority, and then choose whether the show should continue, pause, migrate, become an archive, or close.
Start with the hosting account and RSS feed
For most independently hosted podcasts, the hosting account is the operational center. Spotify describes an RSS feed as a file containing the show's titles, descriptions, audio links, artwork, and other information. Listening directories use that feed to learn what episodes exist and where to fetch them.
This distinction matters. Access to an Apple Podcasts or Spotify dashboard does not necessarily provide access to the third-party host. A family might be able to view analytics in a directory but still be unable to publish an episode, update the source feed, download master audio, or keep hosting bills paid.
Record these facts before doing anything irreversible:
- Hosting provider and account owner
- Current RSS feed URL
- Login email and recovery method, without copying secrets into an ordinary document
- Billing plan, renewal date, and payment source
- Podcast website and domain registrar
- Apple Podcasts Connect, Spotify for Creators, YouTube, and other directory accounts
- Team members and their roles
- Original audio, project files, artwork, transcripts, and show notes
- Advertising, subscription, donation, and sponsor accounts
- Business entity, copyrights, licenses, releases, and contracts
Save the show URL and feed contents as evidence of the current state. If the host permits exports or downloads, preserve them before changing ownership, billing, or distribution settings.
Separate access from legal authority
Possessing a password is not the same as being legally authorized to operate the show. An executor, business partner, co-owner, producer, or family member may have different rights depending on contracts, estate documents, local law, and provider terms.
Avoid guessing. Identify who owns the podcast name, episode copyrights, music licenses, advertising agreements, and hosting subscription. If the show belongs to a company, the company may continue to own it even though its host died. If co-hosts jointly created episodes, the estate may not control every recording by itself.
An authorized successor should also consider privacy. Hosting dashboards can expose unpublished recordings, listener messages, email addresses, financial details, and analytics. Use only the access needed for the task, keep a decision log, and consult a qualified professional when ownership or authority is disputed.
Use team roles before a crisis
The best continuity plan does not depend on a shared password. It gives trusted people named accounts with appropriate roles.
Spotify for Creators allows owners to invite team members using their own Spotify accounts and assign access by feature. Spotify also says a team can have more than one Admin. Apple Podcasts Connect provides Legal, Admin, Finance, Show Manager, and Analyst roles, and Apple explicitly recommends adding more than one person to an account.
Those tools are useful because podcast work has different levels of sensitivity. A producer may need to upload episodes without seeing payouts. An accountant may need financial reports without editing a show. A successor may need administrative rights, while an analyst needs read-only data.
Creators should review role lists twice a year. Remove former contractors, confirm that invitations were accepted, require strong authentication, and ensure at least one trusted person can perform an emergency check. Delegated platform access still does not replace a will, business agreement, power of attorney, or provider-specific estate process, but it prevents avoidable single-person lockout.
Preserve the actual creative archive
Do not assume that a public directory is a backup. A compressed episode delivered to listeners is not the same as the master recording, edited session, transcript, cover-art source, music license, or sponsor approval.
Before migrating or closing anything, preserve:
- final published audio and video
- master recordings and editing projects
- episode titles, descriptions, publication dates, and GUIDs
- show artwork and source design files
- transcripts, captions, chapters, and linked resources
- analytics exports and audience reports
- release forms, guest permissions, music licenses, and contracts
- sponsor reads, insertion orders, affiliate records, and invoices
- payout, tax, refund, and subscription reports
- listener messages that the estate is lawfully entitled to retain
Spotify warns that deleting a hosted account can permanently delete associated data. Its backup list includes episodes, audio, analytics, artwork, voice messages, and descriptions. Treat deletion as the last step, never the first response to a death.
Protect the feed when changing hosts
If the old host cannot remain in use, the successor may need to move the podcast. A careless migration can split the audience, create duplicate episodes, or leave subscribers following an abandoned feed.
The normal pattern is to create the new hosting account, import the full archive, compare every episode, and then redirect the old RSS feed to the new one. Apple advises self-hosted publishers to return an HTTP 301 redirect and use the itunes:new-feed-url tag. It says the redirect and tag should remain for at least four weeks.
Episode GUIDs are especially important. Apple warns that changing them can produce duplicate episodes, distort analytics, and affect a show's status. A successor should therefore preserve each existing GUID even if file locations, titles, or other metadata change.
Test the new feed before redirecting. Confirm that episode counts, dates, artwork, descriptions, explicit-content labels, and enclosure files are correct. After the redirect, check multiple listening apps over several days. Keep the old host paid and accessible until the transition is demonstrably stable.
Treat directory ownership as a separate layer
Apple Podcasts Connect and Spotify for Creators may contain their own team roles, analytics, subscriptions, comments, and platform-specific settings. Inventory them separately from the host.
Apple documents a podcast ownership-transfer process. An Admin may need to initiate the transfer, and RSS-based transfers can require verification through metadata in the feed. Some shows with channels, subscriptions, Apple-hosted audio, or other conditions need support assistance. This is why current feed control and a list of account IDs belong in the succession file.
On Spotify, a team with multiple Admins can reduce administrative lockout. But the show may still depend on a different hosting provider, and the email address published in the RSS feed may be used for verification. Keep that address under durable control through a business domain or appropriately planned mailbox rather than an undocumented personal inbox.
Reconcile revenue and obligations
A monetized podcast may continue earning or charging after its creator dies. List every revenue stream: dynamically inserted advertising, host-read sponsorships, paid subscriptions, donations, affiliate programs, video revenue, merchandise, licensing, and live events.
For each one, identify the contract owner, payment processor, bank destination, tax records, remaining deliverables, cancellation rules, and support contact. Spotify says podcast subscription payouts are processed through Stripe and that payout failures produce email and dashboard notices. Access to the publishing dashboard therefore may not be enough to solve a banking, identity, or estate problem.
Communicate promptly with sponsors and subscribers, but do not make promises before confirming authority and funds. A sponsor may be entitled to a replacement placement or refund. Subscribers may need to know whether benefits continue. Pending revenue may belong to an estate or business and may require formal documentation before a provider releases or redirects it.
Choose a clear outcome
Continuation works best for a team-run show with documented rights, another Admin, a production plan, and a person authorized to manage money and contracts. Tell listeners honestly if the host or format will change.
A pause can create time for the family and partners to decide. Keep hosting and the domain paid, publish a brief notice if authorized, stop promising new benefits, and set a review date.
An archive preserves the back catalog without implying that production will continue. It still needs durable hosting, domain renewal, rights clearance, security reviews, and a named caretaker. An archive is a maintained asset, not an abandoned account.
Closure may be right for a deeply personal show or an estate that cannot assume its obligations. Back up everything first, reconcile payouts and contracts, notify listeners, allow feed migrations or downloads to settle, and only then delete accounts that should not remain.
What podcasters should document now
A useful podcast succession note should state:
- Who may act during incapacity and after death
- Whether the show should continue, pause, archive, migrate, or close
- Who owns the name, feed, recordings, website, and back catalog
- Which people have host and directory roles
- Where original media and business records are stored
- Which domain, email, and cloud accounts support the show
- How advertising, subscriptions, sponsors, and payouts should be handled
- Which guest, music, and distribution rights limit future use
- What listeners and collaborators should be told
- Which lawyer, accountant, producer, or technical contact understands the setup
Store this map with estate or business-continuity records. Keep secrets in an appropriate password manager or controlled recovery process, not in a public will or casually shared spreadsheet. Review the plan after changing hosts, adding monetization, forming a company, or changing the production team.
Conclusion
A podcast hosting account after death is the entrance to a larger system. Preserving the show means protecting the RSS feed, episode identifiers, original media, domains, directory roles, contracts, and payment records together.
The most resilient plan uses named team access, durable business contact details, independent backups, clear ownership documents, and written instructions for the show's future. When a death has already occurred, preserve first and change later. That order gives the family or authorized successor the best chance to honor the creator, protect listeners, and avoid turning a manageable transition into a permanent loss.