Convert any image to PNG online, free

Hold on to both facts as you read the rest of this page, because every recommendation here traces back to them. PNG is the right target when you need clean edges, transparency, or both. When you need neither, you are usually paying for PNG without getting anything for it.

How each input format behaves on the way to PNG

WebP, AVIF, GIF, and SVG can all carry transparency, and when they do, converting to PNG preserves the alpha channel intact. This is the headline reason to choose PNG over JPG for these inputs: a transparent WebP logo stays transparent as a PNG, whereas the same file converted to JPG would have its background flattened to solid white. If your source has see-through areas you want to keep, PNG is the format that respects them.

A JPG converted to PNG is a special case worth setting expectations on. JPG already discarded detail when it was first saved, and PNG cannot conjure that detail back. You simply stop further loss and get a larger, lossless copy of the current state. It does not get sharper, it does not get cleaner, and for a photo it gets a lot bigger. Convert JPG to PNG only when a tool or form demands PNG, not in the hope of better quality.

An SVG is a vector, defined by maths rather than pixels, so converting it to PNG rasterises it to a fixed pixel grid. The result is locked to one size and no longer scales without blurring. This page rasterises at a sensible default, but when you care about the exact output dimensions, use the dedicated SVG to PNG tool where you can set the pixel size before rendering.

HEIC and HEIF, the photo format iPhones shoot, are decoded in your browser and then written to PNG. Be warned that the file balloons, because a compact HEIC photo becomes a fat lossless PNG with no quality gain. For plain photographs straight off a phone, JPG is usually the smarter target. And an animated GIF is reduced to its first frame, transparency kept, since a single PNG cannot hold motion.

When choosing PNG is the right call

Reach for PNG whenever the image has crisp geometry: logos, app icons, wordmarks, diagrams, charts, screenshots, and exported UI. PNG keeps every edge razor-sharp where a lossy format would soften them and scatter artefacts around the text. If the picture is mostly flat colour and clean lines, PNG is almost always correct.

Choose PNG when transparency has to survive. A product cut-out, a sticker, a badge, or an overlay meant to sit on a coloured background needs its alpha channel, and PNG is the most universally supported format that keeps it. Converting any transparent WebP, AVIF, GIF, or SVG to PNG is the safe way to carry that transparency into tools and forms that expect a PNG.

Pick PNG when a destination simply demands it. Some upload forms, asset pipelines, app-store listings, and older design tools accept only PNG. When the requirement is fixed, you convert, and the larger file size is just the price of admission. This universal page is the quick way to get there from whatever format you started with.

Use PNG as a clean working master for flat-content edits. If you are about to retouch a graphic across several saves, working in PNG means repeated saves cost you nothing, because there is no lossy re-encode each time. The same is not true of editing and re-saving a JPG, which degrades a little on every pass.

When to walk past PNG to JPG instead

For ordinary photographs, PNG is the wrong target. A continuous-tone photo, all gradients and texture, is the worst case for PNG: it refuses to approximate any of that detail, so the file lands several times larger than a JPG with no visible quality benefit at all. A 2 MB JPG photo can balloon to 8 or 12 MB as a PNG for nothing.

The honest rule is short. Graphics, transparency, or text means PNG. Photographs mean JPG, or WebP if you want small files that can still hold transparency. If your image is a person, a landscape, a meal, or any real-world scene captured by a camera, PNG is rarely what you want.

This matters most for HEIC and HEIF, because those are almost always phone photos. Decoding a HEIC to PNG produces a huge lossless file of an image that was never going to benefit from losslessness. Routing those photos to JPG instead keeps them small and universally readable, which is what a photo actually needs.

If your only goal was a smaller file, PNG moves you backward. Keep the source as JPG, convert a photo to JPG, or shrink it to a target with the compress tools. The MDN image format guide lays out which format suits which kind of image if you want the longer version.

Why PNG files get large, and what to do about it

PNG's losslessness is exactly what makes it heavy. It stores texture and gradient literally rather than approximating them, so a busy or photographic image carries a lot of data. The more varied the pixels, the bigger the PNG, which is why photos balloon and flat graphics stay reasonable.

For the graphics PNG is built for, the size is usually fine. A logo or screenshot has large areas of identical colour that PNG compresses efficiently, so a clean UI export might be a few hundred kilobytes rather than a few megabytes. The cost only spirals when you feed PNG an image it was never meant to hold.

When a legitimate PNG still comes out larger than you would like, run it through Compress PNG, which reduces colours and optimises the encoding without touching the lossless pixels you care about. It is the right second step after converting, especially for assets headed onto a web page where weight matters.

If you only need the image at a smaller pixel size, shrinking the dimensions cuts the file dramatically before you even compress. Resize in pixels first, then convert, and a 4000-pixel-wide export destined to be displayed at 800 pixels stops carrying five times the data it needs.

Converting a mixed pile of formats in one drop

The reason this page is universal is the mixed folder. You collect assets from a dozen sources and end up with a WebP here, an AVIF there, a couple of SVGs, a stray JPG, and a HEIC straight off a phone. Rather than visiting five different format-specific pages, you drop the whole lot here and everything comes out as PNG.

Each file is decoded and re-encoded in parallel using a worker pool in your browser, so the batch finishes far faster than processing one file at a time. Up to 100 files at 50 MB each go in a single drop, and the results arrive as one ZIP with the original names preserved and the extension swapped to .png.

Because nothing uploads, the batch size is bounded only by your device's memory, not by a server quota or a paid tier. There is no per-file fee, no watermark, and no cap on how many batches you run back to back. When the first ZIP finishes, the queue is clear for the next folder.

If your pile is genuinely mixed and PNG is not the right single target for all of it, the bulk image converter lets you pick any output format for the whole batch. Use this page when PNG specifically is what you want out the other end.

A quick mental model for getting it right

Ask one question before converting: does this image have sharp edges, flat colour, text, or transparency? If yes, PNG is the right home, and this page gets you there from any source format in one step. If no, the answer is almost always a lossy format and you should keep reading.

If the image is a photograph, do not convert it to PNG at all. Send it to JPG for the smallest universally readable result, and reach for the dedicated photo-friendly pages when you want fine control. PNG will only make a photo larger without making it better.

If the image is the most common case, a single ordinary JPG you need as a PNG for a form or a tool, the dedicated JPG to PNG page covers exactly that with the same lossless pipeline. This universal page exists for everything else and for mixed batches.

And if you care about the exact output dimensions of a vector, rasterise it on the SVG to PNG tool where the pixel size is yours to set. Match the tool to the job and PNG stops being a guess and becomes a deliberate, correct choice.