Skip to content

Research

Transcription speed and accuracy, measured

We ran the Whisper models that power TryScriptorium (tiny, base and small) on public test clips, on our own server. On 487 seconds of English speech the small model's word error rate was 3.4% on clean speech and 4.0% on harder speech, and 31.8% on 246 seconds of Arabic. These are measurements on specific clips, not a promise about your recording.

Last updated:

Measured on 24 October 2026. Every number is real and stored in a downloadable data file: transcription-speed.json.

Results: English

ModelWER, clean speechWER, harder speechReal-time factorCPU-seconds per audio-secondPeak memory (MB)
tiny5.7%9.3%0.240.15379
base4.6%5.7%0.530.29460
small3.4%4.0%1.250.78901

WER is word error rate (lower is better). "Clean" is LibriSpeech dev-clean; "harder" is dev-other, which has more difficult speakers and recordings. Real-time factor is wall-clock processing time divided by audio length.

Results: Arabic

ModelWERReal-time factorCPU-seconds per audio-secondPeak memory (MB)
tiny64.4%0.440.31382
base60.2%0.620.46485
small31.8%1.271.361335

Read Arabic sentences from FLEURS (ar_eg, Egyptian speakers reading standard written text), scored after Arabic letter normalisation (diacritics removed; alef, yeh and teh-marbuta forms unified).

What the speed means

The server was busy with other work during the run (1-minute load average between 9.4 and 24.4 on 4 vCPUs) and the benchmark was limited to 150% of one CPU-second per second (cgroup cap), so wall-clock times are slower than an idle machine would give. The better figure is CPU-seconds per audio-second. The small model used 0.78 CPU-seconds per second of audio, about 47 CPU-seconds for each minute of recording.

Method

  • Hardware: Intel Core Processor (Broadwell, no TSX, IBRS), 4 vCPUs, 7.7 GB RAM, no GPU. This is the same server that runs the website, so it was not idle.
  • Software: faster-whisper 1.2.1, CTranslate2 4.8.2, Python 3.14.4.
  • Settings mirror the production engine: CPU, int8, beam size 5, voice-activity filter on. The language was set explicitly (no auto-detection).
  • Data:
  • Clips: 6 English and 3 Arabic clips of roughly 75-100 seconds, built by joining consecutive sentences, each with its reference text.
  • WER: word-level edit distance divided by reference word count. English: lower-cased, punctuation removed, no number normalisation (so "10" against "ten" counts as an error). Arabic: diacritics removed, letter forms unified.
  • CPU time is the process's user plus system CPU time while transcribing. Memory is peak resident size of a separate process per model.
  • Repeats: one run per model, no confidence intervals.

What these numbers do not show

  • Only clearly recorded read speech. Phone calls, noise, crosstalk and strong accents give higher error rates.
  • Only English and Arabic. We did not measure other languages.
  • The medium and large models were not run: the shared production server cannot safely fit them while serving the site.
  • Few clips, one run: small differences between two models are not evidence.
  • Arabic scoring is strict: spelling variants (for example hamza forms) and dialect words count as errors even when a reader would accept them, so the Arabic error rates are not directly comparable with the English ones.
  • This is not a promise of accuracy for your audio. The free preview uses the small model.

How to cite

TryScriptorium. "Transcription speed and accuracy, measured." 24 October 2026. https://tryscriptorium.com/research/transcription-speed

See also the fact sheet and Arabic transcription.

Per-clip data
ClipModelAudio sWall sRTFCPU-s per audio-sReference wordsErrorsWER
dev-clean-2035-147960tiny76.924.650.3210.154231156.5%
dev-clean-2035-147961tiny75.220.680.2750.151236135.5%
dev-clean-2035-152373tiny79.418.670.2350.139205104.9%
dev-other-116-288045tiny78.019.580.2510.146204199.3%
dev-other-116-288046tiny98.419.710.20.151284269.2%
dev-other-116-288047tiny79.414.640.1840.146231229.5%
dev-clean-2035-147960base76.941.820.5440.322231156.5%
dev-clean-2035-147961base75.238.040.5060.27423693.8%
dev-clean-2035-152373base79.450.380.6350.27520573.4%
dev-other-116-288045base78.046.170.5920.305204125.9%
dev-other-116-288046base98.442.410.4310.267284134.6%
dev-other-116-288047base79.439.770.5010.309231166.9%
dev-clean-2035-147960small76.986.221.1210.782231135.6%
dev-clean-2035-147961small75.2140.831.8730.8123641.7%
dev-clean-2035-152373small79.473.470.9250.67420562.9%
dev-other-116-288045small78.079.321.0170.77320494.4%
dev-other-116-288046small98.4132.671.3480.818284113.9%
dev-other-116-288047small79.498.171.2360.78923193.9%
fleurs-ar-eg-1tiny83.621.10.2520.1861356447.4%
fleurs-ar-eg-2tiny82.124.740.3010.231419668.1%
fleurs-ar-eg-3tiny80.261.960.7730.5081239778.9%
fleurs-ar-eg-1base83.633.780.4040.2961356648.9%
fleurs-ar-eg-2base82.133.460.4080.3131419265.2%
fleurs-ar-eg-3base80.286.51.0790.7851238266.7%
fleurs-ar-eg-1small83.678.650.9410.9241352216.3%
fleurs-ar-eg-2small82.174.830.9110.9991414431.2%
fleurs-ar-eg-3small80.2158.861.9812.1831236149.6%

Try it with your own file

No account needed for a first transcript.

Frequently asked questions

How fast is the Whisper small model on a CPU?
On our 4-vCPU server it processed audio at a real-time factor of 1.25 while the server was busy with other work. The load-independent figure is CPU time: 0.78 CPU-seconds per second of audio.
What is the real-time factor?
Processing time divided by recording length. A factor of 0.5 means a 10-minute recording took 5 minutes.
What is word error rate?
The number of word substitutions, deletions and insertions divided by the number of words in the reference text. Lower is better.
Which model does the free preview use?
The small model.
Do these numbers apply to my recording?
Not necessarily. They describe clearly recorded read speech. Phone audio, noise, crosstalk and accents raise error rates, so always check the transcript.

Keep reading