Optimize an Image for Web
Large images are one of the most common causes of slow page loads. This targets a web-friendly size (200KB by default, editable) directly, resizing the image only if compression alone can't get there.
Drop a file here, or click to browse
Video, audio, image, or PDF — up to 500 MB without an account
or paste from your clipboard (Ctrl/Cmd+V)
Why file size matters for page speed
Every extra 100KB an image weighs is bytes a visitor's browser has to download before that part of the page finishes rendering — on a slow connection, that's directly felt as lag. 200KB is a commonly recommended ceiling for a typical content image; smaller for anything above the fold on a mobile-heavy site.
Resizing vs. just compressing
FileBench reduces compression quality first; if the target still isn't reached (common for very large source images, e.g. a 12MP phone photo), it resizes the image down as well, since serving a 4000px-wide image at web display sizes is wasted bandwidth regardless of compression.
Format matters too
This tool works on your existing format, but converting to WebP first (see PNG to WebP or JPG to WebP) often gets you a smaller file at the same visual quality before you even apply a target size — the two techniques stack.
What image size should I target for a website?
200KB is a reasonable general-purpose target for a content image. Hero/banner images that need to look sharp at large sizes can go higher (400-600KB); small thumbnails or icons should be far lower.
Will this make my image blurry?
Only if the target size forces significant compression or downscaling relative to the source — a high-resolution source photo has much more room to compress cleanly than an already-small image.