Your users want a video, not a video editor

A real estate agent wants a listing video. A sales rep wants a personalized intro. An events team wants 500 invitations by Friday. None of them want a timeline or a full editor.

Form to video gives them fields and a Generate button. The layout is fixed and every video comes out on brand. You make the template. Users control the words, images, and clips that go into it.

A multi-track timeline editor next to a four-field form with a Generate button
As millions of users interact with these types campaigns we were going to have to render thousands videos every minute. It quickly became apparent that this type of volume was no issue for Shotstack at all. Raúl Uranga, Technical Director, Grupo W for Ikea

Battle-tested, category-defining performance.

1.1M+

Videos rendered per month

50,000+

Developers

7x

Faster rendering speeds

How form to video works

Three parts, and you already have most of them.

  • Design the template. Build it in Shotstack Studio or write the JSON. Mark the parts that change with merge fields such as {{ HEADLINE }} and {{ FOOTAGE }}.
  • Connect a form. Use a web form, or a hosted form tool that can send a webhook. Map each form field to a merge field.
  • Render on submit. Your handler posts the merge values to the Shotstack API. The video renders in the cloud and the URL comes back through a webhook.
Start for Free Talk to an Expert

Any form, any stack

Bring the form you already have

Form to video does not need a new interface. It needs a place where a person types in the details.

  • Your own app: a React, Vue, or plain HTML form that posts to your server.
  • Hosted form tools: Typeform, Google Forms, HubSpot, or Airtable, connected through a webhook or with Zapier, n8n and Make.
  • Internal tools: an admin panel or a Slack command that submits on behalf of a team.

However the values are connected, the Shotstack call is the same: a template ID and a list of merge fields.

Web app, hosted forms, CRM, and automation tools feeding one webhook that calls the Shotstack API

Guardrails you can build in

Validate before you render

Renders cost credits and take time. Catch problems while the person is still looking at the form.

  • Cap text length so a headline never overflows the layout.
  • Check that uploaded files are the right type and size before you spend a render.
  • Offer a fixed set of options for colors, music, and duration instead of free text.

The template stays under your control, so a form can never break the brand.

A form with a too-long headline flagged, a verified footage URL, and a locked brand color

Where it fits

One template, thousands of personal videos

Any video where the layout stays the same and the details change is a form to video job.

  • Real estate listing videos from a property form.
  • Personalized sales and welcome videos from a CRM record.
  • Event invitations and certificates from a registration list.
  • Product launch clips for social from a product form.
  • Onboarding and training videos for each new hire or customer.
Six example videos from one form template: listings, sales intros, invitations, launches, onboarding

Start small, grow later

Ship a form now, add an editor later

A form and a full editor produce the same Edit JSON and render through the same API. Start with a form for the people who only need to fill in details. When users ask for more control, mount the Studio SDK, a white-label video editor, and open the same template in it.

Your rendering pipeline does not change. Only the amount of editing surface you expose does.

A simple form and a full Studio SDK editor both producing the same Edit JSON

Frequently asked questions

What is form to video?

A way to create videos from a form instead of an editor. You design one template with merge fields. A form collects the values. Each submission renders a new video with those values in place. The person filling in the form never sees a timeline.

Do I need to build the form myself?

You can, or you can use a form tool you already have. Any form that can call a webhook or post to your server works. The Shotstack part is always the same: a template ID plus a list of merge values sent to the render endpoint. If you use n8n, our guide to the official Shotstack n8n node builds this exact flow.

How do I create the template?

Design it in Shotstack Studio, our browser-based template editor, or write the Edit JSON by hand. Wrap anything that changes in double braces, for example {{ AGENT_NAME }}. Save it as a template and render it with the templates endpoint. See the merge fields and templates guides.

Can the form upload photos and video clips?

Yes. Upload the file to your own storage or to Shotstack with the Ingest API, then pass its public URL as a merge value. The template places it in the right slot, and Shotstack handles resizing, trimming, and encoding.

How long does a render take?

Most renders finish in well under a minute. Rendering is asynchronous: submit the job, then receive a webhook or poll the status endpoint when the video is ready.

What does it cost?

Pricing is based on the length of video you render. The developer sandbox is free and unlimited for building and testing, with a watermark on the output. See the pricing page for current plans.

Guides

A video editor embedded in the ACME Corp web app, editing a vertical July sales promo with a timeline below.

Add video creation to your app

Embed an editor, go headless, or ship a form. The same promo video built three ways, with working code.

Row of new cars lined up at a dealership lot at sunset

Bulk create videos from a CSV

Turn every row of a spreadsheet into a rendered video with one template and a short script.

personalized

Personalized Video Technology

Build your own personalized video campaigns without agency costs.