Speech to PDF Converter — dictate a document, with an honest account of where your voice goes
Speak, watch your words appear, then download as a PDF or text file. The document itself is built entirely on your device — the dictation step works a little differently, explained plainly below.
In Chrome and Edge, your voice audio is sent to Google's or Microsoft's servers to generate the transcript. This is how those browsers' built-in speech recognition works by default — it is not processed only on your device. The PDF and text file generation afterward genuinely is 100% local.
The dictation console
Choose a language, start speaking, then download.
Document generation is local; dictation typically isn't
Editing, generating, and downloading your PDF or text file never leaves your browser. Speech recognition uses your browser's own engine, which in Chrome and Edge sends audio to that vendor's servers.
Your transcribed text
Words: 0 | Chars: 0Recording
Your browser will ask for microphone permission. In Chrome/Edge, your audio then goes to that vendor's servers to produce the transcript.
Language
Actual accuracy and availability depend on your browser, not this page.
Actions
After dictating
Common next steps for refining your document.
Two very different privacy stories
One half of this tool is entirely private. The other depends on your browser, and deserves a straight answer instead of a blanket claim.
Genuinely 100% local
- The text area itself — anything you type or edit directly never touches speech recognition or any server.
- PDF and TXT generation — verified directly: a multi-page test document's pagination was checked word-for-word against an independent PDF reader, with nothing lost.
- Copying text and clearing the editor — plain browser operations, no network involved.
Depends on your browser
- Speech recognition in Chrome and Edge sends your voice audio to Google's or Microsoft's servers to produce a transcript — verified against current documentation, not assumed.
- Safari can do on-device recognition in some cases with permission and a language pack — genuinely more private, but not something this page can control or verify for you.
- Firefox doesn't support this feature by default, so dictation simply won't work there.
Three steps from voice to PDF
Choose a language, dictate, then download.
Choose a language and start
Pick your spoken language, click Start, and grant microphone access when your browser asks.
Speak, watch, edit
Your words appear as you speak. Click Stop whenever you're done, and edit the text directly — typed edits never involve speech recognition.
Review
Check the word and character counts, and read through before downloading.
Download
Save as a PDF or plain text file — this step happens entirely on your device.
What this tool is genuinely good for
And where you might want to type instead of speak.
| Use case | Why | Fit |
|---|---|---|
| Drafting an ordinary letter or note quickly | Faster than typing for many people, with real multi-page PDF output. | Strong fit |
| Brainstorming or a rough first draft | Speak freely, then edit and clean up the text before exporting. | Strong fit |
| Turning typed notes into a formatted PDF | You can skip dictation entirely and just type — generation is still fully local. | Strong fit |
| Dictating confidential or sensitive content | In Chrome/Edge, that audio goes to a third-party server to be transcribed. | Type instead |
| A fully offline, no-cloud dictation workflow | Not achievable with the standard Web Speech API this tool uses in most browsers. | Not a fit |
Where your voice actually goes
This varies by browser, which is exactly why a single blanket "it's all private" claim doesn't hold up.
| Browser | What happens to your audio |
|---|---|
| Chrome | Sent to Google's servers for processing by default. This is the standard behavior of the API this tool uses, not an edge case. |
| Edge | Sent to Microsoft's servers for processing, for the same underlying reason. |
| Safari | Can process on-device in some cases, once you grant permission and install the language pack — genuinely more private. |
| Firefox | Speech recognition isn't supported by default, so this tool's dictation feature simply won't work there. |
None of this affects the PDF or text file itself — that part is generated entirely in your browser regardless of which browser you're using, verified by checking a multi-page test document's content word-for-word against an independent PDF reader.
When something doesn't work as expected
What's actually happening, and the fastest way through it.
"API Not Supported"
Your browser doesn't implement speech recognition — this is expected in Firefox, which disables it by default.
Switch to Chrome, Edge, or Safari, or just type directly into the text area.
"Microphone access denied"
Your browser blocked the microphone permission request, or it was previously denied for this site.
Check your browser's site settings and allow microphone access, then click Start again.
"No speech detected"
Recognition timed out without hearing anything, often due to silence or a very quiet microphone.
Click Start again and speak clearly and promptly.
Transcription stopped on its own
Browsers automatically end a recognition session after a period of silence or a maximum duration.
Click Start again to continue — your existing text is preserved.
"API Not Supported"
Why: Browser doesn't implement it (e.g. Firefox).
Fix: Use Chrome/Edge/Safari, or type instead.
Mic access denied
Why: Permission blocked or previously denied.
Fix: Allow it in browser site settings.
No speech detected
Why: Silence or quiet microphone.
Fix: Start again, speak clearly.
Stopped on its own
Why: Browser session timeout.
Fix: Click Start again; text is kept.
Getting clean dictation
A few habits that make a real difference.
Set the language before you start
Recognition accuracy depends heavily on matching the selected language to what you actually speak.
Speak in a quiet space, at a natural pace
Background noise and rushed speech are the most common causes of poor transcription.
Keep sensitive dictation to Safari, or type it
If privacy matters for what you're writing, Safari's on-device option or direct typing avoid sending audio anywhere.
Review before downloading
Speech recognition isn't perfect — a quick read-through catches misheard words before they're in your PDF.
Speech to PDF FAQs
Start with the first question — it's the one that matters most.
Is my voice sent to a server?
For the speech recognition step, usually yes — and this is worth knowing plainly rather than assuming otherwise. This tool uses your browser's own built-in speech recognition, and in Chrome and Edge specifically, that means your audio is sent to Google's or Microsoft's servers to generate the transcript. It is not processed only on your device for most people. The PDF and text file generation, editing, and downloading afterward are entirely local and never touch any server.
Which browsers work best, and does that affect privacy?
Chrome and Edge have the most reliable speech recognition support, but both send audio to a cloud service to do it. Safari can do on-device recognition in some cases once you grant permission and install its language pack, which keeps audio on your device — a real privacy difference worth knowing about, not just a technical footnote. Firefox does not support this feature by default.
Should I dictate sensitive information with this tool?
Think of it the way you would any cloud dictation service, since that's what it typically is under the hood. If you wouldn't say it into your phone's voice assistant, consider typing it directly into the text area instead — typing never involves speech recognition at all.
Is the PDF generation itself private?
Yes, completely. Turning your transcript into a PDF or text file, and any edits you make in the text area, all happen locally in your browser with no server involved.