ToolsHub4u

Dictate text with your browser's speech recognition

Speak and the transcript appears in the box, ready to edit, copy or download. Ten languages, a running word count, and a filler-word tally for the draft you just spoke.

  • Uses the browser's recogniser
  • Editable transcript
  • No ToolsHub4u upload
Ready Text & Writing
The browser may use a remote serviceIn Chrome and Edge, speech recognition can send audio to the browser vendor's service. The transcript stays on this page and is never sent to ToolsHub4u, but the audio is not necessarily processed on your device.
1Enter
2Adjust
3Copy result

Speech to Text

1

Dictation and transcript

Dictation

Not listening. Your browser will ask for microphone permission when you start.

Edit freely. The counters below use whatever is in this box.

Pick the language you will speak. The list comes from this page, not from the recogniser.

No text yet Live
2

Transcript

Nothing dictated yet. Press Start listening, or paste a transcript to count it.

Press Start listening, speak, and the words appear in the transcript box. The page uses the speech recognition built into your browser, so there is no account, no upload to ToolsHub4u and no recording kept after you close the tab.

The transcript is a draft, not a finished document. Recognition is good at ordinary sentences and weaker on names, numbers and specialist terms, and it punctuates by guessing where a sentence ended. The counters below the box help you judge the result: word count, sentence count, how long it takes to say and to read, and how many filler words survived.

Ten languages

The language list is fixed on the page, not read from your browser. It covers ten locales:

The ten recognition languages and their locale codes
LanguageCodeLanguageCode
English (United States)en-USPortuguese (Brazil)pt-BR
English (United Kingdom)en-GBItalian (Italy)it-IT
English (Australia)en-AUHindi (India)hi-IN
Spanish (Spain)es-ESJapanese (Japan)ja-JP
French (France)fr-FRGerman (Germany)de-DE

Pick the language you will speak, not the language of the page. An English recogniser listening to Spanish produces confident nonsense. If the browser's engine does not support a locale, the panel reports that the language is not supported and stops; try another one or paste the transcript instead.

How a dictation session works

Recognition runs continuously with interim results. That means the panel shows a phrase in grey while you are still saying it, then commits it to the transcript when the engine decides the phrase is final. Interim text is not added to the box until it is final, so a phrase that changes on screen is normal rather than a fault.

Final phrases are appended to the transcript with a space between them. The Keep the transcript when starting again option decides what happens at the start of the next session:

  • Ticked (the default). The existing text is trimmed and kept, and new speech is appended. Use this to dictate in several sittings.
  • Unticked. The box is cleared the moment you press Start listening, so each session starts empty.

Press Stop when you have finished. The phrase in progress may still arrive if the engine returns it as a final result, so wait a moment before editing. Press Start listening again to continue; recognition does not resume on its own.

Sessions also end by themselves. Chrome and Edge stop after a stretch of silence, after a network problem, or when the tab has been in the background for a while. The panel says "Stopped" and the transcript is kept, so press Start again rather than assuming the page has broken.

The error messages

Each recognition error and what it means
MessageWhat happenedWhat to do
Microphone access was blockedThe browser denied permissionAllow the microphone in site settings, then reload
No microphone was foundNone connected, or another app is using itConnect one and close the other app
The recognition service could not be reachedNetwork failureCheck the connection and try again
Nothing was heardSilence, or the microphone is too far awayMove closer and speak again
The browser refused the recognition servicePermission or policy blockCheck site permissions, or try another browser
That language is not supportedThe engine lacks that localeChoose another language or paste the text

The first session always asks for microphone permission, and that prompt comes from the browser rather than this page. If the Start button is disabled instead of showing an error, the browser does not expose the recognition API at all — Firefox is the usual case, and in-app browsers often behave the same way.

What the counters mean

