How to Blur Sensitive Info in a Screen Recording (2026)
Blur sensitive info in screen recordings before you share: drag a blur box, keyframe it if content moves, export the redacted file. No upload required.
Say you scrub to a frame and find an API key in the corner. The fix is a per-frame blur baked into the exported video, not a static box over one screenshot. Record the tab, drag a blur rectangle, keyframe it if content scrolls, export. Nothing uploads.
Key takeaways
- A static blur box holds its position. The recorder defaults to 30 fps, so the target may shift many times across the clip. The blur must track it.
- The blur renders into the exported file, frame by frame, on your machine. No upload, no account, no telemetry.
- Keyframing lets the blur follow scrolling or moving content. Scroll-follow automates this for tab recordings that captured scroll data.
If the box stays put while the key scrolls to a new position, the “redacted” file still shows it.
How to Blur Sensitive Info in a Screen Recording
Five steps, in order:
- Record the tab, window, or screen locally. Tab recording uses
chrome.tabCaptureand skips the OS screen picker. - Open the timeline editor. Drag a blur rectangle over the sensitive area. The region appears on the preview and in a list under the timeline.
- If the target scrolls or moves, keyframe the blur so it follows.
- Set the region’s start time, end time, and strength (5 to 30 px).
- Export to WebM or MP4. The blur is baked into every frame of the encoded file.
| Method | What the file contains after export | Holds up when someone plays it? |
|---|---|---|
| Baked-in blur (local editor) | Blur rendered into the video frames; no separate track | Yes. There is no overlay layer to toggle off. |
| Overlay / black box | A rectangle drawn on top of the video as a separate track | No. A viewer could toggle off the overlay track. |
| Web-upload redaction | Raw file sent to a server, processed, returned | Not guaranteed to matter: the raw, unredacted file reaches a server before any blur is applied. |
The distinction that matters is where the blur lives relative to the pixels: painted into them, or sitting above them.
Why a One-Frame Blur Fails on Moving Content
A static rectangle sits at fixed pixel coordinates, while a recording at the default 30 fps holds 30 separate frames for every second of footage.
The fix is per-frame: the blur region needs a new position for every frame where the target moved. That is what keyframing does. You set the blur’s position at a start point, set it again at an end point, and the editor interpolates the path between them. Before the first keyframe, the blur holds its initial position. After the last, it holds the final position.
For tab recordings that captured scroll data, the editor can follow whole-page scroll automatically: the region tracks the page scroll offset so you do not keyframe every scroll event by hand. This requires a tab recording with scroll data. A window or screen recording does not carry scroll data, so keyframing is the only option there.
The blur itself samples real pixels from the frame and is composited over an opaque base. There is no edge bleed-through from the underlying content, and the effective radius is floored at roughly half the region’s short edge.
The recording step is the easy part: the getDisplayMedia web API prompts you to pick a display, window, or portion, and the resulting stream can be recorded. The redaction step requires a separate editor, which is the part most people skip and then regret at the moment they attach the file to an email.
Step 1: Record the Tab, Window, or Screen
The recording half of the workflow determines what the editor can do later. Three capture modes are available:
- This tab. Uses
chrome.tabCapture. The extension records the active tab’s visible area without opening the OS screen picker.The stream survives page navigations within the tab and stops when the tab closes. Only tabs where the extension has active-tab permission are usable. - Window. Uses
getDisplayMediato capture a specific window. - Screen. Uses
getDisplayMediato capture the full display.
Resolution options are 480p, 720p, and 1080p (default 1080p). Frame rate: 24, 30, or 60 fps (default 30). Bitrate: Low 4, Medium 10, or High 20 Mbps (default Medium). There is no imposed recording time limit and no watermark on the output.
Capture is blocked on chrome://, edge://, about: URLs, and the Chrome Web Store. The store build ships with no host permissions. An opt-in setting called “Record across sites” adds all-URL access if you need it.
The suggested shortcut to toggle recording is Alt+Shift+V, though you can rebind it. Chrome silently drops a key that collides with another extension, so if the shortcut does nothing, check your extension list.
Step 2: Place and Configure the Blur Region
Open the recording in the timeline editor. The editor supports trim, split, full undo and redo, and autosave.
Find the annotation toolbar. Drag a rectangle over the sensitive area. The rectangle appears on the preview and in a list under the timeline. You can place multiple independent regions, each with its own start and end time, both editable.
The strength slider ranges from 5 to 30 pixels. For card numbers, tokens, or names, use the upper half of the range.
Set the start and end times so the blur only covers the seconds where the sensitive content is visible. If the key was on screen for only part of the clip, the region does not need to run the full duration. This keeps the rest of the clip clean and unobstructed.
Step 3: Keyframe a Moving Target
If the content is static within the frame, the blur box from Step 2 is sufficient. If it scrolls, slides, or animates, keyframe the region.
Scrub the timeline to the moment the target first appears. Press the keyframe button at the playhead. Drag the region to the correct position. Scrub to the end of the target’s visible span. Add another keyframe at the new position. The editor interpolates the movement between keyframes with smooth transitions.
For whole-page scroll in a tab recording, enable the scroll-follow option. The region tracks the page scroll offset so it stays on the content without manual keyframes for every scroll event. Scroll-follow requires a tab recording that captured scroll data. It follows whole-page scroll only.
If the target jumps position (a dialog opens, a panel expands), add a keyframe at the jump. Interpolation between two keyframes assumes a smooth path, so a discrete jump needs its own key to avoid the blur sliding across the wrong area.
Step 4: Export the Redacted File
Choose your output format: WebM, MP4 (where the browser can encode it), or GIF (capped at 120 seconds). WebM and MP4 are the practical choices for a redacted clip you are attaching to a ticket or emailing to a client.
The export renders the blur locally, frame by frame, on your machine. The recording is not uploaded for processing. No account is required. No telemetry is sent. The file that leaves your disk is the redacted file.
After export, scrub through the output and check that the blur covers the sensitive content for the full duration it was visible. The standing habit is to verify the export before sharing. No tool can guarantee that every pixel is covered in every frame, and a quick pass through the timeline catches a region that ended one frame too early or a keyframe that missed the target’s actual path.
The live store version of the capture extension is 1.2.5.
Before You Hit Send
If the recording is for a support ticket, a client demo, or a bug report and it carries a credential, a customer name, or a card number, the order is fixed: redact, export, then share. The export is the last local step. Everything after it is outside your control.
If the clip is a screenshot rather than a recording, the screenshot editor has a separate pixelate brush for still images. The video blur tool does not apply to stills, and the pixelate brush does not apply to video. Pick the right editor for the file type.
If the sensitive content only appears briefly and you are not sure the blur region covers it, extend the region’s end time. The cost is a slightly longer blur over non-sensitive content. The alternative is a credential in a file that has been opened by someone else.
Frequently Asked Questions
Is the blur tool free?
Does the recording upload to a server for redaction?
Can I use the same blur for screenshots?
What formats can I export the redacted file in?
Don't miss the next release
Be first to know when we ship something new.
Related Articles
How to Blur or Redact a Screenshot in Chrome (2026)
Cropping or a black box can be undone; pixelating the pixels cannot. Blur faces, emails, and card numbers inside the shot before you post. (August 2026)
How to Record a Chrome Tab for Support in 2 Steps (2026)
Screen-record one Chrome tab in 2 steps. You get a local WebM or MP4 with audio, no picker, no watermark, no account. The file stays on your device.
Record a Chrome Tab With NO Screen Picker (2026)
Most recorders pop the OS screen-picker because they use getDisplayMedia. Tab recording via chrome.tabCapture skips it: pick the tab, recording starts.
How to Screen Record Chrome on Windows: 3 Ways (2026)
Chrome has no built-in screen recorder on Windows. Record a tab, window, or screen with audio. Built-in tools or a free extension, local export, no watermark.