Blur a screenshot online without uploading it

“Online” does not have to mean “on someone else’s disk.”

A lot of blur sites take the file, POST it, wait, then hand you a result. That is convenient. It is also a copy of your HR screenshot on a machine you do not run. If the page is free and covered in ads, ask what the upload is paying for. Storage is cheap. Your salary band in a PNG is not.

Can I blur a screenshot online without uploading it?

Yes. A page can decode the image in JavaScript, draw it on a canvas, let you paint, and trigger a download from the same tab. The pixels never need a server. That is a local editor that happens to live at a URL.

The other kind of “online” is a web app with a backend. You pick a file, the browser sends a large request, a worker blurs it, a URL comes back. Fine for a meme. Poor for a passport, a payroll export, or a customer ticket.

How can I tell if the image left my device?

Open DevTools. Network tab. Paste or pick the screenshot. If you see a large POST or PUT to an API, with a payload around the size of your PNG, it left the device. If the only traffic is the page’s own scripts and maybe a tiny analytics ping, the pixels likely stayed in RAM.

Filter the Network panel to Fetch/XHR if the waterfall is noisy. Look at request size, not just the domain. A 12 KB analytics hit is not your screenshot. A 1.8 MB POST named upload is.

BlurThis is the canvas kind: you work in the tab, you download a PNG, there is no login. The privacy page is the place we say we do not keep a database of images. You can still verify with the Network tab on your own machine. That habit transfers to every other “free blur” domain you will meet this year.

Why do some tools still upload?

OCR, auto-detect emails, batch folders, “AI unblur.” Those features almost always need a server and a GPU. For one Slack snip, they are optional. Drag a box yourself. Auto-detect that misses the URL bar is worse than no detect, because you trusted it.

Mobile browsers make this harder to inspect. You may not have DevTools on a phone. Prefer a tool that states, in plain language, that processing is local — then still avoid uploading passports to a site that will not say. If you only have a phone, a filled shape in the OS editor can be safer than a random APK that demands contacts.

After it stays local, did I still pick the wrong cover?

Local is about where the bytes went. It is not a promise that blur was the right tool. Short numbers survive a polite smear. A solid bar replaces pixels. Blur versus a black bar is the decision. Local blur on an OTP is still a weak OTP cover.

Format still matters. Download PNG. Chat apps may recompress. Starting from a mushy JPEG with ringing around a bar is how edges leak. PNG, not mushy JPEG.

Extensions and “privacy” uploaders

A Chrome extension that blurs the live page can be useful for a demo. It can also read every site you visit. For a single screenshot, edit the file. You do not need an extension with full-site access to cover one email in a PNG.

Desktop apps that “sync to the cloud for OCR” are the same upload with a nicer icon. Read the first-run dialog. If it wants an account to “save your projects,” that is a copy on their disk. Close it. Use the tab.

Private windows are not a substitute

A private window stops the browser from keeping history. It does not stop a POST. If the page uploads, the server still received the PNG. Incognito is not a local canvas. Check the Network tab in a normal window if that is easier, then use the tool you actually trust.

A short verification ritual

• Network tab: no large POST of the image.
• Zoom 100%: the secret is gone, not lightened.
• You are attaching the download, not the original from Recents.
• Headers, toasts, and the URL bar got a look.

Convenience is not the enemy. Unexamined convenience is. Blur the screenshot in a tab if that is faster than Paint. Just know whether the tab is a canvas or a drop box.