Troubleshooting

Start with the three checks

Almost every problem is one of three failures, and thirty seconds of looking tells you which. Hold your dictation key over any text field and watch.

• Does the mic pill appear? If not, the shortcut is not reaching VoiceSnap Pro — a permission, a conflict, or Pause dictation.
• Does the level meter move while you speak? If not, the microphone is the problem, not the app.
• Does the pill name the app you are looking at? If not, focus is the problem.

Nothing is typed at all

If the pill appeared and the meter moved, the audio was fine and the paste failed — and the pill usually says why. On macOS, the common cause is Accessibility: System Settings → Privacy & Security → Accessibility, with VoiceSnap Pro switched on, then restart VoiceSnap Pro. A tick that is already there but not working is the case for removing the entry with the minus button and adding it again.

If nothing pastes anywhere on macOS and Accessibility is definitely granted, an app has probably left Secure Input switched on after a password prompt. Locking and unlocking the screen clears it; if it comes back, quit the apps you had open when it started — a browser with a stuck password field and some VPN clients are the usual culprits.

On Windows, check whether the target window is running as administrator. Windows does not let a normal app paste into it, and the pill says so. Your words are in the dictation history, ready to paste once you are in a normal window.

• No mic pill at all: check Pause dictation, grant Input Monitoring on macOS, and restart VoiceSnap Pro.
• Pill appears, no meter movement: the wrong microphone in Settings → Language and microphone, a muted input, or Microphone permission not granted.
• Pill and meter fine, no text: Accessibility, Secure Input, or a window running as administrator.

The text lands in the wrong app or the wrong field

VoiceSnap Pro targets whatever had keyboard focus at the moment you pressed the key, and it holds that target for the whole dictation. If the text went somewhere unexpected, focus was somewhere unexpected when you started.

The common causes are clicking into another window while speaking, a notification banner or system dialog stealing focus mid-dictation, and a page that was scrolled but never clicked into so no field had a cursor at all. Watch the app name on the pill before you speak — that is exactly what it is for.

• Click into the destination field and see the cursor blinking before you press the key.
• Do not switch apps or click while a dictation is running. Press Escape and start again instead.
• In a multi-monitor setup, the focused window is not always the one under your mouse.
• If the text went somewhere you cannot undo it, the words are still in your dictation history — open it with Control + Option + H (Ctrl + Alt + H) and paste them where they belong.

The first word or two is missing

This is nearly always the microphone opening late rather than VoiceSnap Pro starting late. Some inputs — particularly Bluetooth headsets and Windows devices with driver-level enhancements — need a moment to switch into recording mode, and any speech during that moment is simply never captured.

The habit that fixes it costs nothing: press the key, wait for the pill to say Listening…, then speak. Half a second is enough.

• Windows: Settings → System → Sound → your input → turn off audio enhancements, which can ramp the gain over the first half-second.
• Switch from a Bluetooth headset to a wired one and see whether the problem disappears — it usually does.

Permissions stopped working after an OS update

macOS re-evaluates Accessibility and Input Monitoring grants when an app's signature or path changes, and a major system update can invalidate them even though the switch still looks on. The symptom is distinctive: everything worked yesterday, the toggles look correct today, and nothing pastes.

The fix is to remove and re-add rather than to toggle. In System Settings → Privacy & Security → Accessibility, select VoiceSnap Pro, click the minus button, then add it again with the plus button and pick it from Applications. Repeat in Input Monitoring, then restart VoiceSnap Pro. Restart the Mac if it still refuses.

• Moving VoiceSnap Pro.app to a different folder has the same effect as an update — the permission follows the path.
• Running it from a mounted disk image rather than Applications guarantees this problem, because the path changes every mount.
• Windows loses microphone access less often, but check Settings → Privacy & security → Microphone after a feature update.

The text is right in the history but wrong in the field

VoiceSnap Pro pastes a dictation in one go, so text that arrives garbled, doubled or cut short in one app is that app's handling of a paste, not a transcription problem. Compare the entry in your dictation history with what appeared: if the history has it right, transcription was fine.

Try the same dictation in a plain text editor to confirm the app is the variable. Remote-desktop sessions and terminals with unusual paste handling are the usual suspects; in those, paste from the history yourself, or dictate locally and paste across.

What to send support

If none of the above fixed it, email support with the details below, and there will usually be no need for a second round of questions. The version of VoiceSnap Pro you are running is at the bottom of Settings, under Updates.

• Your OS and its version, and the VoiceSnap Pro version.
• The exact app and window you were dictating into, and whether it was running as administrator or in a remote session.
• Which of the three checks failed: no pill, no meter, or the wrong app named.
• What appeared on screen versus what the dictation history recorded for the same dictation.
• Whether it happens everywhere or only in one app, and whether it started after an OS update.