
Keyboard shortcuts can keep recording and text editing close to your normal writing workflow. VoicePad must be running, and AI actions need the local AI setup.
The Help Center documents Ctrl+Space as the Windows start/stop shortcut. Check the control shown in your build and test it with a short recording.
If the shortcut does nothing, confirm VoicePad is running, including in the system tray. Try the main mic button to check recording, then check whether another app uses the same combination.
Use these when the transcript contains text and Ollama is ready. If the keyboard action is unavailable or conflicts with another app, use the corresponding toolbar button.
The Windows Help Center lists F11 for fullscreen. Use your app’s window controls if the shortcut is not available in your version.
Use the mic or your working recording shortcut to stop and keep a note. Do not rely on an old guide’s Escape behaviour without checking your build; waiting for the finished transcript and saved history entry is the reliable way to confirm the note was kept.
Older shortcut lists include SubPad keys. SubPad remains described separately as planned meeting functionality, so those keys should not be treated as instructions for a released meeting workflow.
If your build offers shortcut capture, choose a combination that your other apps do not use. Avoid common editing and system shortcuts, and test the result before relying on it.