Studio

Draw here, render anywhere.

Export the canonical studio document or the canvas-ready chart in one click, or copy a version-pinned embed snippet straight from the dialog. Golden tests guarantee the render matches the drawing.

Explore highlights

Sound familiar?

Export formats that drift

An editor whose export the renderer barely understands is two products, not one. Studio's canvas export is parity-tested against the renderer.

Hand-converting editor to renderer

Glue scripts between the drawing tool and the map are a tax on every chart. The canvas JSON export is the renderer's native meal.

Does it render? anxiety

Finding out at deploy time is finding out too late. validateCanvasChart and golden fixtures answer it at export time.

One document, every destination

01The canonical studio JSONexportStudioJson downloads the full editable document, your source of truth for future edits.
02Canvas-ready exportexportCanvasJson produces exactly what the renderer eats, blocks, objects, focal point, floors.
03Copy-paste embedsThe embed dialog generates a module-script snippet and an iframe variant, pinned to a renderer version.
04A typed handoffgetCanvasChart returns the typed object for programmatic pipelines, no parsing downloads.
05Validation built invalidateCanvasChart checks the payload against the renderer's contract before it ships.
06Golden-tested parityExports render against canvas fixtures in CI. What you drew is what buyers get.

From drawing to deployed

  1. 01Draw the chartEverything lives in the studio document as you work.
  2. 02Export both worldsStudio JSON for editing, canvas JSON for rendering.
  3. 03Copy the embedThe dialog's snippet drops the live map into any page.
  4. 04Trust the parityValidation and golden tests keep draw and render identical.

Export your first chart

JSON and embeds, live in the demo.