Are my images uploaded to a server?

No. Every image is decoded, redrawn and re-encoded entirely inside your browser using the built-in Canvas API — the files never leave your device and are never transmitted anywhere. That makes this safe for private photos, ID documents, screenshots and confidential design assets you would not want to upload to a stranger’s server.

What happens to transparency when I convert a PNG or WebP to JPG?

JPEG has no alpha channel, so it cannot store transparency. When you convert a transparent PNG or WebP to JPG, the see-through areas are filled with a solid background colour first — white by default, but you can change it with the background-colour picker. If you need to keep transparency, convert to PNG or WebP instead, both of which support an alpha channel.

Does converting between formats lose quality?

Converting to PNG is always lossless — no detail is lost. Converting to JPG or WebP re-encodes the pixels with lossy compression, so there is some loss, controlled by the quality slider (80–90 is visually identical to the original for most photos). Converting a JPG to PNG will not restore detail that the original JPG already discarded — it just stops further loss and gives you a lossless copy.

Can I convert several images at once?

Yes. Drag in or select multiple files and they are all converted to the chosen format in one go. Each result has its own Download button, and the “Download all” button saves every converted image in sequence. Everything is processed locally, so a large batch is limited only by your device’s memory, not by an upload.

Why is my WebP file smaller than the JPG or PNG?

WebP uses more modern compression than JPEG (lossy) and PNG (lossless), so at the same visual quality it is usually 25–35% smaller. That is why it is the recommended format for websites. The trade-off is that some older software (and a few upload forms) still expect JPG or PNG, so check what the destination accepts before choosing WebP.

Does it remove EXIF and GPS metadata?

Yes. Re-encoding through the canvas produces a clean image with no EXIF block, so the camera model, capture date and GPS location embedded by your phone are stripped automatically. This is a privacy benefit when sharing photos online. Keep your original file if you need to preserve that metadata.

Image Format Converter

Convert images between PNG, JPG and WebP — drag in one or many files, pick the output format, and download. Everything runs in your browser; nothing is uploaded.

Drag images here or click to browse

PNG · JPG · WebP · GIF · BMP · AVIF — convert one or many at once

How image format conversion works

When you add an image, the browser decodes it into raw pixels with createImageBitmap(). The tool draws those pixels onto an HTML canvas at full resolution, then calls canvas.toBlob() with your chosen MIME type — image/png, image/jpeg or image/webp — to re-encode them in the new format. The browser’s own image codecs do the encoding, so the output is standards-compliant and the file never leaves your tab.

To PNG — lossless: the exact pixels are preserved, including transparency.
To JPG — lossy: pixels are re-compressed at your quality setting, and any transparency is flattened onto the background colour you pick (white by default).
To WebP — lossy at quality < 100, with transparency kept. Usually the smallest file of the three at a matching quality.

PNG vs JPG vs WebP — which should you choose?

Format	Compression	Transparency	Animation	Best for
PNG	Lossless	Yes	No (APNG rare)	Logos, icons, screenshots, line art, anything needing transparency or pixel-perfect text.
JPG / JPEG	Lossy	No	No	Photographs and complex images where a small quality trade-off for a much smaller file is fine. Required by most exam / government upload forms.
WebP	Lossy or lossless	Yes	Yes	Modern websites — typically 25–35% smaller than JPG/PNG at the same quality, with transparency support. Backed by all current browsers.

Rule of thumb: WebP for your own website (smallest), PNG when you need transparency or crisp text, and JPG for photographs and anywhere a form demands it.

Common conversions

PNG to JPG — shrink a large screenshot or export for an upload form that only accepts JPEG. Remember the background colour replaces any transparency.
WebP to PNG — turn a downloaded WebP into a universally-supported PNG for older software or editors that can’t open WebP.
WebP to JPG — convert a modern web image into a JPEG for email, messaging or a legacy CMS.
JPG to WebP — re-encode photos to WebP to cut page weight and improve Core Web Vitals on your site.
JPG to PNG — get a lossless copy to edit without compounding JPEG artefacts (it won’t recover detail the JPG already lost).

Tips for the best results

Need a smaller file, not a new format? Use the Image Compressor or Compress to Target Size to hit an exact KB limit.
Need different dimensions? Convert here, then resize — or resize first if you’re also changing pixel size.
iPhone HEIC photos? Use the dedicated HEIC to JPG converter — HEIC needs a special decoder that this tool doesn’t bundle.
Quality 80–90 for JPG/WebP photos is visually identical to 100 but far smaller. Drop lower only when you must hit a tight size budget.
Keep transparency? Convert to PNG or WebP, never JPG.

A short field guide to the formats

Every format you convert between was invented to solve a specific problem, and knowing the backstory makes choosing one obvious.

