Turn supported vector artwork into a raster copy
SVG to PNG renders supported local SVG artwork into a PNG at dimensions you choose. It is useful when a presentation, document or publishing tool accepts a raster image but not SVG. The output is a pixel image, not a vector file with editable paths, so keep the original artwork when you may need another size or a later design revision.
Choose an SVG file or use the available source-paste area. The preflight checks the actual document against a restricted static subset before rendering. SVG is capable of much more than a collection of harmless shapes, so this tool does not insert uploaded markup directly into the live page and assume it is safe.
Understand the restricted input policy
Supported artwork can use permitted shapes, paths, text, local fragment references and the allowed gradients, masks and clipping constructs. Scripts, event handlers, foreignObject, animation, filters and external or data references are outside this shared platform's accepted scope. Unsupported namespaces, document type declarations and entities are also refused.
That restriction is deliberate. A file that opens in a general-purpose SVG viewer may still be unsuitable for this conversion. Do not remove a reported warning by renaming the extension or treating a rejected document as already sanitized. Use a compatible editor to prepare a genuinely self-contained supported source when appropriate.
Editor has a separate, narrower vector-import adapter. Successful rendering here does not prove that every shape and paint relationship remains editable there. Conversely, the PNG result can be opened as raster content without claiming that its paths or text survived as independent vector objects.
Choose the dimensions the recipient needs
The width and height controls describe the raster result. Aspect-ratio lock helps preserve the artwork's shape when you change one dimension. A scale preset provides another way to create a larger representation, but every requested size still has to fit the output edge and pixel budgets.
A dimensionless SVG needs explicit user dimensions before conversion. The document may define a viewBox without declaring the exact pixel size you need for delivery. Think about the destination: a small icon in a document does not need the same raster grid as a graphic placed across a large slide.
Do not confuse vector scalability with unlimited raster output. A vector can describe a shape compactly, but rendering it at a large pixel size creates a large surface. The configured maximum is 6,000 pixels per edge and 12 megapixels overall. A 6,000 by 6,000 request exceeds the pixel limit even though each edge is within its individual ceiling.
Decide what should happen behind the artwork
Transparent background retains supported alpha around and within the rendered artwork. This is useful for an icon or logo placed on different backgrounds. Open the PNG against a contrasting color to inspect pale edges, shadows and partially transparent paint that may not be obvious on the page preview.
If you choose an opaque background, select the color deliberately. It becomes part of the generated pixels. A white field behind a logo may look fine on a white document but form an unwanted rectangle on a dark slide. Keeping a transparent working PNG can be useful even when one final delivery also needs an opaque version.
The background choice does not remove an opaque rectangle already drawn inside the SVG. That rectangle is part of the artwork. If the original design needs editing, change it in an appropriate vector workflow rather than expecting a renderer's transparency checkbox to understand which painted object you meant to discard.
Review text, clipping and small shapes
An SVG can depend on fonts whose metrics differ from what is available to a renderer. Check line endings, lettering and alignment in the actual output. A recognizable word is not proof that every glyph has the intended shape or that the original font licensing permits redistribution.
Inspect clipped edges and transparent intersections. The allowed subset is narrower than all SVG features, and supported-looking artwork can still require visual review. A tiny preview may hide missing fine lines or a clipping boundary that becomes visible in a larger PNG.
For a small icon, judge it at the size where it will appear. More output pixels do not automatically make a poorly sized line clearer in the final document. For a larger illustration, inspect both overall composition and a few detailed regions. Keep the source so that another raster size can be generated without enlarging a small PNG later.
The raster copy changes what the file can do
PNG stores the rendered pixel grid without a lossy quality slider. It no longer contains editable SVG geometry or accessible title and description structures as equivalent vector document content. If the image will be used on a website, provide useful alternative text in the receiving page rather than assuming that the raster file recreates the source SVG's accessibility semantics.
The conversion is not a universal metadata sanitizer or a promise of preserving every source profile. It is a bounded rendering operation. If the visible artwork itself contains private names or identifying details, those remain in the PNG until you deliberately change them.
Input limits and completion
The configured SVG input cap is 2 MiB, with up to 10,000 nodes and a maximum nesting depth of 64. Output limits and available browser resources apply separately. A small textual SVG can still describe demanding geometry, so file bytes alone do not establish an unlimited rendering workload.
Read the reported actual format and dimensions, download the result and open the saved PNG. Confirm transparency, text and important edges in the receiving application. A download starting is not proof of completed saving. For a smaller supported SVG while retaining vectors, SVG Optimizer is the separate workflow; for a layered composition from the raster copy, use Editor. Save first, because files do not transfer between those tools automatically.