Local first
The blurs you draw and the pages you blurred stay on your device. The blur engine makes zero network calls and keeps working offline. Only your saved rules sync, and only when you choose to sign in.
About
The person and the principle behind Blurr.ing
Blurr.ing is an independent product, built and maintained by one developer, with one job: make sure nothing private is on screen when you screenshot, stream, or share it.
Updated August 2026
Why Blurr.ing exists
Every screen share, screenshot, and recording carries the same risk: the page you present holds more than the thing you meant to show. A salary column, a customer's email, an API key in a dashboard. The meeting apps cannot hide part of what you share, and editing blurs into screenshots after the fact is slow and easy to get wrong.
Blurr.ing puts the blur inside the page itself, before anything is captured or transmitted. Draw a box, click an element, or let keyword rules hide sensitive text wherever it appears. Whatever then screenshots, records, or shares the page sees only the frosted version.
Who builds it
Blurr.ing is built by Artyom Shimanski, an independent developer who also makes the tools listed at the bottom of this page, including Post Formatter and Excel Perfect. Small team, direct email, no support queue: write to [email protected] and the person who wrote the code reads it.
How it is built
Three rules the product keeps
No third-party trackers
The extension ships no third-party analytics or tracking scripts. It records anonymous product events, such as an install, against a random id and never against page content. The full detail is in the privacy policy, written to be read.
Honest limits
A browser extension cannot hide OS notifications or anything outside the page, and the security page says so in plain words. The pages on this site state what Blurr.ing cannot do next to what it can, because that is what makes the rest believable.
From the same team
Blurr.ing has siblings
The other tools built and run by the same developer.