Just Tool It
Just Tool It / Video Toolkit
On-device — nothing uploaded

Video Toolkit

Compress, trim, mute, resize, convert and extract audio — all in your browser using FFmpeg.wasm. First operation downloads ~30 MB of engine (cached thereafter).

Drop a video here

MP4, MOV, MKV, AVI, WebM, GIF — or browse

Why edit video without uploading?

Family videos, product demos, and screen recordings are huge and personal. Cloud “free compressors” upload multi‑hundred‑MB files and often keep them for hours. Just Tool It’s Video Toolkit runs FFmpeg.wasm inside the browser: compress, trim, convert (MP4/WebM/MOV and more), extract audio, or build a GIF. The ~30 MB engine loads on demand the first time you process — so first content paint stays fast — then caches for later. Zero-server processing for media is rare; treat it as a privacy feature, not a gimmick.

How to compress or convert video on-device

  1. Drop a video file onto the toolkit dropzone.
  2. Pick an operation: compress, convert, trim, extract audio, GIF, etc.
  3. Tune options (CRF/quality, format, start/end times) for your goal.
  4. Run the job — first run may download FFmpeg core; then download the result.

Frequently asked questions

Is my video uploaded to compress it?
No. After optional CDN downloads of the FFmpeg.wasm engine (not your media), encoding runs locally. Your video file is not POSTed to Just Tool It.
Why is the first run slow or large?
FFmpeg.wasm core is tens of megabytes. It downloads once, then the service worker / browser cache can reuse it. Subsequent jobs start faster.
Will this melt my laptop?
Video encode is CPU-heavy. Prefer shorter clips on laptops; close other tabs for big 4K files. There is no free lunch — local encode uses local heat.
Do I need special headers?
Some FFmpeg builds need cross-origin isolation (COOP/COEP) for multi-threaded SharedArrayBuffer. See the deployment docs if encode fails in production.

Related tools