JSON2VIDEO Documentation Video scripts
Video scripts are the dashboard's way of producing a video without writing any JSON or calling the API. A script pairs a template with a set of variable values, gives that pairing a name, and lets you render it — again and again, editing the values between runs.
They live at json2video.com/dashboard/videos, under Video scripts in the dashboard menu.
A video script is a saved answer sheet for a template. The template decides what the video looks like; the script decides what goes in the blanks.
Creating one
- Open Video scripts and click Create video script.
- Pick a template, from either Public templates — the ready-made library — or My templates, the ones saved in your own account.
- Fill in the template's variables. The dashboard walks you through them one field at a time, using the labels, help text and field types the template's author declared in its variables schema.
- Confirm, and the render starts.
The result appears in the list with its status. While a render is running the row updates on its own, and the script cannot be edited or deleted until it finishes.
Writing the script with AI
Templates that come with a prompt (several in the public library, and your own copies of them) also offer to write the script for you: you give a topic and a few answers, and the AI fills in the template's variables. For a template that repeats one scene layout per item — a reel, a ranking, a list — the AI also decides how many items, and so how many scenes the video has.
On the free plan the AI keeps videos short
The free plan's maximum render length is 60 seconds, and a longer video is refused. So on the free plan the AI is told to fit that limit: at most 4 scenes or list items and about 90 words of narration in total. This applies even if the template's example has 10 scenes, the title says "Top 10", or your prompt asks for more words.
So a free account will see an AI script with fewer scenes, or a shorter script,
than the template or the prompt asked for. That is not a broken template and not
the AI ignoring the prompt. The script editor shows a notice when it happens, and
the script's message in the list says
Script shortened to fit your plan's 60s limit….
On every paid plan the maximum is 30 minutes and there is no such cap: the AI follows the template and your prompt.
Managing scripts
Each row's ⋯ menu offers:
| Action | Notes |
|---|---|
| Edit | Change the name, description and variable values, then render again |
| Copy script ID | The script's stable identifier |
| Delete | Permanently removes the script. Unavailable while a render is running |
Editing a script and rendering again is the normal loop: same structure, new content. Nothing about the template changes — several scripts can share one template, each with its own values.
Video scripts, templates and the Editor
Three related things that are easy to confuse:
| What it is | Where you work on it | |
|---|---|---|
| Template | The reusable movie structure, with {{variables}} for the parts that change |
Editor |
| Video script | A template plus one set of values, saved and re-renderable | Dashboard → Video scripts |
| Render | One produced video file | Dashboard → Render logs |
If you want to change what the video looks like — add a scene, move an element, restyle the text — that is the template, and the Editor is where it happens. If you want to change what it says, that is the script.
When to use something else
Video scripts are a dashboard convenience. They are not the automation path:
- To render from your own code or a no-code platform, call
POST /v2/movieswith a template ID and avariablesobject. That is the same idea as a script, driven by your system instead of by hand. - To produce many videos at once, drive the API — see Dynamic scenes for generating repeated content from an array.