SaaS Metrics
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
Show HN: VidStudio, a browser based video editor that doesn't upload your files
A frictionless, privacy-centric browser-based video editor that processes files locally (no uploads, no accounts), offering multi-track editing, MP4 export, and mobile compatibility, leveraging WebCodecs, FFmpeg WebAssembly, and WebGL.
View Origin LinkProduct Positioning & Context
AI Executive Synthesis
A frictionless, privacy-centric browser-based video editor that processes files locally (no uploads, no accounts), offering multi-track editing, MP4 export, and mobile compatibility, leveraging WebCodecs, FFmpeg WebAssembly, and WebGL.
VidStudio addresses a significant pain point for businesses handling sensitive media: the privacy and security risks associated with uploading video files to cloud-based editors. Its 'no uploads, no accounts' and local processing model (WebCodecs, FFmpeg WebAssembly) offers a compelling value proposition for industries with strict data governance requirements, such as legal, healthcare, or internal corporate communications. For B2B SaaS, this highlights a market for privacy-by-design media tools that prioritize client-side processing. The technical sophistication (WebGL, Web Workers) ensures a performant user experience, demonstrating that advanced functionality can be delivered without compromising data sovereignty, a key concern for enterprise adoption.
Related Ecosystem & Alternatives
Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.
Deep-Dive FAQs
What is VidStudio, a browser based video editor that doesn't upload your files?
VidStudio, a browser based video editor that doesn't upload your files is analyzed by our AI as: A frictionless, privacy-centric browser-based video editor that processes files locally (no uploads, no accounts), offering multi-track editing, MP4 export, and mobile compatibility, leveraging WebCodecs, FFmpeg WebAssembly, and WebGL.. It focuses on VidStudio addresses a significant pain point for businesses handling sensitive media: the privacy and security risks associated with uploading vide...
Where did VidStudio, a browser based video editor that doesn't upload your files originate?
Data for VidStudio, a browser based video editor that doesn't upload your files was aggregated directly from the Hacker News community ecosystem, representing raw developer and early-adopter sentiment.
When was VidStudio, a browser based video editor that doesn't upload your files publicly launched?
The initial public indexing or launch date for VidStudio, a browser based video editor that doesn't upload your files within our tracked developer communities was recorded on April 21, 2026.
How popular is VidStudio, a browser based video editor that doesn't upload your files?
VidStudio, a browser based video editor that doesn't upload your files has achieved measurable traction, logging over 142 traction score and facilitating 55 recorded discussions or engagements.
Which technical categories define VidStudio, a browser based video editor that doesn't upload your files?
Based on metadata extraction, VidStudio, a browser based video editor that doesn't upload your files is categorized under topics such as: privacy focused video editor, browser based, no accounts, no uploads.
Is VidStudio, a browser based video editor that doesn't upload your files recognized by media or academic researchers?
Yes. It has been covered by media outlets like Vidstudio.app. This indicates the concept has reached a level of mainstream or scientific viability beyond just developer forums.
What are some commercial alternatives to VidStudio, a browser based video editor that doesn't upload your files?
Our semantic intelligence engine identifies potential commercial alternatives in the SaaS space, such as Google Vids 2.0, which offers overlapping value propositions.
How does the creator describe VidStudio, a browser based video editor that doesn't upload your files?
The original author or development team describes the product as follows: "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 o..."
Community Voice & Feedback
I've seen dozens of these posted to HN. Surprisingly, there is a lack of browser based video editors for media libraries, which means I have to load the video over the network using WebDAV or Samba, edit it locally, and then upload it back. It's a niche use case, but the people who manage their own photos and video storage are generally tech savvy, so it's surprising that no such tools exist.
Wild that privacy became a feature and not the default. Building in this space too and the no uploads needed angle is surprisingly hard to communicate to users who've been trained to expect everything to live in the cloud.
Sorry for the significantly unrelated comment:Does anyone know if there is any limitation to create a "https-local://" or something like that, which guarantee that things are only downloaded, and never uploaded?
Curious how you're handling the MP4 export entirely client-side — are you using FFmpeg compiled to WebAssembly, or something custom built around the WebCodecs API?
Wild that apps used to be completely local, no accounts, no uploads, and we're back to that as a value prop.
Let me just say the performance is absolutely incredible, and the persistence is so transparent. I actually was given access to an in-browser video editor that chokes pretty quickly so I'm impressed. The tracks didn't seem to work well for me. I'm on Firefox on Windows and couldn't drag and drop tracks to change the order, there doesn't seem to be any layer transformation tools (position, rotation, scale) that I could find to counteract it not handling footage of different aspect ratios (I.E. portrait and landscape).
Interesting approach—privacy-friendly editing without uploads is compelling. Curious how you handle performance and large files purely in-browser, and what trade-offs there are vs server-based editors.
I've built a similar video editor and have been considering pure client side implementation vs transcoding into a known format beforehand, went with transcoding for wider format support and easier video playback implementation.I'm interested in how you handle demuxing different container formats any which ones are supported?I get "Audio decode failed: your browser cannot decode the audio in "41b1aee9-ac65-43f6-b020-e8fed77c3c72_webm.bin". Try re-encoding the file with AAC audio." for a WEBM with no audio.h264/aac MP4 works, is that demuxed with mp4box.js?
I noticed seeking (clicking or scrubbing on timeline) initializes a new VideoDecoder and destroys the previous one for every new frame, leading to abysmal performance as you lose decoder state and a lot of decoding work has to be repeated. Plus the decoder reinitialization time.
Is that because the demuxing logic doesn't give precise access to encoded frames? iirc mp4box.js didn't support that last time I checked.
I noticed seeking (clicking or scrubbing on timeline) initializes a new VideoDecoder and destroys the previous one for every new frame, leading to abysmal performance as you lose decoder state and a lot of decoding work has to be repeated. Plus the decoder reinitialization time.
Is that because the demuxing logic doesn't give precise access to encoded frames? iirc mp4box.js didn't support that last time I checked.
How does it compare to https://omniclip.app/, https://tooscut.app, or https://clipjs.mohy.dev/ ?
> FFmpeg compiled to WebAssembly handles final encodeFFmpeg's license is the LGPL 2.1. VidStudio looks like closed source software, I couldn't see any indication that it's free software. You're distributing this software to run in the client's browser. I'm not a lawyer but I think you're in breach of the terms of the LGPL.https://www.ffmpeg.org/legal.html
Discovery Source
Hacker News Aggregated via automated community intelligence tracking.
Tech Stack Dependencies
No direct open-source NPM package mentions detected in the product documentation.
Media Tractions & Mentions
Deep Research & Science
No direct peer-reviewed scientific literature matched with this product's architecture.