Free browser tool
This converter re-encodes an image into a different container: JPEG for maximum compatibility, PNG for lossless pixels and transparency, WebP for the smallest files on the modern web. The before-and-after byte counts are shown so you can see whether the change was worth making.
It is useful when an upload form only accepts certain extensions, when a site needs lighter assets, when a logo has to sit on a background that JPEG cannot represent, or when a colleague sends a file in a format your software refuses to open.
Conversion runs on your own machine. The browser decodes the source, draws it into a canvas and re-encodes it with its built-in encoder — no server, no upload, no waiting in a queue.
One important caveat: every conversion re-encodes the pixels. Going to a lossy format costs a little quality, and going to a lossless one preserves whatever damage is already there without repairing it. Converting between lossy formats repeatedly is what visibly degrades an image.
Convert · format bridge
Drop an image here
Bring in a JPEG, PNG, WebP, GIF or BMP and export JPEG, PNG or WebP.
or paste with Ctrl / ⌘ + V
Step by step
Drop in a JPEG, PNG, WebP, GIF or BMP. The tool checks immediately whether it contains transparency.
Choose JPEG, PNG or WebP. The panel shows the conversion you are about to make and the resulting size.
If the source has an alpha channel and you are converting to JPEG, choose the colour those transparent pixels should be flattened onto.
For JPEG and WebP, adjust the encoder quality until the size is right, then save the converted file.
Practical guide
The three web formats were designed for different problems. Picking the right one usually saves more bytes than any amount of slider tuning.
JPEG has been the default for photographs since 1992 and is readable by essentially every device, printer and application ever made. It discards detail the eye is bad at noticing, which works beautifully for continuous-tone images and badly for hard edges.
Its two real limitations are the lack of an alpha channel and visible ringing around text and line art. Choose it when compatibility is the constraint, or when a system explicitly demands .jpg.
PNG reproduces every pixel exactly and supports a full 8-bit alpha channel, which makes it the right choice for logos, UI assets, diagrams, screenshots of text and any image that will be edited again later.
For photographs it is a poor fit: with millions of unique colours there is almost nothing for its lossless compressor to exploit, and files are routinely five to ten times larger than a visually identical WebP.
WebP offers both lossy and lossless modes plus transparency, and is supported by every current browser. In lossy mode it is typically 25–35% smaller than a JPEG of matching quality; in lossless mode it usually beats PNG by around 25%.
It is the right default for web delivery. The main reason to avoid it is a downstream system that does not accept the extension — some older desktop software, print workflows and email clients still reject it.
Every trip through a lossy encoder adds artefacts to artefacts. Converting JPEG to WebP to JPEG again is measurably worse than converting the original once, even though each individual step looked fine.
Keep a master file — ideally the original camera or design export — and generate each delivery format from that master. Convert once, from the best source you have.
Before you export
Honest limits matter more than a longer feature list. These are the trade-offs worth knowing before you download the result.
There is no way to move pixels between containers without running an encoder. Expect a small quality cost going into JPEG or WebP, and a size increase going into PNG.
Transparent pixels are flattened onto the colour you select. Choose the colour of the surface the image will sit on, or switch the target to PNG or WebP.
The tool can only convert what your browser can decode. HEIC, AVIF and RAW files may fail depending on the browser and operating system you are using.
Animated GIF and animated WebP sources are converted as a single still frame — the first one.
EXIF, XMP and ICC colour profiles are lost in conversion. For wide-gamut images that depend on an embedded profile, convert in colour-managed software instead.
Renaming a file from .png to .jpg does not convert it and often breaks the image. Real conversion means re-encoding, which is what happens here.
Questions
WebP is the best default on the modern web: it is supported everywhere that matters and is typically 25–35% smaller than an equivalent JPEG, with transparency support on top. Choose JPEG when a system is old or strict — some CMSs, print shops and email clients still expect it. Choose PNG when you need lossless pixels, transparency, or crisp text and line art.
No. PNG stores the JPEG's already-damaged pixels perfectly, including its compression artefacts, and usually produces a much larger file in the process. Converting to a lossless format preserves quality — it cannot restore it.
JPEG has no alpha channel, so transparent pixels must be given a colour. This tool detects an alpha channel automatically and asks which background to flatten onto. Pick the colour of the page the image will sit on, otherwise you get a visible rectangle around your logo.
Because you are re-encoding an already-compressed image. If the source JPEG was saved at a low quality and you convert at 100%, WebP faithfully encodes all the existing artefacts and spends bytes doing it. Drop the quality slider to around 80% and the size normally falls well below the original.
Only if your browser can decode them, which most cannot — HEIC works in Safari on Apple devices and RAW essentially nowhere. Export a JPEG or PNG from your photo app or camera software first, then convert that here.
No. The canvas holds one still frame, so an animated GIF is converted as its first frame only. For animation, convert to an animated WebP or MP4 with a dedicated video tool.
The conversion is performed by your browser's own image encoders, inside the page you are reading. Your file is never uploaded, so there is no server-side copy, no processing queue and no retention window to worry about.
The transparency check works the same way: a small sample of the decoded image is inspected in local memory to see whether any pixel is non-opaque. That inspection, like everything else here, happens on your device.