For content creators, course makers, developer advocates
Record tutorials without blurring anything in post
Hide API keys, emails and revenue numbers on the page before you hit record. No re-takes, no masking keyframes in your video editor.
Updated
Most screen recordings are made in real accounts. The dashboard you are explaining has a real Stripe balance, the settings page has a real API key, and the sidebar shows real customer emails. The usual fix is to record first and blur later: scrub through the timeline, draw a mask, track it as the page scrolls, export, and hope you didn’t miss a frame.
BlurSite flips the order. You blur the sensitive parts of the webpage itself, then record. Because the blur is part of the page, every recorder captures it: Loom, OBS, QuickTime, Camtasia, ScreenFlow, or the recorder built into Zoom.
What usually leaks in a tutorial
- API keys and tokens on developer settings pages, in .env previews, or in a dashboard’s “reveal key” field.
- Revenue and usage numbers on analytics, billing and admin dashboards.
- Customer names and emails in tables, inbox previews and support tools.
- Your own account details: the avatar menu with your email, billing addresses, and the last four digits of a card.
These are easy to miss when you are concentrating on the explanation. A single frame showing a live secret key is enough for someone to pause the video and copy it, and once a video is public you can’t take that frame back.
How to set up a recording with BlurSite
- Open the page you’re about to record and click the BlurSite icon.
- Run Smart Scan to find emails, card numbers and API keys on the page, and blur them in one click.
- Click any other element you want hidden, such as a revenue figure or a customer row. Use area blur to draw over a region, like a chart or a whole table.
- Turn on keep blur for the page so the same blurs come back when you reload or record a second take tomorrow.
- Switch on presentation mode so BlurSite’s own toolbar and notifications stay out of the recording, then hit record.
Why blur before recording beats blurring after
Blurring in an editor is a per-video cost that grows with every scroll and page change, because each one means another mask to place and track. Blurring the page is a one-time setup per page. Saved blurs carry over to the next video, so a weekly tutorial series stops costing editing time.
It also removes a failure mode. A missed frame in post-production is invisible until a viewer spots it. When the page itself is blurred, the sensitive value is never in the recording.
Good habits for creators
- Keep a demo account for tutorials where you can, and use BlurSite for the details a demo account can’t hide, like your own email in the header.
- Rotate any key that has appeared unblurred in a published video, even briefly.
- Close unrelated tabs, because tab titles and favicons show up in full-screen recordings.
- Re-check saved blurs after a site redesign. If the layout changes, an element blur may need to be placed again.
For a longer walkthrough, read blur before you record and the getting started guide.
Frequently asked questions
- Which screen recorders work with BlurSite?
- All of them. BlurSite changes the webpage itself, so Loom, OBS, QuickTime, Camtasia, ScreenFlow, Zoom’s recorder and any other tool capture the blurred page.
- Will the blur stay in place when I scroll during a recording?
- Yes. Element blurs follow the element they’re attached to, and an area blur stays in place on the page while you scroll.
- Can I reuse the same blurs for every video?
- Yes. Turn on keep blur for a page and BlurSite restores your blurs whenever you open that URL again.
Try it on your own screen
7-day free trial with every feature, no card needed. 5-day refund policy.