Guide
One sentence carries this page: the editing needs no connection at all, but loading the page does — so open it before you lose signal, and from then on treat the open tab as the only copy of your work.
Two questions hiding inside “does it work offline?”
Separate them and both become answerable. Does the tool need a network while it runs? No. Can you open it without a network? Not dependably. Almost every disappointment with browser-based tools in a dead spot comes from assuming that a yes to the first implies a yes to the second.
The reason they come apart is that a web page is delivered once and then lives in your tab. Delivery is a network event. What happens afterwards depends entirely on what the page asks for next. A tool that sends your file somewhere to be processed asks for something on every single action, so it dies the instant the connection does. A tool that does the work in the page asks for nothing further, so it is as available as the tab it sits in. The distinction is not a matter of degree or of a good connection versus a bad one. It is whether there is a request in the path at all.
That makes the useful mental model less like an app and more like a document you have already been handed. Getting hold of it requires a trip. Reading and writing on it afterwards does not. Losing it before you are finished means another trip to get another copy — and that is exactly where the risk sits.
What this page requests, and what it does not
Worth being specific, because the claim is checkable rather than a matter of taking anyone's word. The editor's code holds no fetch call, no XMLHttpRequest, no WebSocket and no address of any kind. The path your image takes is: the file input or the clipboard handler gives the browser your file, the browser decodes it into an image, the image is drawn onto a canvas created at its exact pixel dimensions, and from then on every Black Box, Blur or Pixelate operation is arithmetic on those pixels. Undo restores a stored copy of the pixels. Clear repaints the original that is still held in memory. Download PNG asks the canvas for PNG data, places that data in a link, and clicks it. There is no step in that chain where anything is asked of anything outside your browser.
The page does load three things from elsewhere, and none of them is the tool. A web font, so the type looks the way it is meant to. An analytics tag. Advertising. All three are loaded in a way that does not hold up the page, and the editor's code does not reference any of them — so when they fail to arrive, they fail on their own. You lose the font, which means the text renders in your system's default sans-serif because that is the fallback the stylesheet names. You lose the ads, leaving blank space. The analytics tag records nothing, which is to say your offline session is not counted. The layout survives intact because the styling is written inside the page rather than fetched as a separate file, and so does every button, every mode, every shape and the download.
One more absence is worth naming because people expect it: there is no connection check anywhere in the code. The page will not tell you that you are offline, warn you, grey anything out, or behave differently. It simply has nothing to say about the network, which is the correct behaviour for a tool that does not use one, but it does mean you get no feedback either way.
Load it before you need it
Given the asymmetry, the whole technique is sequencing. If you know you are heading somewhere without a connection, do this while you still have one.
Open the page and leave the tab open. Not bookmarked — a bookmark is an address, and following it offline is the cold start that may not work. Open, loaded, sitting there.
Test it once with a throwaway image. Load any picture, draw one box, press Download, confirm a file arrived. Thirty seconds, and it converts an assumption into a fact. Then press Clear, or reload deliberately while you still can, so you are not carrying someone else's picture into the dead zone.
Get the image you are going to work on onto the device first. This is the step people forget. The tool being offline-capable does you no good if the screenshot is still in an email you cannot open, a chat thread that will not sync, or cloud storage showing a placeholder. Offline, the file has to be a real file on local storage.
Decide where the result is going. You can produce a redacted PNG with no connection. You cannot send it. Work out in advance whether the point is to have it ready for later, or to put it somewhere local, because a finished file you cannot deliver may mean the whole task waits anyway.
Open a second tab on the same page if the job has several images. They are independent, and a mishap in one does not take the other with it. The tab is the unit of safety.
The reload is what will actually hurt you
Of everything on this page, this is the part that costs real work. The editor keeps no persistence whatsoever: no saved progress, no stored cover positions, no project file, nothing written outside the open tab. Your image, the undo history and the retained original exist only in that tab's memory. Refresh it, navigate away, or close it, and all of that is discarded immediately and completely.
Connected, that is an inconvenience — the page reloads, you open your file again, you redo the covers. Offline it is worse in two compounding ways. The reload may not return the page at all, so you are left with no tool as well as no work. And the instinct that produces reloads in the first place is a page that looks wrong, which is exactly what an offline page looks like when the font is missing and the ad slots are blank. The page looking a bit broken is not evidence that it is broken.
So in an unreliable place: do not refresh. Be careful with gestures that close tabs and with back navigation. If the job is long, press Download at sensible intervals rather than only at the finish, because each export is written from the canvas as it stands and you can export as many times as you like. The related question of why the tab has to stay alive at all, and what else depends on it, is worked through in why your browser tab must stay open during large batch jobs.
A blocked network is not an absent one
A good proportion of the people who need this are not without a connection at all. They are on one that will not let them do the thing. A corporate network where uploads to outside services are stopped by policy. A guest or hotel network that allows ordinary browsing and blocks the rest. A captive portal that has to be signed into before anything works. A device managed so that only approved destinations are reachable.
The relevant property in all of those cases is the same, and it is a slightly unusual one: there is nothing here for the policy to act on. The page loads like any other page, and the redaction that follows produces no traffic to inspect, allow or stop. That is a reason this approach survives in restricted environments, and it is also why the honest framing is about mechanism rather than compliance. Whether a particular tool is permitted on a particular network is a question for whoever administers it and for the rules you work under — not something any page can answer for you. If you are in a setting where that matters, the thing to take to them is the mechanism: the file is opened by the browser, altered in the page, and written back to local storage.
Captive portals deserve one specific warning, because they produce the most confusing failure. Before you sign in, the network answers requests with its own sign-in page instead of the page you asked for. A tool whose address you follow in that state does not fail cleanly; it hands you something that is not the tool and may look briefly like it is loading. If the page you expected looks strange, check whether you are looking at a portal before concluding anything about the page.
Metered, slow and expensive connections
Related case, same mechanism, different motivation: the connection works but you are paying for it, by the megabyte or in time. What matters here is that your image never contributes to that cost. A large photograph or a tall screenshot is decoded and painted entirely locally, so its size is a question for your device's memory and not for your data allowance. The only data the page costs you is the page itself, once, plus the font, the analytics and the ads — and all of those are small next to the file you would otherwise have moved twice, up and back.
The same is true of the output. The exported PNG is assembled in memory and handed straight to the browser, so a fifty-megabyte result costs nothing to produce no matter how little signal you have. Whether you can then send it is a separate matter, and a redacted PNG is frequently larger than the file you started from, which on a metered connection is the cost that actually bites. What to do about that is its own subject.
What the editor above does and does not do here
The tool on this page is region-based: three methods — Black Box, Blur, Pixelate — across three selection shapes, rectangle, oval and freehand lasso. Each operation replaces the pixels inside the path you drew and leaves every other pixel alone. The canvas is created at your image's exact pixel dimensions, Download PNG writes that canvas out as a timestamped PNG, and all of it happens in your browser on your own machine with nothing stored anywhere.
Four points matter when the connection is in question. Every feature is available offline, because none of them is a request: modes, shapes, Undo, Clear and Download all work identically with the network gone. Nothing is saved anywhere, which is the flip side of the same design — there is no draft, no recovery and no autosave, so the open tab is the entire state of your work. There is no offline worker, so the address is not guaranteed to open without a connection and you should not rely on it doing so. And there is no network status in the interface, so nothing will tell you that the font is missing because you are offline rather than because something is wrong with the page.
Common mistakes and misconceptions
“It runs in my browser, so I can open it on the plane.” Running in your browser means it needs nothing once it is open. Opening it is still a web request.
“I bookmarked it.” A bookmark saves an address, not a page. Following it offline is a cold start.
“The connection dropped, so my image might be half-sent.” There is nothing in this page that could send it. A drop interrupts no transfer because there is no transfer.
“The page looks broken offline, so I refreshed it.” The plainer look is the missing font and the empty ad slots. The refresh is what destroys your work, and offline it may not bring the page back.
“I will finish this later from where I left off.” There is no later. Nothing is stored outside the tab, so a session is a single sitting.
“Offline means my image is safe; online means it is not.” The image is handled the same way either way. Being offline removes a worry you did not have, rather than adding protection.
“The file is in my cloud folder, so I have it.” A placeholder that has not been downloaded is not a file. Make sure it is really on the device before you lose the connection.
“I am on the guest network, so uploads are blocked and I cannot redact.” Nothing needs to be sent, so there is nothing for the network to block.
“I can see a page, so I am connected.” On a captive portal you can see its page and nothing else. Sign in before you judge whether anything loaded.
“I will export at the very end.” Somewhere unreliable, export at every point worth keeping. Download can be pressed repeatedly and each press writes the canvas as it is.