How to blur sensitive information after recording in Loom
You recorded a screen video in Loom, watched it back, and spotted a problem: a password, an API key, a customer’s email, or some other piece of sensitive information is sitting right there in the frame. The recording is otherwise perfect and you would rather not redo it. You just want to blur that one region, now, after the fact. That is a reasonable thing to want, especially for support, sales, and onboarding videos that go to people outside your company.
This guide covers exactly what Loom supports today for blurring sensitive content, what is missing, the workarounds people use, and how to blur a region after recording in Tight Studio.
What Loom supports today
Loom does have a blur tool. The catch is when and how it works. Loom’s blur is something you set up before or during a recording, not after it. You select the on-page elements you want hidden, and Loom keeps that content out of the capture from that point on - the sensitive data is never recorded in the first place. That is a genuinely privacy-respecting design. It just does not help you with a finished video.
According to Loom’s own documentation on blurring sensitive information, as of May 2026 the blur tool:
- Cannot blur a recording after it is finished - only before or while recording
- Works by selecting DOM elements on a web page, not by drawing a freeform region over the video
- Pauses the recording while you pick what to blur, so the hidden content is never captured
- Works only through Loom’s Chrome extension - it is not available in the Loom desktop app
- Works only on standard DOM websites - it does not work on Google Docs, Notion, or Figma, whose canvases are not the kind of DOM Loom can target
- Has no automatic sensitive-data or PII detection - you choose every element by hand
- Is available on Business, Business + AI, and Enterprise plans only (not the free Starter plan), per Loom’s pricing
A quick clarification, because the two get mixed up: this is different from Loom’s camera-background blur, which softens the background behind your webcam bubble. That is a separate, unrelated feature. The blur discussed here is screen-content redaction.
The official feature request: Loom users have asked for the ability to blur a recording after the fact. Loom’s public Atlassian feedback portal has request LOOM-18, “Blur after recording,” at status “Gathering Interest” (3 votes, 9 watchers, created June 2025): jira.atlassian.com/browse/LOOM-18. Loom has acknowledged the request but has not built post-recording blur as of May 2026.
Workarounds in Loom
If you are committed to Loom, here are the options. None of them let you blur a region of an existing Loom recording inside Loom.
Workaround 1: Plan the blur before you record
Open the Chrome extension and select the DOM elements you want hidden before you start, so they are never captured. This is the intended workflow and it works well - if you can anticipate every sensitive element in advance, and the content is a standard web page.
- Works for: web pages where you know exactly what is sensitive ahead of time
- Does not work for: desktop apps, Google Docs, Notion, Figma, anything outside Chrome, or anything you only realize was sensitive after watching the recording
Workaround 2: Re-record with the sensitive area hidden
If you only notice the leak afterward, the practical fix inside Loom is to record again - this time logged into a test account, with the panel collapsed, or with the data masked at the source before you hit record.
- Works for: short recordings that are cheap to redo
- Does not work for: long walkthroughs, anything hard to reproduce, or recordings where the moment has passed
Workaround 3: Export and redact in another tool
Download the recording as MP4, import it into a video editor that supports a blur or cover-up mask - Camtasia, ScreenFlow, Final Cut, Premiere Pro, or DaVinci Resolve - and add the blur there.
- Works for: people who own a separate editor and have time to redo the redaction by hand
- Does not work for: quick turnaround, and anyone who chose Loom specifically so they would not need a second editor
The two-tool workflow defeats much of the reason people use Loom, and the pre-record options only help if you saw the problem coming. For fixing a leak you noticed after recording, the practical answer is a tool that can mask a region of the finished video.
How to blur sensitive information in Tight Studio
Tight Studio is the all-in-one screen recorder for tutorials, demos, course videos, and social cuts. It lets you blur or cover a region after recording, on the finished video, regardless of what was captured - a desktop app, a web page, a Google Doc, a terminal, anything on screen, not just DOM elements.
Add a mask over the sensitive region
Open the recording in the Tight Studio editor and add a Mask. A box appears on the video preview - drag and resize it so it sits exactly over the password, key, email, or whatever needs to be hidden. You are drawing the region freehand on the actual video, so it works on any content, not only web pages.
Choose blur or a solid cover-up
A mask can be a blur with three strengths (Default, Strong, Strongest), a solid color block, or a custom image overlay - whichever makes the redaction unambiguous for the content you are hiding.
Set when the mask is visible
Each mask has its own start time and end time, so it only covers the frames where the sensitive data is actually on screen and disappears the rest of the time. You can add multiple masks to one recording, each independently timed - useful when different sensitive values appear at different points in a walkthrough.
All of this is in the free download, and it does not require a browser extension.
Comparing blur support
| Capability | Loom | Tight Studio |
|---|---|---|
| Blur after a recording is finished | No | Yes |
| Freeform region you draw over the video | No (DOM elements only) | Yes |
| Works on desktop apps and non-DOM content (Docs, Notion, Figma, terminals) | No | Yes |
| Works without a Chrome extension | No | Yes |
| Time-ranged mask (visible only when needed) | No | Yes |
| Solid-block or image cover-up option | No | Yes |
| Available on the free plan | No (Business+ only) | Yes |
Frequently asked questions
Can I blur something in a Loom video after recording?
Not inside Loom. As of May 2026, Loom’s blur must be applied before or during recording, by selecting page elements in the Chrome extension so they are never captured. There is no way to blur a region of a recording that is already finished. The request for this (LOOM-18, “Blur after recording”) is at “Gathering Interest” on Loom’s public feedback portal.
Does Loom blur work in the desktop app?
No. Loom’s blur tool is available only through the Loom Chrome extension. It does not work in the Loom desktop app, per Loom’s own documentation.
Why can’t I blur a Google Doc or Notion page in Loom?
Loom’s blur works by selecting standard DOM elements on a web page. Google Docs, Notion, and Figma render their content in canvases that are not the kind of DOM Loom can target, so the blur tool does not work on them.
Will Loom add blur after recording?
Loom has acknowledged the request - it is tracked publicly as LOOM-18, “Blur after recording,” at “Gathering Interest” status (created June 2025). There is no published timeline. Until it ships, Loom can only prevent sensitive content from being captured, not redact it afterward.
Can I move my existing Loom recording into a tool that blurs after recording?
Yes. Export your Loom recording as MP4, open it in Tight Studio, and add a blur or cover-up mask over the sensitive region with its own start and end time. You do not have to re-record.
How much does Tight Studio cost?
Tight Studio has a free tier with limits on Add Clip and shareable videos, plus a Pro plan for unlimited recording, exporting, and sharing. Masks are available on the free download. See tight.studio for the latest pricing.