It’s a real product. The free tier gives you up to 10 paying subscribers — plus up to 250 total subscribers (paying + free combined) — with the full premium feature set: token-based private RSS feeds, per-tier episode scheduling, subscriber management, deep links to podcast apps, the subscriber account dashboard, everything. No time limit. No “free trial” expiry. No hidden capability restrictions.

The only limits are subscriber counts. When you hit 10 paying subscribers, you’re ready for Starter.

Some, yes — and it’s worth understanding before you choose a hosting plan. Here’s the honest picture:

Feed requests are cheaper than they look. Benecaster’s feed cache is per tier, not per subscriber. If you have 500 subscribers across 3 tiers, there are 3 cached RSS documents — not 500. A subscriber’s podcast app polling their private feed URL hits token validation (one database query), then the cache. With a warm cache, the entire request resolves in a handful of milliseconds and never touches the feed compilation logic. This is substantially lighter than a typical WordPress page load.

Object caching makes a big difference. If your host provides Redis or Memcached, the cache lives in memory rather than the database. At that point, feed requests at scale are close to negligible — token validation plus a memory read. Object caching is common on the better managed WordPress hosts, but it’s worth checking rather than assuming — some include it only on higher plans, some charge for it as an add-on, and budget “managed WordPress” plans often don’t offer it at all. Benecaster uses it automatically when it’s available and falls back to the database when it isn’t, so nothing breaks either way.

Feed request logging adds database rows. Benecaster writes one database row per feed poll — useful for tracking re-engagement from cancelled subscribers and feeding the Analytics Dashboard. This is on by default. At volume, the table grows fast: a 500-subscriber show generates roughly 24,000 rows per day. You can adjust the retention window, switch to logging only failed requests (revoked or unrecognized tokens — useful for churn diagnosis with minimal storage overhead), or disable logging entirely in Settings → GDPR / Privacy.

The download proxy is where load actually compounds. If you enable the optional download proxy for analytics, every time a subscriber downloads an episode, the request passes through WordPress before redirecting to your hosted audio file. For a show with frequent releases and a large active subscriber base, this can add up. The proxy is opt-in — if server load is a concern, you can get full feed analytics without it. See Download Tracking → for a full explanation of what the proxy does and when to enable it.

Hosting guidance by plan:

• Free and Starter (up to 50 subscribers): shared hosting is generally fine.
• Growth (up to 250 subscribers): a VPS or entry-level managed WordPress host (Kinsta, WP Engine, SiteGround) is worth the investment.
• Pro and above: managed WordPress hosting with Redis and PHP-FPM is the right baseline. Most hosts at this tier include Redis as standard.

Podcast app polling is not as aggressive as it sounds. Apps typically poll feeds when the user opens the app, not on a fixed interval. A subscriber who checks their app once a day generates one feed request per day. 500 subscribers does not mean 500 requests per hour.

Only subscribers with an active token on a paid tier count toward your plan’s paying subscriber limit. Free-tier listeners — subscribers on a free membership level — do not count toward this limit. Subscribers in a free trial period count — they’re on a paid tier with an active token and a scheduled first payment.

Each plan also has a total subscriber cap covering all active tokens, paying and free combined (Free: 250, Starter: 500, Growth: 2,500, Pro and above: unlimited). Free-tier subscribers count toward this secondary cap but not the primary paying limit. The total cap exists to keep free-tier usage proportionate to the plan — a podcaster with hundreds of free marketing-list subscribers and a handful of paying ones is getting real value and should be on an appropriate plan.

Churned subscribers are removed from both counts immediately on cancellation. Both counts are based on currently active tokens, not your historical high watermark.

Followers on your public feed have no token and don’t count toward either cap.

Yes. Free trial subscribers are on a paid tier — they have an active feed token and a first payment scheduled at the end of the trial. They count toward your plan’s paying subscriber limit.

A genuinely free membership level (no payment required at any point) is different: free-tier subscribers don’t count toward the paying subscriber limit, but they do hold an active token and count toward the total token cap. Free trial ≠ free tier.

