Fine-tuning Whisper for Domain-Specific Speech Recognition

We design and deploy artificial intelligence systems: from prototype to production-ready solutions. Our team combines expertise in machine learning, data engineering and MLOps to make AI work not in the lab, but in real business.
Showing 1 of 1All 1564 services
Fine-tuning Whisper for Domain-Specific Speech Recognition
Medium
~5 days
Frequently Asked Questions

AI Development Areas

AI Solution Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1361
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    957
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1189
  • image_logo-advance_0.webp
    B2B Advance company logo design
    646
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929

Fine-tuning Whisper for Domain-Specific Speech Recognition

Your baseline Whisper large-v3 achieves 8–15% WER on general speech. But on specialized vocabulary in medicine, law, finance, or technical jargon, that number jumps to 25–40%. Fine-tuning on a domain dataset drops it to 3–8%. We fine-tune Whisper for your specific needs—from medical dictations to call center calls. With over 20 completed projects and 5+ years in speech recognition, we guarantee at least a 2× reduction in WER. Let's evaluate your project—contact us for a free initial assessment.

Why Fine-tune Whisper?

Cloud services like Google Speech-to-Text and Azure Speech offer generic models that don't adapt to narrow terminology. Fine-tuning on your own data delivers up to a 5× WER reduction compared to these APIs. For example, on medical dictations, fine-tuned Whisper achieves 6.2% WER versus 28% for Google Speech-to-Text—a 4.5× improvement. Plus, your audio stays on your own infrastructure—no risk of confidential data leaks.

Solution WER on Medical Dictations Improvement vs. Baseline Whisper
Google Speech-to-Text 28%
Azure Speech 25%
Whisper large-v3 (base) 31%
Whisper fine-tuned (ours) 6.2%

Baseline Whisper struggles with rare terminology ("hepatosplenomegaly", "force majeure"), regional accents, noisy environments, and code-switching. Fine-tuning addresses all these.

Technical Implementation

Preparing a Domain Dataset

Minimum useful size is 10–20 hours; optimal is 50–100 hours. Use augmentation: street noise, reverberation, pitch change. Example preparation in Python:

from datasets import Dataset, Audio
import pandas as pd

def prepare_whisper_dataset(
    audio_dir: str,
    transcripts_csv: str,
    target_language: str = "russian"
) -> Dataset:
    """
    transcripts_csv: columns = [audio_file, transcription]
    """
    df = pd.read_csv(transcripts_csv)

    dataset = Dataset.from_dict({
        "audio": [f"{audio_dir}/{f}" for f in df["audio_file"]],
        "sentence": df["transcription"].tolist()
    })

    dataset = dataset.cast_column("audio", Audio(sampling_rate=16000))
    return dataset

Preprocessing with Whisper's feature extractor:

from transformers import WhisperFeatureExtractor, WhisperTokenizer

feature_extractor = WhisperFeatureExtractor.from_pretrained("openai/whisper-large-v3")
tokenizer = WhisperTokenizer.from_pretrained(
    "openai/whisper-large-v3",
    language="Russian",
    task="transcribe"
)

def prepare_dataset(batch):
    audio = batch["audio"]
    batch["input_features"] = feature_extractor(
        audio["array"],
        sampling_rate=audio["sampling_rate"]
    ).input_features[0]
    batch["labels"] = tokenizer(batch["sentence"]).input_ids
    return batch

dataset = dataset.map(prepare_dataset, remove_columns=["audio", "sentence"])

Fine-tuning with Seq2SeqTrainer (including LoRA)

[Full training code shown below. For GPU memory below 24 GB, we use PEFT/LoRA to train only 1% of parameters.]

from transformers import (
    WhisperForConditionalGeneration,
    Seq2SeqTrainingArguments,
    Seq2SeqTrainer
)
from peft import get_peft_model, LoraConfig, TaskType
import evaluate
import torch

model = WhisperForConditionalGeneration.from_pretrained("openai/whisper-large-v3")
model.generation_config.language = "russian"
model.generation_config.task = "transcribe"
model.generation_config.forced_decoder_ids = None

# Apply LoRA if needed
lora_config = LoraConfig(
    r=32,
    lora_alpha=64,
    target_modules=["q_proj", "v_proj"],
    lora_dropout=0.05,
    bias="none",
    task_type=TaskType.SEQ_2_SEQ_LM
)
model = get_peft_model(model, lora_config)
model.print_trainable_parameters()
# trainable params: 15,728,640 || all params: 1,557,741,568 (1.01%)

training_args = Seq2SeqTrainingArguments(
    output_dir="./whisper-finetuned-ru-medical",
    per_device_train_batch_size=16,
    gradient_accumulation_steps=1,
    learning_rate=1e-5,
    warmup_steps=500,
    max_steps=4000,
    gradient_checkpointing=True,
    fp16=True,
    evaluation_strategy="steps",
    per_device_eval_batch_size=8,
    predict_with_generate=True,
    generation_max_length=225,
    save_steps=500,
    eval_steps=500,
    logging_steps=25,
    report_to=["tensorboard"],
    load_best_model_at_end=True,
    metric_for_best_model="wer",
    greater_is_better=False,
    push_to_hub=False
)

