SVG is an XML description of shapes, which is why it scales to any size. JPEG is lossy compression tuned for human vision, and no alpha channel at all. ImageMagick sits between the two, and this page says exactly what happens to an SVG file on the way to becoming a JPG one.
What runs when an SVG file becomes JPG
ImageMagick 6.9.12, on a machine we rent and watch. Your SVG file is uploaded once, ImageMagick runs once, the JPG comes back, and neither file is kept. SVG to JPG is one of the 3649 pairs that engine was probed on with a real file, which is why it has a page here and why the pairs the probe could not prove do not.
What survives from the SVG into the JPG
The pixel dimensions of your SVG file. The JPG comes out the size the SVG went in, because nothing on this path resizes anything.
What SVG to JPG costs you
Scalability. SVG describes shapes, JPG stores a grid of pixels, and the engine rasterises at 150 dots per inch on the way across. That density is a deliberate choice: at the 72 dpi ImageMagick defaults to, an A4 SVG page comes out 595 pixels wide and reads as a failed conversion. Enlarge the JPG afterwards and it blurs, because there is nothing left to redraw from.
Transparency. JPG has no alpha channel, so the engine composites your SVG image onto white before encoding. Without that step ImageMagick lays black underneath, and a transparent SVG logo comes back as a black rectangle.
Exactness. JPG is a lossy encoding, so the file you get back approximates the SVG you sent. The artefacts appear once and never come out again, which is why converting the JPG back to SVG afterwards restores nothing.
If a model is going to read the JPG
A JPG file is pixels, and pixels are expensive for a model to read. Handed this JPG, an assistant spends its budget looking at the picture rather than reading it, and it will paraphrase what it thinks it saw. If your SVG is mostly words, the useful move is to pull the text out of it, not to change which picture format holds it.
SVG to JPG, measured rather than promised
Running SVG to JPG against the real engine with a real file, ImageMagick wrote 2,483 bytes of JPG in under a tenth of a second, machine otherwise idle. That is one SVG file on one day and not an average, which is why the number is given together with the file that produced it.
The SVG to JPG verdict was reached by a format signature, meaning at least four bytes unique to the format were found at the right offset. Which check was used matters, because they do not all prove the same thing, and a status code of 200 proves nothing whatsoever about whether the JPG file has anything inside it.
The same SVG file, sent somewhere else
Other outputs the probe measured out of an SVG file, so the cost of choosing JPG can be read against something. Sizes do not compare across engines, because each family was probed with its own SVG witness file.
SVG to PDF: 4,195 bytes in under a tenth of a second, verified by a format signature.
SVG to PNG: 1,268 bytes in under a tenth of a second, verified by a format signature.
SVG to WEBP: 608 bytes in under a tenth of a second, verified by a format signature.
SVG to GIF: 1,232 bytes in 0.1 seconds, verified by a format signature.
SVG to TIFF: 2,464 bytes in under a tenth of a second, verified by a format signature.
Other ways into JPG, and what they measured
Among the published routes into JPG, SVG is the third largest output of the 13 measured. The witness files differ, so this ranks the probe run and not your document.
PSD to JPG: 1,568 bytes in under a tenth of a second.
ICO to JPG: 1,568 bytes in under a tenth of a second.
HEIF to JPG: 1,666 bytes in under a tenth of a second.
JP2 to JPG: 1,568 bytes in under a tenth of a second.
HEIC to JPG: 1,666 bytes in under a tenth of a second.
What we will not pretend about SVG to JPG
An SVG file over 25 MB is refused before the upload finishes rather than after it, so you do not wait for a rejection.
An SVG to JPG run that passes 30 seconds is killed, and the ImageMagick process is killed with it. A run left behind would sit on one of the machine's two cores until somebody noticed.
No text is read out of the SVG anywhere on this path. Converting a picture to JPG never turns it into words, whatever the picture happens to contain.
ImageMagick was not saturated at sixteen simultaneous conversions: it held 47.5 a second while latency moved from 0.22 s to 0.34 s, and the service memory did not move off 51 MB. That is the measured headroom behind SVG to JPG, not a marketing number.
One SVG file at a time, chosen in the browser. There is nothing else to set up and nothing else on offer.
SVG to JPG: what people ask
What actually converts my SVG file to JPG?
ImageMagick does it, 6.9.12, on a machine we rent and watch. Not a browser trick and not somebody else service: the SVG file is uploaded once, ImageMagick runs once, the JPG comes back, and neither file is kept afterwards.
How long does SVG to JPG take?
On the file the probe used, ImageMagick took under a tenth of a second and wrote 2,483 bytes of JPG. That is one real measurement on one real SVG file, not an average and not a promise about yours: a larger SVG takes longer, and past 30 seconds the run is stopped.
What do I lose going from SVG to JPG?
The one to know about first: Scalability. SVG describes shapes, JPG stores a grid of pixels, and the engine rasterises at 150 dots per inch on the way across. That density is a deliberate choice: at the 72 dpi ImageMagick defaults to, an A4 SVG page comes out 595 pixels wide and reads as a failed conversion. Enlarge the JPG afterwards and it blurs, because there is nothing left to redraw from.
Why did my transparent SVG background turn white in the JPG?
Because JPG has no alpha channel and something has to sit behind the picture. The engine puts white there on purpose. Left to itself ImageMagick puts black, and a transparent SVG logo comes back as a black rectangle. If you need the transparency, send the SVG to PNG or WebP instead.
Is SVG to JPG free?
There is a free allowance every month, and one SVG to JPG conversion costs half a credit against it. When the allowance runs out the tool says so and stops, rather than quietly handing you a worse JPG.