Choose a supported import, processing, or export workflow

Scribe uses different processing workflows for different outcomes. Choosing the right product surface prevents unnecessary conversion, preserves editability, and makes failures easier to diagnose.

This page documents supported behavior and user-visible handoffs. It does not expose private source imports or promise that Scribe's internal processing modules are a standalone software-development kit.

ActivecreatordesktopdeveloperReference

Verified against frontend@2.0.0

Start with the result you need

You have	You need	Use
SVG or SVGZ artwork	Editable normalized vector paths	Vectors → Vector Import
PNG, JPG, WebP, or other supported raster	A normal image object	Images import
High-contrast raster line art	Drawable vector paths	Vectors → Vector Import, then tracing
Template JSON	Editable block, scene, or project state	Import AI JSON or the supported template import
Drawable vector paths	A deliberate hand-drawing route	DRAW and stroke planning
Current scene	Static vector artwork	Static SVG export
Animated project	Timed video with camera and audio	MP4 video export

Do not trace a raster image when you only need to display the original pixels. Do not rasterize a valid SVG before import when editable vector paths are the goal.

SVG and SVGZ intake

The vector importer recognizes supported SVG-family input, sanitizes markup, extracts drawable geometry, applies supported transforms, validates complexity, and reports skipped or unsupported content.

Use it when you need:

• editable paths;
• Draw Steps or Draw Progress;
• stroke materials;
• path-level ordering; or
• a drawing hand to follow the geometry.

SVG files containing scripts, event handlers, unsupported animation markup, or unsafe external content are not treated as trusted input. An SVG can be visually valid in a browser and still be a poor animation source if it has flattened fills, excessive path counts, or an unhelpful path order.

For the complete user workflow, see Import SVG and vector artwork.

Raster image import versus tracing

A normal image import preserves the raster appearance. Tracing creates vector paths that approximate visible edges or color regions.

Choose normal image import for:

• photographs;
• textured artwork;
• gradients;
• screenshots; or
• content that does not need a hand-drawn reveal.

Choose tracing for:

• high-contrast line art;
• simple diagrams;
• clean icons;
• legally reusable logos with simple geometry; or
• artwork where editable draw paths matter more than exact pixels.

Tracing cannot reconstruct detail that is absent from the source image. Noisy photos and subtle gradients usually create too many paths or an unhelpful result. Use the tested PNG/JPG tracing tutorial before publishing a traced workflow.

Template validation and apply

A template envelope contains:

• schemaVersion;
• meta;
• a block, scene, or project payload;
• optional requiredAssets; and
• optional authoring controls.

Scribe validates supported fields and references before applying template data. A valid structure still needs real editor review for clipping, timing, assets, editability, and playback.

Use:

• Template System reference for the public data contract;
• Author reusable templates for a complete authoring workflow; and
• Create and import AI JSON for generated structured input.

Stroke planning and Draw Steps

Stroke planning operates on drawable geometry that already exists in the scene. It can help order paths and create Draw Steps, but it does not understand the semantic meaning of every region.

Always preview:

1. which region starts first;
2. whether the route jumps unexpectedly;
3. whether reveal ranges are contiguous;
4. whether the selected hand/tool aligns with the path; and
5. whether completed sections remain visible.

For deliberate control, use Drawing hands and Draw Steps. For one object split across several steps, use the multi-step SVG tutorial.

Static SVG versus video export

Output	Preserves	Does not preserve
Static SVG	Current vector appearance	Timeline motion, camera movement, drawing-hand playback, or audio
MP4 video	Timed animation, supported camera output, drawing, and mixed audio	Editable Scribe project structure
.scribe project	Editable project data and packaged assets	A universally playable rendered video

Use the export surface that matches the delivery goal, then inspect the actual file. A success dialog is not a substitute for checking dimensions, duration, audio, and playback.

See Choose and verify an export.

Safety and portability

• Treat SVG, SVGZ, template JSON, and remote assets as untrusted input.
• Do not place credentials, signed secrets, personal data, or private URLs inside reusable templates.
• Prefer packaged or approved assets over expiring links.
• Keep file sizes and path counts reasonable.
• Preserve cancellation and wait for an operation to finish before starting another import or export.
• Review warnings even when the operation reports success.
• Save the editable project before applying a scene or project template that can replace state.

Troubleshooting

Symptom	Likely cause	Recovery
SVG imports but important parts are missing	Unsupported markup, embedded content, or non-drawable geometry	Review importer warnings and simplify the source
Raster trace creates hundreds of paths	Source is noisy or too detailed	Use cleaner line art, increase filtering, or keep it as a normal image
Template validates but looks wrong	Structural validation cannot judge layout or reading time	Apply it in the real editor and fix the authored payload
Draw route jumps between regions	Source path order does not match the story	Reorder paths or author deliberate Draw Step ranges
Static SVG has no camera motion	Static SVG is not a timed video format	Export MP4 for camera and timeline motion
Export completes but playback differs	Browser/codec or unsupported media behavior	Inspect the actual file and retry with supported settings

Public integration boundary

External integrations should depend only on documented schemas, import/export formats, and supported product actions. Private source paths, test commands, and application service topology are not compatibility contracts.

If a future public SDK or CLI exposes a processing API, its own versioned documentation will define that contract. Until then, use Scribe's real importer, validator, template, and exporter surfaces.

Related workflows

• Import SVG and vector artwork
• Turn a PNG or JPG into a hand-drawn animation
• Template System reference
• Choose and verify an export

Verification note

This guide was reviewed against the current user-visible SVG, raster, template, stroke-planning, static SVG, and MP4 workflows. Internal module locations and contributor-only test commands are intentionally outside the public contract.