Compress imageson your device
Images stay on this device. Drop a file, check the quality, then download. Core tools are free.
- 21 tools · 5 languages
- 0 image servers
- EXIF/GPS stripped by default
- 100% on-device
01 / FOR YOU
Who uses ImgFlow?
Pick your lane — each tab leads to the tools and presets that job actually uses.
HEIC from your iPhone, batch slimming, EXIF and GPS stripped by default — sharing never leaks the shooting spot.
Marketplace listing specs preconfigured: a 1600×1600 square with a 3 MB size target, ready to upload.
Local Wasm processing, an installable offline PWA, and WebMCP so AI agents can drive the compressors directly.
02 / FEATURES
Why ImgFlow
Core features free forever, no sign-up
Core features stay permanently free with no sign-up, and with no file-count or per-file size limits. Pro is optional — we will never nag you with an “upgrade above 0.5MB” popup.
Images never leave your device
Decoding, resizing, and encoding all run in this browser. There is no upload endpoint, and it works offline.
See before and after
A finished image opens a comparison slider so you can check edges, gradients, and texture before you download.
Global scene presets
Social, marketplace hero, avatar and ID photo packs — one click for size and file budget.
Batch & ZIP download
Drop hundreds of files at once; the memory-budget scheduler keeps it stable. Download singly or as a ZIP.
PWA, works offline
Install to your desktop or home screen and keep working without a network.
04 / PRESETS
Scene presets (social / ecommerce / avatar)
Three packs — social, ecommerce, avatar: square posts, 1600×1600 listing heroes, profile and ID photos. Pick a preset and parameters apply locally in your browser.
05 / STUDIO
This is Studio
Real workbench shots: batch results, the folder tree, and the pipeline — all running in your browser.
06 / VS OTHERS
Compare with Other Tools
ImgFlow vs TinyPNG: free limits, file-size caps, and local processing
TinyPNG free tier caps you at 5 MB per image, 20 compressions and 3 conversions per session, with programmatic ads. ImgFlow has no per-image cap, no session quota, and strips EXIF/GPS by default — also processing locally in the browser. Verified September 2026.
- No 5 MB per-image cap, no 20-per-session quota — the free tier is the full product
- A target-size engine that hits exact sizes (100 KB / 500 KB) across 21 scenario-tuned tool pages
ImgFlow vs Squoosh: fine-tune one image, or ship a hundred
Squoosh and ImgFlow both process 100% locally in the browser (our test saw zero third-party requests). Squoosh is Google’s open-source single-image tuner, famous for side-by-side comparison and experimental JXL/WP2/QOI codecs; ImgFlow focuses on shipping batches: unlimited queue + ZIP, exact target sizes, platform presets. Verified September 2026.
- A complete batch shape: hundreds queued, failures never block, one-click ZIP — no per-file babysitting
- Target-size engine + grouped scene presets: hitting 100 KB or social/listing/avatar specs is one click
ImgFlow vs iLoveIMG: should your images leave your device?
iLoveIMG is a broad online image suite (compress/crop/watermark/AI tools + a PDF ecosystem) built on the cloud model: our September 2026 test caught an upload to api33.iloveimg.com the moment we dropped an image. ImgFlow compresses and converts in the browser: 0 upload endpoints, no per-task quota, works offline. Here is the trade-off, with measured data.
- 0 upload endpoints: images never leaving the device is architectural, and provable by going offline
- Core tools free forever: no task quota, core features need no registration
07 / FAQ
FAQ
Are my images really never uploaded?
Really. All decoding, resizing, and encoding run in your browser via WebAssembly — this site has no image upload endpoint at all. Verify it yourself in the DevTools Network panel: no image request appears during processing, and it keeps working with the network off.
Will compressed images suffer noticeable quality loss?
No noticeable drop. ImgFlow uses the same production encoders as Google Squoosh (mozjpeg, oxipng, libwebp, libavif). By default, Smart quality picks settings for each image to keep files as small as it can with little visible difference; switch to Set quality if you need a fixed value. A real-time 1:1 split comparison slider lets you inspect pixel-level differences yourself.
If processing is local, why is it faster than cloud tools?
Cloud tools require a round trip: local reading ➔ uploading ➔ server queues ➔ cloud processing ➔ downloading. ImgFlow leverages WebAssembly multithreading and SIMD hardware acceleration directly in your browser memory, eliminating the slow upload of hundreds of megabytes of raw image data.
Is it free? Will it nag me with VIP popups like other tools?
Core tools free forever: no file-count limits, no per-file size limits, core features need no registration, no watermark, and no VIP popups. Pro is optional and requires sign-in; core compression and conversion are not behind a paywall.
Which formats are supported?
Input: PNG / JPG / WebP / AVIF / HEIC (iPhone photos), GIF, JXL, SVG. Output: JPG / WebP / PNG / AVIF / JPEG XL. HEIC decodes natively in Safari; other browsers load a decoder automatically — nothing to install.
How many images can I process at once?
There is no limit. A memory-budget scheduler queues work based on your device, so dropping a few hundred large photos on an iPhone will not crash it. Download one by one or as a single ZIP afterwards.
Will processed photos leak where they were taken?
No. Output images strip EXIF and GPS data by default, so sharing them never reveals the shooting location — that is exactly why “metadata does not carry over” is the default behavior.
Does it work without a network?
Yes. ImgFlow is a PWA (an installable offline app). After the first load the core engine is cached locally — compress and convert on a plane or in the subway.