Dictation in a password field is possible, but not all dictation apps support it. The reason is macOS security. Password fields are protected by the operating system to prevent malicious automation, and that protection blocks most input methods—including some dictation approaches. Coii VoiceInput works in password fields because it uses synthetic paste, which the system allows.
Why password fields block dictation
Password fields in macOS are restricted from most forms of programmatic input. The reasoning is sound: if a malicious script could type directly into a password field, it could steal passwords. To prevent that, macOS only allows certain trusted methods to fill password fields.
This blocks dictation apps that rely on keyboard event synthesis—the method where the app simulates key presses to insert text. A password field sees simulated key presses as a potential threat and silently rejects them. The result is that you dictate, the app sends the key presses, and nothing appears in the field.
The restrictions are strict. Many popular dictation tools, including some enterprise solutions, cannot work in password fields for this exact reason. The limitation is not the dictation part—capturing and transcribing audio works fine—but the delivery: getting the text into a field the OS has locked down against automation.
How Coii VoiceInput works in password fields
Coii VoiceInput uses synthetic paste, which is a different input method. Instead of simulating key presses, it places the transcribed text on the clipboard and then simulates a paste operation—⌘V. Most password fields allow paste, because pasting is a normal user action and is indistinguishable from a person manually pasting text from the clipboard.
This is the accessibility API method mentioned in the product description. Where the API works, pasting is allowed. Where the API does not work for some reason, the app falls back to key synthesis, which may not work in sensitive fields.
In password fields, paste wins. Your transcribed password is placed on the clipboard, pasted into the field, and your clipboard is restored to whatever it contained before—all in the fraction of a second after you release the key.
When password field dictation fails
Dictation in a password field can fail if the app does not support paste input or if the password field itself is unusually restricted. Some older or custom applications implement their own password input that bypasses the standard macOS security model, and those may not accept pasted text either.
If you find that dictation does not work in a specific password field, the problem is almost certainly the field itself, not Coii VoiceInput. Test dictation in a normal text field to confirm the app is working; if it works there but not in the password field, the field is blocking input methods the app uses.
Best practice for password dictation
Type longer passwords normally; dictate passphrases. A password is often a jumble of characters designed to be hard to guess, and dictating those is error-prone—you would have to spell every non-word character. A passphrase is a sentence or series of words, and those dictate cleanly and are often as strong as passwords.
If you dictate into a password field, be aware of your surroundings. The password is on your clipboard for a moment and the app restores it, but the text is still visible in the app's history. For truly sensitive passwords, typing remains the safest approach.
The broader accessibility question
Dictation in password fields is part of accessibility — the ability to type without hands. If you cannot use a keyboard due to injury or disability, voice input for passwords is necessary. Coii VoiceInput's support for password fields is an accessibility feature as much as a convenience feature.