Faster conversions and smaller files
Browser conversion works best under 500MB. Learn how to get 2-3x faster conversions and 50% smaller files with the right settings.
Browser-based conversion with ffmpeg.wasm is powerful, but your device is the server. A 2GB 4K video will be slow on any laptop. A few smart choices make it 2-3x faster and produce files half the size.
1. Pick the right resolution
4K is 3840x2160. Most phones and laptops display 1080p or 720p. Downscaling to 1080p cuts pixel count by 75% and speeds up encoding dramatically. In JSM-Video.com, use Resolution: 1080p or 720p unless you need 4K for archiving. The visual difference on a phone is minimal, file size drops by 60%.
2. Choose Speed vs Quality wisely
- Fast (ultrafast, CRF 28): Drafts, previews, quick shares. Smallest files, fastest.
- Balanced (veryfast, CRF 23): Default for most uses. Good quality and speed.
- Quality (medium, CRF 20): Final exports, client delivery. Slower, larger, better.
3. Use hardware acceleration when you can
If you are converting MP4 to WebM and have Chrome/Edge, enable Hardware Acceleration. We use MediaRecorder and Canvas captureStream, which uses your GPU. It's 3-5x faster than WASM and doesn't need the 30MB engine.
4. Remove what you don't need
Audio track can be 10-15% of file size. If you only need video for a background loop, check "Remove audio". Similarly, rotate or flip is applied in the same encode pass - no extra cost.
5. Stay under 500MB for best experience
Our FAQ says best under 500MB, hard limit 1GB. Above that, browsers may run out of memory. For large files, split or compress in steps: first downscale to 1080p, then compress again to lower CRF.
6. Close other tabs
ffmpeg.wasm uses SharedArrayBuffer and Web Workers. Other heavy tabs compete for CPU and memory. Close video editors, keep one converter tab open.
Example workflow for a 162MB file like yours
Your Haydi-don-flamenko video at 162MB is ideal. Choose MP4 Universal, Resolution Original, Speed Fast for a quick share, or Quality for final archive. Conversion should take 30-60 seconds on a modern laptop with multi-thread enabled.
Understanding x264 presets: what "Speed" actually changes
When you pick Fast, Balanced, or Quality, you're choosing an encoding preset — a bundle of dozens of internal decisions the encoder makes about how hard to look for compression opportunities. The preset names (ultrafast, veryfast, medium, slow) control how thoroughly x264 searches for redundant patterns between frames.
- Ultrafast: Minimal searching. Encodes fast but needs ~30-40% more bits for the same quality as medium. Good for drafts.
- Veryfast: The sweet spot — most of medium's quality at a fraction of the time. Our Balanced default.
- Medium: The x264 default. Noticeably slower than veryfast, modest quality gain.
- Slow / slower: Diminishing returns for huge time costs. Only worth it for final archives you'll keep for years.
Key insight: preset and CRF are independent dials. CRF 23 at ultrafast looks worse than CRF 23 at medium, but the file sizes differ too. For the best size-to-quality ratio in reasonable time, pair a moderate CRF (23-26) with veryfast or faster.
Multi-threading: using all your CPU cores
Video encoding parallelizes beautifully — different frames can be encoded simultaneously. ffmpeg.wasm in JSM-Video.com enables multi-threaded mode when your browser supports crossOriginIsolated (Chrome and Edge do by default on this site). On an 8-core laptop, that's roughly a 4-6x speedup over single-threaded. If your conversions feel slow, check the engine banner: "Multi-threaded acceleration active" means you're getting full speed. Firefox and Safari may fall back to fewer threads due to stricter SharedArrayBuffer policies.
Hardware acceleration via MediaRecorder
For MP4-to-WebM conversion, we skip FFmpeg entirely and use your GPU through the MediaRecorder API. Your graphics chip encodes video in dedicated silicon — 3-5x faster than even multi-threaded WASM, with no 30MB engine download. The trade-off: less control over exact settings (no CRF dial, just bitrate targets). It's the right choice when speed matters more than squeezing the last 5% of efficiency.
Memory limits: why big files fail in browsers
Browsers cap how much RAM a single tab can use — typically 2-4GB depending on device. FFmpeg needs roughly 2-3x the file size in working memory during conversion (input buffer + decoded frames + output buffer). That's why a 1GB 4K file can crash a tab with 4GB of system RAM, while the same file at 1080p converts fine. Practical rules:
- Under 500MB: Smooth sailing on any modern device.
- 500MB - 1GB: Works on desktops; close other tabs first. Mobile browsers may struggle.
- Over 1GB: Split the file or downscale first. Desktop FFmpeg (installed locally) has no such limits.
Batch processing efficiently
Converting 10 files? Order matters. Convert the smallest files first to warm up the engine (it's cached after first use), and keep output settings identical across the batch so you can use "Convert all." Avoid mixing 4K masters and phone clips in one batch with one setting — the 4K files will dominate total time. Split by resolution: do all 1080p files at one setting, then handle the 4K ones separately.
Network is not the bottleneck (but it feels like it)
Because nothing uploads, your internet speed is irrelevant to conversion time — a nice side effect of local processing. The 30MB engine downloads once and caches. After that, you can literally disconnect from Wi-Fi mid-conversion and it keeps working. If the first load feels slow on a weak connection, that's the only network-dependent moment.
Frequently asked questions
Why is my conversion stuck at 0%?
Usually the engine is still loading (first visit downloads ~30MB). Wait for the green "Engine ready" banner. If it stays stuck, hard-refresh — a partial engine download can wedge the worker.
Does a faster computer help?
Enormously. Encoding scales with CPU cores and clock speed. An M-series Mac or recent Ryzen finishes in a fraction of the time of a 5-year-old dual-core laptop. GPU via MediaRecorder helps even more for supported conversions.
Why is WebM conversion so much faster than MP4?
Our WebM path uses your GPU hardware encoder instead of software FFmpeg. Different engine, different speed — that's the whole story.
Can I convert while doing other work?
Yes, but encoding will slow down as it competes for CPU. Heavy tasks (gaming, video calls, another encode) can double conversion time. Light browsing is fine.
Do I need to keep the tab in focus?
Browsers throttle background tabs' timers and workers. Keep the converter tab visible — minimized or hidden tabs can slow to a crawl or pause entirely on some browsers.
What's the absolute fastest way to shrink a video?
Downscale to 720p + Fast preset + remove audio, via the MP4 Universal output. That combination hits every lever at once and usually finishes in under a minute for typical clips.