{"id":979,"date":"2026-11-05T13:33:32","date_gmt":"2026-11-05T05:33:32","guid":{"rendered":"https:\/\/en.meishesdk.com\/blog\/?p=979"},"modified":"2026-11-05T13:33:32","modified_gmt":"2026-11-05T05:33:32","slug":"make-videos-programmatically-with-json","status":"publish","type":"post","link":"https:\/\/en.meishesdk.com\/blog\/979.html","title":{"rendered":"Make Videos Programmatically with JSON"},"content":{"rendered":"\n

The cleanest definition of programmatic video: a video is a document, rendering is a function, and the document is JSON.<\/strong><\/p>\n\n\n\n

Describe the timeline as structured data \u2014 which clips, on which tracks, what text, which effects, how long \u2014 hand it to a rendering engine, and collect an MP4. No framework lock-in, no browser choreography, no proprietary project files that only one application can open. Just data in, video out.<\/p>\n\n\n\n

Meishe’s rendering pipeline works exactly this way, and its JSON examples are worth reading even if you end up choosing another engine \u2014 they show how completely a professional video can be expressed as plain data.<\/p>\n\n\n\n

The Anatomy of a Video-as-JSON<\/h2>\n\n\n\n

Strip the specifics and every JSON video description has the same skeleton:<\/p>\n\n\n\n

timeline\n\u251c\u2500\u2500 videoTracks[]        \u2192 clips with paths, in\/out points, speed, flips\n\u251c\u2500\u2500 audioTracks[]        \u2192 music and voice, volumes\n\u251c\u2500\u2500 captionTracks[]      \u2192 text: styling, animation, timing\n\u251c\u2500\u2500 stickerTracks[]      \u2192 images, stickers, watermarks\n\u251c\u2500\u2500 timelineVideoFxTracks[] \u2192 filters and effects with intensity\n\u2514\u2500\u2500 duration, fps, resWidth\/resHeight, videoSize<\/code><\/pre>\n\n\n\n
The parts that surprise teams new to JSON video:<\/p>\n\n\n\n
Time is in microseconds.<\/strong> Not seconds, not frames \u2014 microseconds, because the engine resolves frame boundaries itself at the output fps. Precision belongs to the machine.<\/p>\n\n\n\n
Effects are parameterized.<\/strong> An effect isn’t baked into a clip; it’s an object with a type, an intensity between 0 and 1, and a parameter list. “Warm filter, 60% strength, from second two to second five” is three JSON fields.<\/p>\n\n\n\n
Everything is addressable.<\/strong> Because every element is a field, every element is automatable. The title, the clip order, the transition timing \u2014 nothing in the document requires a human at an editing surface.<\/p>\n\n\n\n
\"Make<\/a><\/figure>\n\n\n\n
Why JSON Beats Code-Described Video<\/h2>\n\n\n\n
Frameworks that describe video as code (React components and the like) are powerful for developers. But data as the source of truth has structural advantages for products:<\/p>\n\n\n\n
Any stack can generate it.<\/strong> Python, Go, Node, a no-code zap, an LLM \u2014 anything that can assemble a JSON object can author a video. Your rendering pipeline stops caring what your backend is written in.<\/p>\n\n\n\n
Templates are data, not codebases.<\/strong> A template is a JSON document with holes in it. Fill the holes from your database, post the result. Versioning templates is versioning documents \u2014 diffable, reviewable, roll-back-able.<\/p>\n\n\n\n
Storage, search, and audit work.<\/strong> Millions of render requests as JSON documents are queryable: which templates ran, which assets appeared, what durations shipped. Try doing that over a folder of React components.<\/p>\n\n\n\n
The same document opens in an editor.<\/strong> This is the Meishe-specific kicker: the JSON your pipeline renders is the project the interactive editor edits. Machine output and human refinement share one format \u2014 no export\/import bridge, no lossy conversion.<\/p>\n\n\n\n
A Real Payload, Abbreviated<\/h2>\n\n\n\n
From Meishe’s examples \u2014 one clip, one styled caption, enough structure to recognize:<\/p>\n\n\n\n
{\n  \"timeline\": {\n    \"duration\": 49200000,\n    \"fps\": 25,\n    \"resWidth\": 960,\n    \"resHeight\": 540,\n    \"videoSize\": \"16:9\",\n    \"videoTracks\": [{\n      \"videos\": [{\n        \"path\": \"https:\/\/your-cdn.com\/clip.mp4\",\n        \"inPoint\": 0,\n        \"outPoint\": 49200000,\n        \"trimIn\": 0,\n        \"trimOut\": 49200000\n      }]\n    }],\n    \"captionTracks\": [{\n      \"captions\": [{\n        \"text\": \"Spring Sale\",\n        \"inPoint\": 5200000,\n        \"outPoint\": 20000000\n      }]\n    }]\n  }\n}<\/code><\/pre>\n\n\n\n
Every field there is one you could generate from a spreadsheet row. That’s the entire trick: if your data has a title, a clip URL, and a duration, your data has a video.<\/strong><\/p>\n\n\n\n
Designing Your Own Video JSON Layer<\/h2>\n\n\n\n
If you’re building a product on JSON-driven video, three practices pay for themselves immediately:<\/p>\n\n\n\n
Separate business data from timeline data.<\/strong> Your API should accept {\"product\": {...}, \"template\": \"promo-v2\"}<\/code> \u2014 not raw timelines. Let a template-resolution step merge them. Designers change templates; your payload schema stays stable for years.<\/p>\n\n\n\n
Validate before you queue.<\/strong> Missing media URLs, zero durations, unreachable paths \u2014 catch them at payload build time, not at render time. A render farm discovering a broken URL is the most expensive possible validation.<\/p>\n\n\n\n
Treat renders as idempotent jobs.<\/strong> Same JSON in, same video out. Retry-safe, cache-friendly, and the foundation for per-template metrics when volume grows.<\/p>\n\n\n\n
From JSON to Farm<\/h2>\n\n\n\n
Single videos validate the pipeline; scale proves it. Meishe’s batch rendering architecture \u2014 task scheduler, worker fleet, shared storage \u2014 exists precisely for the JSON-in\/video-out loop at volume: nightly catalog runs, personalized campaigns, continuous content generation. The same payloads that render once in testing are the payloads the farm chews through in production.<\/p>\n\n\n\n
Start with one timeline, one render, one honest look at the JSON examples. The moment a video becomes data, everything downstream \u2014 generation, versioning, scaling, automation \u2014 becomes an engineering problem you already know how to solve.<\/p>\n","protected":false},"excerpt":{"rendered":"
The cleanest definition of programmatic video: a video is a document, rendering is a function, and the document is JSON. Describe the timeline as structured data \u2014 which clips, on which tracks, what text, which effects, how long \u2014 hand it to a rendering engine, and collect an MP4. No framework lock-in, no browser choreography, no […]<\/p>\n","protected":false},"author":1,"featured_media":980,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[155,4,10],"class_list":["post-979","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-video-editor-sdk","tag-make-videos-programmatically","tag-meishe","tag-video-editing-sdk"],"_links":{"self":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/979","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/comments?post=979"}],"version-history":[{"count":1,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/979\/revisions"}],"predecessor-version":[{"id":981,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/posts\/979\/revisions\/981"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/media\/980"}],"wp:attachment":[{"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/media?parent=979"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/categories?post=979"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/en.meishesdk.com\/blog\/wp-json\/wp\/v2\/tags?post=979"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}