I compressed a video on 8mb.video to see what "free" means there. Position 64 in line, and a paywall behind the one feature that would have solved my problem.
Why 8MB specifically
Almost nobody wakes up wanting an 8MB video for its own sake. They want to send a clip somewhere that caps uploads at 8MB — usually Discord without Nitro, sometimes an old forum or a slow upload form — and their phone just handed them a 40MB file. "8MB video compressor" is a size problem with a deadline, not a hobby, which is exactly the moment a queue is the worst possible answer.
What "free" gets you on 8mb.video
I opened 8mb.video to compress a video to 8MB — the same job my own 8MB compressor does. Instead of a progress bar, I got this:
Waiting in Line
You are position 64 in line. There are hundreds of people using the service right now, hold on a second and we'll be with you soon.
HOLD MUSIC: clink clank clinkity clop
💖 A labor of love by a cool girl. Upgrade for a few dollars and skip the line immediately while funding continued improvements.
I checked twice while writing this, a few minutes apart, from a normal residential connection with nothing unusual going on. Both times: a queue, a position number, and the same offer to pay to skip it. That's not a bad day for their servers — it's the free tier working as designed. Every video someone uploads has to run through 8mb.video's own hardware, one at a time per worker, so when enough people show up at once, someone waits. The wait is also part of the pitch: it's what makes "upgrade for a few dollars" worth clicking rather than closing the tab.
The custom size field is a paywall, not a feature
8mb.video's presets are 8MB, 10MB, 20MB, 25MB, 50MB and 100MB. Below the presets there's a "Custom" field that looks like it takes any number up to 200MB — which would matter if you needed a 15MB file for a form with an odd limit, or a 35MB file because that's what someone specifically asked for. Type a number in and try to run it, though, and what comes back isn't a compressed video — it's a subscription prompt. The field shows you what you're missing rather than giving it to you.
So a free account on 8mb.video really does mean six sizes and no others. Anyone who needs a seventh number is the customer the upgrade prompt is built for, not an edge case the site forgot to handle.
Why a browser-based compressor doesn't have either problem
SquishyFile compresses video with WebAssembly running in your own browser tab. There's no upload step, because there's no server on the other end doing the work — your device does it, the same way it would if you'd installed FFmpeg locally instead of using a website at all.
That has one direct consequence for each problem above. There's no queue because there's nothing to queue: my video doesn't wait behind anyone else's, because it's never in a line with anyone else's — it just runs on my own CPU while I watch. A thousand people could be compressing video on SquishyFile at the same moment and none of us would notice, because none of us are sharing a server or a worker pool. There's no capacity to run out of.
And the target size box takes any number I type, not six of them. It's the same input whether I want 8MB or 37MB, free, because there's no server cost that scales with how unusual my number is — the work happens on my machine either way, so there's nothing to gate behind a subscription.
None of that is free of trade-offs. A browser tab needs to stay open and in the foreground while it works — some browsers throttle background tabs — and a large 4K source on an old laptop takes real time and real battery, because it's using that laptop's CPU rather than a server farm's. That's the one place 8mb.video's model genuinely helps: if your device is weak enough that local encoding would crawl, borrowing someone else's hardware is a real advantage, queue or not.
How I tested this
Same 42-second 1080p H.264 clip on both, targeting 8MB, over a normal home connection, no VPN, checked on two separate visits a few minutes apart. 8mb.video queued both times with a different position number; SquishyFile started encoding immediately both times, as it always does, since there's no shared server to queue behind. I'm not claiming 8mb.video is always this busy — server load moves around — but the custom-size paywall isn't load-dependent. That one's there every time, queue or no queue.
Side by side
| 8mb.video (free) | SquishyFile | |
|---|---|---|
| Where it runs | Their server | Your device |
| File leaves your device | Yes, uploaded | No |
| Size options | 8/10/20/25/50/100MB presets only | Any number you type |
| Custom size | Paywalled | Free |
| Queue at busy times | Yes, with a position number | None — nothing to share |
| Skip the wait | Pay to skip | Nothing to skip |
| Good for weak/old hardware | Yes — uses their servers | Slower on very old devices |
Common questions
Why do I have to wait in line on 8mb.video?
Because it compresses video on its own servers, one file at a time per available worker. When enough people use it at once, new jobs queue behind the ones already running — and the site offers to let you pay to jump the line.
Can I get a custom size for free on 8mb.video?
There's a custom size field, but entering a number and submitting it prompts a subscription upgrade rather than compressing the file. Free accounts are limited to the six preset sizes.
Is there a free video compressor with no queue and no size limit?
Yes — anything that runs in your browser instead of on a server, like SquishyFile. Since it uses your own device's processing power rather than shared server capacity, there's no line to wait in and no reason to cap which sizes are free.
Does my video leave my device with 8mb.video?
Yes. It has to — the compression happens on their servers, so the file uploads before any processing starts.
Why does Discord need an 8MB video anyway?
8MB is Discord's upload limit for accounts without Nitro. It hasn't changed in years, phone cameras keep getting bigger files, and the gap between the two is exactly what an 8MB compressor exists to close.
The honest version
8mb.video isn't broken — it's a server-based tool with a free tier shaped to nudge people toward paying, which is a completely reasonable business to run. If your device is old enough that local compression would genuinely be slow, uploading to someone else's hardware is a fair trade, queue or not. But if you just need a video under a certain size and you're not in a hurry to fund someone's server bill, running it locally skips the queue and the upsell by never having either one to skip.
Top comments (0)