filehugger.comThe exact steps
- Decode the photo
- Resize to ≤ 1920 px (longest side)
- Encode as JPG at 75%
One web-ready JPG per photo; grab everything as a ZIP on the download page.
Why this chain
Phones save photos far larger than any screen shows. Resizing before encoding is where the real savings live — the quality setting only polishes what is left. 75% JPG at 1920 px is visually clean on the web at a fraction of the original size; if the destination supports WebP, the plain converters can take you further.
Doing it without the recipe
By hand this is three tools: HEIC to JPG to get out of Apple’s format, Resize Image to cap the long side at 1920 px, and Compress Image to set the quality. The chain does all three in one pass per photo and, more usefully, does them in the order that matters — decoding first, resizing second, encoding last — so the photo is only re-encoded once instead of three times.
When this chain is the right one
This is for the everyday problem of a phone full of HEIC files and a form, CMS or colleague that will not accept them. Modern iPhones shoot 12-megapixel HEIC by default, which is both a format most of the web cannot read and several times more pixels than any screen will show. If the destination can take HEIC, or if you are archiving rather than publishing, do not run this: it throws away resolution you might want later, and that is not recoverable.
Honest limits
Downscaled means downscaled — keep your originals for printing and future crops. Transparency (rare in photos) is flattened to white by JPG.