FAQ

The free trial gives you 14 days of access to whichever plan you select when you sign up — no credit card required. You can switch plan tiers or upgrade at any time during or after the trial.

The free trial is available once per account. If you cancel and re-subscribe, you are billed immediately from day one — there is no second trial period.

The feature lists on our Pricing page will give you an idea of what you can do with our plans. You can also take a look at our Use Cases for examples of how Podbite can help with your specific scenario. If in doubt, start a free trial of our Automate plan and give the full range of our features a whirl. You can switch plan tiers at any time.

You can upgrade or downgrade your plan via Manage account in the user menu, then the Billing tab.

You can cancel your plan via Manage account in the user menu, then the Billing tab.

Promote includes one custom playlist. If you move from Curate or Automate to Promote and you had more than one playlist, your most recently updated playlist stays active — it remains publicly visible and fully editable.

Any additional playlists become locked:

• They're still in your account and you can delete them at any time.
• Their public links show a "not available on this plan" notice to visitors.
• You can't edit their content while they're locked.

To unlock a locked playlist, upgrade back to Curate or Automate. Everything is restored immediately — no content is lost while locked.

When you cancel your plan your Podbite account and content remain intact until the end of your current billing period.

After your billing period ends, your profile and playlists will no longer be publicly visible. Your individual bites and any embeds or links to them will continue to work.

You can still access your account settings after cancellation — including billing, data export, and account deletion — by visiting your account page.

You can reactivate your account at any time — your profile and playlists will be restored immediately.

When you delete your account your subscription will be cancelled and your profile, playlists, and personal information will be permanently deleted.

Your bites remain on Podbite as permanent references to the podcast moments they clip — an embedded bite functions like an audio blockquote that others may have built on. When your account is closed, your name and comment are removed, but the bites remain as unattributed references.

If you create a new account later, those bites cannot be reclaimed as yours — the association is permanently removed at deletion.

Any embeds or links to your bites on other sites will continue to work, but will no longer show your profile information.

If you wish to request removal of your captions as part of a formal erasure request, contact us at hello@podbite.link and we will respond within 30 days.

You will be notified via email, and payment will be attempted again over the following 15 days. If payment could not be completed in that time, the plan will be cancelled.

Plays — the number of times the audio player was started for your bites in the selected period. One person playing the same bite twice counts as two plays. If someone replays a bite without navigating away, a replay count appears next to the play total.

Completion rate — the percentage of plays where the listener reached the end of the bite clip. A 100% completion rate means every play went all the way through; 0% means no play did. It is the clearest signal a bite resonated — the listener stayed until the end.

Top source — the channel that accounted for the most plays in the period: bite page, embed player, episode page, or playlist.

For a full breakdown by source (bite page vs embed vs playlist vs episode page), open the per-bite analytics for an individual bite.

It depends on where you're counting.

On Podbite, a play is recorded the moment the audio player starts. There is no minimum length — a mic drop moment can land in under 10 seconds, and an insightful story might run for 90. What resonates cannot be gated by duration, so Podbite doesn't try.

On your hosting platform, it's a different story. Bites stream audio directly from your podcast host's CDN, so each play is a real request to your host. Whether it registers in their own stats depends on how long the listener plays. The AMP standard (used by Spotify and others) recognises 30 seconds of actual playback; the IAB standard sets 60 seconds downloaded. Making your bites at least 30 seconds long gives each play the best chance of counting where it matters on your hosting platform.

Why bite length matters for your podcast stats →

Referrer and embed domain breakdowns are available on the Curate and Automate plans. On Promote, those sections of the per-bite analytics page show a blurred preview.

If you are on Curate or Automate and the sections appear empty rather than blurred, it means no data has been recorded yet for the selected period — either the bite has no plays in that window, or the plays came through sources that don't have referrer information (for example, direct navigation with no referring site).

To upgrade, go to Manage account → Billing.

You can find your API key via Manage account in the user menu, then the Developers tab.

You can find your API usage for the current period via Manage account in the user menu, then the Developers tab.

Each bite or playlist created via the API counts as one against your monthly allowance. Automate plans include 500 creations per calendar month.

Updates and deletes do not count against your quota. Check your current usage at any time with GET /v1/quota.

Your monthly allowance resets at the start of each calendar month. If you consistently need more, get in touch and we can work something out.

The API is rate-limited to 60 requests per minute per API key. If you exceed this, you'll receive a 429 Too Many Requests response. The limit resets on a rolling 60-second window.

Your monthly creation quota (500 bites and playlists combined per calendar month) is a separate limit. Check your current usage with GET /v1/quota.

Episode resolution rate limit

Episode resolution (GET /v1/episodes/resolve and POST /v1/bites with episode_url) is additionally limited to 10 requests per minute per API key. This limit exists to protect upstream podcast data providers. It resets on a rolling 60-second window.

GET /v1/episodes/resolve also has a daily cap of 10 provider lookups per API key, resetting at midnight UTC. Repeat resolves of episodes Podbite already knows about are free and do not count against this limit.

Pass episode_url in your POST /v1/bites request body:

{
  "episode_url": "https://podcasts.apple.com/podcast/id123456789?i=987654321",
  "bite": { "caption": "Great quote", "start_time": "01:23.000", "end_time": "01:45.000" }
}

Supported URL formats: Apple Podcasts (podcasts.apple.com) and Podchaser (podchaser.com).

First-encounter latency

The first time you use an episode URL, Podbite fetches metadata from the podcast provider. This adds 1–3 seconds to the request. Subsequent requests for the same episode are fast (the episode is cached).

Two-step pattern for automation workflows

If you are creating many bites from the same episode, or want to separate the lookup from the write, pre-resolve the episode first:

# Step 1 — resolve once
GET /v1/episodes/resolve?url=https://podcasts.apple.com/...
→ { "episode_short_id": "abc123", "episode_title": "...", ... }

# Step 2 — create bites using the short_id (fast, no provider lookup)
POST /v1/bites
{ "episode_short_id": "abc123", "bite": { ... } }

GET /v1/episodes/resolve does not create a bite and does not consume your monthly quota. It counts against the episode resolution rate limit (10/min) and a daily cap of 10 provider lookups per day, resetting at midnight UTC. Repeat resolves of episodes Podbite already knows about are free — the cap only applies when a provider fetch is needed.

Need more? If your workflow needs more than 10 new episodes a day, get in touch — I'd love to hear about what you're building.

It depends on your plan:

• Promote — 1.91:1 landscape card (the standard Open Graph aspect ratio, suited to Twitter/X link previews and most blog post headers)
• Curate and Automate — all of the above, plus 16:9 (widescreen), 9:16 (portrait/Stories), and 1:1 (square)

Bite cards are generated from the podcast and episode title, episode artwork, and your bite caption. Playlist cards use the playlist name. They download as image files you can attach directly to a social post, include in a newsletter, or use anywhere you want a visual without embedding a player.

The Social card action is in the owner bar at the top of the bite page — visible on both the public bite page and the edit page. Click it to choose a format and download the image.

The same action is available on playlist pages; playlist cards use the playlist name rather than episode details.

The owner bar is only shown when you are signed in as the owner of the bite or playlist.