Voice commands

What counts as a command

A voice command is a short phrase VoiceSnap Pro acts on rather than transcribes. Commands are recognised at phrase boundaries — after a natural break in speech — so an ordinary sentence containing the same words is left alone.

Editing commands apply to the text of the current dictation only. VoiceSnap Pro never edits what was already in the field before you started, and it never touches text from an earlier dictation.

The command list

These are the commands available in every language VoiceSnap Pro supports. In non-English languages you say the local equivalent, not the English phrase.

• new line — break to the next line.
• new paragraph — blank line, new paragraph, next word capitalised.
• scratch that — delete the last phrase you spoke.
• delete last word — delete one word.
• undo that — remove everything this dictation has inserted so far.
• cap that — capitalise the previous word.
• all caps that — uppercase the previous phrase.
• lowercase that — lowercase the previous phrase.
• camel case that / snake case that / kebab case that — reshape the previous phrase as an identifier.
• bullet point — start a list item.
• numbered item — start or continue a numbered list.
• quote that — wrap the previous phrase in quotation marks.
• bold that / italic that — wrap the previous phrase in markdown asterisks or underscores. Off by default.
• stop dictation — end the dictation and insert what you have so far. Useful in toggle mode when your hands are busy.

Fixing what you just said

“Scratch that” is the one to learn. It removes the last phrase — roughly the last thing you said between two pauses — so you can correct a wrong word without reaching for the mouse. Say it twice to remove two phrases.

“Undo that” is the bigger hammer: it removes everything the current dictation has inserted, leaving the field exactly as it was when you pressed the key. After the dictation has ended, use your app's own undo instead.

Lists and structure

“Bullet point” starts a line with a dash and a space; in an editor that already renders markdown, that becomes a real bullet. “Numbered item” tracks the count for you, so three of them in a row produce 1., 2., 3. rather than three 1s.

In an app with its own list handling — Notion, Google Docs, a rich-text mail composer — the app usually converts the dash into its native bullet as soon as it is typed, which is the behaviour you want. In a plain text field you get plain markdown.

Case commands for code and identifiers

Dictating into an editor means saying things a prose model would happily turn into a sentence. The case commands solve that: say “user profile card camel case that” to get userProfileCard, “snake case that” for user_profile_card, or “kebab case that” for user-profile-card.

Pair them with custom vocabulary for the library and API names you use daily, so “use effect” stops arriving as two words.

Turning commands off, or saying one out loud

Every command has its own switch in Settings → Formatting, and the whole set can be disabled at once. Writers who dictate about dictation, or anyone whose vocabulary genuinely contains “bullet point”, will want that.

Without turning anything off, the “literal” prefix escapes a single instance: “literal scratch that” writes the words instead of deleting anything.

The commands VoiceSnap Pro does not have

There is no “press enter”, no “send”, no “click that”, and no command that opens or closes an application. That is a deliberate limit rather than a missing feature.

A dictation app that can press Send will eventually press Send on half a sentence, in the wrong channel, because a colleague said something that sounded like the trigger. VoiceSnap Pro writes text and stops there; you stay in charge of the button that makes it public.