Instagram Reels automation: render 50 reels from one HTML template

Instagram's algorithm rewards volume, but the production tools assume one editor per video. The math doesn't work past ten reels a week. The way out is to template the format — once — and render variants from a spreadsheet.

This guide walks the engineering side of a Reels program: the 9:16 canvas, the safe zones Instagram covers, the audio-sync constraints, and the batch render setup that ships fifty videos overnight.

The Reels canvas

Instagram Reels is 1080 × 1920 at 30fps. The platform overlay budget is slightly more generous than TikTok but follows the same shape:

• Bottom 220px: caption + username + audio attribution.
• Right 160px, lower-third area: like / comment / share / "use audio" rail.
• Top 90px: status bar in the iOS app, less critical but visible.

Design every shot to clear those zones. The viewer-actionable safe area is roughly 800px wide × 1500px tall, centered, biased slightly upward.

The four-shot structure

Reels under thirty seconds get the highest reach. A reliable four-shot template:

Each shot is its own scene in the HTML — the timeline is just data-start and data-end attributes plus CSS transitions. No timeline software.

Audio: the one thing you cannot deterministically render

Audio is the asterisk on "render everything from code." Reels lives or dies by audio, and you cannot embed Instagram's licensed library into your render — the platform requires audio be added in-app to track the licensing.

Two workable patterns:

1. Render silent MP4, add audio in the Instagram app at upload time. Slow, but lets you use the algorithmic-favorite Instagram-library tracks.
2. Render with your own licensed audio embedded. Faster, but the algorithm slightly under-distributes videos with non-library audio.

We default to pattern 1 for the first version of a campaign and switch to pattern 2 once a sound shows traction.

The variable surface

Five variables, no more:

• Hook text (one line)
• Body content (text or asset URL)
• CTA line
• Color theme (one accent color drives everything)
• Duration override (default 24s; some hooks need 8s)

Batch pipeline

Once the template is solid, the throughput math is mechanical:

1. CSV with one row per reel.
2. Render queue produces a 1080×1920 MP4 per row.
3. Thumbnails generate for review.
4. Approved videos sync to a Buffer / Later / Hootsuite uploader.

See the full CSV pipeline for the orchestration code.

Throughput math

A team running this pipeline (one creative, one engineer, weekly batch) ships:

Most of which never get used. That is the point — at this volume, the marketer picks the top 20% and discards the rest, which is the inverse of the "one editor per video" workflow where every video is precious by virtue of how long it took.

The other formats come free

Once a Reel exists as HTML, the same template at 1080×1080 is an in-feed post, at 1080×1350 is a portrait post, at 1920×1080 is a Facebook-cross-post hero. Five formats from one source.

Open the playground, build the first template, queue the batch.