Image tools
Image tools
Both tools here read the file with your browser and never upload it — which is the whole difference between these and the compressors that ask you to hand over the original first.
Shrinking a file without seeing the difference
The compressor re-encodes to WebP, JPEG, AVIF or PNG. The trade is worth stating honestly: lossy re-encoding discards detail your eye is poor at noticing, and each pass compounds, so compress from the original rather than from a compressed copy.
It pays off because a hero image is usually the largest thing on a page, which makes it the cheapest page-weight win available.
Placeholders while you build
The placeholder generator produces images at any dimension as PNG, JPG, WebP or SVG — for wireframes, CMS seed content, and checking how a card handles a 3:2 image versus a square before the real assets land. The SVG output stays sharp at any size and weighs almost nothing.
Why local processing matters here in particular
Screenshots contain interfaces and customer data, and photos carry EXIF metadata including GPS coordinates. A tool that uploads receives all of that. These do not upload, so a client asset can be optimised without a data-handling conversation.