Inkscape Export Guide: SVG, PNG and PDF for Handoff

Suppose you have a product illustration with editable text and a placed photograph. A developer wants a web PNG. Someone else asks for a downloadable PDF. The useful question is what each person needs to receive, including what should remain editable.

Start there. A favorite DPI setting cannot answer a handoff question. Keep the SVG master, agree on the delivery requirements, then create the copies. This guide follows the documented concepts in the Inkscape Beginners' Guide; interface labels can vary by version. The illustration is hypothetical, and the checks below are proposed. No exports were executed for this article.

Choose an editable master and the right delivery format

Keep an Inkscape SVG master

Save an Inkscape SVG before making delivery copies. The saving guide distinguishes Inkscape SVG, which retains editor-specific data, from Plain SVG, intended for sharing with other SVG users. Plain SVG is still SVG. Choosing it does not turn the drawing into a raster image or promise identical editing features in another application.

Use the master for future corrections. Give delivery files distinct names so that a request to change a label leads back to the editable objects. Nobody should have to guess which file contains the source. Keep backups separately, too; frequent saves alone are not a recovery plan.

Use a format decision table before exporting

Ask what the recipient will do with the file. Use that answer to choose the format.

The PNG specification defines a raster format, not an editable Inkscape drawing. PDF can contain both vector content and raster images. The PDF guide warns against keeping only a PDF, because SVG and PDF support different features.

Treat this table as a starting decision. Web optimization and accessibility need their own checks, as do print suitability and compatibility with the recipient's tools.

Choose the PNG export area before changing resolution

Page, Drawing, Selection or Custom?

Set the rectangle first. The PNG export documentation describes the following choices, although your installation may arrange or label the controls differently.

In the hypothetical illustration, imagine a small icon alongside a headline, with generous page margins. The page makes sense for the whole composition. To deliver the icon alone, inspect an area based on its selection. Using the same rectangle for both requests would need a reason.

If the recipient wants whitespace around the artwork, agree on it explicitly. The drawing's bounds need not match the page, and neither automatically settles the delivery rectangle. Raising the resolution will not resolve that decision. The documented page-resizing approach changes the page size itself, so use it only when that is the change you intend.

Separate export bounds from clips and masks

Selection defines an area in this context. Do not assume it also hides every overlapping unselected object. Check the installed version's object-isolation options before relying on that behavior.

The clipping and masking guide describes clips as hiding portions of an object, while masks affect opacity. Neither operation should be treated as deleting or sanitizing the editable source. If you are sharing that source, review its contents separately from the visible crop.

Set PNG pixel dimensions and background deliberately

Start with the destination's width and height

Get the required pixel dimensions and aspect ratio from the destination. A website component may need a different composition from a document illustration. If those requirements are missing, ask for them before choosing a DPI value.

In the documented export panel, image size in pixels and resolution are related: changing one adapts the other values. For a web PNG, use the required final width and height as the acceptance check. Exporting a larger image is not evidence that a placed photograph has gained source detail.

Diagnose each mismatch on its own. A correct pixel count says nothing about whether the crop includes the intended label. Once the rectangle is right, check dimensions. Review the background separately rather than changing several settings and hoping one fixes the problem.

If the requested aspect ratio does not fit the illustration, agree on a crop or revise the layout. Do not silently remove a label or stretch the composition. Record the agreed rectangle and dimensions in the handoff note; the next revision should not have to reopen the same decision.

Check transparent and opaque backgrounds separately

The same PNG guide explains transparent backgrounds and documents background alpha controls for an opaque color. Find the equivalent controls in your version instead of following an older screenshot by position.

Transparency suits artwork intended to sit over another background. An opaque background suits a composition where that color belongs in the delivered image. Choose intentionally. A background change will not repair the wrong crop.

Reopen the exported PNG and inspect its reported dimensions. Check the edges against contrasting backgrounds, then preview it at the intended size in the destination. These are checks for you to run, not results produced for this guide.

If this illustration is also headed into a captioned product video, review the graphics separately from the captions. The Remotion caption and subtitle export guide covers that adjacent timing and output decision; it does not explain Inkscape settings.

Check linked images before handing over an SVG

Choose linked or embedded raster assets intentionally

The photograph brings a dependency into the hypothetical handoff. As the image-import guide explains, linked raster images rely on external files remaining available. Sharing the SVG without those files can break that relationship.

Embedding puts the raster data inside the SVG, increasing its size. That addresses the image dependency. It does not convert pixels to vector paths, and fonts still need attention. Usage permissions are a separate question regardless of how the image is stored.

Review a copy without disturbing original assets