Six statistics sit under the result, all calculated from the text in the box:

  • Words — hyphenated words count as separate words, so follow-up is two.
  • Characters — grapheme clusters, so one emoji is one character.
  • Sentences — split on full stops, question marks and exclamation marks. The splitter mishandles some abbreviations: a.m. and p.m. are cut after the first full stop, which adds a sentence.
  • Speaking time — at 130 words per minute, a comfortable presentation pace.
  • Reading time — at 200 words per minute.
  • Filler words — a fixed list: um, uh, erm, like, you know, sort of and kind of.

The filler count is deliberately crude. It matches like wherever it appears, so "it looks like rain" adds one, and it counts a multi-word filler such as "you know" once rather than twice. Read it as a hint about how spontaneous the transcript sounds, not as an error count.

A worked example

The first loaded sample is a three-sentence meeting note. It produces 33 words, 191 characters, 3 sentences, 15 seconds of speaking time, 10 seconds of reading time and no filler words.

Worked exampleTranscript: Notes from the planning meeting. The first milestone moves to the second week of March. Priya will send the revised schedule on Thursday, and Sam will check the budget before the next review.
Words: 33   Sentences: 3
Speaking: 15 sec   Reading: 10 sec   Fillers: 0

Two names appear in that transcript and both are the kind of word recognition gets wrong. Check every proper noun against what you meant to say before you send the note. A short filler test shows the other side of the count: Um, so I like think that, you know, it is sort of done. Uh, kind of. is 16 words, 2 sentences and 6 filler words — accurate about the ums, and one of those six is the ordinary verb "like".

Limits

  • No audio files. The page listens to the live microphone only. The upload button accepts .txt and loads a text transcript; it will not open an MP3 or a WAV.
  • No timestamps or speaker labels. You get one continuous block of text, so a two-person interview needs marking up by hand.
  • No punctuation guarantee. Some engines accept spoken commands such as "full stop" or "comma"; support varies by browser, so test it before relying on it. Quotation marks and paragraph breaks are safer added in the edit.
  • Ten locales only. A language outside the list cannot be selected even if the browser supports it.
  • Quality depends on the room. A headset in a quiet room beats a laptop microphone near a conversation every time.

Where the audio goes

ToolsHub4u does not receive your audio or your transcript. The recognition request is made by the browser, from this page, to whichever speech service the browser vendor uses: Chrome may send audio to Google, Edge to Microsoft, Safari to Apple. Whether that processing happens on a device or on a remote server is decided by the browser and the platform, and this page cannot tell you which you got.

If the audio must not leave the device, do not use browser dictation. The transcript itself is ordinary page text: it is not saved, synchronised or sent anywhere by this site, and closing the tab discards it. Copy or download it first.

Questions

Common questions

Short answers to what people ask before using this tool.

Does my audio leave my device?

It may. Chrome, Edge and Safari can send audio to their vendor's speech service. ToolsHub4u does not receive it, but browser dictation is not guaranteed to run locally.

Why is the Start button disabled?

Your browser does not expose the speech recognition API. Firefox and many in-app browsers lack it. Open the page in Chrome, Edge or Safari, or paste a transcript instead.

Why does dictation stop by itself?

Recognition sessions end after a stretch of silence, a network error or time with the tab in the background. Press Start listening again; the transcript is kept when the keep option is ticked.

Can I transcribe an audio file or a podcast?

Not here. The page uses the live microphone only. The upload button accepts a .txt transcript, not audio. Play the recording aloud into the microphone only if you accept the quality loss.

What does the keep option do?

Ticked, the existing transcript is kept and new speech is appended. Unticked, the box is cleared the moment you press Start listening, so each session starts empty.

How is the filler-word count calculated?

A fixed list: um, uh, erm, like, you know, sort of and kind of. "Like" is counted wherever it appears, including as an ordinary verb or preposition, so treat the figure as a rough signal.

Why is the sentence count too high?

The splitter mishandles some abbreviations. "a.m." and "p.m." are cut after the first full stop, so each one adds a sentence. Initials and "e.g." can do the same.

Is the transcript stored or uploaded?

No. It lives in the text box until you close or reload the page, and ToolsHub4u never receives it. Copy or download the transcript before you leave.