Capture controls
Pause and resume capture, read paused state at a glance, and control what capture-enabled builds may record.
Last updated: 2 April 2026
You decide when recording runs
You are always in control of what Overshow captures. When you pause, the app stops screen capture and any active meeting audio for Overshow’s indexing pipeline. Nothing new enters the local index while paused. there is no background “light” capture mode that contradicts the paused state.
When you resume, capture continues according to your settings. In the meeting-focused public beta this means meeting audio, which resumes only for meetings that are explicitly resumed or newly started; the public beta does not capture the screen. (In builds where screen capture is enabled, resume also restores it according to your monitor, exclusion, and category settings.)
How to pause and resume
You can pause or resume from:
- Keyboard shortcut. Use the shortcut configured in Settings (see Keyboard shortcuts for the current default).
- Menu bar. Use the menu bar extra on macOS.
Pick whichever fits the moment: a quick shortcut during a sensitive call, or the tray when you are already working near the menu bar.
Seeing paused state
The capture pill in the top-right of the app shows whether capture is paused, so you can confirm at a glance before continuing a conversation or sharing a screen.
Excluding applications and domains
Beyond global pause, builds with screen or app capture can exclude specific applications in Settings so their windows never contribute to the index. They can also exclude custom domains alongside the built-in categories, so pages on those sites are never recorded. Built-in denies also cover private browser windows, remote-desktop surfaces, and protected domains. The meeting-focused public beta keeps screen capture off, but these controls remain relevant for dogfood, evaluation, and future capture-enabled builds.
Category and custom domain exclusion changes apply as soon as you save. There is no need to relaunch for them to take effect.
Settings changes and relaunch
Changes to monitors or audio devices typically require an app relaunch to apply consistently across the capture stack. Category, custom domain, and allowed-app changes apply on save. If something still appears after a hardware change, restart Overshow once before assuming a fault.
Pause is immediate for Overshow’s capture path; it does not replace muting yourself in a meeting client or closing sensitive windows if your organisation expects that separately.