JsonCut

Bring the rows.Keep every result visible.

Run a versioned image or video template against CSV or JSON data while preserving row-level validation, status and delivery.

Every row becomes a file.A bad row never stops the rest.

JsonCut bulk workflows use the same template input contract as single rendering and isolate the state of every submitted row.

  • Map once

    Use the published template fields as the stable contract for CSV columns and JSON keys.

  • Fail only the bad row

    A missing asset or invalid value remains attached to that row instead of hiding successful outputs.

  • Deliver deliberately

    Observe the batch summary and hand each completed file to storage, publishing or customer delivery.

Made in JsonCut.Open one to see the project behind it.

Every title, clip and caption in these is still a layer. Open the project and change whatever you like.

Connect JsonCut.Render and deliver.

  1. Step 1

    Connect JsonCut

    Create an API key in Studio under Integrations → API keys and choose the project or template the workflow should fill.

  2. Step 2

    Map data and media

    See which fields the template has, upload your files and map only the values it needs.

  3. Step 3

    Render and deliver

    Start the render, wait for it to finish and pass the file to the next step.

What people make with it.

  • Campaign variant batches
  • Localized media packs
  • Catalog-driven output

Before you start.The questions we hear most.

Do I need to build the visual in code?

No. Create and approve it in Studio, then expose typed fields for the integration.

Can the workflow generate images and video?

Yes. Both project types use the same media, template and job foundations.

How are large media files supplied?

Upload them as project media first and use the returned reference instead of embedding large base64 strings.

Design it once in Studio.Then let your workflow fill it.