Skip to content

Local-first processing

Compress, resize and convert images.
Nothing leaves your browser.

No installing, no account, no queue. 55 of the 58 tools run entirely on your own device, so your images never leave it. The other 3 can send an image, and each says so before it does.

Compress

Resize

Convert

Edit

Privacy

Extract

Why ImageUtility

Almost nothing is uploaded
55 of the 58 tools decode, process and save images entirely in your browser, so there is nothing to leak, store or delete. The exceptions are alt text and remove background, each labelled as such and each asking first, and compress + resize can send it too if you switch that step on.
No waiting in a queue
For the tools that run on your device - almost all of them - there is no upload time and no shared server to compete for. Most images finish in well under a second.
Free, with no account
Every tool is free with no sign-up and no watermark. Processing on your device costs us nothing per image, which is why there are no quotas on it; the one AI tool that uses an external service is rate limited so it stays free too.

How local processing works

When you select an image, it is read directly from your device into the page. A Web Worker decodes it, applies your settings and encodes the result, then hands back a file your browser saves. At no point does the image travel over the network - you can confirm that yourself by watching the network panel in your browser’s developer tools while a tool runs: no request carries your image.

You will see one small anonymous event in that panel, recording which tool was opened and whether it finished. It names the tool and nothing else - no filename, no dimensions, no file size and no part of your image - and it never leaves this domain. The privacy page lists every field it can contain.

58 tools are available today, and 55 of them work exactly like that. The 3 that do not are alt text, remove background and compress + resize. Describing a picture in words and separating a subject from its background both need models far too large to run in a browser, so those tools send a reduced copy of your image to an external service. The third only sends when you switch that step on. Each names the service and asks before it sends anything. We would rather mark the exceptions clearly than quietly route your images through a server.

See every tool