ShrinkVideos
About ShrinkVideos

A video compressor that doesn't need your files to work

Most online video compressors work the same way: you upload your file to a stranger's server, wait in a queue, and hope it comes back looking right. We wanted something different — a compressor that runs on your own device, so a large video never has to leave your computer just to get smaller.

Why we built this

The trigger was mundane: a video too big for WhatsApp, an inbox that rejected an email attachment, an Instagram upload that looked worse after the platform re-compressed it. Every existing tool either buried the free option behind a watermark, forced an account before showing a single result, or quietly uploaded the file to a server with no explanation of what happened to it afterward. ShrinkVideos is the tool we wanted to use ourselves: drop a file in, pick a quality level, get a smaller video back — nothing more required.

How it actually works

For files under 200MB, compression runs entirely inside your browser using FFmpeg compiled to WebAssembly — the same encoder used by professional video tools, just running on your device instead of a server. Nothing is uploaded, so there is nothing for us to see, store, or lose. Larger files are compressed on our own server (native FFmpeg on a small VPS), because no browser can reliably hold a multi-gigabyte file in memory — those uploads are deleted automatically a few hours after processing. The full breakdown is in our Privacy Policy.

Privacy by default

Most videos never leave your device. Compression runs locally in your browser using WebAssembly — we simply never see the file.

No dark patterns

No watermark on the free tier, no forced signup to try the tool, no fake countdown timers. What you see is what you get.

Fast, on purpose

Because compression happens on your own hardware, there's no upload queue and no server load to wait behind.

Honest about limits

Larger files do need our server, and we say so plainly — along with exactly how long that file is kept before it's deleted.

Questions, feedback, or a bug to report?

We'd genuinely like to hear it.