Why Client-Side Image Tools Are More Private
Most "online image tool" sites work the way you'd guess: you pick a file, it uploads to a server somewhere, that server processes it, and it sends the result back down. PhotoShrink doesn't do that step at all — every tool here runs using the browser's own Canvas API, which means the actual image processing happens on your device, in the tab you already have open.
What "client-side" means concretely
When you drop a photo into, say, the resizer, the browser reads the file directly from your disk into memory, decodes it, and draws it onto an invisible <canvas> element at the new size — all of this is standard JavaScript running locally, the same kind of code that draws animations or games in a browser tab. The resized result is then handed back to you as a downloadable file, generated locally too. At no point does that image data get packaged into a network request and sent anywhere. You can verify this yourself: open your browser's network inspector, use any tool on this site, and watch — no image upload ever appears in the request list.
Why this matters
- No copy left behind. A server-based tool necessarily receives your file, even if it claims to delete it immediately afterward — you're trusting a policy, not a mechanism. A client-side tool structurally can't retain your file, because it never had it.
- No upload wait, no size limit. Server-based tools often cap file size or take a while on a slow connection. Local processing is limited only by your device's memory, and starts instantly.
- Works offline. Once the page itself has loaded, the tools keep working without a network connection at all, since there's nothing left to fetch.
What client-side processing doesn't change
This site still loads over the network like any other web page, and it can still show ads (PhotoShrink is ad-supported) or use basic aggregate analytics — see the privacy policy for specifics. Those are separate from, and unrelated to, the image files you actually process: the ad script and any analytics never see your photos, because the photos never leave the canvas they're drawn on.
How to tell if a tool is really client-side
Don't just take a claim at face value — check it. Open your browser's developer tools, go to the Network tab, use the feature, and look for any outgoing request containing image data. On a genuinely client-side tool, you'll see the page's own assets load once, and nothing else happens when you process a file. If you see a POST request firing off every time you click "convert" or "resize," the processing is happening on a server, whatever the marketing copy says.
