Rankato

Convert any image to PNG

Pixel-perfect lossless conversion with oxipng optimization. Preserves transparency. Batch up to 20 files, 100% client-side.

Files never leave your browser — 100% private

Batch up to 20 images · 20 MB per file · no watermarks, no signup

Drop anywhere
Drag files onto any part of this page
Paste from clipboard
Copy an image, press Ctrl+V
Best-in-class encoders
MozJPEG + oxipng + sharp-YUV WebP · production tuned

PNG is the universal lossless raster format: pixel-perfect reproduction, full alpha channel, supported by every browser, editor, and OS since the late 1990s. Convert to PNG when you need a mathematically identical result (UI mockups, logos, technical diagrams, screenshots), transparency (buttons, icons, product cutouts), or wide compatibility (any tool that can't read WebP or AVIF). This tool takes any input format and produces a PNG, then passes it through oxipng — the same optimizer used in production by GitHub, Google, and every serious asset pipeline — to strip metadata and re-pack the bytes losslessly. Effort level 6 (max) can shave 5–15% off the raw PNG output with zero pixel changes.

When to choose PNG in 2026

Choose PNG for anything that needs to be lossless: UI mockups, logos, icons, technical diagrams, screenshots, product cutouts with sharp edges, and anything you'll re-edit later. PNG's alpha channel is pixel-perfect, unlike JPEG which has none, or WebP-lossy which slightly softens alpha edges. The tradeoff is size — PNG is 2–5× larger than JPEG for photographic content and 1.5–2× larger than WebP-lossless. For photos meant for the web, prefer WebP or AVIF; for design assets and screenshots, PNG is the right choice.

oxipng — why the tool's output is smaller

Most PNG encoders (browsers, image editors, screenshot tools) produce PNGs that are 5–15% larger than they need to be because they use fast, generic zlib compression. oxipng is a specialized PNG optimizer that tries multiple compression strategies (different filter types, block sizes, zopfli-level entropy coding at max effort) and picks whichever produces the smallest output. This tool runs oxipng at level 6 (max) by default — the same effort GitHub uses when optimizing repository README images. Every byte matters when your site's LCP is measured against Core Web Vitals thresholds.

Handling JPEG and photo input

Converting a JPEG or HEIC photo to PNG produces a much larger file — typically 3–8× the JPEG size — because PNG is lossless and can't throw away the DCT compression artifacts already baked into the source. This is expected and correct behavior: PNG faithfully preserves whatever pixels are handed to it, including the JPEG artifacts. If you need smaller files, keep the photo as JPEG or convert to WebP/AVIF. Convert photos to PNG only when a specific downstream tool requires PNG input.

Transparency and alpha

PNG's alpha channel is bit-perfect. If your source is a WebP, AVIF, or HEIC with lossy alpha, the PNG output preserves whatever alpha data the source contained. If the source is transparent PNG or SVG, the alpha round-trips identically. Because PNG is lossless, you can convert PNG → any format → back to PNG and get identical pixels back (as long as the intermediate format supports alpha).

Tool FAQs

Everything you need to know about using Convert Image to PNG.

Why is my PNG bigger than the original JPEG?+

PNG is lossless — it can't discard any pixel data. JPEG throws away perceptually-unimportant detail using DCT compression, which is why it's so small. When you convert JPEG → PNG, all the JPEG artifacts get faithfully preserved in the PNG at zero savings. Typical ratio: PNG is 3–8× larger than the source JPEG. This is normal. Convert photos to PNG only when a downstream tool specifically needs PNG.

What does oxipng actually do?+

oxipng is a lossless PNG optimizer. It tries multiple PNG filter strategies (None, Sub, Up, Average, Paeth), multiple zlib compression settings, and at max effort a zopfli-level entropy coder. It picks the strategy that produces the smallest output, then re-writes the PNG with that. Result: 5–15% smaller PNG with pixel-identical output. This tool runs it at level 6 (max) by default.

Will my transparency survive?+

Yes. PNG has the industry-standard alpha channel; transparency round-trips losslessly. If your input has soft alpha (like a WebP or AVIF with lossy alpha), the output PNG preserves those exact alpha values.

Can I convert HEIC to PNG?+

Yes — drop HEIC/HEIF files directly. The tool decodes them in-browser using libheif WASM (no Apple software needed) and produces a PNG. Because PNG is lossless, the output preserves every visible pixel of the HEIC source (though HEIC's compression artifacts are baked in). Use this when you need HEIC pixel data in a tool that only accepts PNG.

Should I use PNG for the web?+

Only for UI graphics, logos, icons, and screenshots — anything where lossless matters. For photos and hero images, use WebP or AVIF (2–5× smaller than PNG). If you need PNG as a fallback for very old browsers, ship it via <picture> with WebP/AVIF sources first — this tool's "Copy HTML" button generates that markup for you.