How to optimize web video without installing handbrake
- Step 1Open the tool — nothing to download — Web Optimize loads in your browser. There's no installer, no Homebrew/winget step, no FFmpeg path to configure. On a managed work laptop where you can't install HandBrake, this still works.
- Step 2Drop your video — MP4, MOV, MKV, or WebM, one file per run. Free up to 1 GB, Pro 10 GB, Pro + Media 100 GB. The source is read locally; nothing is sent to a server.
- Step 3Note there are no settings (unlike HandBrake) — HandBrake greets you with presets and tabs. Web Optimize shows one line: "No options needed." The recipe is fixed at 1280px H.264 CRF 23 + AAC 128k + faststart. If you specifically need HandBrake-style control, see the last step.
- Step 4Run it — FFmpeg.wasm performs the same kind of decode → scale → H.264 encode → faststart mux that HandBrake's Web Optimized preset does, just in the browser. Progress tracks FFmpeg's
time=output. - Step 5Verify like you would after HandBrake — Confirm the moov atom is at the front (
ffprobe -v trace out.mp4 2>&1 | grep moov) and the width is ≤1280. Both are guaranteed by the recipe — same checks you'd do on a HandBrake export. - Step 6Need real HandBrake-level control? Use a configurable tool — If you want custom CRF, two-pass, a specific resolution, audio passthrough, or denoise, this one-button tool isn't enough. Use video-transcoder (codec/CRF/container) or video-bitrate-set (exact bitrate) — closer to HandBrake's flexibility, still in-browser.
JAD Web Optimize vs HandBrake's Web Optimized preset
Same web goal, different control surface. Web Optimize values are verified against the processor; HandBrake values reflect its Web Optimized + Fast presets.
| Aspect | JAD Web Optimize | HandBrake (Web Optimized) |
|---|---|---|
| Install | None — runs in browser | Download + install desktop app |
| Video codec | H.264 (libx264), fixed | H.264/H.265/AV1, your choice |
| Quality control | Fixed CRF 23 | Any CRF, two-pass, target size |
| Resolution | Width capped at 1280px (auto) | Any resolution / preset |
| Audio | AAC 128k, fixed | Passthrough or any codec/bitrate |
| faststart | Always on | "Web Optimized" checkbox |
| Privacy | Local (in-browser) | Local (desktop) |
| Configurability | None (one button) | Extensive |
Which JAD tool maps to which HandBrake capability
If you came for a HandBrake feature, here's the in-browser tool that covers it.
| HandBrake feature you want | JAD tool | Notes |
|---|---|---|
| Web Optimized preset (H.264 + faststart) | web-optimizer (this tool) | One-click equivalent |
| Custom CRF / codec / container | video-transcoder | H.264/H.265/AV1/VP9/ProRes, your CRF |
| Target bitrate / file size | video-bitrate-set | Set exact video + audio kbps |
| H.265 for smaller files | h265-encoder | ~half the bytes at equal quality |
| Strip metadata before sharing | metadata-scrubber | HandBrake doesn't do this cleanly |
Cookbook
Mapping HandBrake's web workflow to JAD's one-button equivalent. The FFmpeg commands are what JAD runs in your browser.
HandBrake Web Optimized → JAD Web Optimize
The HandBrake Web Optimized + Fast 1080p preset produces an H.264 MP4 with faststart. JAD's recipe lands in the same place, capped at 1280px wide, with no app to install.
HandBrake: Preset 'Fast 1080p30' + 'Web Optimized' ☑
→ H.264 MP4, moov at front
JAD Web Optimize (in-browser, equivalent FFmpeg):
ffmpeg -i in.mp4 \
-vf "scale='min(1280,iw)':-2:flags=lanczos" \
-c:v libx264 -preset medium -crf 23 -pix_fmt yuv420p \
-c:a aac -b:a 128k -movflags +faststart out.mp4No command line, no install — the whole point
If you were going to run the FFmpeg above by hand, you'd need FFmpeg installed and comfort with the CLI. JAD does the same thing on a button.
Without JAD you'd need: 1. brew install ffmpeg / winget install ffmpeg 2. open a terminal 3. type the 6-flag command correctly With JAD: 1. drop file → 2. click run → 3. download
When the one-button recipe isn't enough
HandBrake's strength is tuning. If you need a non-default CRF or codec, switch to the configurable JAD tool rather than this preset.
Want HandBrake's 'RF 20, H.265, 1080p kept'?
→ video-transcoder: codec h265, crf 20, targetFormat mp4
/video-tools/video-transcoder
Want 'two-pass, target 10 MB'?
→ video-bitrate-set: compute kbps for your duration
/video-tools/video-bitrate-setVerifying parity with a HandBrake export
The two outputs should pass the same checks: faststart on, H.264, yuv420p, AAC. Confirm with ffprobe.
$ ffprobe -v error -show_entries \ stream=codec_name,pix_fmt -of default=nk=1:nw=1 out.mp4 h264 yuv420p aac $ ffprobe -v trace out.mp4 2>&1 | grep moov # at front
Optimising on a locked-down work machine
On managed devices you often can't install software. A browser-based optimiser sidesteps that entirely — same result as HandBrake, no admin rights needed.
Corporate laptop: HandBrake install BLOCKED by IT policy. JAD Web Optimize: opens in the browser, processes locally, no install, no admin rights. Same H.264 + faststart MP4.
Edge cases and what actually happens
You wanted HandBrake's preset picker / custom CRF
Not configurableWeb Optimize is one fixed recipe — no preset list, no CRF slider, no two-pass, no denoise. That's the trade for zero-install simplicity. If you need HandBrake-level tuning, use video-transcoder (codec/CRF/container) or video-bitrate-set (exact bitrate), both in-browser.
Expected H.265/AV1 like HandBrake offers
H.264 onlyThis tool always outputs H.264 for maximum compatibility. HandBrake lets you pick H.265 or AV1 for smaller files. JAD does too — just not here: use h265-encoder or av1-encoder for those codecs.
Wanted audio passthrough (no re-encode)
Re-encodes audioHandBrake can pass the source audio through untouched. Web Optimize always re-encodes audio to AAC 128k. If preserving the original audio bitstream matters, this isn't the tool — for a no-re-encode export use lossless-trimmer (stream-copy), or transcode with explicit audio settings.
Big 4K source that HandBrake would chew through fine
OOM on mobileA native desktop app like HandBrake uses system RAM; FFmpeg.wasm uses the browser's WebAssembly heap (~512 MB practical on mobile). A 4K source can OOM in-browser on a phone where HandBrake wouldn't on a desktop. Run large sources on a desktop browser, where the heap is far larger.
File larger than your tier limit
RejectedHandBrake has no file-size limit; JAD gates by tier — Free 1 GB, Pro 10 GB, Pro + Media 100 GB. For very large masters, upgrade or trim with lossless-trimmer first. The limit is bytes, not duration.
Need a specific output resolution
Use video-transcoderHandBrake lets you pick any resolution. Web Optimize caps width at 1280px (downscale-only) with no override. If you need 1080p kept or an exact size, use video-transcoder or video-resizer.
Source format HandBrake reads but FFmpeg.wasm struggles with
Rare format gapFFmpeg.wasm supports the common containers/codecs (MP4, MOV, MKV, WebM, H.264/H.265/VP9/AV1). An exotic camera codec HandBrake handles via system libraries might not decode in-browser. If a source fails, transcode it to MP4 first elsewhere, then optimise.
Wanted batch encoding like HandBrake's queue
Single file onlyHandBrake has a job queue. Web Optimize processes one file per run with no queue. Run files sequentially. The fixed recipe makes each run identical, so there's no per-file setup to repeat.
Result quality differs slightly from your HandBrake output
ExpectedHandBrake's presets use different default CRF, preset speed, and tune settings than this fixed recipe (CRF 23, preset medium). Minor quality/size differences from a HandBrake export are normal. If you need to match a specific HandBrake output, replicate its CRF/codec in video-transcoder.
Privacy concern about a web tool vs desktop app
Equivalent privacyA common worry is that a "web" tool uploads your file. Web Optimize does not — FFmpeg.wasm runs in your browser, so the media stays local just like HandBrake on the desktop. Only an anonymous processed-file counter (no content) is recorded for signed-in users, and it's optional.
Frequently asked questions
Is this really equivalent to HandBrake's Web Optimized preset?
For the web outcome, yes: both produce an H.264 MP4 with the moov atom at the front (faststart) plus AAC audio. The difference is control — HandBrake exposes every setting; JAD's Web Optimize is one fixed recipe (1280px, CRF 23, AAC 128k, faststart). Same destination, no install, less tuning.
Do I need to install anything?
No. Web Optimize runs FFmpeg.wasm directly in your browser tab — no HandBrake download, no FFmpeg install, no command line. It works on any OS with a modern browser, including locked-down work machines where you can't install software.
Is my video uploaded, since this is a website?
No. Despite being a web tool, processing happens locally in your browser via WebAssembly — the file never leaves your machine, the same as a desktop app. Only an anonymous "file processed" counter (no content) is logged for signed-in users, and you can opt out.
Can I choose the CRF or codec like in HandBrake?
Not in this tool — it's deliberately one button with no options. For HandBrake-style control over CRF, codec (H.265/AV1/VP9), and container, use video-transcoder. For an exact bitrate/target size, use video-bitrate-set.
Does it support H.265 / AV1 like HandBrake?
Web Optimize itself outputs only H.264 for maximum compatibility. JAD does offer those codecs in dedicated tools: h265-encoder and av1-encoder. Use those when smaller files matter more than universal playback.
Can I pass through my original audio?
No — audio is always re-encoded to AAC 128k. HandBrake offers passthrough; this tool doesn't. If you need the original audio bitstream untouched, use a stream-copy export like lossless-trimmer instead.
Will it handle a 4K source like HandBrake does?
It can, but with a caveat: FFmpeg.wasm uses the browser's WebAssembly heap, which is much smaller than a desktop app's access to system RAM — especially on mobile (~512 MB). A 4K source can OOM in a phone browser. Run large sources on a desktop browser, where the heap is far larger.
How big a file can I optimise without HandBrake?
Free up to 1 GB, Pro up to 10 GB, Pro + Media up to 100 GB. HandBrake has no built-in limit, but for most web videos these tiers are plenty. The limit is file size, not duration. Trim first with lossless-trimmer if you exceed it.
Why might my JAD output differ from my HandBrake output?
Different defaults: HandBrake presets use their own CRF, encoder speed, and tune; this recipe is fixed at CRF 23, preset medium. Small size/quality differences are expected. To match a specific HandBrake export, replicate its CRF and codec in video-transcoder.
Can I batch a queue like HandBrake?
No — Web Optimize handles one file per run with no queue. Process files sequentially. Because the recipe is fixed, there's no per-file configuration to redo between runs.
What resolution does it output?
It caps width at 1280px (downscale-only) and auto-computes an even height. A 1080p source becomes 1280×720; anything already ≤1280px wide keeps its width. For a different resolution, HandBrake-style, use video-transcoder or video-resizer.
Is it free?
The Free tier optimises sources up to 1 GB at no cost, entirely in your browser. Paid tiers only raise the maximum file size (Pro 10 GB, Pro + Media 100 GB) — there's no per-file charge and no upload, just like running HandBrake locally but with nothing to install.
Privacy first
Every JAD Video tool runs entirely in your browser via WebCodecs and FFmpeg (WebAssembly). Your video files never leave your device — verified by zero outbound network requests during processing.