ToolJutsu
All tools
PDF Tools

PDF to SVG

Convert each PDF page into a scalable SVG.

Processed on your device. We never see your files.

How to use PDF to SVG

What is a PDF?

A PDF (Portable Document Format) is a self-contained document file that stores text, vector graphics, raster images and layout information inside a single binary file. Modern PDFs use the same drawing model as PostScript — characters are drawn at specific positions in a chosen font, lines and curves are described as paths, and images are embedded as JPEG or PNG streams. That is why a well-made PDF stays crisp at any zoom level: most of what looks like a graphic is, underneath, a vector description.

What is an SVG?

SVG (Scalable Vector Graphics) is the W3C standard for vector graphics on the web. An SVG file is XML — human-readable text describing shapes, paths, text spans, gradients and embedded images. Because everything is described mathematically, an SVG scales from a 16-pixel favicon to a billboard without losing sharpness, and every modern browser, design tool and operating system can render it. SVG is also editable: you can open one in a text editor and change a colour by hand, or open it in Illustrator and rework the artwork.

Why convert PDF to SVG?

The most common reason is design reuse. A logo, a diagram, an illustration or a chart trapped inside a PDF is hard to drop into a web page, a Figma file or an Illustrator artboard. Convert the page to SVG and you get a vector asset you can paste anywhere, resize freely and restyle.

The second reason is the web. Embedding a PDF page directly into a website requires either a clunky <embed> tag or a heavy PDF.js viewer. An SVG drops straight into HTML, scales with the viewport, looks crisp on Retina displays and weighs a fraction of the original PDF.

The third reason is printing and signage. Sign-making, screen printing, vinyl cutting, laser engraving and CNC routing all consume vector input. Converting a PDF page to SVG is often the first step in getting a customer’s artwork into a production tool.

How to use this PDF to SVG converter

  1. Drop your PDF onto the dropzone, or click to browse. The file is opened locally by pdf.js — nothing is uploaded.
  2. Pick a render scale between 1× and 3×. This only matters if the converter falls back to raster mode — vector output is resolution independent. 1× is web-sized, 2× is Retina-sharp, 3× is print-grade.
  3. Click Convert. The converter walks each page of the PDF, asks pdf.js for an SVG representation, and either captures the native vector output or rasterises and wraps it.
  4. When the conversion finishes, you get a single ZIP containing one SVG per page (named page-1.svg, page-2.svg, …) plus the option to download each page individually.

Quality tips for PDF to SVG

If the source PDF was made from a vector design tool (Illustrator, Affinity, Figma export, InDesign), the native vector backend will almost always succeed and you will get small, editable SVGs. PDFs from scanners, photo apps or PDFs that have been “flattened” before export are essentially images, and the converter will hand you raster SVGs no matter what scale you pick.

If you only need one page out of a 200-page PDF, use ToolJutsu’s PDF Splitter first to extract that single page, then convert. The converter loads every page into memory, so big PDFs are slower.

When the output goes into Figma or a website, leave the render scale at 1× — vector SVGs look the same regardless, and rasterised ones get needlessly heavy at higher scales. Bump the scale to 2× or 3× only when you know you need it for print or large displays and the converter is falling back to raster.

Privacy

Your PDF never leaves your browser tab. pdf.js opens it in memory, each page is converted in JavaScript on your device, JSZip packs the result locally, and the download streams straight from the browser. No upload, no temporary server copy, no metadata logged. The pdf.js and JSZip libraries are loaded once from this site and then cached — turn off Wi-Fi after the page loads and the converter still works.

Browser compatibility

The tool runs in any modern browser with full File API and Blob-download support — Chrome, Edge, Firefox, Safari, Brave, Arc and Opera on desktop, recent iOS Safari and Android Chrome on mobile. Output SVG files conform to SVG 1.1 and open identically in browsers, Inkscape, Adobe Illustrator, Affinity Designer, Figma and Sketch. Note that very large PDFs (hundreds of pages, or pages with dense artwork) may exceed mobile-browser memory limits — for those, use a desktop browser.

Frequently asked questions

Will the SVG output be true vector or a rasterised image inside an SVG wrapper?
It depends on the PDF and on which pdf.js build your browser loaded. When pdf.js's native SVG backend can interpret the page (text drawn as glyphs, vector paths, simple gradients), the result is a real, scalable, editable SVG with selectable text and vector shapes. When pdf.js falls back — most often for PDFs that use unusual fonts, custom shaders or scanned pages — the converter rasterises the page to a PNG at your chosen scale and wraps that PNG inside an SVG <image> element. You still get an .svg file, but the contents are pixels, not paths. The tool tells you which mode was used after conversion.
How large will the output files be?
Vector SVGs for a typical text-heavy PDF page are usually 20–80 KB each — sometimes smaller than the original PDF page. Rasterised SVGs are larger and scale with the render scale you pick: 1× gives roughly 100–300 KB per page, 2× gives 400 KB to 1 MB, and 3× can hit 2 MB on a complex page. Pick the lowest scale that still looks crisp on your target display.
Can I open the result in Illustrator, Inkscape or Figma?
Yes — every output is a standards-compliant .svg file. Adobe Illustrator, Affinity Designer, Inkscape, Sketch and Figma all import SVG. If the SVG is the vector kind, you can select and edit text, recolour shapes and rearrange paths. If it is the rasterised kind, you can still place it on a canvas and trace over it, but the embedded image itself is not editable as vectors. For Figma in particular, drag the .svg straight onto the canvas — it becomes a frame containing the page contents.
What happens to fonts in the SVG?
When the vector backend runs, pdf.js converts each glyph into an SVG path, so fonts are baked in as shapes — no font file dependency, no licensing issue, and the SVG renders identically everywhere. The trade-off is that the text is technically no longer selectable as characters in a text editor; tools that recognise SVG text do still let you edit by re-typing on top. When the converter falls back to raster mode, the fonts are simply part of the pixel image.
Is my PDF uploaded or stored anywhere?
No. The PDF is opened in the browser by pdf.js, the page-by-page conversion runs entirely in JavaScript on your device, JSZip packs the SVGs into a ZIP locally, and the download is served straight from the browser's memory. Nothing is sent to a server, no copies are kept after you close the tab, and the libraries the page uses are cached after first load so you can verify by disabling Wi-Fi before clicking convert.

Related tools