Compress Images for Web — Optimize for Page Speed and SEO
Reduce image file sizes to Google-recommended targets for faster loading, better Core Web Vitals scores and improved search rankings.
Compress Images for Web — FreeJPG, PNG, WebP, AVIF, HEIC — web-optimized output, batch download as ZIP.
Compress images for web the right way — down to the specific file sizes Google recommends for fast pages and strong SEO. Optimizing images for website performance means hitting concrete targets: hero images under 300 KB, inline images under 100 KB, thumbnails under 30 KB. Use this tool to reduce image size for website deployment, improve Core Web Vitals LCP scores and give Google PageSpeed Insights fewer reasons to flag your pages. No upload, no account — runs entirely in your browser.
Why compressing images for web directly improves SEO and page speed
Compressing images for web is not just about file size — it is about the direct relationship between image weight and Google search rankings. Google confirmed that Largest Contentful Paint (LCP) is a ranking factor in mobile search. LCP is the time it takes for the biggest element on the page to fully render — on most pages, that element is a hero image or a large product photo. A 4 MB hero image takes roughly 4 seconds to load on a 4G connection. At 300 KB, the same image loads in under 0.3 seconds. That 3.7-second difference is the difference between a passing LCP score and a failing one.
Google PageSpeed Insights and Lighthouse surface this problem explicitly. Under "Opportunities," Lighthouse flags images that exceed recommended sizes with an estimated load time saving. The recommendation to "serve images in next-gen formats" (WebP or AVIF) typically appears alongside the size recommendation — a compressed WebP is 25–35% smaller than a compressed JPG at the same visual quality. Optimizing images for website delivery means addressing both size and format together.
The best image size for website use depends on the image's role on the page. Hero images and full-width backgrounds: under 300 KB, ideally 100–200 KB. Inline content images (article photos, product images, feature graphics): under 100 KB each. Thumbnails and listing images: under 30 KB. Profile pictures and avatars: under 20 KB. Any single image over 500 KB will be flagged by PageSpeed Insights. Applying these targets before uploading is the most reliable way to reduce image size for SEO.
Reducing image size for website pages also reduces server bandwidth costs and improves loading for users on slow mobile connections. For ecommerce sites, where product pages may load 20–50 images simultaneously, the cumulative impact of compressing each image to under 100 KB is a page weight reduction of 2–4 MB per load. For ad-driven content sites, faster page speed improves ad viewability rates — because users reach the ads before bouncing.
This tool compresses images for web entirely in your browser. No file is uploaded to any server — all processing runs locally using JavaScript and the Canvas API. Upload any number of images in JPG, PNG, WebP, AVIF or HEIC format, set a target quality level, and download the compressed results individually or as a ZIP. Batch compress an entire image library before a site deployment, or optimize individual assets as part of a page build workflow.
You can also convert images to WebP for the best web format, resize images to exact dimensions before compressing, or compress JPGs specifically to target JPEG files.
- 1Upload your images
Drag and drop one or more image files onto the upload area, or click to browse. Supports JPG, PNG, WebP, AVIF and HEIC. Upload any number of files — all processing runs locally in your browser with no upload to any server.
- 2Set target quality
Adjust the quality slider to balance file size against visual quality. For web images, quality 75–85 delivers an optimal result — files small enough to meet Google's targets with no visible degradation. Check the before/after size numbers for each file.
- 3Compress all files
Click "Compress All" to process all files in parallel. Each image is compressed to the target quality level. Output file sizes and savings percentages are shown for every image. Images that are already under the target size are passed through unchanged.
- 4Download and deploy
Download compressed images individually or click "Download All" for a ZIP archive. Replace the original images on your server or CMS with the compressed versions. Run Google PageSpeed Insights after deployment to confirm LCP and image size improvements.
Who optimizes images for website performance — and why
Web developers — pass Core Web Vitals before launch
Every site deployment involves an image audit. Google PageSpeed Insights flags oversized images on nearly every site that has not compressed its assets. Compressing all images to recommended web sizes — hero images under 300 KB, inline images under 100 KB — resolves the "Opportunities" section of a Lighthouse report in one step. Batch compress the entire image library, download as ZIP and replace the originals on the server before going live.
Ecommerce — faster product pages reduce bounce rate
Product pages with 20–50 images per load are the most affected by image weight. An uncompressed smartphone photo at 4–6 MB creates a page that fails Core Web Vitals. Compressing each product image to under 80–100 KB reduces the total image payload of a product page from 100 MB to under 5 MB. Faster product pages reduce bounce rate, improve mobile search rankings and lower server bandwidth costs — all measurable improvements.
Content teams — optimize images for website blogs and landing pages
Blog posts and landing pages with multiple inline images benefit from per-image size optimization. A blog post with five 3 MB photos loads slowly on every device. Compressing each inline image to under 80 KB keeps the total page weight manageable while preserving visual quality that readers expect. Smaller uploads also mean faster CMS publishing workflows and lower cloud storage costs.
SEO and performance auditors — fix image issues from Lighthouse reports
Lighthouse and PageSpeed Insights reports frequently list image compression and next-gen format conversion as the top opportunities on client sites. Compressing images for page speed — specifically to hit the file size thresholds that eliminate Lighthouse flags — is a repeatable deliverable. Batch compress the flagged images, replace them on the site and document the before/after LCP improvement for the client.
Why use this tool to compress images for web
Page-speed-targeted compression, privacy-first processing, and batch capability — built for web optimization workflows.
Compress images to the sizes Google recommends for fast pages
Google's guidance on image optimization is specific: hero images should be under 300 KB, inline images under 100 KB, thumbnails under 30 KB. Compressing images to these targets directly improves Largest Contentful Paint (LCP) — a confirmed Google ranking factor. A 4 MB hero image takes roughly 4 seconds to load on a 4G connection. At 300 KB it loads in under 0.3 seconds. That difference is the gap between a user staying on the page and bouncing. Use this tool to hit Google's recommended file sizes before every site deployment.
Your images never leave your device
All compression runs locally in your browser using JavaScript and the Canvas API. No file is uploaded to any server, transmitted over a network or stored anywhere. The tool works without an internet connection after the initial page load. Safe for product images under NDA, personal photos and any content that cannot touch a third-party server.
Compress an entire website image library in one session
Upload as many images as needed — there is no batch size limit. All files are processed in parallel in your browser. When all files are done, download them individually or use "Download All" to get a ZIP archive. Compress an entire product catalog, blog image library or marketing asset folder before a site launch or deployment. No upload limits, no daily cap.
Complete guide — optimizing images for web performance and SEO
Why image size is the biggest factor in page load speed
On a typical web page, images account for 60–80% of total page weight. Text, CSS and JavaScript are rarely the bottleneck — images are. When a browser loads a page, it downloads every image in the viewport before it can render them. The heavier those images are, the longer the user waits. Google's Largest Contentful Paint (LCP) metric measures how long it takes for the biggest element on the page — usually a hero image — to fully render. LCP is a confirmed Google ranking factor: pages with slow LCP scores rank lower in mobile search results. Compressing images to recommended web sizes is the single most impactful step you can take to improve page speed, LCP and search visibility.
Target image sizes for web — what Google recommends
There are no official Google pixel-size mandates, but performance best practices are consistent across PageSpeed Insights, Lighthouse and Google Developers documentation. Hero and full-width background images should be under 300 KB, with a practical target of 100–200 KB for most use cases. Inline images (article photos, product images in listings, feature graphics) should be under 100 KB each, with a target of 30–80 KB. Thumbnails, avatars and icon-sized images should be under 30 KB. For most images on a website, 200 KB is the recommended upper limit. Hero images that genuinely require more detail should stay under 400 KB. Any single image over 500 KB is likely slowing your page and will be flagged by Google PageSpeed Insights as an optimization opportunity.
WebP vs JPG for websites — the format choice that saves 25–35%
WebP produces files that are 25–35% smaller than JPEG at the same visual quality — not by compressing harder, but through a fundamentally more efficient encoding algorithm. Google PageSpeed Insights explicitly flags pages that serve JPG as an opportunity to "serve images in next-gen formats." Switching from JPG to WebP at the same quality level is the easiest way to cut 25–35% from your image payload without any visible quality change. Browser support for WebP now exceeds 97% globally, covering all modern Chrome, Firefox, Safari, Edge and Opera versions. For web delivery, WebP is the recommended format. Use this tool to compress images and select WebP output for the best combination of compression and quality.
How to optimize images for Core Web Vitals and SEO rankings
Core Web Vitals are the three metrics Google uses to measure page experience: LCP (Largest Contentful Paint), INP (Interaction to Next Paint) and CLS (Cumulative Layout Shift). Of these, LCP is the most directly affected by image optimization. LCP measures how long the largest visible element takes to load — on most pages, this is a hero image or a large inline photo. To pass the LCP threshold Google considers "good" (under 2.5 seconds), the hero image must be small enough to download before the deadline. The practical workflow: compress every hero image to under 300 KB before upload, convert to WebP, and set explicit width and height attributes in the HTML to prevent CLS. Run Google PageSpeed Insights after each deployment to confirm the LCP score. Images flagged under "Opportunities" in Lighthouse are almost always over the recommended size thresholds.
Frequently asked questions — compressing images for web
For most web images: hero and full-width images should be under 300 KB (target 100–200 KB), inline content images under 100 KB, thumbnails under 30 KB. The practical upper limit for any single image on a web page is 200 KB. Hero images can go up to 400 KB if detail requires it. Any image over 500 KB will be flagged by Google PageSpeed Insights.
Google uses Largest Contentful Paint (LCP) as a ranking factor. LCP measures how long the biggest page element — typically a hero image — takes to load. Smaller images load faster, improving LCP. Google PageSpeed Insights also explicitly flags "serve images in next-gen formats" and oversized images as ranking opportunities. Fixing these issues directly improves your search visibility, especially on mobile.
WebP is the best image format for web delivery. It is 25–35% smaller than JPEG at the same visual quality, and browser support exceeds 97% globally. Google PageSpeed Insights recommends WebP (and AVIF) over JPG for web images. Use WebP for all images served on websites and web applications.
Compress images to the recommended file sizes for their role on the page, convert to WebP format, and set explicit width and height attributes in HTML to prevent layout shift. Run Google PageSpeed Insights after changes to confirm the impact on LCP and image-related opportunities.
Use this tool to compress images to under 200 KB (most images) or under 400 KB (hero images), then convert to WebP. These two steps — size reduction and format conversion — resolve the most common image-related items in a Google Lighthouse report and directly improve LCP.
Compress the hero image — the element most likely to be the LCP element — to under 200 KB. For a passing LCP score (under 2.5 seconds), the hero image must download fast enough to render within that window. On 4G, a 200 KB image takes approximately 0.2 seconds to download. A 4 MB image takes roughly 4 seconds — a guaranteed LCP failure.
Use quality 75–85 for most web images. At this level, the file size reduction is 60–80% compared to the original, but the visual difference is imperceptible to users in a browser context. Only quality settings below 60 introduce visible degradation.
Yes — completely free. No account, no payment, no watermark, no daily limit. Compress as many images as you want, always free.
Yes. All compression runs locally in your browser. Your files never leave your device. No server upload, no third-party access.
Yes. Upload any number of images and click "Compress All". All files are processed in parallel. Download individually or use "Download All" for a ZIP archive. No batch size limit.
Ready to optimize your images for faster web loading?
Compress Images for Web — Free