Image Converter

Use this image converter to change one image up to 50 MB into JPG, PNG, WebP, AVIF, GIF, TIFF, BMP or ICO locally in your browser.

Drop files here or choose files
JPG, PNG, WebP, AVIF, GIF, TIFF, BMP, ICO, SVG, HEIC · one image up to 50 MB · stays on your device
Target format
Fill color for transparent areas

JPG and BMP can't store transparency, so transparent areas are filled with this color.

How to use

  1. Choose one image: Drop a file onto the box or click to pick it. JPG, PNG, WebP, AVIF, GIF, TIFF, BMP, ICO, SVG and HEIC/HEIF are accepted, up to 50 MB, one picture at a time. The page names the format it recognized and the pixel size it measured.
  2. Pick the target format: Press one of the eight buttons under Target format: JPG, PNG, WebP, AVIF, GIF, TIFF, BMP or ICO. JPG is selected by default. If you choose JPG or BMP, a Fill color for transparent areas picker appears, because neither format can store transparency.
  3. Convert and save: Click Convert image. You get the source and target format, the output pixel size and the file size before and after, plus a preview. Download keeps the original name and swaps the extension — photo.webp converted to JPG arrives as photo.jpg. On a phone the result goes through the system share sheet when the browser supports sharing files, and is downloaded otherwise.

How this image converter works

This image converter rewrites one picture in a different file format. Ten formats can go in — JPG, PNG, WebP, AVIF, GIF, TIFF, BMP, ICO, SVG and HEIC/HEIF — and eight can come out: JPG, PNG, WebP, AVIF, GIF, TIFF, BMP and ICO. SVG and HEIC are input-only, so you can turn an iPhone HEIC photo into a JPG but not the other way round. The picture itself is left alone: the content and the pixel dimensions are carried over unchanged, with the single exception of ICO, which is capped at 256 px on its longest side.

Nothing is uploaded. The main engine is libvips compiled to WebAssembly (wasm-vips), which is downloaded with the page and run by your own browser; Apple's HEIC and HEIF photos go through libheif instead, and BMP and ICO are handled by small hand-written JavaScript codecs. The browser isolation that engine needs also blocks third-party scripts, which is why this page carries no ads and no analytics. The converted file is a temporary link inside the page, so closing or reloading the tab discards it — download it before you leave, and expect to pick the format again next time, as the tool keeps no history.

The format is identified from the file header, not from the extension. A photo saved as .jfif, or a WebP someone renamed to .jpg, is still recognized correctly. Two limits apply: 50 MB per image, which the drop box enforces before anything is decoded, and roughly 100 megapixels — about 10000 × 10000 — beyond which the decoder refuses the picture rather than exhausting the browser's memory.

Which format to convert to

JPG — forms and email
PNG — transparency and screenshots
WebP/AVIF — smaller web images; compare the result
ICO — one icon size, longest side ≤256 px

Measured with Node 22, wasm-vips 0.0.18 and this tool's fixed settings; output sizes are sample results, not guaranteed savings.

800 × 600 PNG, 214,657 B
JPG 207,273 B (−3.4%)
WebP 162,224 B (−24.4%)
AVIF 128,702 B (−40.0%)
GIF 281,317 B (+31.1%)
TIFF 346,032 B (+61.2%)
BMP 1,440,054 B (+570.9%)
PNG rewritten 617,284 B (+187.6%)
ICO 143,806 B (−33.0%, scaled to 256 × 192)

1200 × 800 JPG, 541,541 B
JPG 401,680 B (−25.8%)
WebP 322,650 B (−40.4%)
AVIF 262,766 B (−51.5%)
GIF 611,517 B (+12.9%)
TIFF 2,518,866 B (+365.1%)
BMP 2,880,054 B (+431.8%)
PNG 1,997,583 B (+268.9%)
ICO 130,339 B (−75.9%, scaled to 256 × 171)

