Runs in your browser
Voice
Speak instead of typing, and have replies read aloud. Recognition and speech use your browser's own APIs.
Where the audio goes
Audio path
Speaking
- You speak In place of typing the message.
- Your browser handles it Recognition is the browser's own API.
Chrome, Edge
Send the audio to Google to be recognised.
Off your machine
Firefox, Safari
No recognition at all. The interface says so.
Path ends
Listening
- A reply arrives The answer, as text.
- Your browser reads it aloud Speech is the browser's own API too.
Dashed rail: the audio leaves your machine
What this does not mean
Audio never reaching this server is not the same as audio staying on your machine.
Chrome and Edge send it to Google to be recognised, which is the honest cost of this path. Firefox and Safari have no recognition at all, and the interface says so rather than failing quietly.