TTS savings calculator: ElevenLabs vs Audra at volume — Audra
Every pricing post on this blog ends the same way: run your volume on /calc. This is the post that explains what that tool actually does — which inputs matter, which it deliberately ignores, and how to read the output when the decision is borderline.
What to feed it
- Total characters synthesized per month, not API call count — Audra meters rendered characters, so export that number from your current vendor's dashboard.
- Your current effective rate — the last invoice total divided by rendered characters, which is usually not the list rate you think you pay.
- Engine mix if you already know it; the calculator defaults to Essential (1.0×), and each multiplier scales the Audra side proportionally.
What it ignores on purpose
- Mastering cost — Audra's −16 LUFS is in the export, so there is no ffmpeg line to model; if your current pipeline pays for normalization, that savings never shows in the calculator and you should count it yourself.
- Failed renders — Audra auto-refunds QA failures, and your current vendor probably does not; treat that as a one-to-three percent effective discount that the tool does not credit.
- Engine switching cost — if moving off a subscription, unused included credits are sunk either way.
Worked example: a borderline case
A docs site renders 160k characters a month for its listen-mode feature. The calculator shows a small monthly gap at that volume — this is exactly the ~200k chars/month threshold where OpenAI tts-1's $15/1M can still be the cheaper raw choice. What flips the decision is the mastering line the calculator does not model: 1,600 audio files a month through a loudness pass, versus files that arrive already normalized. That is the difference between a number and a decision.
The line-item comparison at 500k–10M characters is a different post — /blog/elevenlabs-api-pricing-2026 — because that is a different regime. When your number clears the borderline, the migration path is /migrate and the trial is at /dashboard.