Convert SVG to JPG in your browser

An SVG has no pixel size, so you choose how wide the JPG should be. JPG has no transparency either, so anything transparent in the drawing comes out white.

SVG
No SVG selected
Drop a file to start
Drop SVG files here

or browse your device. Everything is processed on this device

No SVG to hand?

Got it on your clipboard?

How to convert SVG to JPG

01
Drop the SVG files

Or paste the markup straight into the box, which is often quicker when the drawing came out of an editor panel or a code block rather than a file.

02
Set the width in pixels

This is the whole decision. Match what the JPG is going to be used for, since the file has no opinion of its own: the height follows the shape of the artwork.

03
Check the background, then save

Drag the divider. Anywhere the drawing was transparent is now white, and that is permanent, so it is worth a look before the file leaves the page.

What an SVG loses on the way to a JPG

It loses the ability to be any other size. An SVG is a list of drawing instructions, so it is as sharp at 4000 pixels as at 40 and costs the same either way. A JPG is a fixed grid of pixels, so the width you choose here is the width you have from now on, and enlarging it later will only make it blurry. Choose from the destination: around 600 for a marketplace listing, 1200 to 2000 for a document or a slide, the maximum for anything going to a printer.

It loses the transparency. JPG has no alpha channel at all, so the background cannot simply be absent: it has to be some colour, and here it is white. If your logo is meant to sit on a dark page, or on a coloured card, converting it to JPG will put it in a white rectangle that cannot be removed afterwards. PNG is the format that solves this, and the conversion is on the next page over.

It also loses a little sharpness at the edges, which is worth expecting rather than being surprised by. JPG was designed for photographs, where colour changes gradually; artwork made of flat fills and crisp outlines is the case it handles least well, and at low quality it shows as a faint shimmer running alongside every line. The quality default here is deliberately high to hold that off.

SVG to JPG FAQ

Should I be converting to JPG or to PNG?

PNG, unless something specific is asking for a JPG. PNG keeps transparency, it stores flat artwork losslessly, and for a logo or an icon it is usually the smaller file as well, because a few flat colours compress far better than a photograph would. Choose JPG when the thing at the other end will not take anything else, or when the drawing is a full-bleed illustration with a lot of shading in it.

What happens to the transparent background?

It becomes white, and it cannot be recovered from the JPG afterwards. If you want a different colour behind the artwork, add a filled rectangle underneath it in your editor before converting, and it will be drawn exactly as you drew it.

What width should I pick?

Whatever the JPG is for, plus a bit of headroom for high-density screens. Roughly 600 covers a listing image or a forum post, 1200 to 2000 is right for a slide or a document, and print wants everything you can give it. Going larger costs nothing in quality here, because there is no original resolution to run out of, only file size.

The text in my SVG came out in the wrong font.

Your own browser draws the file, so it can only use fonts your machine actually has. An SVG that names a font you have not installed falls back to something else, and the JPG records the fallback. Converting text to outlines in your editor before exporting removes the problem completely, and is worth doing for anything you are handing to someone else.

Does it load images or stylesheets the SVG links to?

No. The drawing is rendered from a local data URL, so nothing it references over the network is fetched. That is what keeps the promise that no request leaves this tab, and it means an SVG assembled from remote pieces will be drawn without them.

Are my SVG files uploaded to convert them?

No. The SVG is decoded and the JPG is written by your own browser, in this tab. There is no upload endpoint in the site for a file to go to, which you can check in your network tools: convert something and watch that no request carries it. Disconnect from the network after the page loads and it still works.

Does this remove EXIF, GPS and AI metadata?

Yes, every time, and there is no way to turn it off. The image is decoded to pixels and encoded again from those pixels alone, so EXIF and GPS, the XMP packet, embedded colour profiles, and any Content Credentials or AI-generation tags the file arrived with do not survive. There is no switch for this, because there is no way to keep them. What no compressor can remove is a watermark written into the pixels themselves, such as the invisible marks some image generators add: those survive re-encoding here and everywhere else.

Drop more files

Same format joins the queue. Anything else re-routes to its own tool.