Insights

Product films written in code

Product films written in code

Several of the case studies on my work pages now carry a short film: a phone or a browser window moving through a real website, with cards flying in on the beat and a sound bed underneath. None of them was edited on a timeline. Each one is a text file of decisions that a computer turns into picture and sound. This is what that means, and why a small studio would bother.

Why a website needs a film at all

A website is hard to show off. A screenshot shows one moment of something built to move. A screen recording shows everything, including the mouse hunting for a button and the half-second while a page loads. And the places where people actually discover a studio like mine, Instagram and LinkedIn, are built for short video.

So I wanted films. Twenty or thirty seconds each, made from the real sites rather than mock-ups, sharp enough to hold up on a large screen, and cheap enough to remake whenever the site changes. That last requirement is the one that pushed me towards code. A film cut by hand is finished when the editor stops. A film written as a list of instructions can be rebuilt in an evening when the website underneath it moves on.

What "written in code" means

The tool at the centre is Remotion, a library that treats every frame of a video as a web page. You describe what should be on screen at frame 240, and it renders frame 240. That sounds like a programmer's toy, but it has become a serious way to make video. Remotion's own blog, in a post on 11 November 2026, says that with its new agent skills it "has become the default way people make videos with Remotion": you describe the film to an AI agent, and the agent writes it. The 4.0.540 release on 2 November 2026 gave every effect a WebGPU version, which is the kind of plumbing work that makes this approach faster with each release.

My films are built in four stages, and the second one is where the craft lives.

The film pipeline in four stages. One: film the live site in a browser on a controlled clock, read only. Two: write the edit list on a 112.5 beats-a-minute grid, with a camera solver that frames only whole elements. Three: render picture in Remotion and synthesise sound from the same list. Four: gates for loudness, Instagram safe zones and file size. Outputs: 9:16 reels for Instagram and 16:9 4K copies for LinkedIn.
One edit list drives both the picture and the sound, so a cut and its whoosh can never drift apart.

Filming. A browser opens the real demo site and plays it on a clock I control, so a scroll or a fade takes exactly as many frames as I asked for, every time. It films at up to six times normal screen sharpness, which leaves room to zoom in later without the text going soft. Because these are live sites with real forms, the filming browser is locked to reading: anything that would send data is blocked, and the helper that clicks buttons refuses any button that submits or sends. A film shoot should never be able to fill in a contact form.

The edit list. Film people call it an edit decision list: shot one runs from here to here, the camera pushes in on this panel, a card flies in on beat nine. Mine is a single file. The most useful piece of it is a small camera solver. It knows where every heading, paragraph, image and button sits on the page, and it will only accept a camera position where each of them is either wholly in the frame or wholly out of it. Half a sentence at the edge of a frame looks like a mistake, so the solver simply does not allow it.

Picture and sound. Remotion renders the picture frame by frame. The sound is synthesised from the same edit list: every whoosh, riser and soft collapse is placed by the cut it belongs to. The reels in the latest version run on a grid of 112.5 beats a minute, which works out to exactly sixteen frames a beat, so a cut always lands on a beat and a beat always lands on a frame. Because I synthesise the sound rather than license it, there is no music licence to manage.

Gates. Before anything is exported, the film has to pass checks. Loudness is mastered to -14 LUFS, a common playback target for social platforms, so my film is not the one that is suddenly quieter or louder than the clip before it. Peaks are mastered to about -3 dBTP, which leaves headroom so the platform's own processing does not crunch them. And there is the check I learned the hard way, which needs its own section.

"Too big for insta"

On 14 November I looked at the second round of reels and my note was blunt: "None of this. Remake all 3 sets, better sounds, more epic, Ulric branded dark." I rebuilt them that day with one rule above all others: one hero subject per shot, and no tiny interface that nobody can read on a phone.

The rebuild looked strong on my monitor. Then I watched it the way people actually see it, inside Instagram, and my note was four words: too big for insta.