GIF (1987) — created by CompuServe, led by Steve Wilhite. It introduced web animation and simple on/off (1-bit) transparency, but its palette is limited to 256 colours. It uses LZW compression, and the patent on LZW (held by Unisys) is the very reason PNG was created. Those patents expired by 2004; today GIF is really only worth using for short legacy animations.
JPEG (1992) — the ISO/IEC 10918 standard from the Joint Photographic Experts Group. Its lossy, photo-oriented compression made digital photography practical and it has been universally supported for over three decades, which is why upload forms still ask for it.
PNG (1996) — a W3C Recommendation built by a volunteer group specifically as a royalty-free replacement for GIF when Unisys began enforcing the LZW patent. It is lossless, supports a full alpha channel and truecolour, but has no native animation.
WebP (2010) — Google's format, derived from the VP8 video codec. It does lossy and lossless, supports transparency in both modes, and adds animation — a genuine all-rounder.
AVIF (2019) — the newest of the group, built on the royalty-free AV1 video codec by the Alliance for Open Media. It typically compresses better than everything above and adds HDR, wide colour and up to 12-bit depth.

You will also meet BMP (Microsoft's old uncompressed bitmap, large but lossless) and TIFF (a flexible container Aldus created in 1986, still the archival favourite in print and scanning).

What lossy compression actually does

JPEG, WebP and AVIF are lossy: they throw away detail your eye is unlikely to notice in exchange for dramatically smaller files. JPEG is the clearest example. It splits the image into 8×8 pixel blocks, runs each through a discrete cosine transform (DCT) to express it as frequencies, then quantises those frequencies — discarding the fine ones. The "quality" slider is really controlling how aggressively that quantisation happens. It also uses chroma subsampling (typically 4:2:0): because we perceive brightness far more sharply than colour, JPEG keeps full brightness detail but halves the colour resolution.

That design has visible consequences. At low quality you see blocking (the 8×8 grid becomes apparent) and ringing or "mosquito noise" — shimmering speckles around sharp edges and text. It is exactly why JPEG is poor for screenshots, logos and line art, where edges are everything. Two more facts worth knowing:

Generation loss is real. Every time you open and re-save a JPEG it is decoded and re-quantised, so artefacts compound. Editing a photo over several JPEG saves visibly degrades it; work in a lossless format and export to JPEG once at the end.
Converting a JPEG to PNG cannot un-lose detail. A PNG copy of a JPEG is lossless from that point forward, but it preserves the artefacts the JPEG already baked in — it just stops them getting worse.
Progressive JPEG stores the image as coarse-to-fine scans, so a blurry preview appears quickly and sharpens — handy on slow connections at a similar file size to baseline.

Colour depth and the alpha channel

"Transparency" is one column in the comparison table above, but the underlying differences run deeper. PNG can store an image as an indexed palette (up to 256 colours, like GIF), as 24-bit truecolour (8 bits each for red, green and blue — about 16.7 million colours), or as 32-bit RGBA, which adds an 8-bit alpha channel for smooth, variable transparency. That variable alpha is why a PNG logo can have a soft, anti-aliased edge that blends onto any background.

JPEG, by contrast, is always 8 bits per channel and has no alpha channel at all — it simply cannot store transparency. That single limitation is the reason this converter has to flatten see-through pixels onto a background colour when you convert to JPG. WebP and AVIF sidestep the whole problem: both keep an alpha channel even in their lossy modes, so they give you transparency and small files.

AVIF, WebP and the modern web

For your own website, the newer formats are a clear win. Google reports WebP files are commonly around 25–34% smaller than JPEG at matching quality, and web.dev notes AVIF can be more than 50% smaller than JPEG in some cases, with fewer blocking artefacts and less colour bleeding around hard edges. Smaller images load faster, and since an image is frequently the page's Largest Contentful Paint element, choosing a modern format directly improves that Core Web Vital.

Browser support is no longer the obstacle it once was. WebP works in every current browser (Safari added it in 2020). AVIF is supported in Chrome, Firefox, Safari and — more recently — Edge, covering the large majority of users. So why not convert everything to AVIF? A few honest reasons: some older software, image editors, content management systems, email clients and upload forms still don't accept WebP or AVIF, and AVIF encoding is slower and more CPU-hungry. The safe pattern is to serve modern formats with a fallback rather than forcing one everywhere:

Goal	Best choice
Smallest file on your own site	AVIF, with a WebP or JPEG fallback
Transparency or crisp text / logos	PNG, or lossless WebP
A photo for email, messaging or an upload form	JPG (universally accepted)
Maximum compatibility, no questions asked	JPG (photos) or PNG (graphics)

The clean way to deliver them is the HTML <picture> element. List your modern sources with a type attribute and let the browser pick the first one it understands, falling through to a universal <img>:

<source type="image/avif"> — used by browsers that support AVIF
<source type="image/webp"> — the next fallback
<img src="photo.jpg"> — the guaranteed default for everything else

That gives modern visitors the smallest file while everyone else still sees the image — and the conversions you do here are how you generate those alternate sources.

Why a "converted" file can come out bigger

Conversion changes the container and compression scheme, not the image's inherent complexity — so the file size can go either way, and people are often surprised when it grows. The usual culprits:

Photo to PNG. PNG is lossless, so it has to record every subtly different pixel of a photograph faithfully. A 200 KB JPEG photo can balloon to several megabytes as a PNG. PNG shines on flat graphics and text, not continuous-tone photos.
Quality set too high. A JPG or WebP at quality 100 keeps detail you can't see and bloats the file. For photos, quality 80–90 is visually identical and far smaller.
Already-optimised source. If the original was already well-compressed, re-encoding to another lossy format may not help and can even add a little overhead.

The fix is to match the format to the content: keep photos in a lossy format (JPG, WebP or AVIF), reserve PNG for graphics and transparency, and reach for the dedicated Image Compressor when your real goal is a smaller file rather than a different format.

Animation: GIF, APNG, WebP and AVIF

Only some of these formats can move, which matters if your source is animated. GIF was the original animated web format, but it is capped at 256 colours per frame and produces large files. PNG has no animation in its core spec — that requires the separate APNG extension. Both WebP and AVIF support full-colour animation at a fraction of GIF's size, which is why short looping clips are increasingly served as animated WebP. A practical caveat for this and any canvas-based converter: redrawing through a canvas captures a single frame, so converting an animated GIF to a static format keeps only one frame. To preserve motion, keep it in an animation-capable format end to end.

EXIF, GPS and the privacy angle

Photos straight from a phone or camera carry a hidden block of EXIF metadata: the camera and lens model, the exact date and time, the settings used — and frequently the GPS coordinates of where the shot was taken. That location data is a genuine privacy risk when you post a photo publicly, because it can reveal your home or a child's school. A useful side effect of re-encoding through the browser's canvas, the way this tool works, is that the output is a clean image with no EXIF block — the camera details and GPS location are stripped automatically. That is a privacy win when sharing online. The flip side: if you actually need that metadata (for cataloguing or copyright), keep your original file, because the converted copy won't have it.

Choosing a quality setting without guessing

The quality slider only applies to the lossy formats — JPG and WebP; PNG ignores it entirely because it is always lossless. For those lossy formats, a few rules of thumb take the guesswork out of it:

80–90 is the sweet spot for photos. The result is visually indistinguishable from quality 100, but the file is dramatically smaller. The last ten points on the slider add a lot of bytes for detail almost no one can see.
Below roughly 70, artefacts appear. You start to see blocking and the shimmering "mosquito noise" around edges — and they show up worst on text, logos and sharp lines, so drop this low only when you must hit a strict size budget.
WebP and AVIF degrade more gracefully than JPEG at low quality, so if you need an aggressively small file they hold detail better.
For graphics, screenshots and anything with crisp text, don't use a high-quality JPEG at all — choose PNG or lossless WebP. No JPEG quality setting handles hard edges as cleanly as a lossless format.

In short: lossy quality is a dial for photographs, where a little imperceptible loss buys a much smaller file. For everything edge-heavy, the format choice matters more than the slider.

Frequently asked questions

Are my images uploaded to a server?: No. Every image is decoded, redrawn and re-encoded entirely inside your browser using the built-in Canvas API — the files never leave your device and are never transmitted anywhere. That makes this safe for private photos, ID documents, screenshots and confidential design assets you would not want to upload to a stranger’s server.
What happens to transparency when I convert a PNG or WebP to JPG?: JPEG has no alpha channel, so it cannot store transparency. When you convert a transparent PNG or WebP to JPG, the see-through areas are filled with a solid background colour first — white by default, but you can change it with the background-colour picker. If you need to keep transparency, convert to PNG or WebP instead, both of which support an alpha channel.
Does converting between formats lose quality?: Converting to PNG is always lossless — no detail is lost. Converting to JPG or WebP re-encodes the pixels with lossy compression, so there is some loss, controlled by the quality slider (80–90 is visually identical to the original for most photos). Converting a JPG to PNG will not restore detail that the original JPG already discarded — it just stops further loss and gives you a lossless copy.
Can I convert several images at once?: Yes. Drag in or select multiple files and they are all converted to the chosen format in one go. Each result has its own Download button, and the “Download all” button saves every converted image in sequence. Everything is processed locally, so a large batch is limited only by your device’s memory, not by an upload.
Why is my WebP file smaller than the JPG or PNG?: WebP uses more modern compression than JPEG (lossy) and PNG (lossless), so at the same visual quality it is usually 25–35% smaller. That is why it is the recommended format for websites. The trade-off is that some older software (and a few upload forms) still expect JPG or PNG, so check what the destination accepts before choosing WebP.
Does it remove EXIF and GPS metadata?: Yes. Re-encoding through the canvas produces a clean image with no EXIF block, so the camera model, capture date and GPS location embedded by your phone are stripped automatically. This is a privacy benefit when sharing photos online. Keep your original file if you need to preserve that metadata.