Saltar al contenido principal

Convertir imagen

Convert Image changes an image between JPG, PNG, WebP and AVIF in your browser. The conversion uses the browser's own codecs, and the one thing tools usually get wrong — converting a transparent image to a format with no alpha channel — is handled by painting a background you choose rather than letting transparency encode as black.

Solo local

La interfaz de esta herramienta está en inglés.

Drop images here

or drop anywhere on this page · Choose files · 100 MB

La guía de abajo solo está disponible en inglés.

How does Convert Image work?

Converting an image is a decode followed by an encode. The source is turned into raw pixels, and those pixels are written out under a different set of rules. Nothing is translated directly between formats, which is why a conversion is never entirely free and why the choice of target matters.

The transparency trap

JPEG has no alpha channel. When a PNG with a transparent background is converted to JPEG, those pixels have to become something, and a canvas that has not been painted is transparent black — so they become black. This is behind almost every “my logo came out on a black square” report on the internet.

The fix is one rectangle: fill the canvas with a chosen colour before drawing the image, so semi-transparent pixels composite against it properly instead of being interpreted as zero. That colour is a control here rather than a hard-coded white, because a logo built for a dark site needs a dark background and white would be just as wrong as black.

What each format is for

JPEG is lossy, universal, and has no transparency. It is built for continuous tone, which is why it is excellent on photographs and poor on text — its artefacts hide in detail and stand out against flat colour. Every device made in the last thirty years opens it, which is still the reason to choose it.

PNG is lossless and keeps transparency. Screenshots, logos, diagrams and anything with sharp edges belong here; a lossy format smears exactly the edges that make them readable. The cost is size: a photograph as PNG is often ten times the JPEG.

WebP is typically 25–35% smaller than JPEG at the same visible quality, supports transparency, and has a lossless mode that usually beats PNG. It is supported by every browser in current use and is the sensible default for the web now.

AVIF is smaller again — often 20–30% below WebP — and noticeably better at low bit rates, where JPEG falls apart. The costs are encoding time and availability: not every browser can produce one. This page tests that by encoding a 1 × 1 image before offering the option, rather than guessing from the user agent, which would be wrong within a year.

Lossy to lossless does not undo the loss

Converting a JPEG to PNG produces a lossless copy of an image that has already lost information. The artefacts are now preserved perfectly and the file is several times larger. It is occasionally the right move — if the image is about to be edited repeatedly, a lossless intermediate stops the damage compounding — but it is not a way to recover quality, and nothing is.

Going the other way costs a generation

Converting a JPEG to another JPEG, or to WebP, re-quantises data that was already quantised. Each pass adds artefacts on a block grid that may not line up with the previous one. Convert from the original whenever you have it.

What happens to metadata

Because the pipeline goes through raw pixels, EXIF blocks do not survive: camera model, timestamp and GPS coordinates are all dropped. For most uses that is a feature — a photo posted online carries its location otherwise. The single tag that is honoured rather than discarded is orientation, which is applied to the pixels during decoding so that a sideways-shot photo comes out upright.

Input

logo.png — 148 KB
transparent background
target: JPG, background #ffffff

Output

logo.jpg — 22 KB
white composited behind
alpha channel dropped

What options and edge cases does Convert Image support?

Formats
ParameterTypeDefaultBehaviour & edge cases
JPGlossy—Lossy, universal, and no transparency. Best for photographs, where its artefacts hide in the detail. Every device made in the last thirty years opens it.
PNGlossless—Lossless with transparency. Best for screenshots, logos and line art, where a lossy format smears the edges. Large for photographs.
WebPlossy / losslessdefaultTypically 25–35% smaller than JPEG at the same visible quality, with transparency and a lossless mode. Supported by every current browser.
AVIFlossy—Usually 20–30% smaller again than WebP, and much better at low bit rates. Encoding is slow and is not available in every browser, which the tool detects rather than assumes.
Quality0.1 – 1.00.85Applies to JPG, WebP and AVIF. PNG ignores it, being lossless.
Backgroundcolour#ffffffPainted behind the image when the target has no alpha channel. Prevents transparency encoding as black.
HEIC inputsupported—Decoded with libheif, loaded only when a HEIC is dropped. See the HEIC to JPG tool for detail.

Frequently asked questions

Why did my PNG turn black when converted to JPG?

Because JPEG has no alpha channel, and a transparent pixel drawn onto an unpainted canvas is transparent black — so the encoder writes black. It is the most common bug in browser image conversion and it has a one-line fix: paint a background before drawing the image. This tool does that, and lets you pick the colour, because a logo designed for a dark site needs a dark background and white would be just as wrong.

Which format should I convert to?

WebP for the web: 25–35% smaller than JPEG at the same visible quality, transparency included, supported by every current browser. JPG when the destination is a system you do not control — an old CMS, a print service, an email client. PNG for screenshots, logos and diagrams, where lossless matters more than size. AVIF when size is critical and you know the recipient can read it.

Will converting to PNG improve my JPEG?

No. It makes a perfect lossless copy of an image that has already lost information, at several times the file size — the JPEG artefacts are preserved in full fidelity. Nothing can recover detail a lossy encoder discarded. Converting to PNG is worth doing only when the image is about to be edited repeatedly and you want to stop the damage compounding across saves.

Can it convert HEIC files?

Yes. If the browser refuses the file and its bytes are a HEIF container, a WebAssembly build of libheif is loaded to decode it — and only then, so nobody converting a JPEG pays for that download. Safari decodes HEIC natively and never needs it at all. There is a dedicated HEIC to JPG page with more detail about why this is necessary.

Is there a limit on how many images I can convert?

100 files per selection, 100 MB per file and 250 MB in total — limits set by what a browser tab can hold rather than by a paywall, since everything runs on your machine. Files are processed one at a time instead of in parallel, deliberately: several large bitmaps alive at once is what actually kills a mobile tab.

Does the conversion strip EXIF and GPS data?

Yes, as an unavoidable consequence of decoding to pixels and re-encoding from them. Camera model, timestamp and GPS coordinates do not survive, which is usually what you want before posting an image publicly. Orientation is the exception: it is applied to the pixels rather than dropped, so a photo taken sideways is upright in the output instead of falling over.