Resizing reduces the pixel dimensions, which slashes file size on top of compression. This tool caps the longest edge at 1920 pixels — perfect for full-width web display — while keeping the aspect ratio. Combine with JPEG compression for the smallest result.
Why dimensions matter more than you think
File size scales with the number of pixels, and pixels scale with the square of the dimensions. Halve the width and height of an image and you don't remove half the data — you remove roughly three-quarters of it, because the area shrinks fourfold. That is why resizing is often the single largest saving available, ahead of any quality tweak. A 4000-pixel photo dropped into a 1000-pixel column is carrying sixteen times the data the screen can show, and no compressor can fix that without first removing the surplus pixels. This tool caps the longest edge at 1920 pixels, a size that still fills a full-width hero on a high-resolution display while discarding the wasteful excess above it.
Resize first, then compress — the order matters
Sequence changes the outcome. Resize before compressing and the compressor only has to encode the pixels you'll actually display, so it can spend its quality budget where it counts. Compress first and you've optimised pixels you're about to throw away — wasted effort. The reliable pipeline is short:
- Resize the source down to its display dimensions here.
- Compress the result with JPEG compression for photos.
- Convert to WebP if you want the smallest modern delivery.
Each step is one upload, and together they routinely cut a multi-megabyte original to a few hundred kilobytes.
Aspect ratio stays locked, so nothing stretches
Resizing here is uniform: width and height shrink by the same factor, so circles stay round and faces stay natural. You won't get the squashed look that comes from forcing an image into a fixed box of the wrong shape. Because the cap applies to the longest edge, a tall portrait and a wide landscape both end up appropriately sized without you doing any maths. If the image also has redundant bytes after scaling — and it usually does — finish with compression or send graphics through PNG optimisation. The full toolkit on compressjpeg.onl is built to be chained this way.