How to Compress Images Online for Free, Without Uploading

By Alex Johnson. Image file sizes were one of those problems I kept running into when building web projects. A designer sends over a 4MB hero image, the client wants it on the homepage, and PageSpeed Insights immediately flags it as the number one performance issue. Most online compressors I tried uploaded the image to their servers, which felt wrong for client work. So I built one that runs entirely in your browser. Here is the complete guide to image compression and when to use each format.

Image compression is one of the highest-impact fixes for a slow website. Images are usually the heaviest files on a page, and the largest one often decides how quickly the page appears to load. Compressing images before you upload them is the quickest way to make a page lighter without touching any code.

Why image compression matters more than most people think

Speed matters most on phones. Google's 2016 study The Need for Mobile Speed found that 53% of mobile site visits were abandoned when a page took longer than three seconds to load. Networks are faster now, but photos have grown too, and an uncompressed phone photo can easily run to several megabytes.

For context on file sizes: a typical smartphone camera produces JPEG photos between 3MB and 8MB. A professional camera raw file can be 25MB or more. A website image serving at that size would cause even a fast broadband connection to stall visibly. The target for a hero image on a website is generally under 200KB. A product image thumbnail should be under 50KB. Compression gets you there.

Google's PageSpeed Insights, a free tool for testing page performance, flags images that are larger than they need to be, either because of the format or because they could be compressed further. Heavy images slow down Largest Contentful Paint, one of the Core Web Vitals that Google uses as a page experience signal.

JPEG vs PNG vs WEBP: which format to use

Choosing the right format before compressing is as important as the compression itself. Using PNG where JPEG would do is a common mistake that produces files 3-5x larger than necessary.

JPEG: the default for photographs

JPEG uses lossy compression: it permanently discards some image detail to make the file smaller. It is tuned for photographs, where the eye is least likely to notice the loss. At quality settings around 80, the file is usually a fraction of the size of a maximum-quality save, and most people cannot tell the two apart at normal screen sizes. The live preview in the compressor shows the exact size for your image before you download.

Use JPEG for: photographs of people, places, and products; hero images and background images; any image where transparency is not needed.

Avoid JPEG for: logos, icons, screenshots with text, images with sharp edges or flat colors. JPEG's compression artifacts are visible on these.

PNG: lossless, with transparency

PNG uses lossless compression: all pixel data is preserved exactly. PNG files are larger than equivalent JPEG files for photographs, but PNG supports transparency (alpha channel) and handles sharp edges, text, and flat colors without artifacts.

Use PNG for: logos and icons, screenshots containing text, images requiring transparency, UI elements, anything where pixel-perfect quality is required.

Avoid PNG for: photographs on web pages where file size matters. A photo saved as PNG is usually several times larger than the same photo as a JPEG.

WEBP: the modern choice

WEBP was developed by Google and released in 2010. It supports both lossy and lossless compression. Google's WebP documentation reports lossy WEBP files 25 to 34% smaller than comparable JPEGs, and lossless WEBP files 26% smaller than PNGs. Every current major browser supports it, including Safari since version 14 in 2020.

Use WEBP for: any web image where broad browser support is acceptable and smaller file sizes are important. WEBP is becoming the default recommendation for new web projects.

Avoid WEBP for: images that need to open in non-browser software (Office, older image editors) or be sent to people who might not use a modern browser.

What quality setting should you use?

The quality slider in the Virtual Text Tools image compressor controls how aggressively the algorithm discards data. Higher quality means larger files and less visual change. Lower quality means smaller files and more visible compression.

Industry-standard recommendations by use case:

• Website hero images and featured photos: 75-85% JPEG or WEBP. Lighthouse, the engine behind Google PageSpeed Insights, estimates potential savings by re-encoding JPEGs at quality 85, which makes that a sensible default. Dropping from 100% to around 80% usually cuts the file size dramatically with no visible loss.
• Product images and portfolio photos: 80-90%. Slightly higher quality since users inspect these closely.
• Thumbnails and previews: 60-75%. At small display sizes, lower quality is barely perceptible.
• Images for email: 70-80%. Email clients impose size limits; aggressive compression helps delivery.
• Social media uploads: 80-90%. Platforms recompress on their end anyway, so starting at high quality gives the algorithm more to work with.
• Images for print (PDF, document): 90-100%. Print requires higher fidelity; file size matters less.

How to compress an image online: step by step

1. Use the image compressor at the top of this page
2. Drag and drop your JPEG, PNG, or WEBP image, or click to browse
3. Your original image appears on the left with its dimensions and file size
4. Adjust the Quality slider: the compressed preview updates in real time
5. Choose your output format: JPEG (smallest, photographs), PNG (lossless), or WEBP (modern, very small)
6. The green badge shows how much smaller the compressed file is compared to the original
7. Click Download to save the compressed file

Compression vs conversion: understanding the difference

Compression and format conversion are related but different operations. Compression reduces the data within a format (a JPEG at 80% quality vs 100% quality). Conversion changes the format itself (JPEG to PNG, or PNG to WEBP).

Often the biggest saving comes from changing format rather than quality. A photo that was saved as PNG can shrink to a small fraction of its size as a JPEG or WEBP, because PNG stores every pixel exactly. Lowering JPEG quality from 100% to 80% helps too, but less. For web use, the format matters as much as the quality setting.

Privacy: why browser-based compression matters

Many popular compressors, including TinyPNG and iLoveIMG, upload your image to their servers to process it. (Google's Squoosh is an exception: it also runs in the browser.) For most personal photos, uploading is fine. But for:

• Client work under NDA
• Screenshots of internal systems or dashboards
• Product images before a public launch
• Images of ID documents or sensitive personal materials

...uploading to a third-party server is a real risk. Virtual Text Tools compresses images using the HTML5 Canvas API: the image is loaded into browser memory, processed, and exported without any network request containing your image data. You can verify this in your browser's developer tools (Network tab): zero outgoing image data.

Frequently asked questions

Does compressing an image reduce quality?

JPEG and WEBP compression is lossy: some data is permanently discarded. At 80% quality, most people cannot see the difference at normal screen sizes. PNG compression is lossless: no quality is ever lost, but file size reduction is smaller.

What is the best quality setting for website images?

75-85% for photographs. Lighthouse, which powers PageSpeed Insights, uses quality 85 when it estimates how much smaller your JPEGs could be. At around 80%, most photos lose a large share of their file size with no visible difference at normal screen resolutions.

Is it safe to compress images with Virtual Text Tools?

Yes. All compression happens locally in your browser using the Canvas API. Your images are never uploaded to any server and never leave your device.

What is the difference between JPEG and WEBP compression?

Both use lossy compression, and WEBP is more efficient. Google reports lossy WEBP files 25 to 34% smaller than JPEG at comparable quality. Every current browser supports WEBP, but some older software, including older versions of Microsoft Office, cannot open it.

Can I compress a PNG image?

Yes, in two ways. Saving as PNG again keeps every pixel, so the quality slider has no effect and the saving is small; sometimes the file even gets bigger. Converting to WEBP usually shrinks it far more and keeps transparency. Converting to JPEG also shrinks it a lot, but transparent areas become white.