A conversion can preserve the picture while losing the information needed to edit
it in the same way. Here are a few common paths, rather than a complete compatibility
survey. External-editor behavior below is based on linked vendor documentation;
possible losses during later re-saving are cautions, not claims that every editor
was tested. Canvas Pilot behavior follows its current import/export implementation.
## Three different things to preserve
| What survives? | What that actually means |
| --- | --- |
| Appearance | It still looks right. Text might now be outlines, or several objects might be one image. |
| Editable geometry | Individual shapes can still move or resize. They need not retain their original names, grouping or behavior. |
| Application structure | Components, diagram connections or Canvas Pilot source mappings still have their original meaning. This normally needs native data understood by the receiving application. |
SVG can contain vectors, text, images and extra metadata. The `.svg` extension alone
does not tell you which of those a particular exporter wrote or an importer reads.
## 1. Figma → SVG → another vector editor
**Typical goal:** send a layout or drawing for further visual editing.
Shapes can remain vector artwork. Figma offers text outlining and layer-name IDs:
outlined lettering keeps its shape but ceases to be editable text; keeping text
requires suitable fonts in the receiving environment. Including IDs gives names a
chance to travel, but does not guarantee the destination uses them as layer names.
See [Figma’s SVG export settings](https://developers.figma.com/docs/plugins/api/ExportSettings/).
Treat this as artwork exchange: do not expect the receiver to reconstruct Figma
components, variants, Auto Layout rules or prototype interactions from the SVG.
That is a workflow inference, not a promise about every importer. Returning the
SVG to Figma does not make it a replacement for the original design file.
**Keep:** the original Figma document if those editing relationships matter.
## 2. draw.io → SVG → draw.io
**Typical goal:** share a picture that can also be reopened as an editable diagram.
With **Include a copy of my diagram**, the SVG carries diagram data alongside the
rendering. draw.io can use that data to reopen the diagram. Without it, the SVG
picture alone is not the original diagram model. This is documented by