Secure server conversion
SVG to JPG Converter
Render an SVG into a JPG at any size you choose. Two things need a decision here that other conversions do not ask for: how large to render, since a vector has no native size, and what colour should sit behind it, since JPG cannot store transparency and almost every SVG has some.
Drag and drop your SVG images here
Add several at once. Each file is processed and then deleted from our server.
Up to 20 MB per file Batch ready
Output width
SVG is a vector format, so it can be rendered at any size without losing sharpness.
Higher keeps more detail; lower makes a smaller file. Applies to images you add after changing it.
JPG cannot store transparency, so it is filled with this colour.
Conversion queue
→
Your browser could not read this file, so it was converted on our server and deleted there straight away.
Your file had frames or pages. Only the first is in this download.
Step by step
How to convert SVG to JPG in 4 steps
-
Add your SVG files
Drag them in or click to browse.
-
Choose an output width
The height follows the drawing's proportions.
-
Pick a background colour
This is the important one — transparent areas become this colour permanently.
-
Apply and download
Format comparison
SVG vs JPG
SVG (Scalable Vector Graphics)
VectorDescribes shapes and text as instructions rather than pixels, so it can be drawn sharply at any size.
- Crisp at any size, from favicon to billboard
- Very small files for logos, icons and diagrams
- Cannot represent a photograph, and many apps cannot import it
JPG / JPEG (Joint Photographic Experts Group)
LossyShrinks photographs to a fraction of their size by discarding fine detail the eye is least likely to notice.
- Small files for photographs
- Opens on virtually every device, browser and app
- Blurs text and sharp edges, and re-saving loses a little more each time
This conversion crosses two boundaries at once, and both cost you something.
Vector becomes pixels. An SVG describes shapes, so it renders perfectly at any size. A JPG is a fixed grid of dots. Once rendered, the scalability is gone — enlarging the JPG afterwards only interpolates and softens.
Transparency becomes a colour. This is the part that catches people out. Most SVGs — logos, icons, illustrations — have a transparent background, because that is what makes them usable on any surface. JPG has no alpha channel whatsoever, so every transparent pixel must be painted onto something solid before encoding. White is the default and suits most documents, but if your logo is going onto a dark page you will get a white rectangle around it that cannot be removed afterwards.
There is a third issue worth being blunt about: JPG is a poor match for the kind of image an SVG usually contains. JPEG compression was designed for photographs, where colour varies gradually. It handles flat areas of colour and hard edges badly — precisely what logos, icons and diagrams are made of. You get faint halos around edges, sometimes called ringing, and subtle blotching in solid colour.
So for most SVGs, PNG or WebP is the better target: both keep transparency, and both handle sharp edges cleanly. Choose JPG when something specifically demands it, or when the SVG is an illustration with photographic shading rather than flat graphics.
What happens to transparent pixels when converting SVG to JPG?
JPG cannot store transparency, so transparent and semi-transparent areas are blended onto a solid background before the file is saved — the colour you choose above, #FFFFFF by default. Keep your original SVG if you may need the transparency again.
Quality
Quality and file size
Because the source is a clean vector, this conversion benefits from a higher quality setting than a photograph would need. The default of 92 is deliberately above the usual 75–85 band.
- 95–100 — Practically no visible artefacts even around hard edges. Worth it for logos and anything containing text.
- 88–94 — The default range. Occasional faint haloing at high contrast boundaries, visible only if you look for it.
- 75–87 — Ringing around edges becomes noticeable, and flat colour starts to blotch.
- Below 75 — Clearly degraded on graphics, whatever it might look like on a photograph.
Rendering larger helps more than raising quality. Artefacts are relative to pixel size, so a 2048 px render at quality 88 usually looks better than a 512 px render at 100, and it stays sharp if anyone displays it larger.
Two practical notes:
- Match the background to its destination. Semi-transparent pixels — a soft shadow, a faded edge — blend with whatever colour you choose. A shadow that looks natural on white reads as a grey halo on black.
- Check your fonts. If the SVG names a font rather than converting text to outlines, the renderer substitutes whatever is available. Convert text to paths in your design tool if the lettering matters.
When JPG is genuinely the right target
- Something demands JPG specifically — some upload forms, print services and older systems accept nothing else.
- The SVG is an illustration with rich shading or gradients rather than flat graphics. JPEG handles those well.
- The image will sit on a known solid background anyway, so transparency was never doing anything.
- File size matters more than edge sharpness and the image is large.
When to choose PNG or WebP instead
If the SVG is a logo, icon, diagram, chart or anything containing text — which describes most SVGs — you almost certainly want PNG. It keeps transparency and compresses flat colour losslessly, so edges stay perfectly crisp.
For a website you control, WebP is better again: transparency, clean edges, and a smaller file than either.
A quick way to decide: if you would be annoyed by a white box appearing around your graphic, do not convert to JPG.
How we handle SVG safely
SVG is a document rather than a block of pixels, and a hostile one can attempt things a photograph never could — reading server files, making outbound requests, or embedding scripts.
You receive a JPG, never the SVG, so nothing embedded in the file can run in your browser. And every upload is screened before anything parses it: files containing document type declarations, entity definitions, scripts, event handlers or external resource references are refused outright rather than repaired. Ordinary exports from design tools are unaffected.
Converting a set of files
Add as many SVGs as you like. Each is rendered at the width you chose and composited onto the background colour you picked, with its own download. If different files need different backgrounds, do them in separate batches — the setting applies to everything in the queue.
Privacy
What happens to your file
This tool runs on our server, so it works the same on every phone and computer. Your file is uploaded, and this is exactly what happens to it:
- Stored outside the public web root under a random name, never under your file's name.
- Processed, with the original upload deleted immediately — whether it succeeded or failed.
- The result sits behind a signed link that only you receive, which stops working after 20 minutes, and the file is deleted the moment you download it.
- Anything never collected is deleted automatically within 30 minutes.
- The image itself is never logged or kept. If a conversion fails, we record the formats involved and the error — not the file.
- Camera metadata, including any GPS coordinates recording where a photo was taken, is removed from the result. Only the rotation needed to show the image the right way up is kept.
Questions & answers
SVG to JPG: frequently asked questions
Why does my logo have a white box around it?
Because JPG cannot store transparency. Your SVG almost certainly had a transparent background, and every transparent pixel had to be painted onto a solid colour — white by default. Choose a colour matching where the image will sit, or convert to PNG or WebP instead, both of which keep transparency.
What size should I render at?
Roughly twice the size it will be displayed at, so it stays sharp on high-density screens. For print, aim for about 300 pixels per printed inch. Rendering larger helps more than raising the quality slider, because compression artefacts are relative to pixel size.
Should I convert my SVG to JPG or PNG?
PNG, for most SVGs. Logos, icons, diagrams and anything with text are exactly what JPEG compression handles worst — you get faint halos around hard edges — and PNG keeps the transparency too. Choose JPG when something specifically requires it, or when the artwork is a richly shaded illustration.
Why do the edges look slightly fuzzy?
That is JPEG ringing: the compression struggles with the hard boundaries between flat colours that graphics are made of. Raise the quality to 95 or above, or render at a larger size, or use PNG or WebP, which have no such problem.
My text renders in the wrong font. How do I fix it?
The SVG references the font by name and the renderer substituted a different one. Convert the text to outlines in your design tool before exporting — usually "convert to outlines" or "object to path" — so the letterforms become shapes that render identically anywhere.
Is uploading an SVG safe?
Yes. Every file is screened before anything parses it, and anything containing document type declarations, entity definitions, scripts, event handlers or external references is refused rather than repaired. You also receive a JPG and never the SVG, so nothing in the file can run in your browser.
Keep going
Related image tools
SVG to PNG Converter
Convert SVG to PNG at any resolution, with transparency preserved. Rendered from the vector so edges stay crisp at every size.
SVG to WebP Converter
Convert SVG to WebP at any resolution with transparency preserved. Smaller than PNG, crisper than JPG for graphics.
Compress JPG
Make JPG photos smaller, free and with no sign-up. Adjust the quality, see the saving for each photo, and download.
PNG to JPG Converter
Convert PNG to JPG free, with no sign-up. Choose the quality, pick a background colour for transparent areas, and download instantly.