Instagram puts its own furniture on top of every reel. The account name and caption sit across the bottom, the like and share buttons down the right side, and more at the top. In the layout I work to, about 14% of the height at the top and 22% at the bottom is covered. My phone mock-ups had been filling the frame, so the part of the website I most wanted people to see was sitting under somebody else's buttons.

A vertical reel frame with the top 14% and bottom 22% hatched as covered by Instagram. The phone mock-up sits in the clear band, 60% of the frame's height, centred at 46% rather than 50%. Notes: the phone eases from 58.5% to 60% across a shot; a checker fails any reel with sharp bright detail in a covered zone; versions 5 and 6 added desktop windows, zooms and feature-card stacks inside the same band.
The middle of the frame is not the middle of what the viewer can see.

The fix was the same day and it is specific. The phone now takes up 58.5% of the frame's height and eases to 60% over a shot, a slow push you feel more than notice. It is centred at 46% of the height, not 50%, because the clear band is not in the middle of the frame. Measured on the export, the phone body comes out 60% tall with 16% clear above it and 24% below.

Then I made the mistake impossible to repeat. A small checker now scans every vertical film and fails it if sharp, bright detail covers more than a tenth of one percent of either covered zone. Soft background colour is allowed to run under the buttons. A headline is not.

More dynamic, same rules

The next note, on the fifth version, asked for more: "more dynamic with desktop chromes, zoom, stacks of features and more full epic demos." The sixth version, made overnight into 15 November, answered it. The camera can now move a full desktop browser window as well as a phone. Feature cards fly in one per beat and stack up before collapsing away. A soft veil darkens the zones Instagram covers, so even the background there stays quiet.

That version produced eight films from three sample websites: an agent dashboard for a realtor, a members-only listing portal for home buyers and Ninebark, the builder's site whose hero I wrote about in a house that builds itself while you watch. Each site gets a vertical reel of 21.3 seconds, there is a combined reel of 31.2 seconds, and all four come again as wide 4K versions for LinkedIn.

LinkedIn brought one more constraint, a ceiling I set myself: the 4K copies there stay under 10 MB. Squeeze a 4K film that hard and it usually looks smeared. So the LinkedIn copies are compressed against a measurement rather than by eye: each one is compared frame by frame with the master using SSIM, a standard score for how alike two images look, where 1.0 means identical. All four came in at about 0.99, at loudness between -14.1 and -14.5 LUFS. They went onto the work pages the same day.

Why this matters if you are not making films

Most of my clients will never write an edit decision list, and they should not have to. What carries over is the approach: a piece of marketing that is described rather than hand-made can be checked, rebuilt and kept in step with the thing it is selling.

The longer film on the Rosie OS case study, the dashboard I built for a real estate agent, is the same idea at a larger scale: 89 seconds with a synthesised music bed and sound effects, made so that it can be regenerated when the product changes rather than reshot. When a website gets a new section, its film gets a new line in a file and an evening of rendering.

The number I check first on every new batch is the file size of the LinkedIn copies, because it tells me whether the compression held: on the sixth version, every one of the four landed between 9.1 and 9.2 MB.

Common questions

What does it mean to make a video in code?

Instead of dragging clips on a timeline, every shot, camera move and sound cue is written as an instruction in a file. A tool such as Remotion renders that file into video, so the film can be checked, changed and rebuilt like any other code.

Why do my Instagram reels look cramped or covered?

Instagram places your name, caption and buttons over the top and bottom of every reel. I keep the main subject inside the clear band, roughly 14% down from the top to 22% up from the bottom, and centre it a little above the middle.

Is the music in these films licensed?

No licence is needed. The sound is synthesised from the same edit list as the picture, so every effect lands on its cut, and it is mastered to a common loudness target for social platforms.

Can a film like this be updated when the website changes?

Yes. That is the main reason to make it this way. The capture is re-run against the live site and the edit list is adjusted, which takes an evening rather than a reshoot.

Related

← All insights