Guide · File exchange
Know what crosses the editor boundary.
Import warnings, font requirements, embedded images, and project files are explicit parts of the workflow.
Import SVG as data.
The importer parses supported SVG elements into the editor document model. It does not inject the source SVG into the application document.
Paths, rectangles, circles, ellipses, lines, polylines, polygons, groups, embedded images, and supported text are converted at the boundary.
A future screenshot will identify the file drop area, warning summary, and apply step.
Read warnings before replacing the document.
Missing fonts, unsupported elements or paint, invalid path data or transforms, skipped external images, and fallback canvas sizes are reported before applying the import.
Warnings describe possible loss. They are not silently treated as a successful round trip.
A future example will compare a source SVG with its warning list and imported result.
Provide fonts when text must become paths.
TTF, OTF, WOFF, and WOFF2 files can be supplied during import. Their original bytes are embedded in the document, so the same glyph outlines remain available on the next session and in the saved project file.
You can also continue without the missing fonts. Editable text is preserved either way, but commands that need exact path conversion stay blocked until a usable font is available.
A future clip will show a text-bearing SVG, font registration, and the resulting path geometry.
Choose the output for the next responsibility.
Use SVG for interoperable delivery. Use the versioned SVG-JSON format when the next step is continued editing in this workspace.
Clipboard paste accepts SVG, SVG-JSON, or raster images. Raster content becomes an embedded image rather than editable curve geometry.