How WhisperAPI Pricing and the Free Trial Work

WhisperAPI uses a pay-as-you-go credit model: you start with 5 free transcription credits and no credit card, then buy more credits as you need them. There are no hidden fees, and payments are processed through Paddle. The site does not publish per-credit rates on the pages referenced here, so treat any specific number as something you confirm on the pricing page before committing.

What you get for free

The free tier is a test allowance, not a recurring free plan:

• 5 transcription credits to try the API or dashboard
• No credit card required to start
• Enough to validate that transcription quality, language support, and output formats fit your use case before paying

If your goal is a one-off short file, 5 credits may cover it. If you're evaluating for a production pipeline, plan to run a representative sample — a noisy recording, a non-English file, a long video — rather than five clean clips.

How credits work

Credits are the payment unit for transcription. The FAQ on the site defines "API credits" as the billing mechanism, but the excerpt provided doesn't state the credit-to-minute or credit-to-file conversion. That ratio is the single most important number for estimating cost, so check it on the pricing page before you scale.

What the site does commit to:

Because there are no minute limits and files can reach 10GB, cost scales with usage rather than with a cap — which is exactly why the credit conversion rate matters.

Pay-as-you-go, in practice

The model is simple: consume credits, top up when low, no subscription commitment described. Two practical implications:

1. Cost tracks volume, not seats. A solo developer transcribing occasionally and a team running bulk jobs pay according to usage.
2. No hidden fees is the site's claim; verify by reading the pricing page for any minimum top-up, expiry on purchased credits, or overage terms. None of those are confirmed in the material here.

Choosing between the API and the dashboard

Both draw on the same credit balance, so the pricing question doesn't change — only how you spend it.

• API — for developers who want control: model selection (speed vs. accuracy), direct uploads or remote URLs, tunable parameters, and video/audio through one endpoint. Example request from the docs:

curl \
  -F "[email protected]" \
  -F "language=en" \
  -F "format=srt" \
  -F "model_size=large-v2" \
  -H "X-API-Key: YOUR_API_KEY" \
  https://api.whisper-api.com/transcribe

• No-code dashboard — drag-and-drop, real-time progress, multiple download formats (JSON, TEXT, VTT, DOCX, PDF shown on the site), all transcriptions managed in one place.

If you're not sure which fits, start with the dashboard on your free credits to judge accuracy, then move to the API if you need automation.

What to check before paying

• The credit-to-usage ratio (minutes or files per credit) on the pricing page
• Whether purchased credits expire
• Any minimum top-up amount
• Refund or failed-job policy — does a failed transcription consume a credit?

The free trial answers "does it work for my audio?" The pricing page answers "what will it cost at my volume?" Confirm both before moving off the free credits.