Resize WebP Online
Resize a WebP image to the exact size you need and download it as WebP, so the file stays small. Transparency is preserved. All processing is local.
Upload an image
Drop an image here, or click to browse
JPG, PNG, WebP · Max 50 MB per file
Your image stays on your device. This tool runs entirely in your browser. Your file is never uploaded to our server.
How do you resize an image to WebP?
Resizing an image to WebP on this page is a four-step loop: drop the file, set the output size, check the preview, and download. The tool accepts JPG, PNG, and WebP files up to 50 MB, and it always writes the result as a WebP with transparency kept where the source had it. Because the whole job runs in your browser with the Canvas API, nothing is uploaded, and the preview shows the exact output dimensions before you download.
- 1Drop or select an image. JPG, PNG, and WebP files up to 50 MB are accepted.
- 2Pick a mode: Pixels for an exact width and height, Percent to scale by a set amount, or Max dimension to cap the longest edge.
- 3Check the preview and the estimated size, then download. The output is always a WebP.
How much smaller is WebP than JPG?
At the same visual quality, WebP files are usually 25-35% smaller than JPG, and the gap is larger still against PNG. A photo that weighs 2.4 MB as a JPG commonly lands around 1.6 MB as a WebP. Combined with resizing, the savings stack: a 4032x3024 camera photo resized to 1600px wide and saved as WebP typically falls from 3.8 MB to roughly 400-600 KB, which is why this page works as a resize and convert in one step.
Common use cases for resizing to WebP
Website images and Core Web Vitals
A hero image shipped at 2.4 MB can add two to three seconds of load time on a phone. Resized to 1920px wide and saved as WebP, the same image drops to around 500-700 KB and loads in under a second, which directly improves the Largest Contentful Paint metric that Google ranks pages on.
Blog and article images
An article with ten inline photos at 1.5 MB each forces 15 MB of downloads before a reader sees the end. Resized to 1200px wide and converted to WebP, each photo drops to roughly 150-250 KB, and the whole article weighs under 2.5 MB.
E-commerce product galleries
A product page with eight images at 2 MB each is 16 MB of loading before a shopper scrolls past the first shot. Resized to 1200px wide as WebP, each image lands around 200-300 KB, and the gallery opens instantly while keeping transparent cutouts transparent.
Portfolio and client review
Freelancers send work-in-progress files that should not arrive as a multi-megabyte attachment. A 3000px JPG resized to 1600px and saved as WebP drops from about 3 MB to under 600 KB, staying visually faithful for review while keeping the message light enough to open anywhere.
Three resize modes
- Pixels: set an exact width and height. Use this when a template or upload slot requires a fixed size, such as a 1200x630 social card.
- Percent: scale by a single number, so 50% halves both the width and the height.
- Max dimension: cap the longest edge at a value like 1600px, and the shorter side follows automatically.
Why is the aspect ratio lock on by default?
The lock keeps width and height linked, so changing one dimension scales the other in proportion. That prevents the squashed or stretched look that appears when the two are typed independently. Leave it on for every normal resize, and turn it off only when you deliberately need to distort the image to fit a non-standard slot.
Does WebP output keep transparency?
Yes. WebP stores an alpha channel, so a transparent PNG dropped in comes out as a transparent WebP rather than a white-filled image. That makes this page a direct drop-in for the PNG assets on your site when you want the transparency to survive and the file to shrink at the same time.
What quality setting should you use for WebP?
The quality slider controls how hard the WebP encoder compresses the result. WebP holds detail better than JPG at the same setting, so 75-85% is usually where a photo looks effectively identical to the original while the file stays light. Dropping below 60% starts to show softening on edges and gradients; going to 90-95% keeps near-original detail for files you may zoom into.
Why resize in the browser?
Every image on this page is processed locally by the Canvas API, so the file never leaves your device. There is no upload, no account, and no queue, which makes the tool a sensible choice for client assets, internal screenshots, and personal photos you would rather not send to a third-party service. Processing starts the moment the file is selected, and a single resize is typically ready in under a second.
Frequently asked questions
Does WebP output keep transparency?
Yes. WebP stores an alpha channel, so transparent areas in a PNG source survive the resize and come out transparent in the WebP file. There is no white fill step, unlike a JPG output.
Is WebP smaller than JPG at the same quality?
Usually, by 25-35% for photos. Combined with resizing to the dimensions the image is actually shown at, WebP output on this page produces files that are dramatically lighter than the original.
Can I resize a JPG or PNG to WebP here?
Yes. Any JPG, PNG, or WebP up to 50 MB is accepted, resized, and saved as WebP. This page is effectively a resize and convert tool in one, with no separate conversion step.
Does resizing to WebP reduce quality?
Shrinking removes pixels without degrading the ones that remain, so visible detail holds up. The only loss comes from the WebP re-encode, and at 75-85% quality the result is effectively indistinguishable from the original.
What happens if I enlarge an image past its original size?
Enlarging past the original adds blur, because the browser has to invent pixels that were never captured. For crisp results, resize to the original size or smaller.
Is there a file size limit?
Input files are limited to 50 MB. The cap exists because the tool decodes the full image into browser memory, and larger files make the page sluggish. Most photos are well below the limit.
Do all browsers support WebP?
Yes. Chrome, Firefox, Safari, and Edge have all rendered WebP for years, with Safari adding full support in 2020. For images served on a website, WebP is a safe default today.