Compress WebP Online

Keep the current dimensions or choose a file-size limit for each static WebP image.

Drag & Drop Images Here

or Click to Upload

WebP

Up to 30 files, 20 MB each

Decide what the next destination needs

A product page may need an image exactly 1200 pixels wide. A submission form may accept anything under 100 KB. Both give you a reason to compress WebP images, but they ask different things of the encoder. Start by finding the requirement you actually have to meet.

If the destination specifies dimensions, choose Keep dimensions. If it specifies a maximum file size, choose Target size and enter that number. You can try a byte target while keeping the current dimensions. Allow a smaller image only when you are comfortable giving up some pixels to reach the limit.

Read the limit literally

A form might say “less than 100 KB” or “up to 100 KB.” TinyImagePro uses 1,024 bytes per KB. Its 100 KB target therefore allows up to 102,400 bytes. A service using decimal kilobytes could enforce a limit of 100,000 bytes. Check the exact byte count or leave a small margin when a strict upload rejects your file.

What happens when the original already fits?

An existing file within the target can be returned as the original. Look at its dimensions and saved bytes before adjusting anything. A zero percent reduction on a file that already passes the receiving site's check is a useful result. It also avoids another round of lossy encoding.

A coral-colored glass on blue woven fabric, with a soft shadow and a visible thread pattern.
The rim, shadow and woven threads give you three different details to inspect when you compress WebP photographs.
compress-webp.webp · 1200 × 800 px · Chrome 157
Compression modeResult (B)
Original146,136
Quality 85%140,602
Target size 100 KB100,212

How to compress WebP while keeping the same dimensions

Choose one static WebP or add several files from the same product shoot. Keep dimensions starts with the width and height of each individual picture. A landscape photograph and a portrait photograph in the same batch keep their own shapes. The quality setting controls how much visual detail the encoding can discard.

Pick a representative photograph first

Start with the most demanding image in the batch. For glassware, that might be a clear tumbler photographed next to a woven cloth. The curved rim, smooth background and tiny threads show different problems as quality drops. An acceptable setting on a smooth studio wall may remove detail that matters on the fabric.

Download a candidate and open it at its intended display size. Then zoom into a small part with fine texture. Look for changes that would affect a buying decision, such as a seam disappearing or a glossy surface looking matte. Those observations are more useful than chasing a particular percentage for every image.

Compare files at the same scale

Two pictures at different zoom levels can look surprisingly different even when their pixels match. Use the same viewer, zoom and background for both. For a mobile product card, also check the picture at the actual card width. Save the larger original separately for a zoom view if the shop offers one.

Reach a target size in KB

To compress WebP for a file-size limit, switch to Target size. Choose a preset or enter a positive whole number. Each image has its own budget. A 100 KB setting for three images means each output is checked against 100 KB; it does not divide one budget into three equal shares.

Try quality adjustment before resizing

The first pass keeps the current dimensions. When the target is reachable at that size, inspect the candidate before accepting it. Fine text, diagonal lines and low-contrast edges are good places to look. TinyImagePro reports whether the encoded bytes meet your chosen ceiling.

If the result remains too large, decide which part of the request is flexible. Increasing the target may preserve small print. Allowing the long edge to shrink may work well for a thumbnail that will never open at full size. Write down the receiving service's maximum dimensions before making that choice.

A worked example with two constraints

Suppose a catalog requires a 1200 by 800 image under 100 KB. Lock the dimensions and start at 100 KB. A result of 103,000 bytes misses this tool's ceiling even if a rounded size display looks close. The result row should show the missed target and preserve the actual width and height.

A 900 by 600 version might meet the byte target, but it would fail the catalog's dimension requirement. Keep the size locked for that job. Discuss a different crop, a simpler background or a revised budget with the person who owns the catalog rather than uploading a file you already know will be rejected.

Protect transparency and check the edges

A transparent product cutout has visible pixels, fully transparent pixels and sometimes a narrow band of partial transparency. When you compress WebP with a transparent background, judge the output on both light and dark surfaces. A white backdrop in a preview can hide an edge that becomes conspicuous in a dark theme.

Where a checkerboard helps

