Headroom
Tools
EncodeInspectPreviewConvertOptimizeBatch
Learn
HDR GuideColor SpacesImage FormatsDisplay TestsAll Guides →
Tools / Optimize

Cut file size without losing the highlights

Resize, requality, and reformat locally. Metadata handling is shown honestly: we can genuinely preserve EXIF for JPEG output by splicing the original segment back in — for PNG/WebP output there's no equivalent path here, so we say so instead of a checkbox that does nothing.

Drop an image here
or choose a file
JPEG · PNG · WebP · AVIF

How Optimize actually works

Optimize runs the same decode/re-encode pipeline as Convert, with two things added on top: resizing (via canvas, before re-encoding — never after, so the resize quality reflects the final output) and, for JPEG output specifically, a genuine EXIF-preserving option.

EXIF preservation works by extracting the original file's EXIF segment directly from its bytes and splicing it into the newly-encoded JPEG's output — a real byte-level operation, not a metadata copy performed by a library that might silently drop fields. It's only offered when the source file actually has an EXIF segment to preserve, and only for JPEG output, since that's the only format this splice path is implemented for.

Quality and resize dimension are both applied locally, in a Web Worker, before you ever see a result — nothing is uploaded to estimate or preview the output.

Questions people actually ask

Does resizing lose quality?
Downscaling always discards detail — that's unavoidable, and true of any resizer. What Optimize does honestly is show you the real before/after: actual file size, actual output dimensions, actual EXIF status, so you can judge the trade-off on your own file instead of guessing.
Why can't I keep EXIF for PNG or WebP output?
Because there's no segment-splice path implemented for those formats yet — genuinely, not as an arbitrary restriction. For JPEG output, EXIF preservation works by extracting the original EXIF segment and splicing it back into the new file, which is a JPEG-specific mechanism. Rather than show a checkbox that would silently do nothing for PNG or WebP, Optimize just says so.
What resize dimension should I actually pick?
Depends what it's for. For web delivery, matching the largest size you'll actually display it at (accounting for retina/high-DPI, so maybe 1.5–2× the CSS display size) avoids shipping pixels nobody sees. For archival or print, leave it at original size and just adjust quality instead.
Is the savings percentage a real measurement?
Yes — computed directly from the actual input and output byte counts after encoding, not estimated or looked up from a table.