Choosing a speech-to-text API in 2026

GuideJuly 15, 2026 · 13 min read
Logos of the twelve speech-to-text API providers compared in this article.

We build live transcription and translation, so before we shipped anything we evaluated the speech-to-text (STT) engines we could send audio to, and picked one. This post is not about which engine we landed on. It is everything we gathered while deciding, across this part and its sequel.

This part covers 12 STT providers and the open-source models you can self-host, on the things you can verify from the outside: what they charge, whether they stream in real time, whether they translate, how many languages they cover, whether you can run them on your own hardware, and what open models actually cost to run.

Part two is the original work all of this builds toward: our own accuracy benchmark, running these engines on identical audio and reporting word error rate.

How to read this

Every figure below was pulled from the provider's own pricing page or docs on July 15, 2026. Prices change often, so treat these as a snapshot from that date.

We show price per hour of audio because most vendors quote it that way and the numbers read more cleanly. Some providers meter per token (Soniox, OpenAI) or per second, so the per-hour figure is a converted equivalent rather than a literal line item.

Pricing

Pricing is where STT providers are least comparable. Some bundle features into one rate, others itemize each one, and a few do not publish a real-time rate at all. Two quirks are worth flagging before you read the table. Deepgram inverts the usual order, charging more for pre-recorded audio than for real-time. And AssemblyAI meters real-time on the full WebSocket session wall-clock, including idle time, rather than the audio you actually send. The table shows the flagship pay-as-you-go rate for each provider.

STT pricing at a glance
ProviderBatch ($/hr)Real-time ($/hr)Free tier
Groq (Whisper turbo)0.04not offerednone
Soniox0.100.12none for new signups
Azure AI Speech0.181.005 hrs/mo
Google Cloud (Chirp)0.18 (dynamic batch)0.96none on V2
AssemblyAI0.210.45$50 credit
Rev AI (Reverb)0.20not published5 hrs
ElevenLabs (Scribe)0.220.394.5 hrs batch / 2.5 hrs real-time per mo
OpenAI (gpt-4o-transcribe)0.360.36none
Amazon Transcribe0.360.6060 min/mo (first 12 mo)
Deepgram (Nova-3)0.460.29$200 credit
Gladia (Solaria)0.610.7510 hrs/mo
Speechmatics (Ursa 2)not broken outnot broken out50 hrs/mo

Rates are the flagship English pay-as-you-go tier, converted to USD per audio hour. Speechmatics publishes only a blended hourly rate, without separate batch and real-time numbers. Google's cheap 0.18/hr is its lower-urgency dynamic-batch rate; standard recognition starts at 0.96/hr and drops with volume. Amazon and Azure prices are US regions and vary elsewhere. Groq is batch only, so it has no real-time rate.

The spread is enormous: at the batch extreme, Groq's hosted Whisper is roughly 15 times cheaper per hour than Gladia's Solaria. Price buys very different feature sets, which is the next table.

Features

Two engines at the same price can do completely different jobs. The big splits: does it stream in real time or only process finished files, does it translate as part of the same request, and can you run it on your own hardware.

Feature matrix
ProviderStreamingTranslationLanguagesDiarizationTimestampsSelf-host
SonioxYesReal-time60YesYesNo
DeepgramYesNo50Add-onYesYes
AssemblyAIYesNo99Add-onYesYes
GladiaYesReal-time99YesYesNo
SpeechmaticsYesReal-time56YesYesYes
ElevenLabsYesNo90+YesYesNo
OpenAIPartialEnglish57NoWhisper-1No
GroqNoEnglishautoNoYesNo
Amazon TranscribeYesSeparate113YesYesNo
Azure AI SpeechYesSeparate148YesYesYes
Google CloudYesChirp 2137YesChirp 2Testers
Rev AIYesAsync58YesYesYes

How to read the short labels. Translation: "Real-time" means translated text comes back inside the same live stream (Soniox, Gladia, Speechmatics); "English" means it only translates into English, which is Whisper's built-in behavior (OpenAI, Groq); "Separate" means translation is a separate or separately billed step (Amazon needs Amazon Translate; Azure's real-time translation is billed on its own); "Chirp 2" means only Google's Chirp 2 model translates, and only synchronously; "Async" means Rev translates only finished files. Streaming "Partial" (OpenAI) means it streams but not at true low latency. Diarization "Add-on" (Deepgram, AssemblyAI) means speaker labels cost extra. Timestamps "Whisper-1" and "Chirp 2" mean word-level timestamps work only on that specific model. Self-host "Testers" (Google) means on-prem is limited to trusted testers. Language counts come from each vendor's supported-language list.

