Shotstack pricing vs Zvid: the video API head-to-head

Shotstack charges $0.30 per rendered minute pay-as-you-go, or $39/month for 200 credits on subscription (an effective rate of about $0.20/min). Subscription overage is billed at a 30% premium. New accounts start with 10 production credits valid for 30 days, while the separate development sandbox is unlimited for ordinary test renders and watermarks its output. High-volume terms begin at 50,000 minutes per year and require a quote.

Zvid starts free with 1,200 credits, Full HD output, and no watermark, and advertises render pricing up to $0.015/min. Videos at or below Full HD consume one credit per second: a 20-second clip uses 20 credits. Actual cost depends on the selected plan or credit pack, resolution, and usage; compare the published allowances and worked examples for your output volume.

Both services meter partial minutes by the second, so a 30-second Shotstack render uses 0.5 credits rather than a full credit. The meaningful difference is the unit price, allowance, expiry, and overage policy—not rounding. Model those four inputs against your real output mix before committing a production budget.

Shotstack Studio is a template builder: you lay out merge fields, then substitute values via the API. It works for fixed-format videos, but there are no loops or conditionals — a “top 10 products” video means generating ten clip blocks in your own application code.

Zvid ships a full drag-and-drop timeline editor that reads and writes the exact JSON the render API consumes: designers polish visually, developers automate the same document. Templates support variables, placeholders, and native iterate / condition logic, so data-driven videos are described once and driven by data — plus 400+ ready-made templates and presets to start from.

Both give you a browser tool to build with, but at different depths. Shotstack Studio assembles merge fields; Zvid is a full video editor where you edit every scene, element, and asset on a timeline, then use the same JSON to create videos programmatically. A creative library of 400+ templates and canvas presets means most users never start from an empty canvas — and teams arriving from Shotstack edit templates visually instead of regenerating JSON in application code.

Shotstack offers callbacks, official SDKs for Node, PHP, Python, and Ruby, Make and Zapier integrations, a CLI, and a beta MCP server that can compose, preview, render, and manage templates from compatible AI clients.

Zvid’s automation surface includes a 30-tool MCP server with schema-aware authoring and zero-credit pre-flight validation, n8n nodes, a Make app, LangChain tools, and Python/TypeScript SDKs. It also provides native bulk rendering, HMAC-signed webhooks, and live WebSocket render progress.

Whatever service you integrate — an AI agent, a bot that fires on a form submission, or a web app that renders automatically when data changes — the Zvid API responds with a job id in milliseconds and generates the video in the background, so your workflow never blocks on a render.

Both APIs are JSON-first and conceptually similar — tracks and clips in Shotstack, scenes and elements in Zvid — so the mental model transfers in an afternoon. Shotstack’s docs and SDK coverage are mature, and its infrastructure has a long high-volume track record.

Zvid counters with a faster feedback loop: schema validation endpoints catch broken payloads before they cost credits, WebSocket progress replaces polling, and the editor doubles as a visual debugger for any JSON you POST. Image rendering (PNG/JPG/WebP) ships from the same templates on every plan.

Under the hood, a Shotstack video is described as tracks and clips and rendered in its cloud; Zvid renders with FFmpeg, which keeps speed high and output deterministic — the same JSON always produces the same frames. For technical teams building video applications, that predictability makes cloud rendering behave like software you can test: from 9:16 mobile clips to Full HD, with multi-track audio and subtitles handled natively.