A voice keyboard that keeps your voice on your phone.
Install Yaps on Android for offline dictation, a familiar full-size keyboard, and no screen capture. Scan the QR on desktop, or tap the Play badge on mobile.
Most voice command guides are full of gimmicks nobody uses. This one focuses on the voice commands that actually matter - the ones that save you minutes every day and hours every week.

Voice commands have a reputation problem. People hear "voice commands" and think of asking Siri what the weather is. Or telling Alexa to play a song. Party tricks. Convenience features that save three seconds at most.
That is not what we are talking about here.
We are talking about voice commands that replace multi-step workflows you do dozens of times a day. The kind that turn a 30-second sequence of clicking, typing, and navigating into a single spoken sentence. The kind that add up to real, measurable time savings by the end of the week.
Not hypothetical time savings. Real ones.
Before we get into specific commands, consider this: an action that takes 30 seconds and happens 10 times a day costs you 5 minutes. Every day. That is 25 minutes a week. Over 20 hours a year.
Now consider that most knowledge workers perform dozens of these small, repetitive actions daily. Opening the same apps. Navigating to the same folders. Creating the same types of events. Sending the same kinds of messages.
Voice commands compress these sequences into a single spoken instruction. The savings per action are small. The savings over time are not.
Here are the voice commands that make the biggest difference in everyday Mac use - organized by what they replace, not by what they do.
The old way: Open Calendar. Navigate to the right date. Click the right time slot. Type the event title. Set the duration. Add notes. Save.
The voice way: "Create a meeting with Sarah tomorrow at 2 PM for one hour about the Q3 budget review."
One sentence. The event is created with the right title, time, duration, and notes. No clicking, no navigating, no typing.
This works because Yaps voice commands understand natural time expressions. "Tomorrow at 2," "next Tuesday morning," "this Friday at noon" - you say it the way you would say it to a person, and the command parses it correctly.
Useful calendar commands:
The old way: Open Reminders. Choose a list. Type the reminder. Set a date. Set a time. Save.
The voice way: "Remind me to follow up with the design team on Monday morning."
Reminders are one of the highest-value voice commands because they happen at moments when you cannot easily type. You are in a conversation. You are walking between meetings. You are cooking dinner and remember something about work.
The friction of opening an app and typing kills most reminders before they are created. A voice command captures them instantly.
Useful reminder commands:
The old way: Cmd+Space, type the app name, press Enter. Or click through your dock. Or find the window in Mission Control.
The voice way: "Open Notes." "Show Slack." "Switch to Safari."
App launching by voice saves a few seconds per switch. That does not sound like much until you realize how often you switch apps. Research suggests knowledge workers switch applications over 1,000 times per day. Even saving two seconds per switch on a fraction of those adds up fast.
Window management is where voice commands get more interesting:
Quick system adjustments that normally require navigating menus or System Settings:
These are small. But they are the kind of interruptions that break your train of thought because they require you to think about which menu or key combination to use. A voice command keeps your mind on your work.
The real time savings come when you create voice commands tailored to your specific workflows. This is where voice commands go from "nice to have" to "how did I work without this."
macOS Shortcuts is Apple's automation framework, and it is surprisingly capable. You can create Shortcuts that chain together multiple actions - opening apps, creating files, sending messages, adjusting settings - and trigger them with a single voice command.
Here is an example: a "Start my day" routine.
What it does:
How you trigger it: "Start my day."
One sentence replaces five separate app launches and a settings change. And because it runs the same sequence every morning, you never forget a step.
The beauty of custom voice commands is that they adapt to how you actually work. Here are examples for different roles:
Writers and Content Creators:
Designers:
Project Managers:
Developers:
For more developer-specific voice workflows, including dictating commit messages and PR descriptions, see our guide to voice input for developers.
Do not try to automate everything at once. Pick the one workflow you do most often - the one that involves the most repetitive clicking and typing - and create a voice command for it. Use it for a week. Then add another. Building the habit gradually is more effective than trying to change everything overnight.
Vague commands produce vague results. "Do the thing" is not a good voice command. "Create a new Markdown file in my blog drafts folder called outline" is. The more specific your command, the more reliably it will do exactly what you want.
You do not need to speak like a robot. Good voice command systems understand natural phrasing. "Set an alarm for 7 AM" and "Wake me up at 7" should both work. Speak the way you would speak to a helpful assistant sitting next to you.
Every voice command system has a set of built-in commands that cover the most common actions. Learn these before building custom ones. They are already tested, already reliable, and cover 80% of what most people need.
Single commands that do one thing are reliable. But sometimes the real value is in chaining - "Start my meeting prep" that opens Calendar, Notes, and the relevant project folder in one shot. Use macOS Shortcuts for chains and trigger them with a single voice command.
Do not try voice commands for the first time during a critical moment. Practice during normal work. Get comfortable with the cadence - how to phrase things, how to pause, how to correct a misheard command. Once it feels natural, it becomes fast.
There is an important distinction between voice commands that run locally and those that require cloud processing.
Cloud-based voice assistants - Siri (in default mode), Alexa, Google Assistant - send your audio to a server. This means every command you speak is transmitted, processed remotely, and potentially stored. Even if you are just saying "set a timer," the audio of your voice goes somewhere.
Yaps voice commands use a hybrid approach. Calendar and Reminders integration uses local macOS APIs, so your events and reminders are created directly on your Mac. However, voice commands use a cloud AI model for text generation, which requires an internet connection. This means your spoken command is processed locally for speech recognition, but the intent parsing and text generation step uses a cloud AI model.
This matters for privacy-conscious users: while Yaps does not send your raw audio to the cloud, the text of your voice command is sent to a cloud AI service for processing. Calendar and Reminders actions are executed locally via macOS APIs.
For workflows that must be fully offline, use dictation, voice notes, and offline TTS - these run entirely on-device. For a deeper look at why offline matters for dictation, see our complete guide to offline dictation on Mac.
Voice commands reach their full potential when combined with other voice features - dictation, voice notes, and text-to-speech - to create a workflow that minimizes keyboard and mouse use.
Imagine this sequence:
That entire workflow - drafting, saving, reviewing, noting revisions - happens without touching the keyboard more than necessary. For anyone managing RSI or repetitive strain, this kind of hands-free workflow is not a luxury. It is how you keep working without making an injury worse.
Install Yaps on Android for offline dictation, a familiar full-size keyboard, and no screen capture. Scan the QR on desktop, or tap the Play badge on mobile.
Yes, you can perform most daily Mac tasks using voice commands, including launching apps, managing windows, creating calendar events, setting reminders, adjusting system settings, and running custom automations through macOS Shortcuts. However, tasks that require precise visual interaction - like pixel-level design work or complex spreadsheet editing - still benefit from a mouse or trackpad. For most knowledge work, voice commands can handle 70 to 80 percent of routine actions.
Mac voice commands in 2026 cover system controls (brightness, volume, Do Not Disturb), app management (launch, switch, close, arrange windows), productivity actions (create calendar events, set reminders, search files), and custom automations via macOS Shortcuts. Built-in commands handle the most common actions, while custom commands let you trigger multi-step workflows with a single phrase. The full range depends on which voice command tool you use - on-device options like Yaps support natural language phrasing without requiring rigid command syntax.
Yes, Yaps integrates with macOS Shortcuts, which means you can trigger any Shortcut with a voice command. This lets you chain multiple actions - opening specific apps, creating files, adjusting settings, sending messages - into a single spoken instruction. You build the Shortcut once in the Shortcuts app, assign a voice trigger, and use it from that point forward. Any Shortcut that runs on your Mac can be voice-activated.
Yaps voice commands require an internet connection because they use a cloud AI model for text generation and intent parsing. Speech recognition itself happens on-device, but the command processing step sends text to a cloud AI service. Calendar and Reminders actions are executed via local macOS APIs. For fully offline voice work, use dictation, voice notes, and offline TTS - these run entirely on your Mac without internet.
Modern on-device speech recognition on Apple Silicon achieves accuracy rates within a few percentage points of the best cloud-based systems for standard commands. Accuracy improves when you speak clearly and use specific, unambiguous phrasing. Natural language understanding has advanced significantly - you can say "create a meeting with Sarah tomorrow at 2 PM" rather than memorizing rigid command formats. Background noise and strong accents can reduce accuracy, so a quiet environment and a good microphone help.
Voice commands in Yaps process speech recognition on-device, so your raw audio never leaves your Mac. However, the text of your command is sent to a cloud AI service for intent parsing and text generation. Calendar and Reminders actions are executed via local macOS APIs. For professionals handling highly sensitive information, dictation (which is fully on-device) is the more privacy-appropriate choice. Voice commands are best suited for routine productivity tasks where the convenience outweighs the cloud processing of command text.
Most people become comfortable with basic voice commands within a few days of regular use. Built-in commands for launching apps, setting reminders, and adjusting system settings feel natural almost immediately because they use conversational phrasing. Custom workflows and multi-step automations take a bit longer to set up - usually an afternoon to configure - but become second nature within a week or two of daily use. The key is to start with three or four commands you use frequently and build from there.
Here is a practical way to start using voice commands this week:
Day 1: Learn three built-in commands - one for launching an app, one for creating a reminder, one for a system setting. Use them at least twice each.
Day 2-3: Add calendar commands. Create a meeting, check your schedule, and reschedule something - all by voice.
Day 4-5: Identify one repetitive workflow and build a custom voice command for it using macOS Shortcuts.
Week 2: Expand your custom commands. Add voice commands for your most common multi-step actions.
The awkwardness fades fast. Within a week, the commands that felt unnatural start to feel obvious. Within a month, reaching for the mouse to do something you can say feels like the strange choice.
Voice commands are not about talking to your computer for the novelty of it. They are about removing friction from the things you do most often - a core principle of any voice-driven productivity workflow. Every click you replace with a word, every navigation you skip with a sentence, every multi-step workflow you compress into a phrase - that is time you get back.
Not someday. Today.