Compress an image for your website
Smaller images mean faster pages and better search rankings.
- Private by defaultDeleted within an hour
- Super FastProcess in seconds
- No Sign-upStart instantly
How it works
Add your images
Drag and drop, paste, or pick files. They upload over an encrypted connection.
Pick a quality or a target size
Use the quality slider, or tell it exactly how many KB or MB you need.
Download
Save each file, or grab them all at once as a ZIP.
Page speed is a known factor in both user experience and search ranking, and images are usually the biggest part of a page's weight. Converting to WebP at a moderate quality setting, and resizing to roughly the dimensions the image will actually display at, typically cuts image weight dramatically with no visible loss.
A common mistake is uploading a camera-resolution photo (often 3000 pixels or more wide) when the page only displays it at 800 pixels; the browser still downloads the full file. Turning on Resize here and setting a sensible maximum width fixes that at the source.
No sign-up is needed, so you can compress and compare a few quality settings before publishing; files are deleted from our servers within one hour. Beyond file size, remember to also set width and height attributes on the image tag in your page's code; that alone prevents layout shift while the image loads. It's worth testing the final page on a slow connection afterward, since real-world load time depends on more than just one image's file size.
A budget for each kind of image
It helps to decide the numbers before you open the editor. A full-width banner at the top of a page: up to 2000 pixels wide and no more than 250 KB. A picture inside an article: 1200 pixels wide, under 120 KB. A thumbnail in a grid of products or posts: 400 pixels, under 30 KB. These are working budgets and no standard dictates them, but a page that keeps to them loads quickly on a phone, and all of them are within reach with WebP at the quality of 75 this page starts with.
The one image that decides your loading score
Google measures how long the largest visible element takes to appear, a figure called Largest Contentful Paint, and counts 2.5 seconds or less as good. On most pages that element is a picture: the banner, or the main product photo. So put your effort there first. Make that one file as light as it can be without looking cheap, and do not mark it for lazy loading, because it should start downloading at once.
Everything further down the page is the opposite case. Mark those images with the loading attribute set to lazy, and the browser fetches them only when the visitor scrolls near.
High-density screens without the weight
Phones and many laptops pack two or three physical pixels into each CSS pixel, so an image shown 600 wide looks crisper when the file is 1200 wide. Serving that larger file to every visitor is wasteful. The srcset attribute lets you offer the same picture at two or three widths and leaves the choice to the browser.
Making the set is quick here: run the batch once at each width and download each ZIP. If the site is already live and full of heavy images, the website optimizer on this site scans your pages and returns every picture as WebP with a list of what to replace.
Frequently asked questions
Why does image size matter for a website?
Images are usually the largest part of a page's total weight, directly affecting load time.
Should I use WebP for website images?
Yes, for almost all modern websites it gives smaller files than JPEG at equal quality.
What size should I resize images to?
Roughly the largest width the image will actually be displayed at on the page.
Does smaller image size really affect search rankings?
Page speed is one of many ranking factors, and images are usually the easiest place to improve it.
WebP or AVIF for a website?
Both display in every current browser. AVIF files are smaller, especially photos at low sizes. WebP is the safer pick when images also pass through other tools, such as a newsletter service or an old CMS plug-in.
Should the image for link previews be WebP too?
Keep that one as JPEG or PNG. The preview image is fetched by social networks and chat apps, and some of their crawlers do not read newer formats.