RESIZE · COMPRESS · CONVERT · WEBP

One Tool for Resizing, Compressing & Converting

Drop in a JPG, PNG, WebP or HEIC photo, pick a size and a quality level, and download — one file, a whole batch as a ZIP, or a WebP-optimized export. Everything runs in your browser, so nothing ever leaves your device.

calendar_monthUpdated: October 1, 2026 personBuilt by Khalil Rahman shield_lock100% client-side
cloud_upload

Drop an image or click to browse

JPG, PNG, WebP, HEIC

cloud_upload

Drop multiple images here

Select a whole folder at once

image

Drop images to convert to WebP

JPG / PNG → WebP (batch supported)

Everything above runs locally in this browser tab. No file is ever uploaded to a server.

verified_user

100% Private: Processing happens on-device via the HTML5 Canvas API. We can't see your images even if we wanted to.

⭐ Rate This Tool

How to Use It

1. Upload

Drop one image, or switch to Batch and select an entire folder at once. HEIC photos from iPhone convert automatically.

2. Choose size & quality

Pick a resize method, an output format, and drag the quality slider. The size comparison updates as you adjust it.

3. Download

Single images download immediately. Batch jobs package everything into one ZIP, in the order you arranged the thumbnails.

4. Nothing to clean up

Since no file ever left your browser, there's no server copy to worry about deleting afterward.

The Actual Cost of an Unoptimized Image

A camera photo straight off a phone is usually 3–8 MB and several thousand pixels wide — far more than any website, form, or inbox needs. That gap causes real, specific problems, not just an abstract "slow page":

Contact forms and CMS uploads reject the file

WordPress media libraries, job-application portals, and government forms often cap uploads at 2–5 MB. An unresized phone photo bounces with a generic "upload failed" error and no explanation why.

Email attachments get silently dropped

Gmail and Outlook both choke past 25 MB combined per message. A handful of full-resolution product photos in one email is enough to hit that ceiling without you noticing until the recipient says they never got it.

Page speed and Core Web Vitals take the hit

Images are typically the single largest thing loading on a webpage. An oversized hero image directly delays Largest Contentful Paint — the metric Google uses to judge how fast a page actually feels to a visitor.

Storage and bandwidth costs quietly add up

If you're running an online shop or a portfolio with hundreds of product images, the difference between 4 MB and 400 KB per photo compounds fast across hosting storage and CDN bandwidth bills.

Frequently Asked Questions

Resizing changes the pixel dimensions of an image. Compressing keeps the dimensions but reduces file weight by simplifying the data inside it. Converting changes the file format entirely, such as turning a PNG into a WebP. This tool does all three in one pass so you don't need three separate uploads.
No. Every operation runs inside your browser tab using the HTML5 Canvas API. Nothing is sent to a server, which is also why there's no file-count limit and no upload progress bar. Your images remain on your own device even after you close the tab.
Yes. Switch to Batch mode, select every file at once, and the tool queues them as draggable thumbnails you can reorder before processing. One click resizes and compresses the whole set into a single ZIP archive. This is designed for people who shoot products, real estate listings, or catalogue images in bulk.
Yes. HEIC files from iPhone are converted automatically before processing using a lightweight library that runs in the browser. This matters because most CMS platforms don't accept HEIC uploads, so converting here saves a whole extra workflow.
Most JPG and PNG photos can drop 60 to 80 percent in file size around a quality setting of 80 before the loss is visible on a normal screen. Below roughly 60 you'll start to see blocky artefacts around sharp edges and text.
WebP is a modern image format developed by Google that typically produces files 25 to 35 percent smaller than JPG at the same visible quality. It supports both lossy and lossless compression, and it handles transparency. Every major browser has supported WebP since around 2020.
Use JPG for photographs. Use PNG for graphics, logos, and images with transparency or sharp edges. Use WebP as a replacement for both when your audience is on modern browsers. A common pattern is to serve WebP as the primary format with a JPG fallback.
Google's Core Web Vitals use a metric called Largest Contentful Paint, which measures how long the main visible element of a page takes to load. On most websites that element is an image. Reducing that image's file size directly speeds up LCP, which feeds into Google's page experience signals.
No. JPG does not support transparency, so transparent areas will be filled with a solid colour. If you need transparency preserved, choose WebP or PNG as the output format instead.
For portfolio or print-adjacent use, use 90 to 95. For general website images, use 80 to 85. For thumbnails, blog images or email, use 70 to 80. For previews where file size dominates, 60 to 70 works.
It depends on the mode. Lossy WebP behaves like lossy JPG. Lossless WebP preserves exact pixels. At quality 80, lossy WebP is visually indistinguishable from the source.
Read our full guide: The Complete Guide to Image Optimization for 2026. It covers format choices, quality settings, platform-specific configuration for WordPress, Shopify and Webflow, and common mistakes.

Related Tools

Khalil Rahman
Written & tested by Khalil Rahman
Founder, SkillsInsider — DigiSkills.pk certified in SEO & Digital Marketing

I rebuilt this page by merging three overlapping resize/compress/convert tools we'd shipped separately, so there's one clear place for general image work. More about the team →