Browser Image Compressor
Last reviewed: May 2026
"Free online image compressor" almost always means: your file gets uploaded to a server, processed there, then downloaded back. Sukat doesn't. The entire compression pipeline — JPEG/WebP encoder, HEIC decoder, AI background-removal model, ZIP packager — runs inside your browser. Open DevTools' Network tab, drop an image, watch the panel: no upload happens. Free, no installation, no signup, no account.
How to use Sukat as a browser image compressor
- Open Sukat in any browser. Visit sukatapp.com in Chrome, Safari, Firefox, Edge — desktop or mobile. No installer, no account, no email confirmation.
- Verify it's client-side (optional but reassuring). Open DevTools (right-click → Inspect, then the Network tab). Drop an image. Watch the Network panel — no upload of the image data appears.
- Drop, set target, download. Drop your image, type a KB or MB ceiling, pick the output format, click Convert & Download. The file never leaves your device.
What "browser image compressor" actually means
The phrase is doing a lot of work, so worth pinning down. A genuine browser image compressor runs the compression code inside your browser's JavaScript engine, on your own device, using the same Canvas API and decoding facilities the browser already uses to render web pages. Your image never travels to a server.
Most "free online image compressor" tools do the opposite. They POST your file to a server in the cloud, run a command-line tool there (typically ImageMagick, libvips, or a wrapper around mozjpeg), and return the compressed result as a download. The marketing copy rarely says this out loud — but the upload step shows up in DevTools' Network tab the moment you try to use the tool.
What runs in your browser when you use Sukat
For the curious — the full client-side stack:
- JPEG / WebP encoder: the browser's native
HTMLCanvasElement.toBlob(). Sukat calls it inside a binary-search loop to land on a specific KB target. - PNG encoder: the browser's native PNG output via the same Canvas API.
- ICO encoder: Sukat's own small implementation of the Windows ICO container format, wrapping a Canvas-rendered PNG.
- HEIC decoder:
heic2any, a JavaScript port of libheif compiled to WebAssembly. Loaded once at page start, cached after. - AI background removal:
@imgly/background-removal, an ONNX segmentation model (~40 MB, fetched on first Remove-Background click and cached after). - ZIP packager:
JSZip, a JavaScript ZIP implementation that bundles batch outputs into one downloadable file. - Crop, paint, undo / redo: Canvas 2D context primitives —
drawImage,getImageData,putImageData,globalCompositeOperation.
None of the above touches a server. Sukat itself is hosted on Cloudflare Workers Assets as a static site — there is no backend.
Why client-side compression matters
- Privacy. Files never leave your device, so they can't leak in a server breach or be retained by an upload service. Particularly important for ID documents, medical images, signatures, financial scans.
- No data-residency question. If your data never crosses a network boundary, the EU's GDPR, India's DPDPA, and the Philippines' Data Privacy Act all become non-issues for the compression step.
- Speed. For most modern devices, local compression is faster than upload + server processing + download. The Canvas API runs on your CPU at native speed; a 4 MB photo compresses in well under a second.
- No accounts, no rate limits, no watermarks. "Free online" tools usually cap free users at 5 photos / hour and add watermarks above that. Browser tools have no upload to throttle.
- Works on captive Wi-Fi. Hotel and airport networks often block file-upload domains as a security policy. Browser-based compression has nothing to upload, so the captive policy doesn't matter.
- Verifiable. Open DevTools → Network and watch — you don't have to trust the marketing copy. You can confirm with your own eyes that no upload happens.
- Works offline once loaded. See Offline Image Compressor for the full breakdown.
Why Sukat specifically
Hits a target file size, not a quality percentage. Most browser-based compressors expose a quality slider and let you guess. Sukat takes the constraint directly: set 100 KB, the binary search finds the highest quality that fits.
HEIC, AVIF, WebP, JPG, PNG, GIF — all decoded in-browser. Many "browser image compressors" reject HEIC because their stack doesn't include a decoder. Sukat ships one.
Multilingual UI. 10 languages including Hindi, Spanish, Portuguese, Arabic, Filipino, Indonesian — most browser-based compressors are English-only.
Static, audit-friendly hosting. Sukat is a fully static site on Cloudflare Workers Assets. The HTML, CSS, and JS your browser executes is exactly what you can see in View Source. No backend, no surprises.
FAQ
What does it mean for an image compressor to run in the browser?
The compression code executes inside the browser's JavaScript engine on your own device, using the same Canvas API and image-decoding facilities the browser already uses to render web pages. Your image never travels to a server. Most "free online" compressors do the opposite — they POST your file to a remote server, run a tool like ImageMagick, and return the result.
How can I verify Sukat doesn't upload my images?
Open DevTools (right-click → Inspect, then the Network tab) before dropping an image. Drop and convert. The Network panel shows no upload of the image bytes — the only network call in the entire app is a small decorative counter ping with no image data. Or simpler: switch to airplane mode after the page loads. Compression still works because there's no network call.
What browser support does Sukat require?
Any modern browser from the last several years — Chrome 80+, Safari 14+, Firefox 75+, Edge 80+, plus the mobile equivalents. iOS Safari and Android Chrome both work end-to-end including HEIC decoding.
Do I need to install anything?
No. Sukat is a website, not an app. Open sukatapp.com in any modern browser. No installer, no account, no email confirmation. You can optionally Add to Home Screen on iOS or Android for a one-tap launcher.
Why is browser-based compression better than online compression?
Three reasons. Privacy — your files never leave your device, so they can't leak in a server breach. Speed — on most modern devices, local compression is faster than upload + server processing + download. No friction — no account, no email, no rate limits, no watermarks.
Does it work offline?
Yes. Once Sukat has loaded, you can disconnect entirely and the tool keeps working. See Offline Image Compressor for the full plane / tunnel / captive-Wi-Fi breakdown.
Related tools
- Offline Image Compressor — sibling positioning page on the no-internet scenarios
- How It Works — full mechanics of Sukat's compression pipeline
- Reduce Image Size in KB — pick any KB target for any image
- Compress Image to 100KB — most-searched compression target
- Image Size Guide — full breakdown by platform and use case