A few things jump out. If you need translation delivered live in the same connection, the field narrows fast to Soniox, Gladia, and Speechmatics. And the Whisper-based hosted options (Groq, OpenAI's whisper-1) only translate into English, which rules them out for most non-English translation work. Self-hosting splits the field too, which the next section covers.

Deployment, privacy, and compliance

If you handle regulated data, this section can matter more than price or accuracy. The dividing line is whether the engine has to run in the vendor's cloud or can run in your environment.

What about accuracy?

This is the number everyone wants, and it is the one you should trust least from a vendor page. Almost every provider publishes a word error rate (WER) that makes it look best. The problem is that they are not measuring the same thing.

The closest thing to apples-to-apples

That said, two third-party benchmarks do run providers on the same audio with one scorer, which is as close to a fair comparison as public data gets. Artificial Analysis covers the commercial APIs; the Open ASR Leaderboard covers the open models. Both sets of numbers below are from July 2026.

Commercial APIs on Artificial Analysis (lower is better)
Provider (model tested)AA-WER
ElevenLabs (Scribe v2)2.2%
Azure (MAI-Transcribe-1.5)2.4%
AssemblyAI (Universal-3.5 Pro)3.0%
Gladia (Solaria-3)3.2%
OpenAI (gpt-4o-transcribe)4.0%
Speechmatics (Enhanced)4.0%
Amazon Transcribe4.1%
Google (Chirp 3)4.3%
Groq (Whisper v3 turbo)4.6%
Deepgram (Nova-3)5.2%
Rev AI5.9%
Sonioxnot listed

Artificial Analysis AA-WER v2, non-streaming, accessed July 15, 2026. A duration-weighted average over about 8 hours of audio from three public sets: AA-AgentTalk (50%, conversational), VoxPopuli-Cleaned (25%), and Earnings22-Cleaned (25%), scored against cleaned reference transcripts. Soniox is not on the leaderboard. Whisper's score shifts with who hosts it (same weights, different serving stack), a caution in itself.

Open models on the Open ASR Leaderboard
Open modelAvg WERSpeed (RTFx)
NVIDIA Parakeet TDT 0.6B v25.39%6,038x
Mistral Voxtral Small (24B)5.65%100x
NVIDIA Parakeet TDT 0.6B v35.66%6,098x
NVIDIA Canary-1B-Flash5.78%2,126x
Mistral Voxtral Mini (3B)6.01%180x
NVIDIA Canary-1B-v26.39%1,821x
Whisper large-v36.55%462x
Whisper large-v3-turbo7.01%783x
Moonshine base8.60%2,767x

Open ASR Leaderboard, average WER (cleaned) over 7 public English sets (AMI, Earnings22, GigaSpeech, LibriSpeech clean and other, SPGISpeech, VoxPopuli), accessed July 15, 2026. RTFx is speed on a datacenter GPU, how many times faster than real time; higher is better. These are read and meeting recordings, which run easier than the conversational audio that dominates the Artificial Analysis set, so the WER here is not comparable to the table above.

These narrow the question but do not close it. Artificial Analysis skips Soniox and the open leaderboard skips the commercial APIs, so no public benchmark runs all twelve providers and the open models on the same audio with the same scorer. Part two of this post does: we send an identical test set through these engines and report word error rate with confidence intervals, using the same open scoring method the research community uses.

Open-source and self-hosted

The 12 above are hosted APIs, but you do not have to use one. Several open-weight models are now as accurate as the commercial engines, a few beat Whisper outright, and some also translate (see the table). If you run the model yourself, or rent it by the second on a GPU platform, the cost math changes.

Open-weight models worth knowing
ModelLicenseRuns locallyStreamingTranslation
NVIDIA Parakeet TDT 0.6B v3CC-BY-4.0Yes, on a laptopYesNo
Mistral VoxtralApache-2.0Mini: yes; 24B: serverYes (Realtime build)Any-to-any
NVIDIA Canary-1B-v2CC-BY-4.0Yes, on a laptopNo24 languages
Whisper large-v3 / turboMIT / Apache-2.0Yes, on a laptopNoEnglish only
Meta MMS / SeamlessM4TCC-BY-NC-4.0Yes, on a laptopNoSeamlessM4T: yes

"Runs locally" means it fits on a modern laptop or Apple Silicon Mac (roughly, models under 3B parameters). Only the largest, such as Voxtral 24B and IBM Granite Speech 8B, need a datacenter GPU. Parakeet v3 is the fastest and near the top on accuracy but transcription-only; Whisper has the widest tooling but is now mid-pack; Voxtral and Canary-1B-v2 add translation. Open-model accuracy moves monthly: a 2025-2026 wave (Cohere Transcribe, Qwen3-ASR, NVIDIA Canary-Qwen, IBM Granite Speech) pushed the top of the Open ASR Leaderboard into the ~5% WER band, ahead of Whisper, so date any "most accurate" claim and check the live leaderboard. CC-BY-NC means research or non-commercial use only.

Running it on your own machine

Unlike large language models, most of these models are small enough to run on a normal computer. Whisper, Parakeet 0.6B, Canary 1B, and Voxtral Mini all run on a modern laptop or an Apple Silicon Mac; only the largest need a server. We ran Whisper and Parakeet on an M4 Pro MacBook ourselves, to check whether on-device transcription was fast enough to ship rather than take vendor throughput claims on faith. On that machine, Parakeet transcribed about 50 times faster than real time and Whisper large-v3 about 1 to 3 times.

When it runs on hardware you already own, the only marginal cost is electricity: power draw, times how long the transcription runs, times your rate. US residential electricity averages about 17 cents per kWh. A laptop draws roughly 45 watts under load, a desktop with a discrete GPU 300 to 400.

Local electricity cost per hour of audio
Setup (hardware you own)Cost per audio-hour
Parakeet on an Apple Silicon laptop (~50x real time)~$0.0002
Whisper large-v3 on the same laptop (~1x real time)~$0.008
Desktop with a consumer GPUwell under $0.01

Electricity only, at about $0.17/kWh (US residential average, EIA) with the machine drawing 45 to 400 watts. Real-time factors are measured from our on-device benchmark on an M4 Pro. You already paid for the hardware; this is only the power it draws while transcribing.

So on a machine you own, transcription is effectively free, a fraction of a cent per hour of audio. The catch: it ties up that one machine, does not scale past it, and you paid for the hardware up front. For a desktop app or an on-device feature this is unbeatable. For a service handling many streams at once, you are back to renting GPUs.

Running it at scale on rented GPUs

At scale you rent GPUs, and an open model has no list price, only your compute bill. To compare it against the APIs above, normalize to dollars per hour of audio. The formula is: cost per audio-hour = GPU price per second times (3600 divided by RTFx), where RTFx is how many times faster than real time the model runs on that GPU. You measure RTFx by transcribing a known length of audio and reading the billed compute time.

You can rent this by the second (fal, Replicate, Modal, and Baseten all host Whisper, and most host Parakeet or Canary too) or run it on a GPU you rent by the hour. Serverless is simplest; a dedicated GPU is cheapest at steady high volume. Here is what that works out to.

What open-source actually costs per hour of audio
SetupCost per audio-hour
Naive, one file at a time (Whisper on an H100)~$6.90
Serverless convenience (fal, NVIDIA Canary)~$2.88
Batched pipeline (Parakeet or Canary on an H100)~$0.006
Self-hosted, GPU fully utilized (Parakeet v3)under $0.002

Figures from the platforms' own published examples and rate cards (Modal, fal, Replicate), July 2026. The roughly 1,000x range means cost is set by how busy you keep the GPU, not by the model.

So self-hosting is not automatically cheaper. Run a model naively, one clip at a time, and it can cost more than a commercial API. Compare the table above to the API prices earlier: Groq is $0.04 per audio-hour, Soniox $0.10, Azure batch $0.18, all cheaper than naive self-hosted Whisper. The open-source cost advantage only shows up at scale, when you batch hard and keep the GPU saturated. Until then, a cheap hosted API (Groq is literally hosted Whisper) gives you the same model with none of the operational work.

When open-source is worth it

Self-hosting also adds fixed costs the APIs absorb for you: building the batching pipeline, autoscaling GPUs, reliability, monitoring, and rebuilding features like diarization and formatting yourself. Whether the savings clear that overhead comes down to two things.

How we would approach the choice

Here is the decision framed as tradeoffs. Match it to the job you actually have.

Whatever you pick, run your own audio through it before you commit. Vendor demos use easy audio. Your users will not.

See live transcription and translation in action

Verli transcribes and translates any audio your computer plays, live. Free for 60 minutes a month.

Frequently asked questions

Is real-time transcription more expensive than batch?

Usually, but not always. Most providers charge more for real-time streaming than for processing a finished file, because low latency is harder to serve. Deepgram is a notable exception where its published pre-recorded rate is higher than its real-time rate. Groq does not offer real-time at all.

Which speech-to-text APIs translate in real time?

As of July 2026, Soniox, Gladia, and Speechmatics deliver translated text inside the same real-time stream as the transcript. Azure and Google offer translation but as a separate or synchronous-only path, and OpenAI and Groq (both Whisper-based) only translate into English. The practical difference: a same-stream translation is one integration and one bill, while a separate path means a second service to wire up, pay for, and monitor.

Can I run these engines on my own servers?

Some. Speechmatics and Azure support fully air-gapped, on-premises deployment. Deepgram, AssemblyAI, and Rev offer self-hosting on enterprise contracts, and Google has an on-prem option in limited testing. The rest are cloud-only APIs. If an enterprise contract is the blocker, the open-weight models (Whisper, Parakeet, Canary) run on your own servers with no vendor agreement at all.

Why does this comparison not name a best provider?

Because there is no single best one. The right choice depends on whether you need real-time streaming, built-in translation, on-prem deployment, wide language coverage, or the lowest price, and no provider leads on all of them. Accuracy, the other deciding factor, cannot be judged fairly from vendor pages, so we test it ourselves in part two.

Are open-source speech-to-text models cheaper than a paid API?

Only at scale. Per hour of audio, a well-batched open model can cost under a cent, far less than any API. But you pay for the GPU whether it is busy or idle, plus the engineering to run it, so at low or spiky volume a cheap hosted API like Groq is cheaper all-in. Serverless per-second GPU hosting sits in the middle: it removes the idle cost, but at around $2.88 per audio-hour it runs pricier than every API rate in our table. Open-source wins when you have high, steady volume, or a hard requirement like on-prem deployment or fine-tuning that no API can meet.

More from Verli