“Video editing” covers compressing a screen recording for email and cutting a multicamera documentary. A browser can do the first group. It cannot do the second. The line is the useful part.
What WebAssembly makes possible
The reason browser video tools got good is WebAssembly (WASM). WASM lets developers compile native code — C, C++, Rust — to a format that runs in any browser at near-native speed.
ffmpeg, the open-source video processing toolkit used in professional pipelines, has been compiled to WebAssembly as ffmpeg.wasm. When a browser video tool uses ffmpeg.wasm, it's running the same processing logic as desktop ffmpeg — the same codecs, the same filters, the same quality. The difference is speed, which we'll cover below.
The practical result: tasks that used to require installing software can now run in a browser tab, and your files never have to leave your device.
What you can do in a browser today
Compress video
Reduce file size by re-encoding with a higher CRF (constant rate factor) or a lower bitrate. The browser tool sends the file through ffmpeg.wasm's H.264 or H.265 encoder.
What works well: screen recordings, talking-head footage, vlogs, lecture recordings. These compress 40–70% with minimal visible quality loss.
What compresses less efficiently: high-motion sports footage and gaming captures. The encoder has to preserve more detail per frame, so compression is less dramatic.
Extract audio from video
Strip the audio track from any MP4, MOV, MKV, or WebM file and save it as MP3, AAC, WAV, or OGG. This can be done with or without re-encoding (extracting the original AAC stream is lossless).
Works for: pulling a podcast episode from a video, grabbing music from a local video file, archiving audio from screen recordings.
Trim start and end
Set a start time and an end time; drop the rest. ConvertYard’s video trimmer has a fast mode that copies the stream (instant, cut on keyframes) and a precise mode that re-encodes (frame-accurate, slower). There is no timeline scrubber like Resolve — you type seconds.
Audio-only trims use the audio trimmer.
Convert between video formats
MP4, MOV, WebM, AVI, MKV — ffmpeg.wasm handles them all. Browser tools can convert any of these to any other.
Practical use: converting MOV from an iPhone to MP4 for sharing on Android or Windows. Converting AVI from an old camcorder to MP4. Converting WebM (common in screen recorders) to MP4 for email.
Convert video to audio formats
MP4 → MP3, MP4 → WAV, any video → any audio format. The video track is dropped and the audio is extracted (and optionally re-encoded).
Batch processing
Drop the files or the folder onto the dropzone, set the options once, download a ZIP. Files encode one after another in the tab. See batch compress videos for settings that scale.
What still needs desktop software
Multi-cut timeline editing
Cutting a video into multiple segments, rearranging clips, inserting cutaways — this requires a non-linear editor (NLE) with a timeline. No browser tool does this well. The right tool is DaVinci Resolve (free), iMovie (free on Mac), or CapCut (free, though it uploads files).
Color grading
Adjusting exposure, color balance, and color science across a video is computationally intensive and requires GPU access. Browsers don't expose GPU video processing in a way that supports professional-grade grading. Use DaVinci Resolve.
Visual effects and transitions
Fades, wipes, lower thirds, animated text, green screen compositing — these require a rendering engine that can work with layers and keyframes. Not available in any browser tool as of 2026.
Long-form re-encoding (speed issue, not a quality issue)
For a 90-minute lecture or a 4K film, the speed difference between browser WASM and desktop ffmpeg becomes significant. Desktop ffmpeg with H.264 hardware encoding can compress a 2-hour 1080p video in under 10 minutes on most modern machines. Browser ffmpeg might take 45–90 minutes on the same file. The output quality would be identical — but the wait time is not.
Output to broadcast or professional formats
ProRes, MXF, DNxHD — these are professional formats used in broadcast pipelines and NLE workflows. Desktop ffmpeg supports them. Browser ffmpeg.wasm builds often exclude them to keep the WASM bundle smaller.
How browser video tools handle privacy
Most browser video tools fall into one of two categories:
Upload-based tools (most online converters, most AI editing platforms): Your file travels to a server. The tool processes it there and returns a download link. You're trusting the service with your file content. File size limits apply.
WASM-based tools (ConvertYard, ffmpeg.wasm implementations): The processing engine runs in your browser. Your file loads into browser memory. No network request is made with your video data. You can verify this by opening your browser's Network tab (DevTools) while processing — you'll see no large upload request.
For personal footage, confidential recordings, business meetings, or sensitive content, the distinction matters.
Speed: what to expect
A rough guide for a 10-minute 1080p MP4 compressed to medium quality (CRF 23):
| Method | Processing time (approx.) |
|---|---|
| Browser WASM tool | 8–20 minutes depending on device |
| Desktop ffmpeg (CPU) | 3–8 minutes |
| Desktop ffmpeg (hardware encoder) | Under 2 minutes |
Browser tools are CPU-only. They cannot use the H.264/H.265 hardware encoder in your GPU or chipset. A multi-thread WASM build can use more than one core; it still loses to desktop ffmpeg. The output is the same. The wait is longer.
For files under 5 minutes, the difference is rarely annoying. For long files you need to process regularly, desktop ffmpeg is worth learning.
When the browser is the right tool
- You have one or a few videos to compress or convert
- The file contains personal or sensitive content you don't want uploaded
- You're on a computer without video software installed
- You need to strip audio from a video quickly
- You want to batch process a folder of screen recordings before uploading them somewhere
Browser video processing is particularly well-suited to screen recordings: they're usually short, compress dramatically (screencasts have low motion content), and are often created on machines that don't have video software installed.
When to use desktop software instead
- The video is over 30 minutes and time matters
- You need to make multiple cuts
- The file is larger than 2–3 GB
- You need color correction, effects, or multicamera editing
- You're processing dozens of long files regularly
For complex editing, DaVinci Resolve is free and handles everything a browser tool can't — and for simple compression and conversion, a browser tool handles everything without an installation.