Hide sensitive content
Cover, blur, or pixelate anything you don't want on screen — by hand, or with an on-device scan that finds it for you.
Real demos are full of things you’d rather not broadcast: an API key in a terminal, a customer’s email, a card number on a checkout page. Playback lets you mask any region of the recording so it’s hidden everywhere the video is seen — the preview, every export, and any frame an agent grabs over MCP.
Drawing a mask
Press the Mask button in the toolbar (the eye-with-a-slash, or ⇧⌘M), then drag a rectangle over the area you want to hide. A hint appears while you’re armed: “Drag over the area you want to hide · Esc to cancel.”
The new mask covers your region for three seconds from the playhead. Once it’s placed you can:
- Resize and move it on the preview using the eight handles around its edge.
- Retime it on the timeline — masks live in their own Masks lane as pills you can drag to move, or trim from either end.
Because the region is pinned to the underlying content, it stays locked over the right spot even as zooms pan and scale the frame.
Cover, blur, or pixelate
Select a mask and pick its Style in the inspector:
| Style | Effect |
|---|---|
| Cover | A solid opaque block. The only true redaction. |
| Blur | Softens the region. Adjustable Strength. |
| Pixelate | Mosaics the region. Adjustable Cell Size. |
Let Playback find it for you
The Mask button does two things at once: it arms the draw tool and kicks off an on-device scan for sensitive content. A chip reads “Scanning for sensitive content” while it runs.
The scan reads the text on screen and looks for:
- Emails, phone numbers, and card numbers
- Secrets — real credential shapes like AWS, GitHub, OpenAI/Anthropic, Stripe, and Slack keys, JWTs, and private-key blocks
(URLs and street addresses are noisier, so they’re off by default.) Everything runs entirely on your Mac — nothing is uploaded, and the matched text itself is never saved.
Reviewing suggestions
Anything the scan finds appears immediately as a suggested mask — a dashed, sparkle-marked pill labeled with its type (“Email?”, “Secret?”). Crucially, a suggestion is already redacting at full strength, so you’re protected the moment it’s found, not after you approve it.
A header pill shows how many are pending (“N suggested”). From there you can:
- Click it to step through each suggestion.
- Right-click for Confirm all or Dismiss all.
- Select one to see its inspector card — “Detected email” with a confidence score and a bulleted preview — then press Confirm Mask to keep it or Dismiss Suggestion to drop it.
Confirming just clears the “review me” flag; the mask keeps doing its job either way.
Where masks apply
Masks are baked in by the compositor, so a region you hide is hidden identically across the preview, every export format, and MCP frame grabs. A suggested mask redacts exactly as hard as a confirmed one — there’s no window where sensitive content leaks through.
Tips
- Scan first, then sweep up. Let the on-device scan catch the obvious keys and emails, then draw masks by hand for anything context-specific it can’t know about.
- Mask before you export, not after. Redaction travels with the project, so fix it once and every export is clean.
- Widen the time range if content moves. If the sensitive text scrolls or reappears, extend the mask’s pill on the timeline to cover the whole span.