Breezo

SVG to PNG

Vector to pixels — a one-way trip, so choose the size well.

Nothing is uploaded

Drop files here, or click to choose

Accepts SVG. No size limit, no sign-up.

    SVG describes shapes mathematically, so it stays sharp at any size. PNG is a fixed grid of pixels. Converting means committing to one resolution, which is why the size you rasterise at matters more than anything else on this page.

    Why you would give up the vector

    Because a great deal of software cannot read SVG. Presentation tools, older office suites, print-shop upload forms, e-commerce product uploaders, social platforms and most photo editors all expect a raster image. Some systems also reject SVG deliberately, because SVG is XML and can contain scripts.

    That last point is a genuine security consideration rather than an inconvenience: an SVG is an active document, a PNG is inert data. Converting is sometimes the requirement, not a workaround.

    Resolution is the decision you cannot undo

    Rasterising discards the mathematics and keeps only the pixels. Enlarging the resulting PNG later will look soft, because the detail is no longer described anywhere. Rasterise at the largest size you will plausibly need.

    We read the width and height declared in the SVG and render at least 1024 pixels on the longest side, upscaling small declarations rather than producing a tiny blurry image. An SVG that declares no dimensions at all is rendered at a sensible square default.

    Transparency and fonts

    Areas with no fill stay transparent in the PNG, since PNG carries a full alpha channel. That is why PNG rather than JPG is the correct target for icons and logos.

    Text is the common surprise. An SVG that references a font by name relies on that font being available when it is rendered. If it is not installed, the browser substitutes something else and your PNG will show the substitute permanently. Converting text to outlines in your vector editor before exporting avoids this entirely.

    Rendered by your own browser

    Your browser is already an excellent SVG renderer, so that is what does the work. The result is captured to a canvas, encoded as PNG through WebAssembly, and optimised with oxipng before you download it.

    Nothing is uploaded at any stage. Since SVG can contain scripts, keeping the file local rather than posting it to a stranger's server is a meaningful difference, not just a marketing line.

    Frequently asked questions

    What resolution will the PNG be?

    We use the width and height declared in the SVG, rendering at least 1024 pixels on the longest side so small declarations do not produce a blurry image.

    Can I convert the PNG back to SVG?

    Not meaningfully. Rasterising is one-way — the shape mathematics is gone. Tracing tools can approximate an outline but will not recreate the original file.

    Is the transparent background kept?

    Yes. Unfilled areas remain transparent because PNG has a full alpha channel.

    My text looks wrong in the PNG. Why?

    The SVG references a font that is not available during rendering, so the browser substituted another one. Convert text to outlines in your vector editor before exporting.

    Is my SVG uploaded?

    No. Your browser renders it locally. This matters more than usual for SVG, since the format can contain scripts.

    Other tools