Adapt the language.Keep the visual system coherent.
Use editable captions, template inputs and replaceable voice or media tracks to create localized video variants.
Change every spoken word.Keep the visual direction.
Video localization in JsonCut treats translated copy, captions and media as editable project content rather than baking them into a flattened export.
Translate visible copy
Bind headlines and labels to typed inputs and adjust layout when language length changes.
Keep captions editable
Review word timing, segment text and global style on a dedicated caption track.
Translate the speech
Transcribe the original, translate it line by line and let a Studio voice speak each line in place while the original is muted.
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.

Rail Pass Campaign
Open this example: Rail Pass Campaign
Language Flashcard System
Open this example: Language Flashcard System
Travel App Feature Card
Open this example: Travel App Feature CardCreate one strong source.Publish every version.
- Step 1
Create one strong source
Build the visual in Studio, with the assistant, or from an existing project.
- Step 2
Keep the useful structure
Expose variables only where content should change and keep creative decisions editable.
- Step 3
Publish every version
Export by hand or generate through a template, API, MCP or bulk workflow.
What you can make.
- Localized product demos
- Regional campaign variants
- Multilingual social video
Before you start.The questions we hear most.
Can non-technical users work in JsonCut?
Yes. Studio is the primary visual workflow; API and MCP are additional paths, not prerequisites.
Can developers use the same projects?
Yes. Projects and templates created visually can be inspected and rendered through the API.
Are AI results still editable?
Yes. The assistant works with normal project layers and restorable versions rather than returning a flattened result.