JsonCutDocs

How JsonCut works

Understand the shared project model and choose Studio, API or MCP for the job.

JsonCut keeps the creative source and the exported result separate. The source remains an editable image or video project. A render turns one pinned version of that source into a downloadable artifact.

One project, three ways to work

WorkflowWhat you controlChoose it when
StudioCanvas, layers, timeline and visual reviewA person wants to design, inspect or refine the result directly
V2 APIProjects, media, templates, renders and webhooksYour application needs predictable server-side automation
MCPThe same public authoring concepts through focused toolsAn Agent should build, review and reuse editable work

You can start in any column and continue in another. A project created through the API can be opened in Studio. A Studio project can become a typed template. An MCP Agent can edit that same project without flattening it.

The durable workflow

  1. Create an image or video project.
  2. Add owned or uploaded media as normal editable layers.
  3. Review the canvas or timeline and save a version.
  4. Export the current version, or publish it as a template.
  5. Reuse the template with controlled values in Studio, API or MCP.

Source, project, template and render

TermMeaning
SourceThe portable jsoncut-html composition with canvas, layers, variables and values
ProjectA durable source with metadata and immutable version history
TemplateA published project version with a discoverable typed input contract
RenderAn asynchronous image or video artifact from a pinned source or template version

The source contract is public. Internal rendering infrastructure is deliberately not part of it.

Where to continue