Professional video editing, right in the browser with WebGPU and WASM

Re:Professional video editing, right in the browser with Web... by caijia on Saturday March 21, 2026 @10:25PM (#47473842)

Curious about the headless story. The "Photopea of video editing" comparison is apt — Photopea's real moat ended up being the API and programmatic access, not just the browser UI. Companies embed it for automated image processing workflows.

For a browser-native NLE, the killer feature might not be the timeline UI — it could be exposing the WGPU rendering pipeline as an API that other tools can call. Imagine CI pipelines that render video assets without needing FFmpeg on the server.

[ Parent | on HN ]

Re:Professional video editing, right in the browser with Web... by mohebifar on Saturday March 21, 2026 @10:32PM (#47473885)

Good point. I agree that could be a very interesting direction.

I have used Remotion for years because the DX is great, but the performance and overhead is significant. Even something like attaching subtitles to a video can take around 10x more time and resources than bare FFmpeg because of the chromium layer.

A headless version of this wgpu renderer with a clean API and eventually a nicer DX layer such as a react renderer could be a strong replacement for that kind of workflow.

[ Parent | on HN ]

Re:Professional video editing, right in the browser with Web... by boppo1 on Saturday March 21, 2026 @11:24PM (#47474161)

>render video assets without needing FFmpeg on the server.

Help me understand: able to do video with less compute? Or offload compute to client browsers?

[ Parent | on HN ]