On this page
Use a vector rendering pipeline
Canvas export turns the complete SVG into pixels. A vector PDF renderer can retain supported paths, shapes, fills, strokes, gradients and text as PDF drawing operations.
Embedded PNG and JPEG elements remain raster by design, but they should not force unrelated vector geometry to become raster.
Make the SVG self-contained
Embed required images and styles rather than depending on remote URLs. External resources may be blocked for privacy, security and reproducibility.
Declare width, height and viewBox consistently so page fitting uses predictable bounds.
- Embed raster images as data URLs.
- Use explicit font-family declarations.
- Remove scripts and foreignObject HTML.
- Review masks, filters and patterns.
Review advanced effects
Complex masks, blur, shadows and blend modes vary across SVG and PDF renderers. Use the preflight warnings to identify where visual comparison matters.
Scaling ordinary vector geometry does not reduce resolution, but scaling an embedded bitmap beyond its source dimensions can reveal pixels.
Put the workflow into practice
Arrange source documents, select the pages you need, and create one PDF locally in your browser. Review the result before choosing any optional next step.
Try SVG Export StudioFrequently asked questions
Clear answers before you merge
Does every SVG feature map directly to PDF?
No. Paths and common paint operations map well, while filters, masks and browser-specific CSS may vary.
Should I convert text to paths?
Only when font portability matters more than searchable and editable text, and only with a reliable authoring workflow.
