Updated
Case evidence: Read the source breakdown report · View case frames and shot timings
Based on a published tool report. Production classifications are analytical judgments; suggested steps are not the original project or a verified recreation.
What code rendering looks like
Watch for pixel-perfect typography that snaps between states, perfect grid alignment, flat vector shapes and icons, identical repeated elements, and loops that cycle with mathematical precision. In product videos, code layers usually sit on top of a real screen recording: title cards, lower thirds, HUD-style overlays and animated numbers around a demo.
The case that named Remotion
In the product-promo breakdown, the report classified the opening titles, feature callouts and interface overlays as code / template rendering, and listed Remotion as the likely tool behind them. That judgment is probabilistic — backed by rendering features and cut structure, not by the project files — and the report keeps that uncertainty visible. It is evidence-based inference, the strongest claim a breakdown can honestly make.
Code vs After Effects vs AI video
After Effects work tends to carry motion blur, organic easing and composited footage. AI video shows texture tells instead: flat color blocks, skies and backgrounds that stay perfectly still while one element moves, fluids that warp slightly wrong — the same signals another case report used to flag AI-generated shots. Code rendering has neither: it is crisp, deterministic and repeatable. When a layer looks too perfect to be keyframed, it was probably computed.
Why it matters for your remake
A code-rendered title sequence rebuilt in an editor costs hours per change; rebuilt in code, it costs a parameter. That is why the breakdown separates code layers from recordings before planning: recordings need a camera or a screen capture, code layers need a component. If you rebuild with React, the Remotion skill ecosystem for coding agents is one route; whatever you choose, keep the layers separate from day one.
A reusable analysis template
Layer / time range Observable features (type, shapes, easing, loop) Verdict: code / AE-style / AI / recording Evidence + alternative explanation Rebuild route (component, AE comp, regeneration) Uncertainty kept visible
Practice with a real report
Open the product-promo case and look for the code / template rendering sections: the report walks through the opening titles and overlays, names Remotion as the likely tool, and separates them from the screen recordings you would capture yourself.
Open the case and download its report →