Optimize a JPG for the web.

60 to 80. Below 60 the artifacts show; above 80 the file grows for nothing the eye can see. Most production sites sit at 70 to 75.

Largest Contentful Paint, one of the three Core Web Vitals, is usually a hero image. A 3 MB JPG can add seconds to it; the same picture at 200 KB loads in a fraction of that, and the score and the ranking follow.

Usually, yes: 25 to 35 percent smaller at the same look. Choose WebP as the output format here, and serve the JPG as a fallback with a picture element where old browsers still matter.

The size it is displayed at. A full-width hero on a 1920 pixel layout should be 1920 wide, a sidebar image a few hundred. A 4000 pixel photo scaled down by the browser wastes every byte above that; the longest-side cap handles it.

Yes. It adds bytes nobody renders and can carry a GPS position; leave Keep EXIF off. Keep it only for a gallery that shows camera settings.

Export at twice the displayed size, 1600 wide for an 800 pixel slot, and compress harder, 60 to 70. The extra pixels cover for the stronger compression and the file stays reasonable.

The slider sets the starting quality, and a size cap makes the tool try lower qualities until the file fits under it. The longest-side cap scales the image down first, which is the biggest lever for a photo straight from a camera. Every change reruns the compression and shows the new size.

Then there was nothing to gain: the file was already smaller than any recompression at these settings. The tool keeps your original, says so under the result, and never hands you a bigger file than the one you dropped.

No. The file is decoded, drawn and re-encoded by your browser's canvas, and the page makes no request with it. You can load the page, go offline and keep working; nothing is stored either.

No. The "Optimize a JPG for the web" tool is free and opens without a sign-in, an account or an install.

Up to 100 MB per file, the limit the tool states under its drop area. A larger file is refused with a plain message instead of being decoded.

No, it takes one file at a time. If you drop or choose several, only the first is used; run the tool again for the next one.

When the output would not be smaller and you kept the same format, the tool hands back your original and says so in the status line.

Closest to the "Optimize a JPG for the web" tool: JPG compressor, Optimize images for a website, JPG to WebP converter, PNG compressor. Each opens on its own page, free and in the browser.

The "Optimize a JPG for the web" tool is one of 44 in its group. The group's page, /tools/jpg, lists them all.

The tool is free. Its interface is built from shadcn.io's own components (Button, Input, Slider and the rest of the registry under /ui), which come in React, Vue, Svelte and Solid. Pro adds the blocks and templates for the product around it.