Our measurement ยท Speech recognition
Bluetooth Headset Dictation Accuracy, Tested
How much accuracy does dictation lose when your voice goes through a Bluetooth headset's call link, narrowband or wideband?
A Bluetooth headset's narrowband call link costs dictation little: Whisper large-v3-turbo went from 3.92 percent word error to 5.18 percent on the CVSD path, the largest rise we measured. The wideband mSBC path left all three engines at or near their original accuracy.
12 results, measured by usUpdated October 22, 2026Free to reuse under CC BY 4.0
3.92percent word error rate
In our October 2026 test on a Mac with an M2 Pro, Whisper large-v3-turbo had a word error rate of 3.92 percent on 100 English FLEURS recordings as recorded (16 kHz, no Bluetooth codec).
How it is calculated
5.18percent word error rate
In our October 2026 test on a Mac with an M2 Pro, Whisper large-v3-turbo had a word error rate of 5.18 percent on 100 English FLEURS recordings after the narrowband voice path of the Bluetooth Hands-Free Profile (CVSD codec, 8 kHz), the one every hands-free headset must support.
How it is calculated
4.53percent word error rate
In our October 2026 test on a Mac with an M2 Pro, Parakeet TDT 0.6B v3 had a word error rate of 4.53 percent on 100 English FLEURS recordings after the narrowband voice path of the Bluetooth Hands-Free Profile (CVSD codec, 8 kHz), the one every hands-free headset must support.
How it is calculated
12data points
The speech recognition accuracy through Bluetooth headset audio dataset holds 12 data points, each a published figure traced to its source.
How it is calculated
Dictation loses a modest amount of accuracy through a Bluetooth headset's call link, and almost all of it comes from the narrowband path. On the wideband mSBC path, no engine got measurably worse. On the narrowband CVSD path, every engine's error rate rose, but the rise was measurable beyond chance only for Whisper large-v3-turbo. This page rests on 12 data points 1: three engines, each run on the same 100 English recordings as recorded and after each of three voice paths.
Whisper loses the most on the narrowband link
Whisper large-v3-turbo scored 3.92 percent word error on the original recordings 2. After the CVSD path every hands-free headset must support, it scored 5.18 percent 3. That is the largest rise of the three engines, and one of only two changes in the test that stayed larger than chance after correcting for all nine comparisons. The other is Whisper on plain 8 kHz audio with no codec, at 5.00 percent 4.
Apple SpeechTranscriber moved from 6.40 percent 5 to 7.43 percent 6 on CVSD. That rise is smaller than Whisper's. Its interval over the 100 recordings stays above zero on its own, but it does not survive the correction for nine comparisons, so we do not call it a measured difference.
Parakeet TDT v3 moved least: 4.11 percent 7 to 4.53 percent 8. Its interval includes zero, so this change cannot be told apart from noise.
| Engine | Maker | Language | Word error rate (%) | Source |
|---|---|---|---|---|
| Parakeet TDT v3 | NVIDIA | English | 4.53 | Calculated 8 |
| Whisper large-v3-turbo | OpenAI | English | 5.18 | Calculated 3 |
| Apple SpeechTranscriber | Apple | English | 7.43 | Calculated 6 |
Most of the narrowband loss is the missing high frequencies, not the codec
The 8 kHz, no codec rows remove the codec and keep only the bandwidth limit. They sit just below the CVSD rows for every engine. Whisper scored 5.00 percent without the codec 4 against 5.18 percent with it 3. Apple scored 7.15 percent 9 against 7.43 percent 6. Parakeet scored 4.39 percent 10 against 4.53 percent 8.
In all three engines the codec adds a little on top of the bandwidth cut, and the gaps are small compared with the cut itself. The practical reading: the damage is done when the link throws away speech above the narrowband ceiling, and CVSD's own distortion adds only a slight extra cost. This test does not examine which words fail.
| Engine | Maker | Language | Word error rate (%) | Source |
|---|---|---|---|---|
| Parakeet TDT v3 | NVIDIA | English | 4.39 | Calculated 10 |
| Whisper large-v3-turbo | OpenAI | English | 5 | Calculated 4 |
| Apple SpeechTranscriber | Apple | English | 7.15 | Calculated 9 |
The wideband path costs nothing you can measure
The mSBC path keeps the full frequency range of the original recordings. Whisper scored 3.69 percent 11, lower than its original 3.92 percent 2. Apple scored 5.93 percent 12, also lower than its original 6.40 percent 5. Parakeet scored 4.20 percent 13, slightly higher than its original 4.11 percent 7.
Two engines improved and one worsened, all by small amounts. None of the three changes is a measured difference after correction. Apple's improvement has an interval that stays below zero by itself, but it is the same kind of result as its narrowband rise: not strong enough once nine comparisons are counted. Do not read it as wideband making Apple's engine more accurate. The honest summary is that wideband and the original recording are indistinguishable here.
| Engine | Maker | Language | Word error rate (%) | Source |
|---|---|---|---|---|
| Whisper large-v3-turbo | OpenAI | English | 3.69 | Calculated 11 |
| Parakeet TDT v3 | NVIDIA | English | 4.2 | Calculated 13 |
| Apple SpeechTranscriber | Apple | English | 5.93 | Calculated 12 |
The best engine depends on which link you have
Whisper has the lowest error on the original recordings (3.92 percent 2, against 4.11 percent for Parakeet 7) and on the wideband path (3.69 percent 11 against 4.20 percent 13). On the narrowband paths the order flips. Parakeet scored 4.53 percent on CVSD 8, below Whisper's 5.18 percent 3, and the same holds on plain 8 kHz audio.
Apple SpeechTranscriber has the highest error in every condition. Its best result, 5.93 percent on wideband 12, is still above Whisper's and Parakeet's worst results. Its narrowband figure of 7.43 percent 6 sits well above the other two.
Where the numbers disagree is the ranking of the top two. The gap between Whisper and Parakeet on each path is small, and we have one test of 100 recordings, so we would not call the flip settled. The finding that holds is the size of the rise: Whisper's was the largest, Parakeet's the smallest.
| Maker | Audio path | Language | Word error rate (%) | Source |
|---|---|---|---|---|
| NVIDIA | Original recording | English | 4.11 | Calculated 7 |
| NVIDIA | Wideband (mSBC) | English | 4.2 | Calculated 13 |
| NVIDIA | 8 kHz, no codec | English | 4.39 | Calculated 10 |
| NVIDIA | Narrowband (CVSD) | English | 4.53 | Calculated 8 |
What this test cannot tell you
The codecs ran in software on studio-clean read speech. A real headset adds its own microphone, noise suppression and radio dropouts, none of which are in these rows, and any of them could cost more accuracy than the codec does. Compare conditions and engines with each other rather than reading these percentages as what a headset in a room will give you. For how engines behave when the room itself is noisy, see our data on noise robustness.
The test also leaves out the newer LE Audio codec (LC3) and makers' own codecs, so it says nothing about headsets that use them. It covers English only. It uses one machine and one set of recordings, so the engine ranking may shift with other speakers, accents or vocabulary. For how these engines compare when run locally without any headset, see the on-device benchmark.
What to do if you dictate through a Bluetooth headset
Prefer a wideband link. Most of the loss we saw comes from the narrowband bandwidth cut, and the wideband path avoided it. If your headset and computer negotiate mSBC for calls, dictation through it should be close to dictating into the original audio. If your device falls back to CVSD, expect somewhat more errors.
Pick the engine for the link you have. On a narrowband link Parakeet had the lower error of the two open engines, and Apple's built-in engine had the highest. On wideband, Whisper led. If you cannot control the link, Parakeet is the steadier choice here, with the smallest rise.
Consider the microphone first. The headset's microphone and room noise are not part of this test and may matter more. A wired or built-in microphone avoids the call link entirely. Our guide to the dictation microphone covers the choices, and the overview of speech recognition explains how engines turn audio into text.
The size of every loss here is small next to the difference between engines in the original recordings. If you already dictate through a Bluetooth headset and are satisfied with the results, this data gives you no strong reason to stop.
Evidence
Every number on this page, with where it comes from. Open a fact to see the exact words in its source.
- 1.
- 2.
- 3.
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
Every data point
Each row is one published figure for one group, in percent. The row opens its fact page with the exact words of the source; the source opens the original.
12 rows. Open a row for the exact words of its source.
Calculated from the rows
Every statistic is calculated by code from the rows above. Open one to see the exact values it summarises.
How this dataset is built
- What counts as a row
- Each engine on the 100 English recordings of our main benchmark, as recorded and after each Bluetooth voice path, every path starting from the same recording at the same speech level.
- What does not
- Real headsets in real rooms (their microphones, noise suppression and radio dropouts), the newer LE Audio codec (LC3) and makers' own codecs, for now.
- How rows are found and checked
- When an app opens a Bluetooth headset's microphone, the link switches to the Hands-Free Profile, which carries voice narrowband (8 kHz, CVSD) or wideband (16 kHz, mSBC). Each recording is brought to a speech level of -26 dB below full scale, then encoded and decoded in software: mSBC with ffmpeg's SBC encoder in mSBC mode, CVSD with the Bluetooth Core Specification's parameters at 64 kbit/s. A fourth path cuts the audio to 8 kHz without a codec, to separate what the bandwidth costs from what the codec adds. Engines and scoring are the same as the main benchmark; the codec code and every file's checksum are in the full record.
- What the data cannot tell you
- The codecs run in software on studio-clean read speech, so this measures the voice path alone: a headset's own microphone, its noise suppression and lost radio packets would add to these errors. One language and one Mac are tested. With 100 recordings (2,141 words) per path, a change of a few tenths of a point is within chance: the full record gives each engine's change from the original recording with its interval over the nine comparisons, and only a change outside that interval counts as measured.
The whole method, from search to calculation, is on the research data page.
Cite and reuse
You may copy, share and adapt this dataset for any purpose, including commercially, if you credit it with a link. Quoted passages remain their authors' words: cite the original source for those.
Yap (2026). Speech recognition accuracy through Bluetooth headset audio [Data set]. https://yapapp.cc/data/asr-bluetooth-audio
License: CC BY 4.0.
Pages built on this data
More datasets
- On-Device Speech Recognition Benchmark: 25 Languages56 data points
- Typing Speed Statistics: Average WPM by Group58 data points
- Speech vs Typing Speed: Text Entry Rates Compared207 data points
- Dictation Punctuation and Capitalization Accuracy56 data points
- Speaking Rate Statistics: Words per Minute50 data points
- Dictation in Noise: Speech Recognition Accuracy Tested15 data points
- Speech Recognition Accuracy: Word Error Rates863 data points
- Speech Recognition Speed: Real-Time Factor Data237 data points
- How Many Languages Speech Recognition Supports208 data points
- Speech-to-Text API Pricing: Cost per Hour of Audio117 data points
- Dictation Software Prices: What Each App Costs248 data points
- How Long Voice Assistants Keep Your Recordings388 data points
- Repetitive Strain Injury Statistics: How Common Is RSI134 data points
- Disability Statistics: Conditions That Make Typing Hard128 data points
- Voice Assistant and Voice Search Usage Statistics73 data points
- Dictation App Problems: What Users Complain About389 data points
- Speech Recognition Market Size: Every Estimate Compared43 data points
- Voice AI Funding: Speech and Dictation Startup Rounds55 data points
- History of Dictation Software: A Dated Timeline45 data points
- Dictation App Features Compared: Offline, Privacy, AI968 data points
- How Much Time People Spend Writing and Typing at Work33 data points
- Voice Recording Privacy Settlements and Fines18 data points
- Dictation App Store Ratings: How Many Each App Has540 data points
- Dictation App Ratings: Average Stars on the App Store326 data points
- Interest in Speech Recognition: Wikipedia Page Views39 data points
- Most Downloaded Speech Recognition Models (Hugging Face)274 data points
- Open-Source Speech Recognition on GitHub: Stars255 data points
- Speech-to-Text SDK Downloads: PyPI and npm102 data points
- Dictation on Hacker News: Mentions per Month23 data points
- Mac vs Windows Market Share: Desktop OS Data by Month36 data points
- Dictation Apps on Google Play: Downloads and Ratings52 data points
- Voice Typing Chrome Extensions: Users and Ratings20 data points
- Dictation Apps in the App Store Charts, by Country166 data points
- Speech Recognition Research Papers per Year10 data points
- Open ASR Leaderboard: Speech Recognition Accuracy, Tracked56 data points
- Speech Recognition and Accents: 13 English Accents Tested42 data points
Read the overview: Speech Recognition: What It Is and How Well It Works