If you want accurate transcription without paying to start, the best free option for most developers is a free-tier API. AssemblyAI's free tier needs no credit card and covers up to 185 hours of pre-recorded and up to 333 hours of streaming transcription on current models, plus an open playground to test your own audio. If you need to run fully offline or self-host with no per-hour fee, the best free option is an open-source engine, and OpenAI's Whisper is the most widely used. Everything below unpacks that answer: the free-tier APIs, the open-source engines, and how to pick between them.
"Free" means two very different things in speech-to-text. A free-tier API is a hosted service you call over the network: someone else runs the model, you get a limited free allotment, and you pay per hour past it. An open-source engine is model weights and code you run yourself: no per-hour fee, but you own the servers, the GPUs and the accuracy gap. Which one is right depends on whether you'd rather manage a bill or manage infrastructure.
What is a speech-to-text API?
A speech-to-text API, also called an automatic speech recognition (ASR) API, takes audio in and returns text out over a network call. You send a file or an audio stream, the provider runs it through a trained speech-to-text model, and you get back a transcript, usually with timestamps, speaker labels and confidence scores. You don't host anything, manage GPUs or retrain models. You make an HTTP request or open a WebSocket and read the response.
The tradeoff is that you pay per hour of audio and send data to a third party, which is why some teams reach for open-source engines instead. Both are legitimate choices. It helps to hold the two categories side by side, because the decision usually comes down to a handful of dimensions:
| Dimension | Free-tier APIs (hosted) | Open-source engines (self-hosted) |
|---|---|---|
| Accuracy | Current production models, updated by the provider | Varies widely; you pick and upgrade the model |
| Setup time | Minutes: an API key and a few lines of code | Days to weeks: environment, GPUs, model tuning |
| Ongoing cost | Per hour of audio past the free tier | No licensing fee; you pay for compute and MLOps |
| Features (diarization, streaming, PII) | Built in | Build them yourself |
| Data privacy | Audio leaves your environment (BAAs available from some providers) | Fully offline on your own hardware |
| Maintenance | Provider handles it | You own it |
Almost every choice below is a point on this spectrum between "manage a bill" and "manage infrastructure."
Free speech-to-text APIs
These are hosted services with a real free tier. The free allotments are meant for evaluation, but they let you test accuracy on your own audio before committing.
Free tier and limits at a glance
Free tiers as listed on each provider's pricing page, checked November 17, 2026.
| Provider | Free to start | Languages | Real-time streaming | Best for |
|---|---|---|---|---|
| AssemblyAI | Up to 185 hrs pre-recorded + up to 333 hrs streaming, no card | 32 on AssemblyAI-STT-3.7 and the 3.7 realtime models; 99 with Universal-2 | Yes | Multilingual audio, meetings, voice agents, production apps |
| Google Cloud Speech-to-Text | First 60 min/month | 125+ | Yes | Existing Google Cloud users |
| Amazon Transcribe | 60 min/month for the first 12 months | See AWS docs | Yes | Existing AWS users |
AssemblyAI
AssemblyAI is a Voice AI platform for turning audio into accurate, structured text, and for building on top of that text. Its current models split by job:
- AssemblyAI-STT-3.7 (
assemblyai-stt-3-7, $0.21/hr) for recorded audio: 32 languages with automatic language detection and native code switching, plus a new speaker diarization model. It replaced Universal-3.5 Pro, which was deprecated on November 17, 2026. - AssemblyAI-STT-3.7-Realtime ($0.30/hr) for live transcripts such as captions and notetakers, with speaker labels that are final the moment a turn ends.
- AssemblyAI-STT-3.7-Realtime-Agent ($0.45/hr) for voice agents. On 12,460 English voice-agent calls it posted 4.53% normalized WER in AssemblyAI's November 2026 benchmark, the lowest of the 26 streaming models we ran, ahead of Soniox, ElevenLabs, Speechmatics, Google and Deepgram.
- Universal-2 ($0.15/hr) for 99 languages. List it after AssemblyAI-STT-3.7, as
["assemblyai-stt-3-7", "universal-2"], and languages outside the 32 fall through to it.
On code switching, where a speaker moves between English and another language mid-sentence, the spread between providers is wide, and AssemblyAI-STT-3.7 has the lowest average WER of the systems measured, ahead of ElevenLabs, Soniox, AWS, OpenAI and Deepgram. Average WER across 16 datasets mixing English with German, Spanish, French, Italian or Portuguese, from the AssemblyAI-STT-3.7 research post (November 2026; most other vendors measured September 2026):
| Model | Type | Average WER (lower is better) |
|---|---|---|
| AssemblyAI-STT-3.7 | Hosted API | 6.2% |
| ElevenLabs Scribe v3 | Hosted API | 6.8% |
| Soniox stt-async-v5 | Hosted API | 10.2% |
| AWS Transcribe | Hosted API | 22.9% |
| NVIDIA Parakeet TDT 0.6B v3 | Open weights | 29.3% |
| OpenAI GPT-4o Transcribe | Hosted API | 44.7% |
| Deepgram Nova-3 | Hosted API | 49.4% |
On speaker diarization for English conversations, AssemblyAI-STT-3.7 has the lowest diarization error rate of the pre-recorded APIs measured, 10.7%, ahead of ElevenLabs Scribe v3 (12.0%), Speechmatics Enhanced (16.2%), AWS Transcribe (16.9%), Deepgram Nova-3 (17.4%) and Soniox (24.2%), per the same research post. If you're comparing free tiers for meeting audio, put your shortlist through your own multi-speaker files. For more on reading these numbers, see how accurate speech-to-text is in 2026.
The transcript is the start. AssemblyAI's Speech Understanding features add speaker diarization, sentiment, entity detection and PII redaction, and the LLM Gateway gives you one endpoint to run summaries or custom prompts against leading LLMs. If you're heading toward voice agents, pair AssemblyAI-STT-3.7-Realtime-Agent with AssemblyAI's Text-to-Speech API for one speech vendor on both ends.
- Free to start: up to 185 hours of pre-recorded and up to 333 hours of streaming transcription, no credit card, plus an open playground.
- Pricing past free: $0.15/hr (Universal-2) and $0.21/hr (AssemblyAI-STT-3.7) pre-recorded; $0.30/hr and $0.45/hr for the two realtime models; no minimums and no spend commitment.
- Pros: native code switching across 32 languages, realtime and pre-recorded from one API key, speaker diarization, a voice-agent model, SDKs for Python and JavaScript (
pip install assemblyai/npm install assemblyai). - Cons: the free tier is hosted only. Self-hosted deployment is available, but you set it up with the sales team, not self-serve.
Google Cloud Speech-to-Text
Google Cloud Speech-to-Text supports 125+ languages, and its pricing page lists the first 60 minutes per month free. If your infrastructure already lives in Google Cloud, it's a reasonable default.
- Free to start: first 60 minutes per month.
- Pros: broad language coverage, tight Google Cloud integration.
- Cons: longer files generally need to sit in a Google Cloud Storage bucket, and setup runs through the Google Cloud console and IAM.
Amazon Transcribe
Amazon Transcribe gives you 60 free audio minutes per month for the first 12 months, starting from your first transcription request, per its pricing page. It also has a separate medical API. Like Google, it pulls you toward its own ecosystem.
- Free to start: 60 minutes per month, first 12 months only.
- Pros: deep AWS integration, a medical-specific option.
- Cons: batch audio generally has to sit in an Amazon S3 bucket first, and free usage ends after a year. On the code-switching table above it averaged 22.9% WER.
Start on the free tier with no card and transcribe your own audio on AssemblyAI-STT-3.7. Move to pay-as-you-go when you're ready.
How to evaluate speech-to-text solutions
Before you commit to anything, free tier or open source, test it against these five dimensions on your own audio, not a vendor's demo clip.
Accuracy testing for your use case
Word error rate (WER) is the standard metric, but the headline number hides a lot. What matters is accuracy on your audio: your accents, your domain vocabulary, your background noise, your code switching. A model that scores well on clean read speech can fall apart on a noisy contact-center call.
A practical way to run this: assemble 30–60 minutes of audio that looks like your production traffic, hand-correct it into a reference transcript, then score each candidate's output against it. Pay attention to entity errors. A name, a phone number or a dollar amount transcribed wrong costs far more than a dropped filler word, and headline WER treats them the same. Here's how to evaluate speech recognition models, including why raw WER can mislead, and the benchmarks page shows how AssemblyAI scores entity errors and speaker attribution.
Feature completeness
Transcription is table stakes. Do you also need speaker diarization, real-time streaming, timestamps, confidence scores, PII redaction, multilingual support or summarization? A hosted API bundles these; an open-source engine usually means building them yourself. Count the features you need before comparing rates.
Be specific about the hard ones. Real-time streaming with natural turn-taking is difficult to build well, because a simple silence timer produces an agent that talks over people. Code switching breaks many models, as the table above shows. Diarization that stays accurate on overlapping speech and short clips is its own research problem. If your use case touches any of these, weight them heavily.
Developer experience and documentation
A clean SDK, accurate docs and predictable errors save more money than a lower rate card. Test the docs during your evaluation; they don't get better after you commit.
Scalability and reliability
Free tiers cap usage and throughput. Ask what production looks like: rate limits, concurrency, uptime history, regional endpoints. AssemblyAI's documented defaults for paid accounts are 200 parallel pre-recorded jobs, with custom limits at no extra cost, and 200 new streaming sessions per minute that rise 10% whenever you open 80% or more of the limit. Free accounts start at 5 new streaming sessions per minute. Confirm the scaling story before you build on a free tier you'll outgrow in a week.
Total cost of ownership
The per-hour rate is one line item. The full picture includes rework from transcription errors, engineering and maintenance time, storage and egress, and, for self-hosted models, GPUs and MLOps headcount. We break the calculation down in our guide to speech-to-text pricing and when to switch providers. The rate card with the smallest number is rarely the smallest total.
| Evaluation factor | Hosted API | Self-hosted open source |
|---|---|---|
| Time to first transcript | Minutes | Days to weeks |
| Accuracy improvements | New models ship from the provider; you choose when to switch | Your responsibility; requires ML expertise to tune |
| Scaling | Pay-as-you-go with documented rate limits that grow with usage | Provision and manage your own GPU fleet |
| Maintenance | Provider patches and upgrades | Continuous: you own upgrades and uptime |
| Feature updates | Shipped for you (streaming, diarization, PII, voice agents) | Build and maintain each feature yourself |
The only benchmark that counts is your own. Test accuracy, speaker labels and streaming on a representative sample in the playground.
Open-source speech transcription engines
These have no per-hour fee: you run them on your own hardware. That's free of licensing cost, but you take on the servers, the scaling, the maintenance and the accuracy gap. For teams with ML expertise and a data-privacy or offline requirement, that's a fair trade. For most product teams shipping on a deadline, a hosted API wins on total cost.
"Open source" and "actively maintained" aren't the same thing. Some engines below were influential in their day but are archived or no longer maintained, and building new work on them means starting on a foundation that won't improve. We've flagged each one's status, checked on GitHub on November 17, 2026.
Whisper (OpenAI)
Whisper is the most widely used open-source ASR model. It's released under the MIT license, so it's free for commercial use, and it does multilingual recognition, speech translation and language identification. Sizes run from tiny to large-v3, plus a faster turbo model, so you can trade accuracy for speed.
- License: MIT (commercial use allowed). Actively maintained.
- Pros: open weights, large community, faster community variants such as faster-whisper and Distil-Whisper.
- Cons: no built-in speaker diarization or streaming, so you'll add separate tools for both, and self-hosting carries real GPU and maintenance overhead. Accuracy varies widely by language, per its own README.
NVIDIA Parakeet
NVIDIA's Parakeet TDT 0.6B v3 is a compact open-weights model under CC-BY-4.0, covering 25 languages per its model card. It's a good fit for self-hosted English and European-language transcription where you want speed on modest GPUs.
- License: CC-BY-4.0 (commercial use with attribution).
- Pros: small and fast, part of NVIDIA's NeMo toolkit, actively updated.
- Cons: 29.3% average WER on the code-switching table above, so mixed-language audio is a weak spot; diarization and streaming are separate work.
Kaldi
Kaldi is the veteran research toolkit, Apache 2.0 licensed, production-tested, with a deep community. It's highly customizable and can train strong domain-specific models.
- Pros: strong accuracy when tuned, full control, mature research ecosystem.
- Cons: steep learning curve, command-line and recipe-driven, and expensive to run and maintain at scale.
SpeechBrain
SpeechBrain is a PyTorch-based toolkit under Apache 2.0, integrated with Hugging Face, which makes pulling in pre-trained models straightforward.
- Pros: flexible, actively updated, easy access to pre-trained models through Hugging Face.
- Cons: real customization takes ML expertise, and documentation can be sparse in places.
DeepSpeech (Mozilla)
DeepSpeech was Mozilla's open-source engine, designed to run everywhere from a GPU down to a Raspberry Pi 4. Its GitHub repository is archived, so there are no updates, no official support and no accuracy improvements coming.
- Pros: easy to customize, can train custom models, runs on modest hardware.
- Cons: archived and unmaintained. Treat it as legacy, not a foundation for new work.
Coqui STT
Coqui STT grew out of the DeepSpeech lineage and returns confidence scores. Its README says the project is no longer actively maintained, and the team has stopped hosting its online model zoo (models remain in a releases repo).
- Pros: confidence scores, pre-trained models, MPL-2.0 license.
- Cons: unmaintained; no ongoing model improvements.
Flashlight ASR (formerly Wav2Letter)
Flashlight ASR, the project once known as Wav2Letter from Facebook AI Research, is a fast C++ engine inside the MIT-licensed Flashlight library.
- Pros: highly customizable, fast processing.
- Cons: complex setup, no ready-made pre-trained model library, and you'll need to source and manage training data yourself.
Understanding free tier limitations and scaling
Common free tier restrictions
Free tiers limit you on purpose: capped monthly minutes or credit, limited concurrency, and sometimes time limits, like Amazon Transcribe's 12-month window. That's fine for evaluation and a problem the moment you go to production.
Planning for scale
Model your real monthly volume early. A hobby project transcribing a few hours a month lives comfortably in a free tier or on a self-hosted Whisper instance. A product doing thousands of hours needs pay-as-you-go pricing with real concurrency, and at that scale the accuracy and maintenance differences between options dwarf the per-hour rate.
| Usage scenario | Monthly volume | Free tier viable? | Best fit |
|---|---|---|---|
| Personal or hobby project | A few hours | Yes | Free-tier API or self-hosted Whisper |
| Prototype or MVP | Tens of hours | Usually, on a generous free tier | Free-tier API, then pay-as-you-go |
| Growing product | Hundreds of hours | No | Pay-as-you-go API with concurrency headroom |
| Scaled application | Thousands of hours | No | Pay-as-you-go at volume, or a custom plan |
| Enterprise or regulated | Thousands+ with compliance needs | No | Hosted API with a Business Associate Addendum (BAA), or self-hosted for full offline control |
Cost modeling beyond free tiers
When you outgrow free, run the full total-cost-of-ownership math: API rate, plus error-driven rework, plus engineering and maintenance, plus (for self-hosting) GPUs and MLOps. A more accurate model at a higher rate often has the smaller total once rework is counted. For a provider-by-provider rate table, see our speech-to-text API pricing comparison.
Migration strategies
Whatever you pick first, keep it swappable. Put the transcription call behind your own interface so switching providers or models later is a config change. Free tiers, unmaintained open-source projects and deprecated model versions are all things you'll want to move off eventually. AssemblyAI accounts that don't set speech_models move from Universal-3.5 Pro to AssemblyAI-STT-3.7 automatically on December 8, 2026; setting the model name explicitly lets you choose the timing.
Which free option is right for your project?
- You want accuracy and speed with the least effort: a free-tier API. Start on AssemblyAI's free tier, test your own audio in the playground, and move to pay-as-you-go when you're ready.
- You must run fully offline or self-host for privacy: Whisper, or Parakeet for fast English and European-language transcription. Budget for GPUs and maintenance, and plan to add diarization yourself.
- You're already deep in a cloud ecosystem: Google or AWS can make sense for the integration, accepting the bucket-storage setup and the smaller free allotments.
- You're building a voice agent: use AssemblyAI-STT-3.7-Realtime-Agent for speech in and AssemblyAI's Text-to-Speech API for speech out, orchestrated with LiveKit, Pipecat or your own loop.
- You need a research toolkit to train custom models: Kaldi or SpeechBrain, if you have the ML expertise to run them.
Avoid building anything new on DeepSpeech or Coqui STT. Both are unmaintained.
Getting started with speech-to-text integration
Quick start with an API
The fastest way to see real accuracy is to transcribe your own audio. With the AssemblyAI Python SDK it's a few lines. This sends a file to AssemblyAI-STT-3.7, falls back to Universal-2 for languages outside the 32, and prints speaker-labeled lines:
# pip install assemblyai
import os
from assemblyai import TranscriptStatus
from assemblyai.prerecorded.v2 import Transcriber, TranscriptionConfig
config = TranscriptionConfig(
speech_models=["assemblyai-stt-3-7", "universal-2"], # 32 languages, Universal-2 covers the rest of 99
language_detection=True,
speaker_labels=True,
)
transcriber = Transcriber(api_key=os.environ["ASSEMBLYAI_API_KEY"], config=config)
transcript = transcriber.transcribe("https://assembly.ai/wildfires.mp3")
if transcript.status == TranscriptStatus.error:
raise RuntimeError(f"Transcription failed: {transcript.error}")
for utterance in transcript.utterances:
print(f"Speaker {utterance.speaker}: {utterance.text}")AssemblyAI-STT-3.7 returns verbatim transcripts by default, with fillers kept and numbers in written form. Add disfluencies=False to the config for clean prose.
Integration best practices
Put the provider behind your own interface, handle errors and retries from day one, and list a fallback model so a language outside your main model's coverage doesn't fail the request. If you're building in Python, our guide to Python speech recognition covers the libraries and patterns in depth. The docs' model selection page lists every model name and parameter.
Moving to production
Before you ship, confirm rate limits and uptime history, budget for volume past the free tier, add monitoring on latency and error rates, and lock in your data-privacy and compliance requirements. If you're still comparing paid providers, our guide to choosing a speech-to-text API has a weighted scorecard and a benchmarking method.
A few lines of Python and an API key get you a speaker-labeled transcript on AssemblyAI-STT-3.7. Start free, no credit card required.
Frequently Asked Questions (FAQs)
What is the best free speech-to-text option for most developers in 2026?
For most developers, a free-tier API is the best free option because it gives current production accuracy with no infrastructure to manage. AssemblyAI's free tier needs no credit card and runs on AssemblyAI-STT-3.7 and the 3.7 realtime models. If you need to run fully offline, Whisper is the most widely used open-source engine.
Is there a free API for speech-to-text?
Yes. AssemblyAI, Google Cloud Speech-to-Text and Amazon Transcribe all have free allotments. AssemblyAI lists up to 185 hours of pre-recorded and 333 hours of streaming transcription with no card; Google lists the first 60 minutes per month free; Amazon gives 60 minutes per month for the first 12 months. Past those limits, each charges per hour of audio.
What is the best free and open-source speech-to-text engine?
Whisper is the most widely used open-source engine: MIT-licensed, multilingual and free for commercial use. NVIDIA's Parakeet TDT 0.6B v3 is a smaller, faster option under CC-BY-4.0. Neither includes speaker diarization out of the box, and on code-switched audio Parakeet averaged 29.3% WER against 6.2% for the hosted AssemblyAI-STT-3.7 in AssemblyAI's November 2026 benchmark.
Is Whisper free for commercial use?
Yes. Whisper is released under the MIT license, so you can use it commercially, modify it and self-host it without a licensing fee. Your real costs are the compute to run it and the engineering to maintain it.
Which free speech-to-text API is most accurate on hard audio?
It depends on what makes your audio hard. On code-switched audio, AssemblyAI-STT-3.7 averaged 6.2% WER in AssemblyAI's November 2026 benchmark, the lowest of the systems measured, ahead of ElevenLabs Scribe v3 (6.8%) and Soniox (10.2%); on multi-speaker recordings, its 10.7% diarization error rate is the lowest of the pre-recorded APIs measured, ahead of ElevenLabs Scribe v3 (12.0%), AWS Transcribe (16.9%) and Deepgram Nova-3 (17.4%). Test candidates on a representative sample of your own audio.
Do free speech-to-text APIs support real-time streaming?
Many do. AssemblyAI's free tier includes streaming on AssemblyAI-STT-3.7-Realtime for live transcripts and AssemblyAI-STT-3.7-Realtime-Agent for voice agents, starting at 5 new streaming sessions per minute on free accounts. Google and Amazon also offer streaming within their free allotments.