Why free compressors add watermarks

If you have searched for a video compressor, you have met all of these: a watermark across the output, a 2-file-per-day cap, a "sign up to download", a 100MB input limit, or a progress bar that reaches 99% and then asks for a card.

These are not separate business decisions. They are all the same decision, and understanding it tells you exactly which tools will do this and which cannot.

The economics

A server-based compressor pays, for every single file:

• Inbound bandwidth. Your 200MB upload costs them to receive.
• CPU time. Video encoding is among the most expensive things you can ask a computer to do. A 10-minute clip can occupy a server core for minutes.
• Storage. Your file and its output sit on a disk until they are cleaned up.
• Outbound bandwidth. The download, which is typically the most expensive line item of the four.

Call it somewhere between a few cents and a few dollars per file depending on size. Now multiply by everyone who found the site today. That cost is real, recurring, and scales linearly with how popular the tool becomes — which means success makes the problem worse, not better.

There are only so many ways to cover it:

Mechanism	What it is really for
Watermark	Make the free output unusable so you pay to remove it
Daily file cap	Cap the cost per visitor
Input size limit	Cap the cost per file
Signup wall	Convert the cost into an email address to market to
Ads	Cover the cost at a fraction of a cent per view
Queue	Ration a fixed amount of CPU across everyone

None of these are villainous. They are what a tool with per-file costs has to do to keep existing. A server-based compressor with no watermark, no cap and no account is a tool that is losing money on every file, and it will eventually either add one of the above or disappear.

So when a server-based tool advertises "free, unlimited, no watermark", the honest reading is "free for now".

What removes the reason entirely

If the compression happens on your machine, every line item above goes to zero. No upload to receive, no CPU to rent, no storage, no download to serve. The operator's marginal cost per file is nothing.

And when the marginal cost is nothing, there is nothing to ration. No watermark, because there is no free tier to make worse than a paid one. No daily cap, because the hundredth file costs exactly what the first one did. No account, because there is no usage to meter. No queue, because you are not sharing a server with anyone.

This is why the distinction matters more than any promise: a tool with no server cannot develop a reason to start charging you per file. It is a structural property rather than a policy, and policies change.

This became possible for video relatively recently. The browser API that exposes your device's hardware video encoder to JavaScript — WebCodecs — is what makes a local compressor fast enough to be worth using. Before it, the only local option was a software encoder compiled to WebAssembly, roughly an order of magnitude slower. See compressing video without uploading it for how that works.

How to tell which kind a tool is, in ten seconds

Open the Network tab in your browser's developer tools and compress a file. Either you will see a large request carrying your video, or you will see nothing after the page loads. That is a definitive answer.

Try it offline. Load the page, disconnect your network, and compress something. A local tool works. A server tool cannot.

Watch what happens with a large file. A local tool starts immediately. A server tool shows an upload progress bar first — and the time that bar takes is time the local tool has already spent encoding.

Read the page for a size limit on the input. An input cap is a cost control, and cost controls imply a server.

The remaining honest trade-offs

Local compression is not free of downsides, and a page claiming otherwise is selling something:

• It uses your battery and warms your laptop. The work has to happen somewhere, and with a local tool that somewhere is your device.
• Speed depends on your hardware. An old budget machine encodes slower than a server core. Most of the time the upload you skipped covers the difference; not always.
• Very old browsers cannot encode video at all. Without WebCodecs there is no local video path, and the honest response is to say so rather than to fail quietly. Images and PDFs do not need it and work much more widely.
• The tab has to stay open. No job queue to come back to later.

What you get for that: no watermark, no cap, no account, no queue, no upload, and a tool whose incentives do not change as it gets more popular.

Trying it

Everything on this site runs in your browser. There is no /api directory in the codebase and no server-side component — the privacy and the lack of limits are the same fact, viewed from two directions.

Compress to 20MB for Discord or to 16MB for WhatsApp. Unlimited files, no watermark, no signup, permanently — not as a promise, but because there is nothing it would cost us to honour it.

FAQ

Is there a genuinely free video compressor with no watermark?

Yes, but check where the compression happens. A server-based tool pays real money for every file it processes, so "free and unlimited" is a position it cannot hold indefinitely. A browser-based tool that encodes on your own machine has no per-file cost at all, which is why it can offer unlimited use without a watermark and keep offering it.

Why do compressors limit how many files I can do per day?

Because each file costs the operator bandwidth and CPU time. A daily cap limits the cost per visitor. Tools that run entirely in your browser have no such cost, so there is nothing for a cap to control.

Are free online compressors safe to use?

The compression itself is fine; the question is what happens to your copy of the file. A server-based tool necessarily receives your video and stores it at least temporarily, and what happens after that is governed by a privacy policy you cannot verify. For anything confidential — legal, medical, HR, financial documents — a tool that never transmits the file avoids the question entirely.

Will this site start charging later?

The thing that would force it is a cost that scales with use, and there isn't one: compression runs on your machine, so a thousand files cost us exactly what one does. That is why the no-watermark, no-cap, no-signup position is stated as structural rather than as a pledge.