Make a separate copy of the intended handoff package and inspect it. Leave real source assets in place; deleting or renaming them is an unnecessary way to test for broken links. Ask the recipient to open the copy in the actual target viewer or editor where possible.

Be precise about what this proves. SVG linking rules allow external resources, so a copied SVG opened on the same computer may still find its original linked files. Moving it to another folder therefore does not establish an independent package. A recipient-side review is preferable; if it cannot happen, mark portability as unverified.

Record the environment you checked and any remaining dependencies. A successful opening there is useful evidence, but it cannot promise portability everywhere. Include font requirements and image permissions in the handoff note rather than describing an SVG with embedded images as completely self-contained.

Create a PDF copy with font and filter trade-offs in view

Preserve the SVG and choose text handling

The PDF export guide describes Save a Copy as a way to create a PDF while retaining the SVG. That is a documented control name, not a walkthrough verified against the latest release.

For searchable text, the PDF guide describes embedding fonts where licensing permits it. Converting decorative lettering to paths is another option, but it changes editability and searchability. Choose according to the recipient's needs and keep the editable master. Neither choice alone establishes PDF accessibility.

Review filtered areas and the recipient's requirements

The PDF guide describes rasterizing filtered objects or areas to preserve their appearance. Its resolution setting applies to those rasterized areas. It does not improve every piece of vector geometry in the document.

Open the PDF in the intended viewer and compare it with the source. Begin with page bounds and text, then inspect placed imagery and filtered effects. Record differences against the delivery requirements. Saving successfully is not approval, and this comparison has not been run for the hypothetical illustration.

For professional print, get the printer's requirements and consider an appropriate desktop publishing workflow. This guide does not establish CMYK handling, PDF/X compliance or press readiness. The older documentation's PDF version choices should not be read as an exhaustive list of current support either.

The Master-to-Delivery workflow: one illustration, checked derivatives

Define the handoff and preserve the source

Master-to-Delivery names the checklist used here: Preserve, Specify, Export and Reopen. It is an editorial framework, not an Inkscape feature or an external standard. It has not been tested as an Optijara process.

For the hypothetical illustration, retain the editable SVG with its photograph. Record the web recipient's PNG requirements, including whether a PDF is needed as well. Each branch below starts with that same source.

Use this checklist to keep the decisions visible while preparing the copies.

Export, reopen and package the deliverables

For the PNG, settle the area before setting the destination's pixels. Choose the background explicitly. For the optional PDF, create a copy and review text handling alongside filtered areas. Keep the SVG even if the derivatives look convincing.

A handoff note records intent. The illustrative JSON below uses identifiers, not instructions or export configuration, and it is not an approval receipt. Record the actual required dimensions and other delivery details in your note. Add observations only after inspecting the files.

{
  "workflow": "master-to-delivery",
  "stages": [
    "preserve",
    "specify",
    "export",
    "reopen"
  ],
  "master": "inkscape-svg",
  "deliverables": [
    "web-png",
    "optional-pdf"
  ],
  "requirements": [
    "bounds",
    "dimensions",
    "background",
    "dependencies"
  ],
  "review_status": "proposed-unexecuted"
}

Use this measurement plan to retain evidence from those inspections. An unperformed check remains unperformed.

Package only the intended files. If AI-generated imagery is involved, keep source records separately; the visual-content provenance guide addresses that evidence question. The proposed checks above contain no measured export results.

Common export mistakes and the limits of this guide

Fix the mismatched decision, not an unrelated setting

The most useful export habit is to stop treating resolution as a universal repair. For the hypothetical icon, a wrong crop calls for checking the area. Unexpected transparency calls for reviewing the background. Neither symptom justifies changing DPI first.

A missing photograph in a shared SVG points you toward linked assets. Changed PDF lettering or effects calls for reviewing font and filter choices. Follow the symptom back to the relevant decision, then inspect the new output.

Keep the source, too. Retaining only a derivative makes the next edit a different problem. Other avoidable mistakes include treating Plain SVG as raster conversion or assuming embedded images also package fonts. The master and dependency note keep those distinctions available at handoff.

Know what still needs application and recipient testing

The cited Beginners' Guide identifies revision 67a2710. It supports the concepts used here without establishing that every current menu or format option is unchanged. No Inkscape installation, application launch, export, font test or recipient-rendering test was performed for this article.

A visual review also has limits. Recipient-specific rendering needs checking in the relevant environment. Accessibility and professional print require separate assessments, as does content sanitization. End the handoff with a record of what was inspected and what remains unresolved. Make it clear which file the recipient should return to for future edits.