A self-hosted WordPress site. Benecaster is a WordPress plugin — it doesn’t work with WordPress.com hosted sites or other platforms.

Audio hosting. Benecaster manages your RSS feed and subscriber access; it doesn’t store or serve audio files. You’ll need an existing podcast host (Buzzsprout, Libsyn, Transistor, Captivate, S3, etc.) or file storage that produces a stable URL per episode.

Membership management. Benecaster includes a built-in membership system for subscriber billing and access control. If you already use MemberPress, WooCommerce Subscriptions, Paid Memberships Pro, or Restrict Content Pro, Benecaster connects to it directly — your existing setup carries over. If you’re starting fresh, the built-in system handles everything with no additional plugin required.

Hosting with room to grow. Benecaster is lightweight for most shows, but a few hosting choices make a meaningful difference:

• Object caching (Redis or Memcached) — strongly recommended for any show with active subscribers. Most managed WordPress hosts include it. Feed requests with a warm cache add minimal server load; without it, each request hits the database.
• A host that allows PHP-FPM — important at Growth tier and above where concurrent feed requests compound.
• Adequate disk space — minimal for most shows, but the optional download proxy generates log data that grows with subscriber count and episode frequency. See How much disk space does Benecaster need? →

Shared hosting works fine for Launch and Starter. A managed WordPress host (Kinsta, WP Engine, SiteGround) is worth the investment from Growth onward.

Public podcast feeds work normally on Spotify. Private token-based feeds — the ones Benecaster generates for paying subscribers — cannot be delivered to Spotify. Spotify does not support custom RSS feed URLs for private podcasts in the same way other podcast apps do.

If you need Spotify distribution for your public feed, that works fine. Your paying subscribers use their personal RSS URL in a standard podcast app.

Spotify also can’t be used as your audio host. When you distribute to Spotify, they re-host your audio internally — those files don’t have URLs you can link to from your own feed or site. Your audio files need to live on a standard podcast host or your own server.

When you map your membership tiers in Benecaster → Settings → Subscription → Tier Mapping, Benecaster reads the price of each tier from your membership plugin and marks it paid or free accordingly. A daily background sync re-checks tier prices so that if you change a paid tier to free in your membership plugin, Benecaster reflects that within 24 hours.

This works automatically for all supported bridges — WooCommerce Subscriptions, MemberPress, Paid Memberships Pro, and Restrict Content Pro.

Subscribers you manually add to a paid tier (admin-comped access) count toward your paying subscriber limit the same as any other paid-tier subscriber. They also count toward the total token cap.

Yes — Benecaster is a standard WordPress plugin and installs on any self-hosted WordPress site running PHP 8.2+ and WordPress 6.4+.

What you may need to rework depends on how you’re currently managing podcast episodes:

If you’re using another podcast plugin (Seriously Simple Podcasting, PowerPress, etc.), those plugins manage episodes in their own format. Benecaster uses its own Episode post type — episodes need to be in Benecaster’s system to appear in Benecaster’s feeds. Benecaster’s setup wizard includes a one-time import step that reads your existing episodes and converts them automatically. You review the results, fill in any Benecaster-specific fields (like per-tier availability), and go.

Running both plugins at the same time works briefly as a transition buffer — your existing public listeners are unaffected and keep receiving episodes while you set up and test Benecaster. But it isn’t a permanent setup. Both plugins manage episodes separately, so any new episode you publish has to go into one system or the other, not both. The typical transition takes a few days: import, test, set up a feed URL redirect, then deactivate the old plugin. After that, Benecaster is the single place you create and manage episodes.

If your episodes are WordPress posts or pages with a player embedded — same situation. The importer handles the conversion. You’d also need to replace any podcast plugin shortcodes in your episode content with Benecaster equivalents; the importer flags these for you.

If you have no podcast management plugin — Benecaster installs cleanly. Create episodes from scratch and you’re set.

If you already have a membership plugin (MemberPress, WooCommerce Subscriptions, Paid Memberships Pro, or Restrict Content Pro) — that’s a head start. Benecaster connects to it rather than replacing it, so your existing members, billing setup, and subscription products stay exactly as they are.

