Why I built BlurSnap

Whatever line of work the article you just read is about, I'm almost certainly not in it. What is the same in all of them is the screen: plenty on it, and only some of it meant for the person you are sending the picture to.

My colleagues and I often need to take 10-15 screenshots a day. Show one part of the screen, then another, then a third — and every time it has to keep enough context to make sense, while showing nothing that shouldn't be there. Nothing belonging to a client, and nothing of my own.

There were two ways to do it, and both were bad. Paint over the extra by hand — slow, and starting from scratch every single time. Or slice the picture into several small pieces, after which it stops meaning anything: the other person sees a handful of fragments and can't tell how they fit together.

And it's nearly always done under time pressure. Grab it quickly, paint over here, strike out there, crop this off, send. And then it turns out you missed something — simply because we're people, not machines.

The worst part starts right there. It's already sent. And instead of working you're looking for whether you can still unsend it — in email, in a chat, in a messenger, anywhere — counting the minutes and hoping nobody has opened it yet.

I've watched colleagues fall into this, and people around me too. So I built a tool that works the other way round — for myself and for everyone who hits the same wall every day. Not "find and cover everything that shouldn't be there", but cover all of it at once and reveal only what you meant to show. Forgetting to cover something becomes impossible, because you aren't covering anything.

If something in these articles doesn't match how it actually works in your line of work, write to me — that's genuinely useful: support@blursnap.app

← Back to all articles