Image & SVG Conversion Utilities

The converter rasterizes SVG at the size you specify using the browser's own renderer, so the PNG you download is what Chrome would actually draw — not what a server-side librsvg build decided to do. For a favicon, render at 16, 32 and 48 and bundle them into one ICO; browsers pick the right size. A single 32px PNG stretched up looks blurry on a retina display.

Two knobs matter most: export the largest size first and let the browser scale down (a 512px source exported straight to 16px loses fine detail), and keep transparency unless your SVG actually has a background — forcing a white fill bakes a visible box into the corners of dark-mode browser tabs.

WebP's win is photographs: a lossy WebP at quality 80 runs roughly 25–35% smaller than the equivalent JPEG with no visible difference, and it keeps an alpha channel, which JPEG cannot. That is the reason it displaced PNG for anything photographic on the web.

It is not a universal answer. Flat UI graphics and logos usually compress better as a well-optimized PNG or just stay as SVG, and some encoders smear hard edges in lossy WebP. Safari did not ship WebP until 14 (2020), so if you still support older iOS you need a fallback source. The converter's lossy/lossless toggle and size preview let you compare before you download instead of after you commit the file.

The compressor re-encodes in the browser, so nothing is uploaded. For photos, quality 75–85 is the sweet spot — below that, JPEG blocking shows up first on faces and smooth gradients. For screenshots with text and flat UI, keep them as PNG: re-compressing to lossy JPEG makes the text fuzzy and is rarely smaller once you account for the artifacts.

Two habits that save you from a bad export: compare before/after at 100% zoom (artifacts hide in the thumbnail), and never re-compress a file that has already been through a lossy pass — a social-media screenshot or an email attachment. Re-encoding it compounds the damage. Start from the original export when you can.