Server-sideDeleted in 30 minutes

Convert SVG to JPG

An SVG is a set of drawing instructions with no size of its own — it is as sharp as whatever renders it. A JPG is a fixed grid of pixels. Converting means choosing a size and living with it, so the only real question on this page is what resolution you need.

Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.

Add to Chrome — free

Drop your SVG file here, or click to browse

Up to 50 MB. Deleted automatically after 30 minutes.

What it does

Rendered with librsvg, the same engine GNOME uses
Transparent areas filled with white
Text rendered using fonts available on our server
Output sized from the SVG's own dimensions

How to use SVG to JPG

1
Add the SVG
Logos, icons, charts exported from a plotting library, or drawings from Illustrator, Figma or Inkscape. Files that reference external images or remote fonts will render without them, so flatten those first.
2
Convert
Rendering runs on our server, because doing it in the browser risks differences in how each engine handles fonts and filters.
3
Check the size and the text
Open the JPG at full size. Two things are worth looking at: whether the resolution is enough for where it is going, and whether the text rendered in the font you expected.

How it works

The SVG is parsed and rendered by librsvg, the same engine GNOME uses for its icons, and the resulting pixels are encoded as JPEG. Transparent regions are filled with white first, since JPEG cannot represent them.

It runs on our server rather than in your browser. A browser could rasterize an SVG, but each engine handles fonts, filter effects and clipping slightly differently, so the same file would come back looking different depending on what you happened to be using. Doing it in one place makes the output predictable.

The resolution decision

This is the whole conversion, and it is the part most people skip.

An SVG has no resolution. It says "a circle of radius 30 at this position", which the renderer draws as sharply as the output allows — at any size, forever. That is why logos are distributed as SVG and why a printer will always ask for one.

A JPG has exactly one resolution, chosen at conversion time and permanent afterwards. Enlarging it later interpolates: the edges soften, and no amount of sharpening puts back what was never rendered.

So the question to answer before converting is where the image is going. Roughly: a website needs about twice its display width to look right on a high-density screen; a slide deck needs around 1920 pixels across for something full-width; print needs about 300 pixels per inch, which means a logo three inches wide needs 900 pixels. When in doubt, render larger than you think — discarding pixels later is free, and inventing them is not possible.

What can go wrong

Missing fonts. The most common problem, and the reason to convert text to outlines before exporting.

External references. An SVG that links to a bitmap or a remote font pulls them in at render time. Ours renders without them, leaving gaps. Embed anything the drawing needs.

Exotic filters. Blurs and drop shadows render, but complex filter chains and CSS-driven effects are rendered as librsvg interprets them, which is not always as a browser would.

Scripts and animation. An SVG can contain JavaScript and SMIL animation. Neither runs; you get the initial state.

Keep the SVG

Whatever the JPG is for, it is a derivative. The SVG is the master: infinitely scalable, editable, and usually smaller. Convert when something downstream refuses to read vectors — a form upload, an older tool, a system that only accepts photographs — and keep the original for everything else.

Examples

A logo for a slide deck

logo.svg — declared 400x120

logo.jpg — 400x120, white background, 18 KB

Fine for a slide, wrong for print. At 400 pixels wide this is about 34 mm across at print resolution, so a logo destined for anything physical should be rendered much larger — or left as SVG, which every professional printer prefers.

An icon with a transparent background

icon.svg — transparent, intended to sit on a dark page

icon.jpg — transparent areas rendered white

A white box around the icon, which is not a bug but the format. JPEG has no transparency at all, so something must fill those pixels. If the icon needs to sit on a colored background, PNG or WebP is the target instead.

Frequently asked questions

What resolution do I get?

The size declared in the SVG's own width and height attributes. That number is often arbitrary — a designer's canvas size rather than a considered output resolution — which is why a logo can come back at 400 pixels when you needed 2000. The SVG itself is resolution-independent, so if you need something larger, editing the declared dimensions and converting again loses nothing.

Why is the background white instead of transparent?

Because JPEG has no alpha channel. The format was designed for photographs, where nothing is transparent, and no version of it has ever supported partial or full transparency. Every transparent pixel has to become some color and white is the sane default. For transparency, convert to PNG or WebP.

My text rendered in a different font.

The SVG referenced a font by name and our server does not have it, so a substitute was used — the same failure that affects Word documents. The reliable fix is to convert text to outlines before exporting the SVG, which every vector editor can do; the text becomes shapes and renders identically everywhere at the cost of no longer being editable or selectable.

Should I use JPG or PNG here?

PNG almost always, and this is the rare page that recommends against its own conversion. SVG content is typically flat color, sharp edges and text, which is exactly what JPEG handles worst — it puts faint rings around every edge. PNG stays lossless and usually produces a smaller file for this kind of image. Choose JPG only when the destination genuinely accepts nothing else.