Shrink an Image for Sharing

Downscale, strip EXIF metadata, and compress a photo in one step — all in your browser, nothing uploaded.

Try:
Shrunk image

Shrink a photo for sharing in one step

Phone photos are huge — a modern camera shot can be 5–12 MB, more than messaging apps, email, and web forms want to carry, and every one of them still holds the GPS coordinates and camera details baked in by your phone. This tool does the three things you actually want before sharing, in a single pass:

  1. Downscale the longest side to a size that still looks sharp on a phone or in a browser (default 1600 px), keeping the aspect ratio and never upscaling.
  2. Strip the metadata — EXIF, GPS location, timestamps and comments — so you are not leaking where and when the photo was taken.
  3. Compress by re-encoding at your chosen quality, optionally converting to a lighter format (JPEG or WebP shrink photos the most).

Everything runs locally in your browser with WebAssembly ffmpeg. Nothing is uploaded to a server.

Worked example

Take a 4032 × 3024 JPEG straight off a phone (about 4.8 MB, with GPS EXIF). With Max size = 1600, Quality = 80, Format = JPEG, and Strip metadata = on, the result is a 1600 × 1200 JPEG of roughly 250–400 KB with no EXIF or GPS — a ~90% smaller file that is still crisp for chat or a web upload. Set Max size = 0 to keep the original dimensions and only compress + strip.

Presets

The chips under the inputs are one-click starting points: Messaging (1600 px JPEG), Story / vertical (1080 px WebP), Email friendly (1024 px JPEG), and Just compress (keep the original size, quality 70). Adjust any field afterwards.

Limits and edge cases

FAQ

How is this different from the resize or compress tools?

The image-resize tool only changes dimensions, image-compress only re-encodes at a quality, and strip-exif only removes metadata. This tool does all three at once with sharing-friendly defaults, so you don't have to chain three steps to get a photo ready for a message or upload.

Does it upload my photo anywhere?

No. The image is processed entirely in your browser with WebAssembly ffmpeg. The file never leaves your device, which is also why stripping GPS/EXIF here is a real privacy win rather than trusting a server.

What size should I pick for messaging apps?

1600 px on the longest side (the default) is a good all-round choice — most chat apps display images around that size, so anything larger is wasted bytes. For a status/story use 1080 px, and for an email attachment 1024 px keeps the file comfortably small.

Should I convert to JPEG or WebP?

For photos, both JPEG and WebP are much smaller than PNG; WebP is usually a bit smaller again at the same quality and is supported by all modern browsers and apps. Keep PNG for flat graphics, logos or screenshots with sharp edges or transparency. Choose keep to leave the format unchanged.

Why did my PNG barely get smaller?

PNG is lossless, so lowering the quality only asks the encoder to work harder — it can't throw away detail the way JPEG/WebP do. A photographic PNG will shrink far more if you set the format to JPEG or WebP.

Developer & Automation Access

Run it from the terminal

Same engine as this page, headless — via the gizza CLI:

gizza tool image-shrink-for-sharing 'url=https://example.com/input' 'max_dimension=1600' 'quality=80' 'format=keep' 'strip_metadata=true'

New to the CLI? Get gizza →

Open it by URL

Pre-fill and auto-run this tool with query parameters — the names match the API/CLI:

https://gizza.ai/tools/image-shrink-for-sharing/?url=https://example.com/input&max_dimension=1600&quality=80&format=keep&strip_metadata=true