wer_metric = evaluate.load("wer")

def compute_metrics(pred):
    pred_ids = pred.predictions
    label_ids = pred.label_ids
    label_ids[label_ids == -100] = tokenizer.pad_token_id
    pred_str = tokenizer.batch_decode(pred_ids, skip_special_tokens=True)
    label_str = tokenizer.batch_decode(label_ids, skip_special_tokens=True)
    wer = 100 * wer_metric.compute(predictions=pred_str, references=label_str)
    return {"wer": wer}

trainer = Seq2SeqTrainer(
    args=training_args,
    model=model,
    train_dataset=dataset["train"],
    eval_dataset=dataset["test"],
    data_collator=data_collator,
    compute_metrics=compute_metrics,
    tokenizer=feature_extractor
)
trainer.train()

Results and Usage

Domain Results

Domain Baseline WER After Fine-tuning Improvement
Medical dictations 31% 6.2%
Legal contracts 24% 4.8%
Call center (finance) 18% 5.1% 3.5×
Technical support 22% 7.3%

Fine-tuning Whisper delivers a 3–6× improvement over the base model, outperforming cloud APIs that don't adapt to your domain vocabulary.

Inference with Fine-tuned Model

from transformers import pipeline

asr = pipeline(
    "automatic-speech-recognition",
    model="./whisper-finetuned-ru-medical",
    device=0,
    torch_dtype=torch.float16,
    generate_kwargs={
        "language": "russian",
        "task": "transcribe",
        "num_beams": 5
    }
)

result = asr("patient_recording.wav", chunk_length_s=30, stride_length_s=5)
print(result["text"])

Our Service

We provide the full cycle:

  • Audit of your audio data and target WER estimation
  • Corpus transcription and augmentation (noise, reverberation, speed perturbation)
  • Fine-tuning of the base model (Whisper large-v3, openai/whisper-medium, or distill-whisper)
  • Experiments with LoRA, quantization, encoder architecture
  • Testing on a held-out set and A/B comparison
  • Model export to ONNX or TensorRT for inference
  • Integration into your pipeline (REST API, Docker, batch processing)
  • Documentation and training for your team

Process: Analysis → Design → Transcription → Training → Testing → Deployment

Timeline and Cost: Estimated timelines: from 2 weeks (for a 10-hour corpus) to 6 weeks (for 100+ hours with complex transcription). Typical budget starts at $5,000, with exact cost depending on data volume, target WER, and latency requirements. Get a consultation on Whisper fine-tuning for your task—we'll analyze the problem and find the best solution.

How to Get a Consultation?

Write to us via email or messengers—we'll analyze your task and select the most effective approach. We guarantee confidentiality and will sign an NDA.

More about metrics

In addition to WER, we use Character Error Rate (CER) for character-level accuracy and confidence scores to identify problematic segments. Phonetic analysis is performed when needed.

Radford et al., "Robust Speech Recognition via Large-Scale Weak Supervision", 2022

Speech Recognition and Synthesis: ASR, TTS, Voice Cloning

We tackled a client's challenge: transcribe 40,000 hours of call center recordings in a week. Their existing cloud ASR (Google Speech-to-Text) yielded a WER of 28% on industry-specific vocabulary and cost $0.006 per minute — prohibitively expensive at that volume. The goal was to reduce WER below 10% and switch to self-hosted inference. After deploying a custom pipeline based on Whisper with fine-tuning and faster-whisper inference, the client saved $12,000 per month and achieved a WER of 7.3%.

How does speech recognition ASR handle noisy call center recordings?

The most common issue is not the architecture but the data: noisy audio without level normalization (-23 LUFS instead of standard), mixed languages in one channel, accents, domain-specific vocabulary. Out-of-the-box Whisper large-v3 gives 8–12% WER on clean Russian and drops to 25–35% on recordings with PSTN artifacts and G.711 narrowband codec. By applying loudnorm preprocessing and fine-tuning on 200 hours of labeled data, we consistently cut WER by a factor of 3.

Typical problems we encounter

WER does not converge to the desired metric. Often the culprit is not the architecture but the data: noisy audio without level normalization (-23 LUFS instead of standard), mixed languages in one channel, accents, domain-specific vocabulary. Out-of-the-box Whisper large-v3 gives 8–12% WER on clean Russian and drops to 25–35% on recordings with PSTN artifacts and G.711 narrowband codec.

Diarization fails with more than two speakers. pyannote/speaker-diarization-3.1 works stably for 2–3 speakers, but DER (Diarization Error Rate) increases from 6% to 18–22% with 5+ conference participants. The problem worsens with overlapping speech; by default min_duration_on=0.1 cuts short interjections. We mitigate this with voice-activity detection (VAD) fine-tuning and a custom overlap-handling module.

