How to Convert SVG to PDF: Size and Font Settings

You exported an SVG from a design program, a charting library produced an SVG, or you have a vector logo — and you need to share or print it as a PDF. SVG to PDF conversion is technically a direct operation because the two formats share the same vector model, but three things need attention: page size, fonts and color.

Why you'd convert to PDF

SVG is an excellent web format but it has limits in the document world:

Sharing. When you email an SVG file, how the recipient will open it is uncertain. It opens in a browser, but double-clicking may open it in a text editor. PDF behaves as expected everywhere.

Printing. Print dialogs generally don't handle SVG well; page size and scaling are uncertain. PDF was designed for print.

Multiple pages. SVG is single-page. If you want to collect several graphics in one document, you need PDF.

Official documents. Documents sent to institutions, archived and signed come as PDF.

Step 1: Nail down your SVG's page size

This is the most problematic point of the conversion and something to solve in advance.

An SVG file's root element can carry three relevant attributes:

<svg width="210mm" height="297mm" viewBox="0 0 595 842">

• viewBox: defines the content's coordinate system. It isn't a physical measurement.
• width / height: the size in physical or pixel units. Can be with units (mm, cm, in, pt) or without.

What happens in conversion depends on these values:

| What's in the SVG | What happens in the PDF | |---|---| | width="210mm" height="297mm" | An A4 page at the right size | | width="595" height="842" (unitless) | Interpreted as points, still A4 | | width="800" height="600" (pixels) | About 282 × 212 mm, an odd size | | Only viewBox, no size | The converter guesses, the result varies |

Practical advice: before converting your SVG to PDF, specify the width and height attributes explicitly in millimeters. Opening the file in a text editor and editing by hand is enough:

<svg width="210mm" height="297mm" viewBox="0 0 595 842" ...>

That single edit guarantees the resulting PDF is exactly A4.

Step 2: Solve the font problem

SVG files don't embed fonts; they say font-family="Roboto" and expect that font to be found.

When converting SVG to PDF, the converter has to decide what to do with the text:

If the font is found, it's embedded into the PDF and the text stays real text — selectable, searchable, accessible.

If it isn't found, the converter falls back to a similar font. Letter widths change, alignment shifts, lines can overflow. With custom and commercial fonts that's practically certain.

There are two safe approaches:

Convert the text to outlines. In the program that produces the SVG (Illustrator, Inkscape, Figma), run the text through "convert to outlines" / "convert to path." Every letter becomes a vector shape, the font dependency disappears, and the appearance is guaranteed. The cost: the text can no longer be selected or searched.

Install the font on the system. If the font is installed in the environment where you do the conversion, it gets embedded correctly. In a browser-based tool that means the browser being able to reach that font.

The decision criterion: if the document will be read and searched, leave it as text; if it will only be used visually or is going to print, convert to outlines.

Step 3: Convert

Open the SVG to PDF converter and upload your file. The processing runs in your browser; the file doesn't go to a server.

If you want to combine multiple SVGs into a single PDF: convert each one to PDF separately, then collect them into one file with a merging tool. You control the page order at the merging stage.

Step 4: Check the output

Open the PDF you downloaded and go through this list:

Is the page size right? Look at the page dimensions in Document Properties. If you expect A4 you should see 210 × 297 mm.

Are the fonts right? Does the text look the way it did in the SVG? Check accented and language-specific characters especially — missing character support shows up there most.

Does the content fit the page? Is anything overflowing or clipped at the edges? That can happen if viewBox and width/height don't match.

Are the colors right? SVG is RGB-based and usually stays RGB in the PDF. If it's going to print and CMYK is required, the conversion doesn't do that — a separate color conversion is needed for your print shop.

Is transparency preserved? opacity and masks in SVG have equivalents in PDF, but complex filters (blur, shadow and so on via the <filter> element) aren't handled the same way by every converter. If you used filters, check for visual differences.

Zoom test. Zoom the PDF to 800%. If the content stays sharp it was carried across as vector. If it pixelates the converter may have rasterized the page — a solution resorted to with some complex SVGs, and one that affects print quality.

Step 5: Extra preparation if it's going to print

You're sending a PDF produced from SVG to a print shop. There are three gaps and the conversion doesn't fill them:

CMYK. SVG is RGB and the resulting PDF is RGB too. The print shop wants CMYK. You need to do the color conversion in a design program or let the print shop do it — in the second case you accept that the colors may not come out exactly as you want.

Bleed. If there are colored areas running to the edge, the design needs to extend 3 mm beyond the edge as a trimming tolerance. There's no such concept in SVG; you have to design the canvas larger to include the bleed from the start.

Crop marks. The marks showing the print shop where to cut. You have to add those to the design by hand too.

If the print job is serious, importing the SVG into a design program and producing a print-ready PDF from there is a more reliable route.

What gets lost

SVG features with no equivalent in PDF are lost in conversion:

| SVG feature | In PDF | |---|---| | SMIL / CSS animation | The first frame is frozen | | JavaScript interaction | Lost | | Mouse events (hover, click) | Lost | | Dynamic styling with CSS | Frozen | | Some filter effects | Approximated or rasterized | | <foreignObject> content | Usually lost |

Hyperlinks (<a> elements), on the other hand, are converted into PDF link annotations by some converters — a rare transfer that actually works.

Common mistakes

Not specifying the page size. The most common problem. Add the width and height attributes in millimeters.

Forgetting to convert text to outlines. On a critical design, the font coming out different can mean redoing the work.

Sending RGB for print. The print shop wants CMYK; colors in an RGB file can print differently than expected.

Working with complex filters. With SVGs containing blur, shadow and blend modes, the converter may choose to rasterize the page; that loses vector sharpness.

Forgetting to merge after converting many SVGs one by one. Each file becomes a separate PDF; merging is a separate step.

In summary

SVG to PDF conversion is a reliable operation thanks to the two formats' shared vector model. Success has three conditions: specifying the page size explicitly in millimeters in the SVG's width/height attributes, eliminating the font dependency (preferably by converting text to outlines), and preparing CMYK, bleed and crop marks separately if it's going to print. SVGs containing animation, interaction and JavaScript become static — that isn't a loss but PDF's nature. Checking the page size, the special characters and the sharpness under zoom after conversion finishes the job.