Zahidul Islam

Founder, Safe Screen Share

Jun 25, 2026

6 min read

How to Blur Sensitive Information in Loom and OBS Recordings

You finish a six-minute Loom walking through your dashboard, hit publish, and then notice it: a customer's email sitting in the corner of frame for the whole demo. Now you're deciding whether to re-record or learn how to blur sensitive information in Loom and OBS after the fact. Both tools can hide things to a point, but neither was built to blur a live page for you, and that gap is where the work piles up.

The short version: for anything in a browser tab, blur it at the source before you record. Fixing it inside Loom or OBS afterward is slower, fiddlier, and easy to get wrong on content that moves. Here's what each tool can and can't do, and the workflow that saves you the re-record.

Blurring sensitive info in Loom

Loom is built for fast recording and sharing, not redaction. It does not blur sensitive data automatically, and it doesn't blur live as you record. What you get is editing after the fact: you can trim the start and end, and cut sections out of the middle.

Trimming helps when the sensitive thing only appears in one clean stretch you can remove. It falls apart the moment the data is on screen while you're talking through the part you actually need. Precise blurring of moving content, an inbox that keeps loading new previews or a figure that scrolls past, is not something Loom is designed to track.

So the practical fix with Loom is upstream: hide the sensitive data on the page before you press record. If it's never visible, there's nothing to trim, cut, or apologize for later.

Blurring sensitive info in OBS

OBS gives you more control than Loom and more rope to tangle yourself in. You can blur a region two common ways: add a blur filter to a source, or drop a separate layer (a blurred duplicate or a solid shape) on top of the area you want to cover. For a static spot that never moves, like a fixed sidebar, this holds up.

The trouble starts with anything that moves. A blur layer is pinned to screen coordinates, not to the content underneath it. Scroll the page, resize a panel, or let a single-page app re-render, and your carefully placed cover is now blurring empty space while the real data sits exposed beside it. Keeping it aligned through a live demo means babysitting a box instead of presenting.

For web content, the simpler path is the same as Loom's: blur it in the browser before OBS ever captures the frame. OBS then records a page that's already clean, and you never touch a filter.

Why blurring at the source wins

For anything in a browser tab, blurring in the page, before capture, beats fixing it in Loom or OBS afterward. Three reasons it's more reliable:

• It tracks the content, not the pixels. A blur that lives on the page element stays on that element when you scroll, resize, or navigate. A blur pinned to screen coordinates doesn't.
• It works live and recorded. The same hidden data protects you on a Zoom call, in a Loom, and in an OBS stream, because the page itself is clean. You set it once.
• There's no post-production. Nothing to trim, no timeline to scrub, no filter to realign frame by frame. You hit record on a page that's already safe.

This is the same point we make in is screen sharing safe: the recording captures whatever is on your screen, so the place to fix exposure is the screen, before it gets recorded.

How to blur web content before you record

A browser blur extension hides sensitive web content before Loom or OBS captures it. Safe Screen Share runs in the tab itself, so the blur is part of what gets recorded:

• SmartBlur auto-detects emails, phone numbers, credit cards, and developer keys (Stripe, AWS, GitHub, OpenAI, and more), plus whole inboxes and sidebars in apps like Gmail, Slack, and Notion. You don't have to find each one by hand before recording.
• The blur persists across scrolling, page reloads, and single-page-app navigation, so it doesn't fall off mid-recording the way a pinned overlay does.
• It runs on-device. Nothing is captured, uploaded, or stored. The blur happens locally in your browser.

It works across Chrome, Edge, Brave, Opera, Arc, and Vivaldi, and it's a one-time purchase rather than a subscription. You can add it to your browser or check the pricing (Pro is $49, Unlimited is $59, both lifetime).

A clean recording workflow

Whether you're capturing with Loom or OBS, the order is the same. Prepare the page, then record:

• Open the tab you're going to record and let the blur settle on emails, keys, and customer data.
• Scroll through the parts you'll show to confirm the blur holds and nothing slips through.
• Silence notifications so nothing pops into frame mid-take.
• Start recording in Loom or OBS on a page that's already clean.

For a fuller version of this, including notifications, tabs, and the rest of the checklist, see how to record a tutorial without leaking personal information. And if you want to compare the tools built for on-page blur, we keep a list of the best blur Chrome extensions.

Loom and OBS are good at recording. Keeping your private data out of the frame is a job for the browser, before either one starts capturing.

Frequently asked questions