Instant — or seconds.
Here's the line.
Browser-based processing has two tiers: operations that are truly instant (and provably lossless), and operations that re-encode and take seconds. We measured both.
The short version: trimming, muting, rotating, and remuxing a video finish in 0.0 seconds — they copy the original data instead of re-encoding it. Compressing or blurring video takes seconds to tens of seconds, scaling with clip length and your device's hardware encoder.
Methodology
Tests ran in Chrome 155 on macOS. The "instant tier" timings come from stream-copy operations on a 6-second 720p MP4 and were verified byte-for-byte (MD5 or pixel comparison). The "re-encode tier" timings come from our automated test environment, which runs in software mode (no GPU) — a regular browser on a laptop or phone with hardware acceleration is typically faster. Treat the second table as upper-bound-ish, not exact.
Tier 1 — instant and lossless (0.0 seconds)
| Operation | Test input | Time | Fidelity check |
|---|---|---|---|
| Trim video (video trimmer) | 6 s 720p MP4, cut to 4 s | 0.0 s | Video stream bit-identical |
| Remove audio (mute video) | Same clip, audio dropped | 0.0 s | Video bitstream MD5-identical |
| Rotate 90° (rotate video) | Same clip, metadata patch | instant | Zero pixel difference vs reference |
| MOV → MP4 (remux) | Same clip in .mov wrapper | 0.0 s | Video + audio bitstreams identical |
| Rotate PDF pages (pdf rotate) | 3-page PDF | instant | Page attribute only; content untouched |
These operations never decode a single frame. Trimming copies the video samples between two keyframes; muting leaves the audio track out; rotation writes a different display transform into the file header; remuxing rewrites the container index. That is why they take the same time for a 10-minute file as for a 10-second one — the limit is disk copy speed, not processing.
Tier 2 — re-encode (seconds, scales with length)
| Operation | Test input | Time (software mode) |
|---|---|---|
| Compress image (image compressor) | 1.13 MB photo | < 1 s |
| Trim audio / export MP3 (audio trimmer) | 3.5 s MP3 | < 1 s |
| Blur faces in video (video face blur) | 6 s 720p clip | ~15 s |
| Compress video (video compressor) | 1 min 1080p clip | 10–40 s (typical laptop) |
| Merge two clips (merge video) | 2 × 6 s 720p → 12.1 s output | ~49 s |
Re-encoding decodes every frame, draws or scales it, and encodes a new stream — the one quality generation that compression, blur, crop, and merge inherently cost. Two levers make it faster: a shorter clip (linear), and hardware acceleration (a real browser with GPU access, unlike our test harness).
Why this matters for choosing a tool
If your task is on the instant tier — cutting, muting, rotating, converting containers — a browser tool isn't just more private than a cloud service; it's faster, because there's no upload. If your task requires re-encoding, the browser is still private and often competitive, but the honest advice is: check the result, and keep the original. Our compression benchmark page has the quality-side numbers; the file size limits reference covers where the results need to land.
Why are some file operations instant and others take time?
There are two classes of operation. Lossless ones — trimming, muting, rotating, or remuxing a video — rearrange or re-label existing data without decoding it, so they finish as fast as the file can be copied (often under a second). Re-encoding operations — compressing video, blurring faces — must decode every frame and encode a new one, which takes seconds and scales with clip length.
Is the "instant" tier really lossless?
Yes, and we verify it. In our tests, a muted video's bitstream was MD5-identical to the source, a rotated video's frames matched a reference rotation with zero pixel difference, and a MOV-to-MP4 conversion produced identical video and audio bitstreams. The original data is copied, not re-created.
Does processing speed depend on my device?
Yes. Re-encoding uses your device's hardware encoder when available, so a modern phone or laptop can be several times faster than our headless test environment, which runs in software. Lossless operations depend mostly on disk read/write speed and are fast on any device.
How long does a typical video compression take?
On a normal laptop, a 1-minute 1080p clip typically takes 10–40 seconds to compress. Longer clips scale roughly linearly. In our software-only test environment, merging two 6-second 720p clips took about 49 seconds — hardware acceleration in a regular browser is significantly faster.
Why process files in the browser at all?
Two reasons: privacy and time. Nothing is uploaded, so sensitive files never leave your device — and you skip the upload/download round trip entirely. For lossless operations the browser is actually faster than any cloud tool, because there is nothing to transfer.