SVG is an XML description of shapes, which is why it scales to any size. PDF is a frozen page layout with no heading structure a machine can rely on. ImageMagick sits between the two, and this page says exactly what happens to an SVG file on the way to becoming a PDF one.
What runs when an SVG file becomes PDF
ImageMagick 6.9.12, on a machine we rent and watch. Your SVG file is uploaded once, ImageMagick runs once, the PDF comes back, and neither file is kept. SVG to PDF 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 PDF
The pixel dimensions of your SVG file. The PDF comes out the size the SVG went in, because nothing on this path resizes anything.
Every pixel value. SVG and PDF are both lossless, so the PDF file adds no compression artefacts that the SVG did not already have.
The shapes stay shapes: SVG and PDF are both vector, so nothing about this pair is rasterised.
What SVG to PDF costs you
Transparency. PDF 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.
The chance of getting text out. The PDF you receive is one page with your SVG picture painted on it. Words inside the SVG stay pixels, and nothing reading that PDF will find them.
If a model is going to read the PDF
Worth knowing before the PDF goes anywhere near an assistant: this is the wrong direction for that. A PDF is a set of positioned glyphs, and a model has to reconstruct the reading order before it can begin. If a machine rather than a person is going to read this SVG file, convert it to Markdown instead and skip the reconstruction entirely.
SVG to PDF, measured rather than promised
Running SVG to PDF against the real engine with a real file, ImageMagick wrote 4,195 bytes of PDF 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 PDF 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 PDF 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 PDF can be read against something. Sizes do not compare across engines, because each family was probed with its own SVG witness file.
SVG to JPG: 2,483 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 PDF, and what they measured
Among the published routes into PDF, SVG is the number 25 largest output of the 26 measured. The witness files differ, so this ranks the probe run and not your document.
HEIC to PDF: 94,782 bytes in under a tenth of a second.
BMP to PDF: 118,745 bytes in under a tenth of a second.
GIF to PDF: 1,092,578 bytes in 0.9 seconds.
HEIF to PDF: 94,782 bytes in under a tenth of a second.
ICO to PDF: 95,344 bytes in under a tenth of a second.
What we will not pretend about SVG to PDF
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 PDF 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 PDF 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 PDF, 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 PDF: what people ask
What actually converts my SVG file to PDF?
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 PDF comes back, and neither file is kept afterwards.
How long does SVG to PDF take?
On the file the probe used, ImageMagick took under a tenth of a second and wrote 4,195 bytes of PDF. 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 PDF?
The one to know about first: Transparency. PDF 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.
Can I put several SVG files into one PDF?
No. One SVG file goes in and one PDF comes out, with that picture on it. Nothing here merges files, orders them or numbers pages: it is one upload, one conversion, one download, and that is the whole of what this page does.
Is SVG to PDF free?
There is a free allowance every month, and one SVG to PDF 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 PDF.