Convert PDF to SVG
Convert the first page of a PDF into an SVG made from traced paths. The server renders that page to a bitmap, thresholds it, and follows the resulting regions; it does not extract the PDF's original text, fonts, or vector commands. This can help with a simple black-and-white diagram, but it is intentionally not sold as a lossless PDF-to-SVG export.
Use this without the search next time. Prathom Workbench puts Prathom's tools in your toolbar.
Add to Chrome — freeDrop your PDF file here, or click to browse
Up to 50 MB. Deleted automatically after 30 minutes.
What it does
- Traces the first PDF page into SVG paths
- Useful for simple monochrome page artwork
- Does not pretend to preserve native PDF structure
- Server-side conversion with temporary-file cleanup
How to use PDF to SVG
- 1
Choose a PDF page source
Use a one-page PDF or put the page you need first. The current converter renders only page one, so later pages are not silently combined into the SVG.
- 2
Upload and convert
The server rasterizes the first page, applies a two-tone threshold, and sends the temporary bitmap through a path tracer before writing the SVG.
- 3
Compare with the PDF
Open both files side by side. Check text, thin rules, holes, and page edges; the SVG is a traced approximation and may need substantial cleanup for a document that was not designed as flat artwork.
How it works
The PDF is sent to the server because the SVG path tracer and the PDF raster utility
are native tools. The worker asks pdftoppm for page one and stores that rendered
page as a temporary PNG. PDF coordinates, font drawing, embedded images, fills, and
strokes have already been painted together by that point. The raster is what the
next stage sees; the source object's identity is gone.
ImageMagick then removes alpha from the working image and applies a 50 percent brightness threshold. Potrace reads the resulting black-and-white bitmap, fits curves around its regions, and writes standard SVG path data. This two-stage design is robust for a page that is effectively ink on paper, but it deliberately trades away the distinctions a PDF normally preserves between a word, a line, and a photograph.
When a PDF trace can help
A single-page stencil, seal, monochrome diagram, or scanned line drawing can benefit from the conversion. Such a page already resembles the binary source the tracer needs, and scaling the paths can be more convenient than carrying a page-sized PDF into a cutting or design workflow. It is also a quick way to obtain a rough outline when the only available source is a PDF exported by an old system.
Use the first-page rule deliberately. If the desired artwork is on page seven, make that page a separate one-page PDF before uploading. If the document contains text that must stay searchable, or if it has multiple pages that need to remain a set, this is the wrong conversion. A PDF-to-image tool or a native PDF import will keep more of what the document actually knows.
Honest tracing limitations
The output is not a lossless representation of the PDF. It covers only the first page, discards selectable text and font identity, reduces color and gradients to a threshold, and can turn thin strokes or small counters into missing or joined regions. Photos and detailed charts often produce a crowded collection of paths. The output may be larger than the PDF and can be less useful even when the server reports success.
Review the SVG at its intended size and compare it with the original page. For a logo or technical mark, plan a cleanup pass. For contracts, reports, presentations, or accessible documents, preserve the PDF and choose a format-aware conversion instead. A scalable extension does not make rasterized page content semantically editable.
Examples
A one-page black ink diagram
This is close to the route's intended use. The page has strong contrast and few visual materials, so the main lines and filled symbols can become useful scalable shapes. Small text still deserves inspection because a PDF rendering step and a threshold can join or erase narrow letter strokes.
A multi-page color report
Conversion succeeds, but the result is a poor replacement for the report. It contains no pages two through eighteen, and the first page's photos, colored charts, and text are reduced to black-and-white regions that may be much larger and harder to edit than the source PDF.
Frequently asked questions
Does this extract the vectors already inside a PDF?
No. The current route renders the first page to a bitmap and traces that bitmap. A PDF may contain excellent native paths, selectable text, embedded images, clipping masks, and font information, but those structures are not passed through as corresponding SVG elements here. Rendering first makes the tool work consistently across mixed page content, while also making the conversion lossy. For faithful editability, use a PDF editor or a true vector import path that understands the particular PDF's objects.
Why is only the first PDF page converted?
The server-side converter produces one SVG file and its PDF raster step is deliberately limited to page one. A multi-page PDF is a collection of pages, while a single SVG document is not an equivalent multi-page container in this tool's download flow. Put the required page first or split the PDF before converting. Uploading an eighteen-page report does not create eighteen SVGs, and the page count should be checked before relying on the result.
Will PDF text remain selectable in the SVG?
No. Text is part of the rendered bitmap before tracing, so letters become outlines or fragments rather than SVG text elements with a font and character content. This means search, copy, accessibility semantics, and easy wording edits are lost. Thin fonts and small labels are especially vulnerable to the brightness threshold. If selectable text is important, keep the PDF or use a conversion designed to preserve text objects instead of this tracing route.