Your existing hosting may also need attention. Benecaster’s feed delivery and caching requirements can differ from a standard WordPress content site — worth reviewing before you go live. See Server Requirements →

If you’d rather not handle the transition yourself, the Setup Service covers the full configuration including episode import.

No — with a few exceptions worth knowing about.

Benecaster gates the RSS feed, not the audio. Your audio files stay wherever they are. Benecaster generates an RSS feed pointing directly at your existing hosted audio URLs. No migration, no bandwidth cost to your WordPress server.

Platforms you’ll need to move off:

Spotify. Spotify creates two separate problems for private podcast setups:

• Spotify for Podcasters as your audio host — If your audio is currently hosted through Spotify for Podcasters (formerly Anchor), moving to a private subscriber model requires switching audio hosts first. Spotify for Podcasters bundles hosting and distribution in a closed platform; the audio URLs it generates aren’t designed to be used independently in another feed.

• Spotify as a distribution platform — Spotify only accepts open, public RSS feeds. Private subscriber feeds — Benecaster’s or anyone else’s — can’t be submitted to Spotify. Your public free episodes can still be listed on Spotify; your private subscriber content can’t. This is a Spotify platform decision, not a Benecaster limitation, but it’s worth knowing before you commit to a subscriber model.

Patreon. If your audio is currently hosted through Patreon, you’ll need to move it to a standard podcast host before switching to Benecaster. Patreon bundles audio hosting with its membership platform — the audio URLs it generates aren’t portable to an independent feed. Any major podcast host (Buzzsprout, Libsyn, Transistor, Captivate, Podbean, S3, etc.) works as a replacement.

A platform that works, but ties you to the subscription:

Castos. Castos-hosted audio sits at ordinary URLs, so a Benecaster feed can point straight at them and everything works normally — no migration needed to get started. The catch is that those URLs stop resolving when your Castos account closes. So you can run Benecaster alongside Castos indefinitely, but you can’t cancel Castos and keep the audio. If your goal is to leave Castos entirely, move your audio files to a host you control first and update the audio URLs on your episodes before you cancel. If you’re keeping Castos for hosting and only using Benecaster for private subscriber feeds, nothing needs to move at all.

Every other major podcast host works without changes.

Cancel anytime from your account dashboard. Cancellation is scheduled for the end of your current billing period — your access continues normally until then, and so do your subscribers’ private feeds. When the billing period ends, there’s a 30-day grace period during which private feeds continue working normally. After those 30 days, subscriber tokens are deactivated and private feeds go dark. New token generation stops immediately on cancellation, so no new subscribers can be added during the remaining period or the grace window.

If you’re within the 30-day refund window, requesting a refund cancels your account immediately rather than at period end.

All your data remains in your WordPress database. Reactivate at any time by resubscribing — existing subscriber tokens restore automatically.

At 80% of your cap you’ll see a notification in your Benecaster dashboard — a milestone callout, not an alarm.

What happens next depends on how you’ve set your upgrade preference (configurable during onboarding and in Settings → Account):

Auto-upgrade (default): When your paying subscriber count exceeds your limit, a 30-day grace period begins — you’ll receive a notification with a one-click upgrade path. If you haven’t upgraded by the end of the grace period, Benecaster schedules an automatic upgrade to the next tier and sends a confirmation before it fires.

Cap: No automatic upgrade. Subscribers who join while you’re at your limit still receive a feed — it’s the public feed rather than their private subscriber feed. When you upgrade manually, their private access restores automatically with no RSS URL change needed.

Apply for Growth. It’s free under the academic program and covers up to 250 paying subscribers and 2,500 total tokens — more than enough for most campus and community shows. If you’re not sure how large your audience will be, start here. You can apply for an upgrade later if you need it.

If you’re running a larger production or multiple shows that genuinely outgrow Growth, Pro, Multi-Show, and Studio are available at 20% off. Apply for the plan you need — if approved, you’ll receive a coupon code to use at checkout for the discounted price.

If you’re not sure which plan fits, the pricing page has the full subscriber count and feature breakdown.

