Home›AI technologies›Video rendering in codeDeutsch

Video rendering in code: a video you can rebuild from a script

Instead of a timeline in an editor, the video is a program. The same code renders a thousand versions with different text, different data and a different voice.

AWS LambdaAWS Elemental MediaConvert

What does rendering in code mean?

A rendered video is produced by code that says what is on screen at each single frame. Change a parameter and you get a different video with the same layout, the same typography and the same timing. That is also what makes it possible for an agent to produce video at all: the agent writes the parameters, not the pixels.

There are two layers under this, and it helps to keep them apart. One is the encoder that turns frames into a file, and FFmpeg is doing that work almost everywhere, including inside the other tools. The other is the layer above, which describes what each frame contains. Remotion is that layer, written in React, so a video is built the way a web page is built.

Goes inA template plus the data for one video: text, images, audio, timings
Comes outAn MP4, rendered the same way every time
Typical usesPersonalised video at scale, data and report videos, social cuts, product explainers

Four ways to render it

This one does not split neatly into one service per cloud. It splits into the layer that describes the video, the machine that renders it and the step that encodes for delivery.

Write the video as code

Remotion[1]

React components that take the frame number and return what is on screen. Remotion renders them in headless Chrome and hands the frames to FFmpeg. It is free for individuals and small teams and needs a company licence above that.

Official documentation →
AWS Lambda
Render at scale on AWS

Remotion on AWS Lambda[2]

The same composition, cut into chunks and rendered by many Lambda functions in parallel, then stitched together. A clip that takes minutes on a laptop comes back in seconds, and you pay for the seconds.

Official documentation →
AWS Elemental MediaConvert
Encode and package, managed on AWS

AWS Elemental MediaConvert[3]

The managed encoder, for the step after the picture exists: several resolutions, the formats a player expects, captions and thumbnails, without a render farm of your own.

Official documentation →
Run it yourself

FFmpeg[4]

The tool underneath all of the above. Running it yourself is the cheapest option and the most work: you own the encoding settings, the queue, the machines and the failures.

Project documentation →

Where I used it

The video pipeline

Every clip is the same Remotion composition with different props: the scenes that were picked, the subtitles and the music bed. The render runs on Lambda, so a batch of clips is finished in about the time one of them takes.

Read the write-up →

The conference highlights film

The highlights video on my AWS Community Day pages is built this way, which is why the next one takes an afternoon instead of a week.

See a talk page →

Managed and self-hosted together: hybrid

Rendering is the step that is easiest to keep in your own house, because it needs no model and no outside service: it is computation on footage you already hold. The parts that reach out are the ones that write the script and read the footage. Where the footage may not leave, the render stays on your machines and only the finished file travels.

What would help you next?

Learn to decide

The course “From Managed to Hybrid” teaches where AI should run: what each layer costs, what you operate and where your data has to stay. It is in preparation, with a free live session first.

Linda MohamedLinda Mohamed
AI and cloud consultant, AWS Community Hero, Vienna

Build it with me

Tell me what you want to build. In 30 minutes we check which of these ways fits your data, your rules and your budget, and whether AWS funding for a proof of concept can cover part of it. How AWS funding works →

You already know what you need

Book the workshop directly:

ai-solutions.wiki

Read more on ai-solutions.wiki

My open knowledge base, with longer comparisons, pricing notes and sources.

Sources

  1. Remotion documentation. https://www.remotion.dev/docs/
  2. Remotion Lambda documentation. https://www.remotion.dev/docs/lambda
  3. AWS Elemental MediaConvert documentation. https://docs.aws.amazon.com/mediaconvert/latest/ug/what-is.html
  4. FFmpeg documentation. https://ffmpeg.org/documentation.html
  5. Remotion, ai-solutions.wiki. https://ai-solutions.wiki/tools/remotion/
  6. FFmpeg, ai-solutions.wiki. https://ai-solutions.wiki/tools/ffmpeg/
  7. Remotion vs FFmpeg, ai-solutions.wiki. https://ai-solutions.wiki/comparisons/remotion-vs-ffmpeg/

Links checked October 2026. Product names and features change: check the linked pages before you decide.