- > FFmpeg compiled to WebAssembly handles final encode
FFmpeg'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
- 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).
- The hvc1 and 10-bit failures a few comments up aren't a FFmpeg-wasm fallback thing, they're a WebCodecs browser-gap. Firefox's HEVC path is partial and 10-bit paths are worse. Chrome mostly works and Firefox fails on the exact files iPhones and modern Androids record by default.
A "your browser can't decode this codec, try Chrome" nudge would probably spare people the bounce, especially on test imports from their phone.
- How does it compare to https://omniclip.app/, https://tooscut.app, or https://clipjs.mohy.dev/ ?
- Wild that apps used to be completely local, no accounts, no uploads, and we're back to that as a value prop.
- Congrats on shipping this!
I went down the same path for videotobe.com, fully client-side with ffmpeg.wasm, and it fell over on longer videos. The memory ceiling and encode times pushed me to a cloud processing pipeline.
You've managed to solve both, the WebCodecs plus Pixi plus ffmpeg.wasm split looks like the right decomposition in hindsight.I processed 3+ hrs of media using VidStudio and it held up. Nicely done!
by Unsponsoredio
3 subcomments
- 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.
- I am really attracted to the idea of local running in-browser tools, since the website is then used only as a distribution medium which is super easy to use. And I really need such a tool, I was eager to test it.
However on both my first and second try it failed. I tried to import a video clip recorded on a Pixel phone. In Firefox it failed with a following message:
"Your browser does not support the codec "hvc1.2.4.L156". Try a different video."
Ok, fair, probably need to use Chrome for this type of tool. Tried it in Chrome:
"Audio decode failed: your browser cannot decode the audio in "..._webm.bin". Try re-encoding the file with AAC audio."
Sad. Hope you manage to work this out. Let me know if you have a newsletter or something where I can get notified if this gets fixed.
- I really like all the compress-to-X links at the bottom and the convert from X to Y tools. Especially the Discord one with presets for different target file sizes based on Discord's subscription tiers.
I've been using server-based (online, upload required) tools for this sort of stuff, but am now going to be using this.
Pretty cool find considering I have no need for a full-fledged video editor right now, and was just checking this out for fun.
- Looks good. Good work on shipping! I love seeing video applications utilizing Web Assembly. However, it usually falls short in when it comes to longer video in the browser's sandboxed environment.
How is the performance? Curious if you've tried using the FFmpeg libraries directly (libav), rather than compiling all of FFMpeg to WASM?
I always end up using running FFmpeg directly since it's faster and more reliable, but I still have some hope for a full functioning browser-based implementation someday.
I also made https://ffmpeg-commander.com a while back to generate commands for FFmpeg.
- 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.
by nopointttt
1 subcomments
- Glad you're holding the "nothing leaves your machine" line. A lot of tools in adjacent categories added cloud sync early, the local audience didn't come back. If you can keep v1 and v2 fully client side you'll find the people who care. ffmpeg-on-wasm will hit a memory ceiling on longer videos, but most people opening a browser video editor are doing short clips anyway.
by woodydesign
2 subcomments
- I love no accounts and no cloud a lot!
Wondering if it support subtitle and transcript? It would be helpful for non-native speaker use case.
Also, can you talk more about the use case difference between VidStudio vs. Finalcut/Imovie/Premiere? I am quite interested. Thanks
by mehmetkeremmtl
0 subcomment
- Running FFmpeg via WebAssembly and rendering with Pixi.js sounds heavy for mobile browsers, which are notoriously aggressive with memory limits. How are you handling OOM crashes or storage quota limits in IndexedDB when users import large 4K video files on mobile?
- 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?
- I recently did something similar but as a Mac app.
It sounds like a similar stack, but distributed as an app. FFmpeg (LGPL compilation).
I haven't tried Pixi.js, looks interesting. I guess it was good for this.
Have you looked at remotion? I found them good for somethings, but ended up using Safari for rendering (instead of remotion's chrome-based rendering) because app packaging was easier that way.
https://www.loremlabs.com/cliproom if you're interested in comparing
by paolatauru
0 subcomment
- webcodecs for timeline scrubbing is the right call. curious how you handle frame caching though - webcodecs decoder buffers are memory mapped and the browser can evict them when under pressure. did you implement your own lru cache on top or are you just letting the decoder handle it. also interested in how mobile holds up on memory constrained devices - iphones especially tend to kill pages that use too much webcodecs memory in the background
by roxana_haidiner
1 subcomments
- I tried multiple times to upload a 1920x1080 video and export it as 1080 x 1920 for tik tok...but I couldn't do this, the last one was blocked at 75%, and it was an 30 seconds of 5 mb video.....
I really need this website if everything works well!
by zane__chen
0 subcomment
- Finally see a local first web based video editor. Cool thing!
by giancarlostoro
0 subcomment
- I worked on something similar for a relative who wanted to know if I could build something like this for them using Claude, and sure enough you can, I wound up having to ditch ffmpeg wasm edition because of a lot of slowness, and when with ffmepg on the backend. Curious how this performs vs ffmpeg on the backend. I'm genuinely surprised there's not 100% browser native solution to this.
- This is great, thank you!
by jamiehugo30
1 subcomments
- 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?
- You probably already know this, but I could not import 10-bit video on Windows which I think would be fairly common among the target audience.
ffmpeg supports decoding 10-bit video.
- What is the performance difference between native FFmpeg and WebAssembly-translated FFmpeg running in a web browser?
- This is so cool - will try it out. Pure browser based video editing is ambitious. Are you using Remotion ?
- LGPL issues aside, will a project like this need to pay the h264 patent fee?
by Sergey777
1 subcomments
- 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.
by shardullavekar
2 subcomments
- looks great. any plans of abstracting these functions with an LLM integration?
- nice
by SilentM68
1 subcomments
- Price?
by lern_too_spel
0 subcomment
- 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.
by Serhii-Set
0 subcomment
- [dead]
- [dead]
Hacker News