Yes. Benecaster has two independent limits — paying subscribers and total tokens (paying subscribers + free-tier subscribers combined) — and you set an enforcement preference for each during onboarding. You can change both in Settings → Account at any time.

Free-tier subscribers are people who have signed up through your membership plugin with a free access tier — they have a feed token, so they count toward the total token cap. They are distinct from anonymous listeners to your public feed, who have no token and are not counted toward any limit.

Paying subscriber limit — default: auto-upgrade. When your count exceeds the limit, you have a 30-day grace period before any restrictions take effect — all subscribers continue receiving their private feed during that window. If you haven’t upgraded when the grace period ends, Benecaster schedules an automatic upgrade to the next tier and notifies you before it fires.

Token cap — default: cap. When your total active tokens exceed the plan cap, you have the same 30-day grace period with no change to feed access. After that, over-limit tokens receive the public feed instead of private subscriber content — no automatic billing event. You upgrade manually when you’re ready.

See How Subscriber Limits Work → for a full explanation of what counts, what doesn’t, and how cap mode behaves for your subscribers.

When your application is approved for a paid plan, we email you a one-use coupon code for 20% off the standard published price. The coupon is valid for 14 days from the date of your approval email.

Starting fresh on a paid plan: Go to the pricing page and click through to checkout for the plan you were approved for. Apply the coupon code at checkout and use the same email address you applied with — the discount won’t link to your academic account otherwise. Your license is provisioned automatically at the discounted price.

Upgrading from Growth: Go to your account dashboard, navigate to your license and plan, and click Upgrade. Apply the coupon code during the upgrade checkout using the same email address you applied with.

The coupon applies to the first billing period; renewals are billed at the standard rate unless you re-apply for a new coupon at renewal time.

If your coupon expires before you use it, email us and we’ll issue a new one.

Free through Pro each support a single show. Multi-Show supports up to 3 shows. Studio supports unlimited shows.

Shows can live on the same WordPress installation, on separate sites at separate domains, or any combination. Your license also carries a site activation limit — 1 installation on Launch through Pro, 3 on Multi-Show, unlimited on Studio — so a Multi-Show license can run its 3 shows on one site, across 3 separate sites, or any mix within both limits. Staging installations don’t count against the activation limit.

Each subscriber’s token is show-specific — access to Show A doesn’t carry over to Show B. The admin UI includes a show switcher to navigate between shows on the same installation.

See Running Multiple Shows for configuration details.

The Academic Program covers the core plan only — the 20% discount applies to Starter, Pro, Multi-Show, or Studio (the Growth plan is free outright). Individual add-ons are not discounted.

Add-ons are separately available at their standard prices to any Benecaster account, including academic ones. If your institution needs the full add-on stack, the All Add-ons Bundle ($499/year) or Studio tier (which includes all podcaster add-ons) are the most cost-effective paths — with Studio at 20% off for qualifying institutions.

No. A single show in Benecaster can have any number of subscription tiers — paid, free, or both. Paid subscribers and free-tier listeners are different membership levels within the same show, each with their own episode availability windows and, if you choose, their own private feed. You only need a second show if you’re running a genuinely separate podcast with different content and a separate audience.

This is a common assumption from platforms where tiers feel like separate products. In Benecaster, tiers are a scheduling and access control layer within one podcast — not separate feeds that require separate shows. One show, multiple tiers.

Multi-Show supports up to 3 shows and unlimited subscribers. Studio supports unlimited shows and unlimited subscribers, includes all current and future add-ons, priority support, and Migration + Setup Service.

Choose Multi-Show if you’re running 2–3 shows and want to select your add-ons individually.

Choose Studio if you need more than 3 shows, want every add-on without managing purchases, or want the setup and support included.

Growth, Pro, Multi-Show, and Studio all include Migration Wizard at no extra cost. For Starter, it’s available as a one-time add-on purchase ($79). Migration Wizard is a one-time-use tool — you pay once for the migration event, not annually.

No. Multi-Show and Studio are multi-site licenses for your own shows — not to share with collaborators, friends, or colleagues. Every site activated under your license must be a podcast you own and operate.

If someone else wants to use Benecaster, they need their own license. The free tier supports up to 10 paying subscribers at no cost — it’s a real starting point, not a demo.

