NeeruJaroliya

Pushing browser-based tech to handle native-level video editing is definitely ambitious—but that's what makes it exciting! I'm focusing on keeping the codebase highly modular, enabling compute-heavy tasks like rendering and AI-driven edits to be offloaded to cloud functions. Additionally, I'm working on optimizing the diffing logic between edits to minimize lag and reduce unnecessary component re-renders. Testing for longer videos is on my radar—while 16GB is quite a stretch for browser memory at the moment, I’d love to know if there's a pressing use case behind it. I'm always up for a challenge!

I have tested the code with videos up to 5 minutes in length, and it works well within that range. Theoretically, it should be possible to process longer videos too, but I haven’t yet optimized the system specifically for very large inputs like 16GB.

Would you be open to sharing your use case for longer videos? It would help me better understand your needs and potentially guide future improvements.

I recently open-sourced Twick, a React-based video editor and player library that brings modern video editing features to the browser. It's designed to be embedded directly into React apps, making it easier to integrate timelines, effects, transitions, captions, and basic animation controls.

What's unique is that the core is modular and supports AI functions (like auto-captioning or smart edits) that can be deployed as Dockerized cloud functions. The idea is to abstract away heavy editing workflows while remaining customizable for different use cases.

I’d love feedback from the HN community—especially around performance, architecture, or features you'd expect in a developer-first video editing SDK. The project is actively maintained and open to contributions.

What’s the longest video duration and highest resolution your SDK can handle smoothly in the browser without lag? Curious how it scales with heavier content.