<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Susan Acharya</title>
    <description>The latest articles on DEV Community by Susan Acharya (@susanacharya).</description>
    <link>https://dev.to/susanacharya</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4187067%2Fa3c96eb2-c975-443e-a6ad-36af6845c7d4.png</url>
      <title>DEV Community: Susan Acharya</title>
      <link>https://dev.to/susanacharya</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/susanacharya"/>
    <language>en</language>
    <item>
      <title>I make my launch videos with a web page, not a video editor</title>
      <dc:creator>Susan Acharya</dc:creator>
      <pubDate>Fri, 23 Oct 2026 09:08:40 +0000</pubDate>
      <link>https://dev.to/susanacharya/i-make-my-launch-videos-with-a-web-page-not-a-video-editor-5f32</link>
      <guid>https://dev.to/susanacharya/i-make-my-launch-videos-with-a-web-page-not-a-video-editor-5f32</guid>
      <description>&lt;p&gt;I don't know Premiere. I didn't want to learn it just to make a 30-second trailer for a side project. So I made the video a web page instead.&lt;/p&gt;

&lt;h2&gt;
  
  
  The idea
&lt;/h2&gt;

&lt;p&gt;The whole trailer is one 1920x1080 page where everything on screen is a pure function of time. No timers, no animation libraries, no Math.random() while rendering. You give the page a time &lt;code&gt;t&lt;/code&gt;, and it draws exactly what frame &lt;code&gt;t&lt;/code&gt; should look like.&lt;/p&gt;

&lt;p&gt;I expose one hook on the page, &lt;code&gt;window.__trailer.seek(t)&lt;/code&gt;. It sets the state, pauses every CSS animation and sets its &lt;code&gt;currentTime&lt;/code&gt; from &lt;code&gt;t&lt;/code&gt;, waits for images to decode, then waits two animation frames so the paint is done.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rendering
&lt;/h2&gt;

&lt;p&gt;A Playwright script opens the page, and for every frame &lt;code&gt;i&lt;/code&gt; it calls &lt;code&gt;seek(i / 30)&lt;/code&gt; and takes a screenshot. Then ffmpeg glues the frames together:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ffmpeg &lt;span class="nt"&gt;-framerate&lt;/span&gt; 30 &lt;span class="nt"&gt;-i&lt;/span&gt; frames/%05d.jpg &lt;span class="nt"&gt;-i&lt;/span&gt; audio.wav &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-c&lt;/span&gt;:v libx264 &lt;span class="nt"&gt;-crf&lt;/span&gt; 17 &lt;span class="nt"&gt;-pix_fmt&lt;/span&gt; yuv420p &lt;span class="nt"&gt;-c&lt;/span&gt;:a aac &lt;span class="nt"&gt;-shortest&lt;/span&gt; out.mp4
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Because nothing depends on the wall clock, a slow machine renders the exact same video as a fast one. It just takes longer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Real UI, not raw recordings
&lt;/h2&gt;

&lt;p&gt;For app footage I record real sessions with the Chrome DevTools screencast (&lt;code&gt;Page.startScreencast&lt;/code&gt;) and save each frame with its timestamp, then turn that into a clean 30fps clip. The stage page drops those clips into device mockups. Raw screen recordings look jittery, mockups with a bit of camera zoom look intentional.&lt;/p&gt;

&lt;h2&gt;
  
  
  The music is code too
&lt;/h2&gt;

&lt;p&gt;The soundtrack is generated with numpy: a kick, hats, a saw bass, pads, a riser before the logo hit. I can't actually hear what the box renders, so I check loudness with &lt;code&gt;ffmpeg -af ebur128&lt;/code&gt; and get a human to listen before posting.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd tell you if you try this
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;CSS animations run on real time unless you pause them and set &lt;code&gt;currentTime&lt;/code&gt; yourself.&lt;/li&gt;
&lt;li&gt;Headless Chrome on a machine with no GPU falls back to software WebGL, so canvas-heavy games come out choppy. Keep those clips short.&lt;/li&gt;
&lt;li&gt;For vertical or 4:5 versions, re-lay out the stage at that size. Don't just crop.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It's free, it's all local, and re-rendering after a copy change is one command. Which is the real win, because I change the copy a lot.&lt;/p&gt;

&lt;p&gt;Have you done video this way, or is it just me being stubborn about learning an editor?&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I build with AI tools every day, and I used AI help to write the scripts behind this workflow and to tidy up this post.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>playwright</category>
      <category>ffmpeg</category>
    </item>
  </channel>
</rss>
