SVG to PDF

Convert your SVG files to PDF, right here in your browser.

Free
Private
No limits
No upload

... or drop files here

Files never leave your device

Add a SVG file to convert.

Frequently asked questions

What is actually inside a SVG file?

A .svg file is XML describing shapes, paths and text rather than a grid of pixels, so it stays sharp at any size.

Are my files uploaded to a server?

No. Your SVG file is read and the PDF is built entirely inside your browser, so nothing ever leaves your device.

Can I convert several files at once?

Yes. Add as many SVG files as you like and download the PDFs one by one, or all together as a ZIP archive.

Will the layout look exactly like the original?

The text, headings, lists and tables carry over and are laid out onto clean A4 pages. This is a content-faithful conversion rather than a pixel-perfect copy of the original formatting.

Is there a file size or file count limit?

No. Everything runs on your own device, so the only practical limit is how much memory your browser has available.

Do I need to install anything?

No. There is nothing to install and no account to create — the converter runs in any modern browser, on desktop and mobile alike.

Will my SVG stay vector in the PDF?

No — it is rendered and embedded as a high-quality raster image. Converting vector-to-vector means resolving the SVG's CSS, fonts, filters and references, which only the browser's renderer does correctly, and it renders to pixels. If you need a true vector PDF, Inkscape exports one for free on any platform.

Why does my SVG look low-resolution?

Almost certainly because it has no width and height on its root element — many SVGs carry only a viewBox and leave sizing to CSS, so there is no intrinsic size to render at and the converter falls back to a default of around a thousand pixels wide. Add explicit width and height attributes at the size you want and convert again.

Why did my fonts change?

Because SVG text references a font by name and resolves it at render time from what is available, rather than embedding it. A typeface installed on the designer's machine will not be found here. Convert text to outlines before exporting — Create Outlines in Illustrator, Object to Path in Inkscape — and the letters become paths that render identically everywhere.

Do gradients and filter effects work?

Yes. The rendering is done by the browser's own SVG engine, which handles gradients, masks, clip paths and filters properly, so the result matches how the file looks in a browser.

What about animated SVGs?

You get the initial state. SMIL animation and CSS animation have nowhere to go in a static PDF page, and scripts inside the file are not executed.

Does an SVG that links to external images convert?

It converts, but without them. The tool makes no network requests, so anything referenced by URL rather than embedded in the file will be missing. Embed images as data URIs in the SVG if they need to appear.

SVG and PDF are unusually close relatives. Both describe a page as vector geometry — paths, fills, strokes, text — rather than as a grid of pixels, and both can be scaled to any size without degrading. On paper, converting one to the other should be a translation between two vector languages.

In a browser it is not, and it is worth being straightforward about why. Rendering an SVG means resolving its CSS, its embedded and referenced fonts, its filters, gradients, masks, clip paths and any `<use>` references, and the only thing in the page that knows how to do all of that correctly is the browser's own renderer — which draws to pixels, not to vector geometry. So the SVG is drawn by the browser and the result is embedded as a high-quality raster image.

The output is a PDF that looks right and prints well. What it is not is a vector PDF whose paths you can select in Illustrator. If you need that, the section below says which tools do it.

How to convert SVG to PDF

Add your .svg files
Drop them in or choose them. Each becomes its own PDF.
Convert
The browser renders the SVG exactly as it would on a web page — applying its styles, gradients and filters — and the rendered result is embedded into a page sized to match.
Download
Save the PDF. The conversion happened entirely on your device.

Set a width and height on your SVG

This is the one thing that determines whether the result is sharp or disappointing, and it is easy to get wrong without noticing.

An SVG is resolution-independent, which means many of them carry no intrinsic size at all — just a `viewBox` describing a coordinate space, with the actual dimensions left to whatever CSS on the page decides. That is exactly right for the web and unhelpful here, because rendering requires a pixel size and a file with no intrinsic size gives no basis for choosing one. When that happens the converter falls back to a default width of about a thousand pixels, which is a reasonable guess and nothing more.

If your logo comes out lower-resolution than you expected, this is why. Open the SVG in a text editor and add explicit `width` and `height` attributes to the root `<svg>` element — `width="2000" height="1200"`, say, keeping your viewBox's aspect ratio — and convert again. Larger numbers give a higher-resolution render, because they tell the browser to draw at that size.

Fonts, which are the other common surprise

Text in an SVG is normally text, styled with a font name — and that font is resolved when the file is rendered, from whatever is available where it is being rendered. Not from inside the file.

So an SVG referencing a typeface installed on the designer's machine, or loaded from a web font on the page it was designed for, will render here in a substitute. The layout may shift and the character of the design changes.

The reliable fix is the same one every print workflow uses: convert text to outlines before exporting. In Illustrator that is Type → Create Outlines; in Inkscape, Path → Object to Path; in Figma, Outline Stroke and flatten. The letters become paths, which depend on nothing external and render identically everywhere.

What is supported

Paths, shapes, gradients and filters: All rendered by the browser's own SVG engine, which is thorough — gradients, masks, clip paths and filter effects come through as they appear on a web page.
Embedded raster images: Images embedded in the SVG as data URIs render correctly, because they travel inside the file.
Externally referenced files: Not fetched. An SVG linking to an image or a stylesheet by URL will render without it — the conversion makes no network requests, which is the same property that keeps your file private.
Transparency: Flattened onto white. A transparent SVG background becomes a white page rather than depending on how a given viewer paints behind the page.
SMIL animation and scripts: Not represented. A PDF page is static, so an animated SVG converts as its initial state, and any script inside it is not run.

If you need a true vector PDF

For print production, laser cutting, or an image that must scale indefinitely, a rasterised PDF is the wrong output and no browser-based tool will give you the right one.

Inkscape is free, available on every platform, and exports genuine vector PDF from SVG — File → Save a Copy, choose PDF. Illustrator does the same. On a command line, `rsvg-convert -f pdf` or Inkscape's own CLI will batch it.

This page is for the ordinary case: an icon, a logo, a diagram or an exported chart that needs to be a PDF so it can be attached, printed or filed, without installing anything and without sending the artwork to a website.

About the SVG format

.svg is the vector image format W3C introduced in 2001. It is published as an open specification under the name SVG 1.1 / SVG 2, so a file can be read without the program that wrote it.

A .svg file is XML describing shapes, paths and text rather than a grid of pixels, so it stays sharp at any size.

Files like this usually come out of Illustrator, Inkscape, Figma, and Sketch.

What comes through

pixel dimensions
vector paths

What does not

transparency
animations and transitions

Worth knowing

Vector artwork is rendered at high resolution on the way into the PDF rather than carried across as paths, so it looks crisp on screen and in print but is no longer infinitely scalable.

Information