<?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: Paul Spaurgen</title>
    <description>The latest articles on DEV Community by Paul Spaurgen (@paul_spaurgen_c5ec1fc6704).</description>
    <link>https://dev.to/paul_spaurgen_c5ec1fc6704</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3975677%2F9d0cee1a-429b-4bf4-b5ab-49084794bcb7.jpg</url>
      <title>DEV Community: Paul Spaurgen</title>
      <link>https://dev.to/paul_spaurgen_c5ec1fc6704</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/paul_spaurgen_c5ec1fc6704"/>
    <language>en</language>
    <item>
      <title>Title: I built a browser-native video editor using WebCodecs and WebGL2</title>
      <dc:creator>Paul Spaurgen</dc:creator>
      <pubDate>Tue, 09 Jun 2026 21:28:05 +0000</pubDate>
      <link>https://dev.to/paul_spaurgen_c5ec1fc6704/title-i-built-a-browser-native-video-editor-using-webcodecs-and-webgl2-1m99</link>
      <guid>https://dev.to/paul_spaurgen_c5ec1fc6704/title-i-built-a-browser-native-video-editor-using-webcodecs-and-webgl2-1m99</guid>
      <description>&lt;p&gt;Building heavy utility tools for the browser is a battle against resource limits. For the past while, I’ve been working on Elah (elah.dev), an engine and SDK for building frame-accurate video editors on the web.&lt;/p&gt;

&lt;p&gt;The Architecture&lt;br&gt;
I wanted to keep the dependency budget incredibly strict. Elah doesn't rely on a massive WASM runtime. Instead, it leans on:&lt;/p&gt;

&lt;p&gt;WebCodecs for a push-based decode pipeline.&lt;/p&gt;

&lt;p&gt;WebGL2 for rendering and compositing layers via a shared quad pipeline.&lt;/p&gt;

&lt;p&gt;Web Workers &amp;amp; OffscreenCanvas for the export pipeline so the main thread doesn't freeze.&lt;/p&gt;

&lt;p&gt;State Management&lt;br&gt;
To keep React from needlessly re-rendering, the TimelineEngine is decoupled from the UI. It acts as the single source of truth using Immer for structural sharing. React just subscribes to a reactive mirror of that state.&lt;/p&gt;

&lt;p&gt;Get Started:&lt;/p&gt;

&lt;p&gt;Live Playground: &lt;a href="https://elah.dev" rel="noopener noreferrer"&gt;https://elah.dev&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;GitHub Repo: &lt;a href="https://github.com/elahlabs/elah" rel="noopener noreferrer"&gt;https://github.com/elahlabs/elah&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;React/Next.js Integration Guide: &lt;a href="https://github.com/elahlabs/elah/tree/main/playground/react" rel="noopener noreferrer"&gt;https://github.com/elahlabs/elah/tree/main/playground/react&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Demo: &lt;a href="https://vimeo.com/1199899188?fl=ip&amp;amp;fe=ec" rel="noopener noreferrer"&gt;https://vimeo.com/1199899188?fl=ip&amp;amp;fe=ec&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I'd love to hear your feedback on the architecture!&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>javascript</category>
      <category>showdev</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
