Frequently asked questions
Answers to the questions store owners ask most about WebP, image compression, dimensions, platform support, and performance. If you cannot find what you need here, the guides go deeper on each topic.
WebP and image formats
What is WebP and why should I use it for my store?
WebP is an image format developed by Google that supports both lossy and lossless compression, transparency, and animation in a single format. For store owners, the main reason to use it is file size: WebP generally produces smaller files than JPEG at a comparable visual quality, and smaller files than PNG for the same lossless content. Smaller images transfer and decode faster, which can improve page-load speed. All modern browsers support WebP, and both Shopify and WooCommerce handle it natively.
Will WebP work on all browsers my customers use?
WebP is supported by all modern browsers, including Chrome, Firefox, Safari, and Edge. The only browsers that cannot display WebP are very old versions (Internet Explorer, and Safari versions before 14, released in 2020). If your analytics show meaningful traffic from those browsers, keep a JPEG or PNG fallback for critical images like your logo. For the overwhelming majority of stores in 2024 and beyond, WebP is safe to use everywhere.
Should I use lossy or lossless WebP?
It depends on the image content. Use lossy WebP for photography — product shots, lifestyle images, banners — where the discarded data is not visible at sensible quality settings. Use lossless WebP for logos, icons, and flat graphics with sharp edges, where lossy compression introduces visible fuzz. Running a logo through lossy compression to save a few kilobytes usually is not worth the softness on hard edges; running a product photo through lossless mode wastes 3–5x the file size for no visible benefit.
What is the difference between WebP, JPEG, and PNG?
JPEG is a lossy format for photography — universal support, no transparency, no lossless mode. PNG is a lossless format for graphics — supports transparency, but produces very large files for photos. WebP combines both: a lossy mode that beats JPEG on file size, and a lossless mode that beats PNG on file size, plus transparency and animation support. For a full comparison with file-size benchmarks, see our WebP vs JPG vs PNG guide.
What about AVIF? Should I use that instead?
AVIF is a newer format that can offer even better compression than WebP in some cases. However, browser support is still not as universal as WebP — Safari support arrived in 2022, and some older browsers cannot display it. For store images today, WebP remains the safer choice for broad compatibility. AVIF is worth watching, but it is not yet the default for ecommerce.
Compression and quality
What quality setting should I use for WebP?
For most product photography, 75–85% quality is a reasonable starting point. Use 85–90% for hero banners where visual quality matters most, 80–85% for product page main images, and 70–75% for small thumbnails that display at small sizes. These are starting points — always check a 100% zoom crop of a detailed area on your own images before batching your whole catalog. For a detailed settings sheet by image role, see our compression settings guide.
Will compressing to WebP reduce my image quality?
At the recommended quality settings (75–85%), the difference is usually not visible to shoppers on a product page. WebP lossy compression discards information the human eye is least sensitive to, and at 80% quality it generally preserves fine detail like fabric texture and stitching. However, pushing quality too low (below 60%) introduces visible artifacts — blotchy color, blurred edges, or blocky patterns around high-contrast lines. Always verify at 100% zoom before committing to a setting.
How much can I reduce my image file sizes?
It depends on your source images and settings. A typical product photo converted from a full-resolution JPEG to WebP at 80% quality and a sensible width often reduces file size substantially. The exact reduction varies by image content, dimensions, quality setting, and encoder. Photographic content with lots of detail compresses differently from flat graphics with few colors. Test on your own images rather than relying on a single percentage.
Should I resize my images before or after compressing?
Resize before compressing. Serving an image much larger than its display size wastes bandwidth — the browser downloads all the pixels even if it scales them down. Match your export width to the largest size the image slot will render at, including a buffer for high-DPI displays. A correctly sized image at 80% quality usually looks sharper than an oversized image crushed to a low quality to hit the same file size.
What dimensions should my product images be?
It depends on your platform and theme. For Shopify, 2048px wide is the standard for product images. For WooCommerce, the default is 800px but modern themes often request 1200–1600px. Collection grid thumbnails typically need 800–1200px, and full-width hero banners need 2560px. For platform-specific dimension guidance, see our Shopify and WooCommerce optimization guides.
Using the compressor tool
Is the compressor really free?
Yes. There are no upload limits, no watermarks, no account required, and no premium tier. The tool runs entirely in your browser using the Canvas API, so there is no server cost to recoup with a paywall. Compress a single image or many — same tool, same price (zero).
Are my images uploaded anywhere?
No. Every file is read and re-encoded locally in your browser tab. Nothing is sent to a server, which also means the tool works offline once the page has loaded. This matters for sellers with sensitive or unreleased product photography — your images never leave your device.
What image formats can I compress?
You can drop in JPEG and PNG files. The compressor converts and compresses them to WebP. The output is a standard WebP file you can upload to your store like any other image. The tool does not accept other formats (GIF, TIFF, BMP) and does not edit metadata, color profiles, or animation.
How many images can I compress at once?
As many as your browser tab can hold in memory — most people batch tens to a couple of hundred product photos at a time without issue. Larger catalogs can be split into a few batches. Processing in chunks of 100–200 images is more stable than one giant batch, and it makes it easier to spot-check quality partway through instead of discovering an issue at the very end.
Does the tool preserve my original filenames?
Yes. The compressor keeps your original filename and only changes the extension. For example, red-leather-bag-01.jpg becomes red-leather-bag-01.webp. Re-uploading with a matching name helps avoid broken references in cached URLs and structured data. Descriptive, hyphenated filenames are also friendlier to search engines than generic names like IMG_4023.jpg.
Does the tool preserve transparency?
Yes. WebP supports alpha transparency, so PNG images with transparent areas convert correctly. For logos and graphics where edge crispness matters, prefer lossless WebP over lossy to avoid fuzz around transparent edges.
Platform-specific questions
Does Shopify support WebP?
Yes. Shopify automatically serves WebP versions of your images to browsers that support the format — you do not need to configure anything. When a shopper’s browser requests an image, Shopify checks the Accept header and returns a WebP variant if supported, falling back to JPEG or PNG otherwise. You can also upload pre-converted WebP files for tighter control over quality. See our Shopify image optimization guide for details.
Does WooCommerce support WebP?
Yes. WordPress 5.8 (released July 2021) added native support for uploading WebP images to the media library. You can upload WebP files directly and WordPress will treat them like any other image, generating the standard resized variants. To convert existing images, you can either re-upload WebP files or use a conversion plugin. See our WooCommerce image optimization guide for details.
Do I need to regenerate thumbnails in WooCommerce?
If you change your image size settings or replace existing images, yes. WordPress generates image sizes at upload time, so changing settings does not affect images already in your media library. Use the free "Regenerate Thumbnails" plugin to re-process existing images after changing sizes or replacing files. New uploads use the new sizes automatically.
Will WebP break my email marketing images?
It might. Email clients are notoriously inconsistent with image format support — many still do not render WebP. For email campaigns, JPEG remains the safest choice for photography. Keep WebP for your storefront where browser support is universal. This is one of the few cases where JPEG is still the better choice.
Performance and SEO
Will compressing my images improve my Core Web Vitals?
It can. Images are often the largest contributor to page weight, and the Largest Contentful Paint (LCP) element is usually an image. Smaller images transfer and decode faster, which can lower LCP. The exact improvement depends on your starting point, your images, your theme, and your traffic. For a detailed action plan, see our guide on reducing image size for Core Web Vitals.
How do I check if my images are slowing down my store?
Use Google PageSpeed Insights (web.dev/measure) or Lighthouse in Chrome DevTools. Both report image-related opportunities, including unoptimized images and the LCP element. PageSpeed Insights also shows real Chrome user data (field data) alongside lab data. Run it on a product page before and after optimizing to measure the change.
What is LCP and why does it matter?
Largest Contentful Paint (LCP) measures how long the largest visible element takes to render. On a storefront, that is usually your hero banner or main product image. Google’s "Good" threshold is under 2.5 seconds. Because images are often the LCP element, optimizing them is one of the most effective ways to improve LCP.
What is CLS and how do images cause it?
Cumulative Layout Shift (CLS) measures how much visible content jumps around as the page loads. The most common image-related cause is an img tag without explicit width and height attributes — the browser does not know how much space to reserve, so it shifts content when the image loads. Adding dimensions or CSS aspect-ratio to every image fixes it.
Should I lazy-load my images?
Lazy-load below-the-fold images (gallery thumbnails, related products) to defer their loading until the shopper scrolls near them. But do not lazy-load the LCP image — the first large image in the viewport should load eagerly. Most modern themes handle this correctly via the native loading="lazy" attribute, but custom hero sections are a common place this breaks.
Still have questions?
These answers are general guidance, not guaranteed outcomes. If you have a specific question about the compressor or our guides, visit our contact page or read our editorial standards to understand how we write these guides.