What you type never leaves your device. Every one of these tools is compiled to WebAssembly and runs inside this browser tab. There is no server to send anything to, and none of them makes a network request while it works. You can open your browser's network panel and use any of them: nothing goes out.
It matters more here than for any other application in this workspace. A photograph is not a paragraph: it carries where it was taken, when, and on what, and a screenshot carries whatever was on the screen. None of it goes anywhere, and you can watch the network panel while you use any of these.
Each tool remembers your settings, and remembers your input while it is small enough
to be worth keeping, under about eight kilobytes. It is kept in your browser's own
localStorage, on your machine, and is never transmitted. That is worth
knowing before you open a photograph on a shared computer — clearing your browsing
data removes it, and a private window keeps nothing at all. Your chosen language and
theme are stored the same way.
No account, no sign-up, no cookies of our own, no analytics script, no fingerprinting, no error reporting. The pages carry no third-party JavaScript except the advertising described below.
These pages carry advertising, which is what pays for hosting them. An advertising network sets its own cookies and sees your IP address and the page you are on, in the same way it does on any other site. It does not see what you type into a tool: that text is never part of the page's markup and is never sent anywhere. If you would rather it saw nothing at all, an ad blocker breaks none of the tools.
Opening a file reads it into the tab's memory and no further. Saving a result writes it with your browser's own download mechanism. Neither passes through a server.
Every result here is re-encoded from its pixels, so nothing that was not a pixel comes with it: the camera, the lens, the date, the software, the copyright field and the location are all dropped. That is the entire point of the tool that strips a location, and it is a surprise to somebody who wanted their authorship kept — so every result says which just happened rather than leaving it to be discovered later.
A blur and a pixelation are both averages of the original, and that is exactly what makes them reversible: published work has recovered faces and number plates by blurring candidate images the same way and comparing. Only a solid fill or noise removes what was underneath. The censoring tool offers all four methods, says on the result which kind you chose, and puts the number on the page when a setting is too weak to hide anything — the block count, or the blur radius as a share of the area it covers.
The tool that reads a photograph's location gives you the coordinates and a link you can choose to click. It does not draw a map, because drawing one would mean asking a map service for tiles — which would tell that service where the photograph was taken, the precise thing somebody opening that tool is worried about.
This workspace ships no binary assets of any kind, and that includes the examples. The example button draws a test pattern from nothing — a checkerboard, a gradient, colour bars, a hue wheel, a scene with a sky and a hill — and the interface says so. It turns out to be the better fixture as well: a drawn image is identical every time, so comparing two settings compares the settings rather than the picture.
The size limit is eight megapixels, and it is checked from the file's own header before the pixels are decoded: reading a 20 000 by 20 000 image in order to refuse it would already have used more memory than a browser tab has. The refusal carries the size it found. WebP opens here and cannot be written, and the save menu says so rather than offering it and failing at the last step.
The same tools are also built as a desktop application. It has no network code at all — not for updates, not for anything — and stores its settings in one small file in your user configuration directory.
If this ever changes, this page changes with it, and the change will be visible in the project's history rather than announced quietly.