Sharing your license key for use on a show you don’t own and operate violates the acceptable use terms. Benecaster may terminate all shows on your license if a violation is confirmed, including the shows that are legitimately yours. See Running Multiple Shows for more on how show management works.

Multi-Show (up to 3 shows) and Studio (unlimited shows) support multiple shows — but all shows must be ones you own and operate, not client shows. Every show under one license must be a podcast operation run by the license holder.

Agency licensing — where you activate Benecaster on sites owned by your clients — is not available. Each client needs their own license purchased by or for that client. Benecaster’s model is built around the podcast operator owning the subscriber relationship; sub-licensing undermines that for both you and your client.

If you’re a developer or agency setting up Benecaster for a client, purchase the license under the client’s account so they own it and can manage it independently going forward.

No free trial, but there’s a genuine free tier (up to 10 paying subscribers, no time limit) and a 30-day money-back guarantee on all paid plans. A trial period isn’t long enough to set up, migrate subscribers, and evaluate real performance. The guarantee removes purchase risk without the complexity of managing trial accounts.

Benecaster requires PHP 8.2 or higher and WordPress 6.4 or higher. For small shows (under 50 active subscribers), any shared hosting plan that meets these requirements is sufficient. As your subscriber count grows, server needs change:

• 50–250 subscribers — VPS or managed WordPress hosting (SiteGround, Cloudways, WP Engine entry plans). Object caching (Redis or Memcached) is recommended.
• 250–1,000 subscribers — Managed WordPress hosting with Redis or Memcached enabled as a baseline. PHP-FPM and OPcache required.
• 1,000+ subscribers — Redis or Memcached should be considered a requirement at this scale.

See Server Requirements for the full specification.

Redis and Memcached are in-memory data stores that WordPress uses as an object cache — a fast layer that saves the results of database queries so they don’t need to be re-run on every request. Think of it as short-term memory for your site: instead of asking the database the same question repeatedly, WordPress stores the answer in memory and reads it directly next time.

Not immediately required, but you will want it as you grow. Benecaster caches your podcast feeds by tier — 1,000 subscribers across 4 tiers produces 4 cached documents, not 1,000. With Redis or Memcached, those cache reads happen in memory with no database query at all.

Without an object cache, feed requests still work but every request involves a database query — more load on your server. Under 500 subscribers most hosts handle this without issue. Above 500, the database load from concurrent feed polls — particularly around episode releases — can noticeably affect site performance.

Most managed WordPress hosts (WP Engine, Kinsta, Cloudways) offer Redis as a one-click feature. LiteSpeed-based hosts (Hosting.com, Namecheap) can use LiteSpeed Cache’s built-in object cache. No Benecaster configuration is needed — it uses the standard WordPress object cache API and picks up any compatible backend automatically.

Yes. Each follower occupies one slot in your plan’s total token pool — the same pool shared with paying subscribers and free-tier members.

Benecaster tracks two separate limits:

Paying subscriber limit — the headline number on your plan (10 for Launch, 50 for Starter, etc.). Only paying subscribers count toward this limit. Followers and free-tier members do not.

Total token cap — all active tokens combined: paying subscribers, free-tier members, and followers. This secondary cap exists to keep the token pool proportionate to your plan.

Token caps by plan:

When you reach the WP.org follower cap (100), the [benecaster_follower_signup] shortcode silently stops rendering the form for visitors — listeners see nothing. Site administrators see a prompt explaining the cap and linking to a free Launch account at benecaster.com, which raises the cap to 250 at no cost — no card required.

See How Subscriber Limits Work → for a full explanation of what counts toward each limit.

Benecaster is currently available in English. Spanish is next — the plugin is built for translation from the ground up and the architecture is in place. If you’d like to be notified when your language is available, contact us →.

When a language ships, here’s how it works: during setup you choose which languages you want to support. If you run an English-only podcast and aren’t comfortable managing content in another language, you pick English — your subscribers always get English. If you support multiple languages, subscribers can set their own preference on their account page and receive emails and subscriber-facing pages in their language when you support it.