The checkerboard is a viewing aid beneath the image. It lets you see holes in a handle, the gap between leaves and the soft boundary of a shadow. The checks should disappear when you place the downloaded image over a colored surface. If they stay, they were already part of the source artwork.

For product photography, examine highlights inside the object as well as the outline. White reflections on clear glass can look like holes against a white page. Move the image to a colored background to see whether the reflection itself has remained opaque. Keep that test separate from inspecting the overall file size.

Static WebP and animated WebP

A WebP filename can refer to a single picture or an animation. This page is designed to compress WebP that contains a single still image. An animated input receives its own message so a batch of still images can continue without producing a misleading first-frame download.

Find the right source when a file is rejected

Play the original in a viewer that supports animation. Some motion consists of a blink or a changing highlight, so watch through a full cycle. If the design is intentionally static, request the original still from the person who exported it. Renaming an animation or taking an arbitrary screenshot changes what you are delivering.

The actual encoded format matters too. A JPEG saved with a WebP filename remains a JPEG. When the browser cannot produce a valid WebP output, the tool reports the problem. To make a WebP from a JPEG in the first place, start with JPG to WebP and check whether the new file already meets your limit.

Review a batch before downloading it

The rows in a batch tell you which files reached the target and which need a second decision. Compare original and output dimensions alongside the two byte counts. A smaller output produced by shrinking the picture has a different use from a smaller output that preserves every position in the original grid.

Keep the exceptions together

A set of catalog photographs may include a logo with small lettering, a detailed fabric close-up and several simple backgrounds. Use one starting setting, then inspect the exceptions. When you compress WebP for a whole collection, files that miss the target often reveal which content needs a different treatment.

Save the successful images and decide whether to include the missed targets in the ZIP. For a strict submission portal, leave those files out until they pass. For an internal design review, the best available version may still be useful if the reviewer can see its dimensions and size.

Check the exported file on its own

Open a downloaded result separately from the tool. Confirm the file type, size and pixel dimensions in the viewer or file inspector. If the image will appear on a website, check which asset the published page actually loads. A content system can generate a different derivative even when your local export is correct.

Match a compression choice to the delivery slot

Imagine handing three versions of a product photo to a store editor. The first sits in a fixed-width gallery, the next goes in a small upload field and the last overlays a colored panel. To compress WebP images for each slot, start by writing down the single requirement that would cause a file to be rejected.

Delivery slot Start with Check in the result
Product gallery Keep dimensions Original width and readable fabric detail
Form attachment Target KB Actual byte count under the stated cap
Transparent panel Keep dimensions Edge against the destination color

Compare two candidates at the same size

Open the candidates at the width the store actually uses. Watch the curved glass rim, the dotted weave and the shadow. Do the same comparison on a phone if that is where visitors place orders. Different display sizes can call attention to different defects, even for two files with similar byte counts.

Keep a record of the accepted file

When you compress WebP assets for a recurring campaign, note the source dimensions, accepted bytes and chosen setting beside the final filename. On the next delivery you can repeat the method and judge the new picture on its own details. A setting that works on plain packaging may soften the lettering on a woven label.

Questions about smaller WebP files

Why did one picture barely change?

An image may already be tightly encoded, particularly if it came from an optimized website. Re-encoding can produce a larger candidate. Returning the smaller original preserves quality and avoids an unnecessary transfer. Compare several different source images before drawing conclusions about the whole collection.

Does changing the slider guarantee a particular number of bytes?

Quality is an instruction to the encoder. The image's detail and dimensions influence the resulting size. For a required maximum, use Target size and read the final result. A number on a quality slider cannot certify that an attachment meets the receiving service's byte limit.

Should I convert my PNG first?

If your destination accepts WebP and the PNG is a suitable source, use PNG to WebP and inspect the output. Keep your editable or lossless master. You can compress WebP again for a narrower delivery requirement, but start from the best original when preparing several sizes for a new release.

Which file should I keep for later edits?

Keep the source image and label delivery copies with their intended use. A small shop thumbnail, an email attachment and a product detail photograph can come from the same original. Having the master lets you create a fresh version when the destination changes its dimensions or gives you a larger size allowance.