WebP conversion
Convert JPG, PNG and WebP files to modern WebP in one click, with transparency preserved where the source allows.
Image Compressor & WebP Converter
Compress JPG, PNG and WebP images, convert between formats, and see the size reduction instantly. Adjustable quality slider, transparency preservation where supported, and no uploads. Everything runs locally in your browser.
Image compressor and WebP converter tool
Private by design. Images are read from your device and processed entirely in the browser using the HTML5 Canvas API. Nothing is uploaded, stored, or logged on any server.
Drop your images here
or click to browse — you can select multiple files at once
JPG, PNG, WebP and GIF — up to ~25 MB per file recommended
Live preview
How to use the image compressor
- Add images. Drag and drop one or more images onto the drop zone, or click Choose images to browse. You can keep adding files later.
- Pick an output format. WebP gives the best compression with transparency. JPG is universally supported but flattens transparency. PNG is lossless.
- Adjust quality. Use the quality slider to trade off visual fidelity for file size. 80–92% is a good starting point for photographs.
- Compare before and after. Each card shows the original alongside the compressed version, with the exact size reduction.
- Download. Save individual files with the download button on each card, or click Download all to grab every compressed image at once.
Key features and benefits
Quality control
Fine-tune compression strength with a smooth slider. Preview the result instantly and see the size change before downloading.
Batch processing
Load multiple images at once, compress them all with one click, and download every result from a single button.
Before / after preview
See the original and compressed versions side by side with the exact file-size reduction percentage for each image.
Optional resizing
Set a maximum size for the longest side to shrink very large images while preserving their aspect ratio.
Fully private
All processing runs in your browser using the Canvas API. Images are never uploaded, stored, or logged anywhere.
Privacy and limitations
- Fully client-side. Images are read via the File API, drawn to a Canvas, and encoded with
canvas.toBlob(). Nothing is transmitted to any server. - No tracking of content. The tool does not record which images you load. There is no analytics on input or output.
- No automatic saving. Images are held in memory only. Reloading the page clears everything.
- Format support. Input: JPG, PNG, WebP, GIF (first frame) and any format the browser can decode. Output: WebP, JPG and PNG.
- Metadata is stripped. The Canvas API drops EXIF and other metadata during re-encoding, which reduces file size but also removes camera information and geolocation data. That is usually a privacy win.
- Large batches. Processing happens in memory. Very large images or batches of many files may be slow. For the smoothest experience, keep individual files under 25 MB and batches under 20 images.
Frequently asked questions
Are my images uploaded to a server?
No. All compression and conversion happens in your browser using the HTML5 Canvas API. Your images are never uploaded, stored, or logged.
What is WebP and why should I use it?
WebP is an image format developed by Google that offers better compression than JPG or PNG at similar quality, and it supports transparency. Browsers have supported it universally since 2020, which makes it a good default for modern websites.
Does compression reduce image quality?
Lossy compression reduces file size by discarding visual details that are hard for the human eye to notice. At quality 80–92 percent, most photographs are indistinguishable from the original, while file sizes drop by 50–80 percent. PNG output is lossless and preserves every pixel.
Will transparency be preserved?
Transparency is preserved when the output format supports it. PNG and WebP support an alpha channel, so transparent pixels remain transparent. JPG does not support transparency, so any transparent area becomes white when exporting to JPG.
Is there a file size or count limit?
You can load multiple images at once. Very large images or batches may be slow because all processing happens in memory. We recommend keeping individual files under about 25 MB and batches under 20 images for the smoothest experience.
Can I convert a PNG to JPG?
Yes. Select JPG as the output format and the tool will convert on download. Note that any transparency in the source PNG will be flattened against a white background because the JPG format does not support alpha channels.
A practical guide to image compression and WebP
Images are usually the largest asset on a web page, and they are often the easiest thing to optimize. A photograph exported straight from a camera might be several megabytes; the same photograph compressed with reasonable settings can often be under 300 KB with no visible difference on screen. Getting from one to the other is what an image compressor is for.
Why compression matters
Every kilobyte counts twice on the web: once when the file is downloaded and once when the browser decodes and renders it. Smaller images mean faster page loads, less bandwidth cost, better Core Web Vitals scores, and a better experience for users on slow connections or mobile data. A single hero image that drops from 2 MB to 300 KB can cut a page's load time by several seconds.
Lossy and lossless compression
There are two broad approaches. Lossy compression (used by JPG and WebP) reduces file size by discarding visual details that the human eye is unlikely to notice. The trade-off is controllable through a quality setting. At 80–92 percent, most photographs look identical to the original, but the file can be 5–10 times smaller. Lossless compression (used by PNG) reduces size without changing any pixel. The savings are smaller, but the result is mathematically identical to the source — which matters for screenshots, logos and images with sharp edges or text.
When to choose WebP
WebP was developed by Google and has been supported by every major browser since 2020. It offers two important advantages. First, at the same visual quality it typically produces smaller files than JPG — often 25–35% smaller. Second, it supports transparency like PNG, so it works for logos and graphics as well as photographs. For most modern websites, WebP is the right default. The main reasons to fall back to JPG or PNG are compatibility with very old software or a specific toolchain that does not yet accept WebP.
Why metadata disappears
When a browser re-encodes an image through the Canvas API, it drops EXIF metadata — camera information, timestamps, and (most importantly) GPS coordinates. This is usually a privacy win: an image that you post publicly no longer leaks where it was taken. If you need to preserve metadata, use a dedicated tool that copies it explicitly.
Common mistakes to avoid
- Compressing an already-compressed image. Re-saving a JPG at low quality again produces visible artifacts. Always start from the highest-quality source you have.
- Setting quality too low. Below 60%, artifacts become obvious, especially in gradients and skin tones. 80–92% is the sweet spot for photographs.
- Using JPG for text or logos. Sharp edges and flat colour are where JPG compression shows its worst. Use PNG or WebP for those.
- Forgetting to resize. A 4000-pixel-wide image displayed at 800 pixels wastes bandwidth. Resizing first, then compressing, gives the best result.
About this tool
This image compressor is part of the TempScript free online tools collection. It runs entirely in your browser, requires no account, and never sends your images anywhere. If you work with images and documents regularly, you may also find our PDF page organizer and social media image resizer useful.
© 2026 TempScript. All rights reserved.