Video Tools

Q: Is the video I upload really not sent anywhere?

Yes. All processing happens in your browser via ffmpeg.wasm. The site operator never sees the contents. Only the ffmpeg library itself (~32MB) is downloaded from the jsdelivr CDN on first use; the video itself never leaves your device.

All processing happens in your browser. Your video never leaves your device.

Your video never leaves your browser. Uploaded clips stay in browser memory and are processed by ffmpeg.wasm — even the site operator can't see the contents.

🗜️

Compress Video

Shrink file size with resolution and quality — fits email and messaging limits

✂️

Trim Video

Cut by start and end times — Fast mode finishes in seconds

🔄

Rotate Video

90°/180° rotation + horizontal/vertical flip — fix sideways phone clips

🎞️

Video to GIF

Turn a short clip into a GIF — for social, reactions, stickers

🎵

Extract MP3

Pull MP3 audio from your own videos — 5 bitrate presets (copyright notice)

— Powered by ffmpeg.wasm

Your video never leaves your browser — compress, trim, rotate, GIF, MP3.

Tools like ezgif, freeconvert, and clideo upload to the cloud. This site uses ffmpeg.wasm (WebAssembly) to process videos entirely inside your browser. Five tools — compress, trim, rotate, GIF conversion, MP3 extraction — free and no signup. The first run downloads the ffmpeg library (~32MB) and caches it. Desktop Chrome is recommended (mobile memory limits).

Last updated: 2026-05-05 5 tools Your video stays local

Processing & limits

Who uses it

Messaging · emailShrink 1GB videos to 100MB for chat / email. 720p downscale, CRF 18–35 quality slider.

Rotated phone videosPhone-shot videos saved sideways or upside down — 90 / 180 / 270 rotation + horizontal/vertical flip. Auto scale option.

SNS GIFsShort clips (5–10s) → GIF for Instagram, X, KakaoTalk emoji. Optimized fps 10–30, width 240–640px.

MP3 extraction (your own)Pull audio from interview / lecture videos you own. 5 bitrate steps (96 / 128 / 160 / 192 / 320 kbps).

Lecture · meeting trimsCut a long video to the important section (e.g. 1:23 to 4:56). Fast mode finishes in seconds.

YouTube upload prep1080p → 720p downscale for faster upload. Crop / rotate to the desired aspect. Personal videos only.

Why mobile fails more often

Single-thread WASM (no COOP/COEP on GitHub Pages → no SharedArrayBuffer). iOS Safari caps at ~500MB; Android Chrome ~1GB. Decode + encode must fit that budget, so 1080p videos OOM easily.

Recommended: ≤ 720p, ≤ 1 minute, desktop Chrome. A 5-minute video compress takes ~1–3 minutes on desktop, 2–3× slower on mobile.

Cancel and memory safety

Every video tool supports mid-process cancel via ffmpeg.terminate() + runSeq / activeRun. Cancellation clears the WASM virtual filesystem and frees memory immediately. Next run starts with a fresh load.

Format / codec support

Input: MP4, MOV, WebM, MKV, AVI, FLV — anything ffmpeg can decode.

Output: MP4 (H.264 + AAC) / GIF / MP3 (libmp3lame). HDR 10-bit is auto-converted to SDR 8-bit. HEVC input decodes fine but always outputs H.264.

Use on content you own or are licensed to process. Audio extraction from third-party music / OTT content for redistribution is illegal. The site provides tools only — legal responsibility lies with the user.

Tech sources

Last verified: 2026-05-19

ffmpeg.wasm — LGPL 2.1 / ffmpegwasm.netlify.app
ffmpeg — ffmpeg.org
libmp3lame — LGPL / lame.sourceforge.io
SharedArrayBuffer — requires COOP/COEP headers (GitHub Pages can't set them → single-thread mode)

Frequently asked questions

Is the video I upload really not sent anywhere?

Yes. All processing happens in your browser via ffmpeg.wasm (WebAssembly). The site operator never sees the contents. Only the ffmpeg library (~32MB) is downloaded from the jsdelivr CDN on first use; the video itself never leaves your device.

Why do mobile browsers fail more often?

Single-thread WASM has memory and CPU limits. iOS Safari caps tabs around 500MB; Android Chrome around 1GB. Decoding plus encoding has to fit in that budget, so 1080p videos can fail with out-of-memory errors. We recommend ≤ 720p and ≤ 1 minute on mobile, or use desktop Chrome for larger files. In-app browsers and older browsers have stricter limits — Chrome or desktop is preferred.

Why is processing slow?

GitHub Pages can't enable SharedArrayBuffer (no COOP/COEP headers), so ffmpeg.wasm runs single-threaded — about 0.3 to 1× the speed of multi-threaded. Compressing a 5-minute video takes about 1 to 3 minutes on desktop Chrome. Mobile is 2 to 3 times slower.

Can I process copyrighted videos?

Technically yes, but please use only on videos you own or have a license for. Audio extraction in particular carries copyright risk — illegal use is prohibited.

Which video formats are supported?

Inputs include MP4, MOV, WebM, MKV, AVI, and most other formats ffmpeg supports. Outputs are MP4 (H.264), GIF, or MP3 depending on the tool.

Good to know

First run downloads ~32MB — the ffmpeg.wasm library (the video processing engine). Wi-Fi recommended. After download, it's cached and subsequent visits start instantly.
Mobile memory limit (iOS Safari ~500MB / Android Chrome ~1GB) — iOS Safari and older Android can stall on large videos (typically 30+ minutes or 1080p). Desktop Chrome is recommended.
Single-threaded processing — multi-threading isn't available due to browser security policy. Compressing a 5-minute video takes about 1 to 3 minutes (relative to source).
Personal use only — please use on content you own and respect audio/video copyright.