03
KEEP
Closing the tab is the uninstall
No app permissions, no kernel extensions, no autoupdater eating your battery. Close the tab and the editor is gone.
02
ENCODE
Same FFmpeg, same timeline
FFmpeg WebAssembly is the same encoder the desktop suites ship under the hood. The only difference is the install step you skipped.
04
BATCH
Works on the Chromebook
Chromebooks, locked-down corporate laptops, even an iPad in desktop-mode Safari. Same editor, same export, no admin policy fight.
0MBInstall
0Admin
100%Browser
What runs in the tab
01 · ENGINE
FFmpeg.wasm — same codec, no install
The actual FFmpeg binary, compiled to WebAssembly, running in a Web Worker on a thread separate from the page. The encoder is the same one the desktop suites use under the hood — H.264, VP9, ProRes-compatible — just sandboxed inside the browser instead of running as a separate native process.
02 · STORAGE
Browser cache, not Program Files
The video editor JS bundle is ~120KB gzipped. The FFmpeg.wasm module is ~25MB and caches after first load. All of it lives in your browser's storage quota. Uninstall by clearing site data — no Programs and Features, no /Applications cleanup, no apt-get remove.
03 · PORTABILITY
Same editor on every OS
Chrome on Windows. Safari on macOS. Firefox on Linux. The same URL, the same editor, the same export. No per-platform installer, no macOS-only restriction, no "version 11 doesn't support your kernel." Works on the work laptop and the personal Chromebook with identical behavior.
How it works
- Open morph.cool/video-editor in any modern browser. Chrome 90+, Safari 16.4+, Firefox 89+, or Edge 90+.
- The first load fetches the FFmpeg.wasm module (~25MB) and caches it. Subsequent loads are instant.
- Drop a video onto the timeline. The file reads from local disk via the File System Access API — never uploaded.
- Edit. Trim, cut, color grade, change speed, ramp speed with keyframes, drop in clips on three tracks.
- Export as MP4, MOV, WebM, or GIF. Close the tab. Nothing was installed, nothing is on your disk, nothing was uploaded.
The case for not downloading a video editor
Desktop video editors solved a real problem when bandwidth was scarce and browsers couldn't run heavy compute. In 2026, every modern browser ships WebAssembly, multi-threaded Web Workers, the File System Access API, and OffscreenCanvas — the platform primitives needed to run a real video editor without a native install. The trade-off used to be obvious: install for capability, suffer the install for the result. The trade-off has shifted. For most editing — trim, cut, color grade, speed change, basic transitions, social-platform exports — the browser is now capable enough that the install cost is no longer worth paying. The desktop suites still win for color science deep-dives, motion-graphics integration, and magnetic-timeline workflows. But for the 80% of cuts that are "open the file, trim it, color-correct it, export it for Instagram," the browser ships the same export quality with none of the install commitment.
Where they still win
Honest disclosure: native installs are still the right tool for a meaningful slice of work. Node-based compositing, full audio mixing, and a color page with nodes-based grading require GPU compute and disk caching that browser sandboxes restrict. Multi-editor productions, auto-reframe for vertical conversion, and a motion-graphics round-trip require a native pipeline. A magnetic timeline and a native compressor are OS-specific advantages browsers can't match. Desktop stability on 4-hour timelines exceeds what FFmpeg.wasm can sustain in a single tab. If your edit is 4-hour multicam with effects-heavy compositing, install something. If it's a 90-second cut for social, the tab works.
Frequently asked
How big is a light desktop editor compared to Morph?
A light desktop editor's installer is ~80MB and the unpacked install is ~350MB on disk plus a separate FFmpeg bundle. Morph's video editor is ~120KB JS plus ~25MB FFmpeg.wasm cached after first load. Total local footprint is about a third of that, lives only in browser cache, uninstalls by clearing site data.
Is the free desktop suite really 32GB?
The download is ~3.6GB compressed, but the full install (including the audio, compositing and studio assets, training projects) is ~32GB on disk. It also ships kernel extensions on macOS that prompt for admin authorization. Phenomenal software. Morph's editor doesn't try to be a colour suite — it covers basic-to-intermediate cuts, in a tab, no install.
What does Morph cost?
Everything that runs on your device is free with no cap. AI and server work is paid in credits, about a cent each. Morph Pro is $9.99 a month for 1,400 credits, live sessions, the Morph API and Soundbend’s full studio.
What does FFmpeg.wasm actually do?
FFmpeg is the open-source media library powering most video software, desktop suites included. FFmpeg.wasm is a WebAssembly port of the same C codebase, running in a browser sandbox at near-native speed. When you click Export in Morph, FFmpeg.wasm runs in a Web Worker, encoding using your CPU. Real MP4, real H.264, real AAC. No server.
Is there any speed penalty vs a native install?
Yes — WebAssembly runs at ~50-80% of native speed. A 30-second 1080p H.264 export taking ~6 seconds in native FFmpeg might take ~10 seconds in Morph. For typical social cuts under 5 minutes the difference is invisible. For multi-hour 4K with complex effects, native installs are still the right tool.