Whisper: OpenAI's Open Source Voice Transcription

By Carlos Montiel | Enterprise AI Specialist
Leer en español →
Published: 2026-07-28 | By: Carlos Montiel | Reading time: ~5 minutes

Whisper is probably OpenAI's most underrated open-weight model: it transcribes speech with near-human accuracy in dozens of languages and is free to run on your own infrastructure.

What it is and why it matters

Whisper is a Transformer-style encoder-decoder model trained by OpenAI on 680,000 hours of supervised multilingual audio, released in 2022 with open weights under the MIT license. Unlike GPT, OpenAI did release the full weights here -- from the `tiny` model (39M parameters) up to `large-v3` (1.55B parameters) -- letting you run it locally with no API limits or per-minute cost.

Its architecture does more than transcribe: in the same forward pass it can detect the spoken language, translate to English, and segment by timestamps, because it was trained multi-task from the start instead of being a pure transcription model adapted afterward.

pip install openai-whisper whisper audio.mp3 --model large-v3 --language Spanish --output_format srt

Real accuracy: what to expect by language

OpenAI's official benchmark shows very competitive WER (Word Error Rate) in English (~3-4% on large-v3 over standard datasets), but accuracy drops unevenly in other languages depending on how much audio in that language existed in the training corpus. Spanish has good coverage and works well even with varied Latin American accents, but we've noticed noticeable degradation with: audio with significant background noise (call centers, industrial environments), overlapping speakers, and very domain-specific jargon or terminology (drug names, local legal terms).

For this last problem, Whisper's "prompting" technique -- passing an `initial_prompt` with expected vocabulary -- improves accuracy on domain terminology with no fine-tuning needed, though its effect is limited compared to a real fine-tune.

faster-whisper: the variant used in production

OpenAI's original Whisper in PyTorch is slow and VRAM-hungry for use at scale. faster-whisper, a reimplementation using CTranslate2 (the same optimized inference engine OpUS-MT uses), gives 4x to 8x more speed with lower memory use and practically the same accuracy, because it uses INT8 quantization and optimized kernels without touching the model architecture.

from faster_whisper import WhisperModel model = WhisperModel("large-v3", device="cuda", compute_type="int8_float16") segments, info = model.transcribe("audio.mp3", language="es") for s in segments: print(f"[{s.start:.1f}s -> {s.end:.1f}s] {s.text}")

For almost any production deployment, faster-whisper (or a server wrapper like whisper.cpp for CPU/edge, or the faster-whisper inference server via WhisperX) is the right choice over the original package.

WhisperX: diarization and word alignment

Whisper alone doesn't do speaker diarization (identifying who said what) and its word-level timestamps are imprecise because it was trained at segment level, not word level. WhisperX solves both problems: it aligns Whisper's output with a forced phonetic recognition model (wav2vec2) for precise per-word timestamps, and adds diarization using pyannote.audio.

This is critical for real use cases like meeting transcription, interviews, or call-center calls where you need to know "who said what and when," not just the plain text.

Deployment considerations at scale

For high-volume transcription (thousands of hours of audio per month), the architecture decisions with the biggest cost impact are: audio batching (processing multiple files in parallel taking advantage of available VRAM), choosing the right model size for the use case (large-v3 isn't always necessary -- `medium` gives good Spanish accuracy at half the compute), and prior VAD (voice activity detection) to avoid spending compute transcribing silence, something WhisperX and faster-whisper natively integrate with models like Silero VAD.

In a recent deployment for a client transcribing sales calls for later LLM analysis, we used faster-whisper with `medium` quantized in INT8 on a shared GPU, processing ~200 hours of audio daily with transcription latency below the audio's real time (transcribing 1 hour of audio takes 8-12 minutes).

When to use the API instead of self-hosting

If your volume is low (a few hours a month) or sporadic, OpenAI's API (or alternatives like Groq, which serves Whisper on LPU hardware at very high speeds) can be cheaper than maintaining dedicated GPU infrastructure. The typical economic break-even point is around 50-100 hours of monthly audio, depending on the cost of your available GPU infrastructure vs. the API's per-minute price.

Carlos Montiel
Enterprise AI Solutions Architect
Specialist in LLMs, Agents, and Orchestration
guatemalia.com/en/#contact · info@guatemalia.com

Need to implement AI at your company?

Carlos Montiel is an enterprise AI solutions architect. He implements LLMs, Agents, RAG, and orchestrators for companies across Guatemala and Latin America. Reach out for a consultation.

Contact Carlos Montiel

info@guatemalia.com