For anything going onto the web, WebP and AVIF are usually the smallest of the eight. Both are modern lossy encoders, and this tool writes them at fixed settings (quality 85 for JPG and WebP, quality 72 for AVIF; GIF uses the encoder's default settings), so the saving comes from the format rather than from a slider. On the two test images above, WebP landed 24% and 40% below the original and AVIF 40% and 52% below. AVIF is also by far the slowest of the eight to encode — tens of times slower than WebP on the same picture in our tests — so a large photo takes visibly longer on a phone than on a laptop.

BMP and TIFF normally go the other way. A 24-bit BMP stores three raw bytes per pixel and compresses nothing at all, so its size is close to width × height × 3 regardless of what the picture looks like: the 800 × 600 test image became 1.44 MB. TIFF is written with lossless LZW compression here, which has very little to work with on a photograph and grew the same samples by 61% and 365%. Both are worth asking for when a scanner, a print workflow or an old Windows application demands them — not when you want a smaller file.

Converting a lossy picture into a lossless container does not undo the loss. A JPG that is already missing detail becomes a PNG or a TIFF that stores that same missing detail pixel by pixel, usually at several times the size — the 541 KB test JPG came back as a 1,997,583-byte PNG, 269% larger, and looked no better. Go the other way if size is the problem, and keep PNG for screenshots, logos, line art and anything that needs transparency, where it genuinely wins.

There is no quality slider, no dimension field and no target size here: the encoder settings are fixed so that the only decisions are the format and, for JPG and BMP, the fill color.

To choose the quality yourself, or to convert and shrink in one step, use Compress Image instead.

What a format change decides for you

Transparency survives everywhere except JPG and BMP. PNG, WebP, AVIF, GIF, TIFF and ICO results keep the alpha channel as it was — in our tests a half-transparent PNG came back with its transparent pixels still fully transparent, even when a fill color had been chosen. JPG and BMP have no alpha channel at all, so transparent areas are filled with the color in the Fill color for transparent areas picker, white by default, and that step cannot be undone afterwards. Pick the color deliberately when the logo or sticker is going onto a colored background.

Embedded photo data travels with the picture almost everywhere, which means converting is not a way to strip it. BMP output contains no metadata — its encoder writes pixels only — and a GIF has nowhere to store any. Everything else can carry the EXIF block and XMP into the new file: JPG, PNG and WebP plainly do, AVIF keeps the EXIF and the XMP, TIFF keeps the XMP, and ICO wraps a PNG that can retain EXIF, including GPS and orientation. Do not use conversion to remove private data.

That is measured, not assumed. A test photo kept its GPS coordinates (3.108, 101.637), its capture time of 2026-05-01 10:20:30 and the device name Apple iPhone 15 Pro through the JPG, PNG and WebP conversions; the same photo converted to ICO still had all three inside the embedded PNG, and the AVIF and TIFF results still carried the coordinates. Only the BMP and GIF results came back with nothing. The page reports what it can actually verify: it reads the finished file back — the embedded PNG in the ICO case — and says nothing at all about containers it cannot read, rather than presenting an unreadable file as a cleaned one.

To remove the location or the whole EXIF block deliberately, use the Photo info (EXIF) option in Compress Image, which can clear the location alone or everything. Converting to BMP does drop the metadata as a side effect, but it costs you transparency and a much larger file — so it is a poor way to go about it.

Two more things change quietly. An animated GIF or animated WebP is decoded as a single picture, so the result is a still image with no animation left, and choosing GIF as the target also produces one still frame rather than an animation. An orientation tag is never written into the pixels either: the rotation is not applied, so the width and height stay as they were. Whether the tag itself reaches the new file depends on the target — JPG, PNG, WebP, TIFF and ICO results carry it along, while BMP and GIF drop it with the rest of the metadata and AVIF keeps the EXIF but not that tag. Since some viewers ignore the tag and show the photo sideways anyway, open the downloaded file in the app you actually need it in before you rely on it; the page flags the tag whenever the picture you chose has one.

The picture is not cropped, sharpened or watermarked. Pixel dimensions stay unchanged except when ICO output requires scaling the longest side down to 256 px. The file bytes do change, though, because the image is decoded and re-encoded at this tool's fixed settings — so the file size moves even when you convert a JPG to a JPG.

HEIC, SVG and ICO: the three special cases

HEIC and HEIF photos from an iPhone are decoded by libheif rather than by the main engine. The reason is narrow and worth knowing: the wasm-vips build used here only carries the AV1 decoder, while Apple's HEIC files are HEVC, so the main engine alone fails on them. With libheif in place, the practical route for a photo that a website or an older Windows PC refuses is HEIC in, JPG or PNG out. There is no HEIC output — nothing on this page writes that format.

An SVG is rasterized, not reinterpreted. It is rendered at the width and height the file itself declares, so a drawing marked width="120" height="80" becomes a 120 × 80 PNG, and enlarging that result later makes it blurry in a way the original SVG never was. For a crisp bitmap at a specific size, edit the width and height inside the SVG first and convert afterwards. Going back — bitmap to SVG — is not something this tool can do, because the vector shapes no longer exist once a picture has been turned into pixels.

ICO comes with two rules. The longest side is capped at 256 px and larger pictures are scaled down proportionally, always, not as an option you can switch off: the 800 × 600 test image came back as a 256 × 192 icon, and the page says so when it has scaled something. The icon holds a single size, wrapped as a PNG inside the ICO container, which keeps transparency — so it is a usable favicon or folder icon, but it is not a multi-size pack with 16, 32 and 48 px entries bundled together. A multi-size ICO dropped in as the *input* is read by taking its largest entry and ignoring the rest.

Limits worth knowing before you start

One image per run. Once a picture is loaded the drop box is gone, replaced by a row with the file name, so moving on to a different image starts with the ✕ (Remove) button beside that name — or with Start over once a result is on screen. Dropping several files at once adds none of them and the page says how many it turned away, so a folder of pictures has to go through one at a time: there is no batch mode and no folder mode. The conversion also runs on the page's main thread, which is why the button reads Converting… and is disabled until the picture is ready.

Only three of the common formats are off the menu as targets, and for solid reasons: SVG (pixels cannot be turned back into vectors), HEIC (nothing here writes it) and PDF (a different kind of file altogether). BMP support is also narrower than the format's full history — 24-bit and 32-bit BI_RGB, 32-bit BI_BITFIELDS and 8-bit palette files are read, while RLE-compressed BMPs, OS/2 headers and 1-bit or 4-bit files report a failure instead; BMP output is 24-bit only. ICO input is limited to PNG entries and 32-bit or 24-bit DIB entries.

A broken file usually announces itself: when the header is not an image the tool can read, you get a message saying the file is not a valid image or is damaged. Truncated pixel data is the awkward case — a PNG that was cut off halfway can still decode into a half-gray picture without any error, so look at the preview before you trust the result. If the picture is simply enormous, the pixel limit (about 100 megapixels) stops it rather than the file size limit.

When a form insists on a file under a specific number of kilobytes, convert first and then use Compress Image to Size.

Frequently asked questions

How do I convert a HEIC photo from my iPhone to JPG?
Drop the .heic or .heif file in, press JPG and click Convert image. HEIC photos are decoded by libheif inside your browser, because the main image engine on this page only handles AV1 and Apple's files are HEVC. One photo per run, up to 50 MB. The reverse is not possible here: HEIC can be read but not written.
How do I convert WebP to JPG?
Choose your WebP file, select JPG and click Convert image. Transparent areas use your chosen fill color, which defaults to white.
How do I convert SVG to PNG?
Choose the SVG file, select PNG and click Convert image. The SVG is rasterized at its declared dimensions; this tool has no output-size control.
Does converting an image remove its GPS location?
Usually not. JPG, PNG and WebP results carry the original EXIF block and XMP along, including GPS coordinates, capture time and device name — a test photo kept all three through those three conversions. ICO wraps a PNG that can retain EXIF, including GPS and orientation, and the AVIF and TIFF results kept the coordinates too, so none of those clean a photo. BMP output contains no metadata, and a GIF cannot store any. The page reads the finished file back where it can and stays quiet about containers it cannot read. To strip the location on purpose, use the Photo info (EXIF) option in Compress Image.
Can I convert several images at once?
No, one image per run. Drop several files at once and none of them is added — the page tells you how many it turned away and asks for a single file. While an image is loaded there is no drop box either, so the next one begins with the ✕ (Remove) button next to the file name, or with Start over after a result. A folder of photos therefore goes through one by one; for a whole batch in one command you need a desktop or command-line tool.
Should I convert to WebP or AVIF for my website?
AVIF was the smaller of the two on both of our test images (40% and 52% below the original, against 24% and 40% for WebP), but it is also the slowest format here to encode, noticeably so on a phone with a large photo. WebP is the safer default for everyday use; reach for AVIF when the file size matters more than the wait.
Why did my JPG get bigger when I converted it to PNG?
Because PNG is lossless and has to store every pixel of a picture that JPEG already simplified, including its compression noise. Our 541 KB test JPG came back as a 1.9 MB PNG, 269% larger, and did not look any better. Converting a JPG to PNG never restores detail that JPEG discarded — keep PNG for screenshots, logos and transparency instead.
Can I turn a PNG into a favicon .ico file?
Yes, with one caveat. Press ICO and you get a single-size icon that wraps a PNG, so transparency is kept — a usable favicon or folder icon. But the longest side is always capped at 256 px (an 800 × 600 test image came back 256 × 192), and the result holds one size rather than a 16/32/48 px multi-size pack. Start from a square picture if you want a square icon.
What happens to an animated GIF?
It becomes a still picture. Animated GIFs and animated WebPs are decoded as one single image, so the animation is gone from the result, and choosing GIF as the target produces a still image too. The page warns you about this as soon as it recognizes a GIF input.
My file is a .jfif — will it work?
Yes. The format is detected from the file's header rather than its extension, so .jfif files, and files someone renamed to the wrong extension, are recognized correctly. A .jfif is a JPEG, so converting it to JPG mainly fixes the name that some apps refuse — and it is re-encoded at quality 85 in the process, so the size will change.