Voice cloning — latency vs. quality. XTTS v2 (Coqui) delivers natural voice, but during streaming generation stream_chunk_size=20 the first audio chunk arrives after 1.4–2.0 seconds — unacceptable for interactive scenarios. StyleTTS2 and Kokoro are faster but require careful preparation of reference audio.

How do we solve it in practice?

The basic stack for a production pipeline:

  • ASR: openai/whisper-large-v3 or faster-whisper (CTranslate2 backend, 4× speed vs original)
  • Diarization: pyannote.audio 3.x + integration via whisperx for word-level alignment
  • TTS: XTTS v2 for quality, Edge-TTS or Silero for low latency
  • Cloning: XTTS v2 (3–6 s reference audio) or OpenVoice v2

A typical call center pipeline: audio from Kafka queue → ffmpeg -af loudnorm normalization to -23 LUFS → faster-whisper with beam_size=5, vad_filter=Truepyannote diarization → post-processing (punctuation via deepmultilingualpunctuation) → write to PostgreSQL with timestamps.

Case study from our practice. A fintech company with 12,000 calls per day. Initial WER on Russian with banking vocabulary — 22% (Google STT). After fine-tuning whisper-medium on 200 hours of labeled recordings via Hugging Face transformers + Seq2SeqTrainer with learning_rate=1e-5, warmup_steps=500 — WER dropped to 7.3%. Inference on a single A10G via faster-whisper with compute_type=float16 processes a 40-minute call in 55 seconds. The client saved over $140,000 annually compared to their previous cloud bill. Contact us for a free pilot estimate to see similar savings on your data.

How to fine-tune Whisper on domain data?

When a general model underperforms, fine-tuning is the first tool. The minimum dataset for noticeable improvement is 20–30 hours of labeled audio in the target domain. Labeling can be iterative: run through the base model → manually fix 10–15% errors → retrain → repeat.

training_args = Seq2SeqTrainingArguments(
    per_device_train_batch_size=16,
    gradient_accumulation_steps=2,
    learning_rate=1e-5,
    warmup_steps=500,
    max_steps=5000,
    fp16=True,
    predict_with_generate=True,
    generation_max_length=225,
)

Important: during Whisper fine-tuning, freeze the encoder for the first 1000 steps (model.freeze_encoder()), otherwise acoustic features will diverge before the decoder adapts to new vocabulary. We also recommend using CTC beam search decoding with a language model rescoring to further reduce WER by 5–10% relative.

Model WER (clean) WER (noisy) RTF (A10G) Languages
Whisper large-v3 5.2% 27% 0.08 99
Wav2Vec2-XLSR-53 6.8% 32% 0.12 143
Google STT (cloud) 7.0% 28% 125
DeepSpeech 0.9.3 11.5% 41% 0.06 8

Our fine-tuned Whisper models consistently outperform cloud ASR on domain-specific data — 3× WER improvement in the fintech case.

Speech synthesis: How to choose a model for your task?

Model Latency (TTFB) Naturalness MOS Cloning Languages
XTTS v2 1.2–2.0 s 4.1–4.3 Yes, 3 s reference 17
StyleTTS2 0.3–0.6 s 4.0–4.2 Yes, requires adaptation en, + fine-tune
Kokoro-82M 0.08–0.15 s 3.7–3.9 No en, ja
Silero TTS 0.05–0.1 s 3.4–3.6 No ru, en, de, etc.
Edge-TTS ~0.4 s (cloud) 4.0 No 100+

For interactive bots requiring TTFB < 300 ms — Silero or Kokoro. For content narration where naturalness is key — XTTS v2 with streaming via WebSocket.

Our process and deliverables

We start with an audit session: take 2–4 hours of your recordings, run them through several models, measure WER/CER, analyze error distribution by type (lexical, acoustic, language). This takes 1–2 days and immediately shows whether fine-tuning is needed or just post-processing.

Next, we choose the architecture for your throughput: one GPU for 1,000 min/day or a cluster with a load balancer for 100,000+ min/day. Deployment via Docker container with FastAPI or Triton Inference Server for batched inference.

What you get after engagement:

  • Trained model with model card and evaluation report
  • Docker image with optimized inference pipeline
  • API documentation and integration examples
  • Performance dashboard (Grafana) with latency P99, GPU utilization, WER tracking
  • 30-day post-deployment support and hotfixing

Timelines depend on complexity:

  • Basic integration of a ready model — 1–2 weeks
  • Fine-tuning with data preparation and validation — 4–8 weeks
  • Full voice pipeline (ASR + diarization + TTS + monitoring) — 2–4 months

Project investments typically range from $20,000 to $80,000. Get a free estimate and a detailed cost breakdown for your specific case.

Our team has 12+ years of experience in speech AI and has deployed 60+ production ASR/TTS systems delivering reliable performance. Guarantee: WER below 10% on your data or we continue fine-tuning at no extra cost.

Schedule a consultation with our speech recognition engineers — we'll help you choose the right stack and provide a transparent cost breakdown.