It is not on your plan
Loom limits its blur tool to Creators and Admins on Business, Business + AI and Enterprise plans. On the free Starter plan the button simply is not there, whatever you are recording.
Loom + Blurr.ing
Blur before Loom records, not after
A Loom gets forwarded, downloaded and paused on any frame, so the moment to hide the sensitive parts is before the pixels exist. Blurr.ing frosts them inside the page itself, which is why it works on every Loom plan and on the surfaces Loom’s own blur skips.
- Any Loom plan, including free
- Google Docs and Figma too
- Works with the desktop app
Updated August 2026
Quick answer
Blur the page before you hit record, and it stops mattering which Loom plan you are on. Loom’s own blur is limited to Business, Business + AI and Enterprise plans, runs only in its Chrome extension, and by Loom’s own docs cannot be applied after recording and does not work on Google Docs, Notion or Figma. Blurr.ing frosts the content inside the page itself, so Loom simply records pixels that are already safe; on canvas surfaces like Docs and Figma, draw a box over the region.
Why “Loom blur” fails people
Three reasons Loom’s blur button lets you down
None of these are bugs, and none of them are secrets: every one is stated in Loom’s own support documentation. They are simply the shape of a blur that belongs to the recorder instead of the page.
It is not built for that site
The tool works only on DOM-based sites. Loom’s docs name Google Docs, Notion and Figma as unsupported, and note that Microsoft OneDrive blocks it: exactly the surfaces walkthroughs live on.
It is not in the desktop app
Loom’s blur exists only inside its Chrome extension. Record with the Loom desktop app and there is no blur tool at all, on any plan, even for the browser windows in the recording.
All three limits come from Loom’s support page “Blur sensitive information”, checked August 2026. If Loom’s blur fits your plan and your site, it is a fine tool; this page is for everyone it leaves out.
How Blurr.ing helps
Frost the page itself, and every recorder is covered
When the blur is part of what the browser paints, Loom has nothing sensitive to record in the first place. No plan gate, no supported-sites list, no blur step inside Loom at all.
Any plan, any recorder
The blur lives in the page, not in the recorder. Loom on the free Starter plan, on Business, or the desktop app pointed at a Chrome window: all of them capture the same already-frosted pixels.
Covers Docs, Figma and Sheets
Canvas-rendered surfaces defeat element pickers, Loom’s and Blurr.ing’s alike. The drawn box does not care: it frosts a region of the page regardless of what renders beneath it.
Redact repeat offenders once
Customer names, emails, card numbers, API keys: Blur Text frosts them across the whole page from one rule, with 34 presets plus your own words combined with AND, OR and NOT.
Take two without re-blurring
With Premium, saved blurs re-apply before the page paints on every visit, so a re-record tomorrow starts exactly as safe as today’s take. Free blurs last for as long as you stay on the page.
Frost it past squinting
A viewer can pause a recording and study a frame for as long as they like. Premium dials any blur up to a heavy 20px frost, so a paused frame gives away nothing either.
Quiet edges around the page
Recording a whole window rather than a tab? Tab Privacy masks your tab titles and hides favicons, so the strip above your walkthrough stops naming your other work.
Step by step
Record a safe Loom in five steps
The blurring happens before Loom is even open, which is the point.
- 1
Open the page you are about to record
Pull up the app, document, or dashboard for the walkthrough before you open Loom, so you can see what needs hiding while nothing is being captured yet.
- 2
Blur the sensitive parts in the page
Press Ctrl + Shift + Y (Cmd + Shift + Y on Mac) to open the Blurr.ing toolbar, then draw a box over a region, click an element, or select a run of text. On Google Docs, Notion or Figma, use the drawn box: canvas surfaces give element pickers nothing to grab.
- 3
Add keywords for anything that repeats
Put recurring values, a customer’s name, emails, account numbers, into Blur Text so they are frosted wherever the walkthrough wanders. Free holds one saved rule at a time; Premium removes the limit.
- 4
Record with Loom as usual
Start the recording on any plan, from the extension or the desktop app. The page is already frosted, so the recording only ever contains safe pixels, with no blur step inside Loom at all.
- 5
Reload safely between takes
Free blurs survive navigation within an app and the back button, and clear when you refresh. With Premium, saved blurs are restored before the page first paints, so take two never opens on the real values.
Why is Loom’s blur not working?
Nearly always for one of three documented reasons: Loom’s blur is available only to Creators and Admins on Business, Business + AI and Enterprise plans, it runs only in the Chrome extension rather than the desktop app, and it works only on DOM-based sites, which rules out Google Docs, Notion and Figma. Check those three against your setup and the mystery usually dissolves. If the answer is “wrong plan”, “desktop app”, or “wrong site”, blurring in the page with Blurr.ing sidesteps all three at once, because the recorder no longer needs to understand the page it is capturing; it just films frosted pixels.
Can you blur a Loom video after recording it?
No: Loom’s docs state that information cannot be blurred after recording, only before or while recording, and Blurr.ing cannot blur recorded video either, because once pixels are captured they are outside any browser extension’s reach. The only genuine after-the-fact fix is a video editor, masking the region frame by frame, which is slow enough that most people re-record instead. That asymmetry is the whole argument for order of operations: a blur applied in the page costs seconds before the take and survives into every copy, while a leak discovered after publishing costs the take itself, plus everyone who already watched it.
How do you blur Google Docs in a Loom?
Draw a box over the region: Google Docs paints its text onto a canvas, so element pickers, Loom’s blur and Blurr.ing’s click-to-blur alike, have nothing to grab, but a drawn box frosts whatever sits beneath it regardless of how it is rendered. The same trick covers Figma boards and the Google Sheets grid. Drag the handles to size the box to a paragraph, a column, or a single cell, and it stays put while you talk over the document. Drawing boxes is free and unlimited; with Premium the box is saved and re-applied before the page paints, so the second take of the walkthrough starts already covered.
Keep exploring
More ways to blur before you record
The same in-page blurs hold for live calls, streams and screenshots, not just recordings.
FAQ
Loom and blur, answered
How do I blur sensitive information in a Loom recording for free?
Blur it in the page before you record. Loom’s own blur tool is not on the free Starter plan, but a free Blurr.ing install can draw a box over any region, blur any clicked element, and blur any selected run of text, without limits and without an account. Loom then records the frosted page like any other page, on every plan, because the blur is part of what the browser paints.
Which sites does Loom’s built-in blur not work on?
Loom’s support docs say the blur feature works only on DOM-based websites and name Google Docs, Notion and Figma as unsupported, while Microsoft OneDrive blocks the DOM manipulation it relies on. It also runs only in Loom’s Chrome extension, never in the desktop app. Blurr.ing covers those canvas-style surfaces with its drawn box, which frosts a region of the page no matter how the content underneath is rendered.
Can I blur part of a Loom after it is recorded?
Not inside Loom, and not with Blurr.ing either. Loom’s docs are explicit that information cannot be blurred after recording, only before or while recording, and a browser extension cannot reach captured video pixels at all. Once readable pixels are in the file, the only fix is masking them frame by frame in a video editor, which is why blurring before capture is the reliable order of operations.
Do the blurs survive reloads and re-records?
On the free plan a blur lasts while you stay on the page: it survives navigation inside single-page apps and the back button, and clears on a refresh, a new address, or a second tab. Premium saves your blurs and re-applies them before the page first paints on every later visit, so re-recording a walkthrough days later starts with every blur already in place and no flash of the real content.
Does this work when I record with the Loom desktop app?
For the browser part of the recording, yes. The blur is painted by Chrome inside the page, so the desktop app, like any recorder, simply captures frosted pixels wherever that page is on screen. What Blurr.ing cannot do is blur the rest of a desktop recording: other apps, terminals, notifications and your wallpaper are outside any browser extension’s reach, so keep them out of frame or record the browser window alone.