Video mail merge
one MP4 per row, not one template for everyone.

Manual video personalization doesn't scale past a handful of recipients, and generic AI video generators don't know your data. Pictify renders a personalized video from every spreadsheet row and delivers it to its recipient, automatically.

Send Your First Batch Free See Pricing

ONE ROW, ONE PERSONALIZED VIDEO

01

Why "personalized video at scale" breaks every tool you already have

Video tools are built for one video, or every video. Not one row, one video.

Manual editing (Canva, CapCut, Premiere)

Doesn't scale past a handful

Personalizing a name, stat, or logo per recipient means opening the editor and re-exporting for every single row. Fine for 5 videos. Impossible for 500.

AI video generators (Sora, Runway, Veo)

No data mapping

Generative tools take a prompt, not a spreadsheet row. They can't reliably drop in an exact name, score, or brand asset, and every render can look different from the last.

1:1 video email tools (Vidyard, BombBomb)

Recorded, not rendered

Built for a person recording themselves once, not for turning 500 CSV rows into 500 distinct branded videos automatically.

Raw video as an email attachment

Too large, blocked by most inboxes

Video files routinely exceed attachment limits and get stripped or bounced by mail servers; a rendered, delivered pipeline is the only thing that reliably works.

02

Stop editing one at a time. Start rendering from data.

Pictify treats video like any other deliverable in the same render pipeline that already generates certificates, badges, and reports: define the template once (in a visual timeline studio or in code), map your spreadsheet columns to it, and every row renders into its own video and goes out to its recipient.

  • One template, unlimited personalized outputs, not one video per customer
  • Author visually or in code; same render pipeline either way
  • Triggered by CSV upload or a signed webhook, same as document workflows
  • Render and delivery status tracked per recipient, same as every other Pictify workflow
03

Data in. Personalized videos out. Three steps.

1

Build the video template

Design it in the visual timeline studio, or author it in code as a Remotion scene; both share the same render pipeline and variable contract.

2

Map your data

Upload a CSV or point a webhook at the workflow. Map each column (name, score, logo, whatever the template exposes) to a template variable.

3

Run and deliver

Every row renders its own video and is delivered to its recipient. The run screen shows render and delivery status per person, same as document workflows.

04

Every row rendered. Every run provable.

Documents & Videos, at Scale

1

The run is the unit of work

A CSV upload or a signed webhook in, one rendered document per row out. Not a design tool you drive by hand, once per person.

2

Per-row proof

Every row reports its own status and its own output URL. A row that fails is re-run on its own, without repeating the batch.

3

One engine, every deliverable

Certificates, badges, tickets, reports, personalized video. The same template and data contract renders PNG, PDF, GIF, and MP4.

4

Real expression engine

{{ price * 0.9 | currency }} is a first-class template feature. Conditionals, filters, loops: logic lives in the template, not your backend.

5

Wizard + API + agents

Organizers run the wizard. Developers sign a webhook. AI agents author templates over MCP. Same template, same run history.

6

AI Template Maker

Describe the document or video and get an editable HTML-native template with your brand and variables in place.

Get API Key Read API Docs

Prefer to see it first? Generate a certificate in your browser →

05

Frequently asked questions

Can I really generate a different video for every row in a spreadsheet?
Yes. Pictify's video templates take the same variable contract as every other template type: map CSV columns (or webhook payload fields) to the parts of the video that should change per recipient: a name, a score, a logo, a highlight clip. Each row renders its own video.
How do I build the video template itself?
Two ways, sharing one render pipeline: a visual timeline studio for scene-by-scene editing, or a code editor for authoring a Remotion scene directly. Both expose the same variables to the render and workflow layer, so how you built it never matters downstream.
Does video count against my regular render limit?
Yes: images, PDFs, GIFs, and video renders all draw from the same monthly render pool on your plan. There's no separate video quota to manage.
Can I trigger video rendering automatically, not just from a CSV upload?
Yes. Every workflow, video included, exposes a signed webhook. Point a form tool, CRM, or Zapier/Make/n8n flow at it and each payload renders and delivers one video, the same way document workflows do.
What happens if a video fails to render or a delivery bounces?
Failed renders and bounced deliveries show up per row in the run history, same as every other workflow type, so you can fix and re-run just that one recipient instead of the whole batch.
Is this the same as an AI video generator?
No. Pictify doesn't generate video from a text prompt. You design the template once, visually or in code, and Pictify renders it deterministically with your data swapped in, so every video is on-brand and predictable, not a fresh AI guess each time.