Transparent logo at 2×
The standard high-DPI export: double resolution, alpha intact.
Input
logo.svg (natural 240 × 80) · PNG · 2× · transparent backgroundOutput
logo.png at 480 × 160 with transparency preservedConvert SVG files to PNG, JPG, or WebP at 1–4× scale or custom dimensions, with transparency or background colour control.
Content last reviewed
Drop an SVG file or click to upload
Accepts .svg files up to 5 MB. Conversion runs in your browser.
Choose PNG for transparent logos, icons, screenshots, and crisp graphics where quality matters more than file size.
Choose JPG for solid backgrounds and smaller files. It cannot preserve transparent SVG areas.
Choose WebP for modern websites when you want strong compression with optional transparency.
Drop in an SVG file — its natural dimensions are read from the markup.
Pick PNG, JPG, or WebP (AVIF where supported), then a 1–4× scale or custom dimensions.
Keep transparency or choose a background colour, adjust quality for lossy formats, and download.
The standard high-DPI export: double resolution, alpha intact.
Input
logo.svg (natural 240 × 80) · PNG · 2× · transparent backgroundOutput
logo.png at 480 × 160 with transparency preservedJPG cannot hold transparency, so the background colour fills it.
Input
diagram.svg (viewBox 800 × 600) · JPG · 1× · background #ffffff · quality 90Output
diagram.jpg at 800 × 600 with the artwork composited onto whiteSVG scales forever, but half the web refuses to accept it: upload forms, marketplaces, chat apps, office documents, and social platforms all want pixels. This converter rasterizes your SVG into PNG, JPG, or WebP — with AVIF appearing as an option when your browser can encode it — at whatever resolution the destination needs.
Resolution is the decisive setting when leaving vector land, so it gets first-class controls: export at 1×, 2×, 3×, or 4× the SVG's natural size, or enter custom width and height with an aspect-ratio lock. A 2× or 3× export is the standard move for high-DPI screens — the file is raster, but at sufficient resolution nobody can tell. Transparency is handled per format: PNG and WebP can keep it (a toggle), while JPG has no alpha channel, so you choose the background colour that replaces it.
The tool reads the SVG's dimensions from its width/height attributes or viewBox, warns when neither exists, and enforces sane output limits (up to 8,000 pixels per side and 64 megapixels) so a typo cannot lock up the browser. Conversion happens entirely on your device. Two boundary notes: ICO output is deliberately not here — favicons need multi-size packaging, which the Favicon Generator does properly — and if the SVG itself should be cleaned before export, the SVG Optimizer is the upstream step.
Drag an SVG file onto the drop zone or click to select it (up to 5 MB). Its natural dimensions are read from the markup and shown with a preview.
Choose the output format: PNG for transparency and crisp graphics, JPG for smallest solid-background files, WebP for the modern web — AVIF appears when your browser supports encoding it.
Pick the size: 1×, 2×, 3×, or 4× the natural dimensions, or Custom with width and height fields (aspect-ratio lock on by default).
Set the background: keep transparency for PNG/WebP, or choose a background colour — required for JPG, which cannot store transparency.
Adjust quality for lossy formats, click Convert, review the output size, and download the raster file, named after your SVG.
Format support is detected in your browser; AVIF is offered only when the canvas can actually encode it.
1× to 4× the SVG's natural size, or exact width and height with an aspect-ratio lock.
Alpha is preserved for formats that support it; JPG exports composite onto your chosen colour.
Natural size is read from width/height or the viewBox, with an explicit message when the SVG declares neither.
Exports are capped at 8,000 px per side and 64 megapixels, failing with a message instead of freezing the tab.
A quality slider governs JPG, WebP, and AVIF encoding.
Export a transparent PNG of the logo for forms, marketplaces, and profiles.
Render icons and illustrations at 2–4× for retina screens, presentations, and print-ish uses.
Produce WebP versions of vector artwork for pages that serve rasters.
Convert diagrams to PNG for tools that embed pixels more reliably than vectors.
Composite artwork onto a chosen colour when the destination wants a photo-style file.
The SVG file is read as text and parsed to determine its natural size — from explicit width and height attributes first, falling back to the viewBox; if neither exists, conversion stops with an instruction to add one. Your scale or custom dimensions produce the output size, which is validated against the 8,000-pixel and 64-megapixel caps.
Rendering loads the SVG into an image and draws it onto a canvas at the target size — the browser's vector rasterizer does the scaling, which is why a 4× export is genuinely sharp rather than an upscaled blur. For JPG (or when transparency is toggled off), the canvas is filled with your background colour first; for PNG and WebP with transparency on, the alpha channel passes through. The canvas encodes to your chosen format at the set quality, and format support (notably AVIF) is feature-detected beforehand so unsupported options never appear.
A single .svg file up to 5 MB, with dimensions declared via width/height or viewBox.
PNG lossless with transparency; JPG smallest with a solid background; WebP modern with optional transparency; AVIF only where the browser encodes it.
PNG, JPG, WebP, or AVIF (feature-detected).
1×, 2×, 3×, 4×, or custom width and height with an aspect-ratio lock.
Transparency toggle for supporting formats; background colour picker otherwise.
Encoding quality for JPG, WebP, and AVIF.
The file declares neither width/height nor a viewBox, so there is no natural size to scale from. Open the SVG and add a viewBox (or explicit dimensions) — design tools include one by default; hand-edited files sometimes lose it.
The requested export exceeds 8,000 pixels on a side or 64 megapixels. Reduce the scale or custom dimensions — few destinations need more.
SVGs that reference external assets (linked images, external CSS, remote fonts) rasterize without them, since the renderer only sees the file itself. Inline the dependencies or flatten text to paths in your design tool, then re-export.
Your browser cannot encode AVIF through the canvas — support is feature-detected, not assumed. WebP is the closest alternative.
Input is one SVG at a time, capped at 5 MB, and the file must declare its dimensions (width/height or viewBox). Rendering uses the browser's SVG engine, so features it does not rasterize — external references, some filters, animations (which render as their static state) — will not survive into the raster. Output is capped at 8,000 pixels per side and 64 megapixels. ICO is intentionally excluded (the Favicon Generator owns that job), and AVIF availability depends on the browser. As with any rasterization, the output no longer scales — keep the SVG as the editable master.
The SVG is read, rendered, and encoded on your device — the basic conversion workflow involves no upload of your file. Note that an SVG which itself references remote resources would have the browser fetch those during rendering; self-contained SVGs (the normal case) touch no network at all.
Export at 2×–4× the display size for high-DPI screens; resolution is decided at export time.
Use PNG for transparency and crisp graphics, JPG for solid-background size, WebP for the web.
Keep the SVG as your editable master — raster exports are one-way outputs.
Convert text to paths in the design tool when font fidelity matters.
Check the export at its real display size before publishing, not zoomed to fit.
Rasterize last. Every edit — colour tweaks, resizes, cleanups (the SVG Optimizer belongs here) — happens in the SVG, and the raster export is the final step for one specific destination. When the destination changes, you re-export from the master rather than resampling a raster.
Size for the worst case: find the largest size the image will display — including 2× for retina — and export at least that. Storage is cheap; a blurry logo is not.
And choose formats by content and destination together: transparent UI assets want PNG, photographic-looking artwork on the web wants WebP or JPG, and anything destined for a favicon should skip this tool entirely and go through the Favicon Generator, which packages the multi-size ICO correctly.
The file is read via FileReader and parsed with DOMParser; natural size resolves from width/height attributes, falling back to viewBox, else a descriptive error. Output dimensions are scale-multiplied or taken from the custom fields (aspect-locked by default) and validated against MAX_DIMENSION 8000 and 64 MP. Rendering draws the SVG into a canvas at target size — background-filled unless transparency is on — and encodes via canvas.toBlob at the chosen quality. AVIF (and general format) support is probed with a tiny test encode before being offered. The 5 MB input cap and all processing are client-side.
| Format | Transparency | Compression | Best for |
|---|---|---|---|
| PNG | Yes | Lossless | Logos, icons, crisp graphics |
| JPG | No — background colour applied | Lossy | Smallest solid-background exports |
| WebP | Yes | Lossy | Modern web delivery |
| AVIF | Yes | Lossy | Smallest files, where the browser encodes it |
Designers and developers who keep assets as SVG but constantly meet destinations that demand pixels — upload forms, docs, marketplaces, chat — and anyone producing high-DPI raster variants of vector artwork. For favicon output specifically, the Favicon Generator is the purpose-built path; for pre-export cleanup, the SVG Optimizer.
Yes — but JPG has no transparency, so the tool composites the artwork onto your chosen background colour first. Pick the colour in the settings; white is the common default.
PNG is lossless and keeps transparency — the safe choice for logos and UI graphics. WebP gets close at much smaller sizes for web use, and JPG wins on size when a solid background is acceptable.
It was exported at fewer pixels than it is displayed at — the classic raster problem SVG doesn't have. Re-export at 2×, 3×, 4×, or custom dimensions at least as large as the biggest display size.
The SVG declares neither width/height attributes nor a viewBox, so there is no natural size to scale from. Add a viewBox to the file (design-tool exports include one; hand-edits sometimes drop it) and retry.
AVIF export requires the browser itself to encode it through the canvas, and support is feature-detected before the option is shown. Where it is absent, WebP is the modern-format alternative.
Deliberately not — favicons need multiple sizes packaged into a proper ICO plus manifest files, which is the Favicon Generator's job. This tool covers general-purpose raster exports.
No — reading, rendering, and encoding happen in your browser. A self-contained SVG involves no network at all; only an SVG that itself links remote resources would cause the browser to fetch them while rendering.