Skip to main content

Command Palette

Search for a command to run...

Start Here


title: Start Here slug: /start-here nav_label: Start Here recommended_nav: true

Start Here

Welcome to the Zvid blog. This publication is for developers, founders, marketers, agencies, and automation teams who want to generate videos from structured JSON through an API.

If you are new to Zvid, start with the core idea: instead of editing every video manually, your application can assemble a render payload with text, images, video clips, GIFs, audio, subtitles, timing, dimensions, and output settings. Zvid queues the render job and returns a final video URL when the job completes.

What you will learn here

  • How JSON-to-video rendering works.
  • How to design reusable video templates.
  • How to submit render jobs through the Zvid API.
  • How to poll job status and handle completed or failed renders.
  • How to use structured data for product videos, listing videos, course videos, agency campaigns, and short-form social variants.
  • How to avoid common mistakes in timing, layout, media handling, captions, and review workflows.

A simple Zvid API flow

Most Zvid workflows follow this pattern:

  1. Create an API key in the Zvid dashboard.
  2. Build a JSON render payload in your backend.
  3. Submit the job with POST https://api.zvid.io/api/render/api-key.
  4. Store the returned jobId.
  5. Poll GET https://api.zvid.io/api/jobs/{id} until the render is completed or failed.
  6. Use the completed result.url in your app, CMS, dashboard, or review workflow.

The official docs are a good companion while reading the blog:

Best first articles

Start with these guides if you want the practical path:

Who this blog is for

This blog is for people building repeatable video systems:

  • Developers adding automated video rendering to an app.
  • SaaS teams that need server-side video generation.
  • E-commerce teams creating product videos from catalogs.
  • Real estate, automotive, and education teams generating many structured videos.
  • Agencies creating campaign variants for clients.
  • AI app builders who need a reliable rendering backend for approved scripts, captions, and media.

What this blog is not

This blog is not a promise that every video should be automated. Manual editing is still the right choice for many bespoke, high-concept, or cinematic projects.

The goal here is narrower and more useful: automate the repeatable production layer after the message, brand rules, data source, and review process are clear.

Ready to build?

Open the Getting Started guide, create a small render payload, and test one video end to end. Once that works, design a reusable template around real data from your product, listing, course, client, or content workflow.