VidStudio, a browser based video editor that doesn't upload your files

Hi HN, I built VidStudio, a privacy focused video editor that runs in the browser. I tried to keep it as frictionless as possible, so there are no accounts and no uploads. Everything is persisted on your machine.Some of the features: multi-track timeline, frame accurate seek, MP4 export, audio, video, image, and text tracks, and a WebGL backed canvas where available. It also works on mobile.Under the hood, WebCodecs handles frame decode for timeline playback and scrubbing, which is what makes seeking responsive since decode runs on the hardware decoder when the browser supports it. FFmpeg compiled to WebAssembly handles final encode, format conversion, and anything WebCodecs does not cover. Rendering goes through Pixi.js on a WebGL canvas, with a software fallback when WebGL is not available. Projects live in IndexedDB and the heavy work runs in Web Workers so the UI stays responsive during exports.Happy to answer technical questions about the tradeoffs involved in keeping the whole pipeline client-side. Any feedback welcome.Link: https://vidstudio.app/video-editor

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

72

out of 100

Verdict

VALIDATE

medium confidence

Competition

No competitor data yet

Trend

No signal yet

Browser-based video editor that processes everything locally, eliminating upload friction and privacy concerns that plague cloud editors.

The pain

Video editing requires uploading large files to cloud servers, creating privacy exposure, bandwidth costs, and waiting time. Users distrust where their footage goes. Cloud editors are slow for scrubbing and seeking because decode happens server-side. Mobile users have no viable options.

The gap

Existing browser editors (Kapwing, Clipchamp) all upload to servers. Desktop editors (Premiere, DaVinci) require installation and powerful hardware. No tool combines zero-upload privacy with the frictionless access of a browser and works on mobile.

Build angle

The technical execution is solid, WebCodecs for hardware-accelerated decode, FFmpeg WASM for encoding, IndexedDB for persistence, Web Workers for responsiveness. The real question is whether privacy-conscious users will choose a limited browser editor over feature-rich desktop software, and whether the performance ceiling of browser tech (especially on mobile) satisfies real workflows.

Strengths

  • No account friction removes a major adoption barrier
  • Hardware-accelerated decoding makes scrubbing responsive, solving a real UX problem in browser editors
  • Mobile support addresses an underserved segment
  • Privacy positioning is defensible and increasingly valuable
  • Technical implementation shows deep competence with modern web APIs

Risks

  • Feature set is basic (multi-track, text, audio, images) compared to what professionals expect; unclear if this is intentional positioning or a limitation
  • Browser performance ceiling will hit hard on longer videos or complex timelines; mobile export times could be prohibitive
  • No clear monetization path, free tool with no accounts means no direct revenue lever
  • Market is crowded with free options (CapCut, iMovie, Shotcut); privacy alone may not differentiate enough to build a business
  • User acquisition without accounts or viral loops is expensive; unclear how to reach target audience
  • Dependency on browser APIs that vary across devices creates support burden

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “VidStudio, a browser based video editor that doesn't upload your files”.

Open FlyBot