Local system onlineAPI docs
LESS FRICTION. MORE FORWARD.

Free batch file compressor — up to 50 files

From “file too large” to ready to go. Pick a size or a destination. We’ll handle the rest.

1

Add your file

Up to — MB on server
+

Drop it here. We’ll make it fit.

Select up to 50 files free. Browser processing first; cloud limits apply.

Images, PDFs, documents, video & audio
ImagesPDFs & docsVideoAudio
2

Tell us where it needs to fit

Popular sizes
Private by defaultRust/WASM in your browser → Rust edge → server only if needed.
Quality preserved where possible. Every output validated.
Checked, not guessedDeterministic validation on every output
Only yours to accessPrivate storage and short-lived download links
Here for a little whileDelete now, or let automatic cleanup do it

How to use this target

Prepare a batch of up to 50 supported files with one set of size settings. The browser processes a small number concurrently and keeps the rest queued, so selecting 50 files does not start 50 memory-intensive encoders at once. This page starts with a 200,000-byte target; change it to your upload limit.

  1. Select up to 50 files. Use a batch whose files share the same output requirements; choose automatic format for a mixed image/PDF batch.
  2. Set a maximum size and, if required, a minimum size. Choose on-device-only when files must not leave your browser.
  3. Process the queue and inspect each result. A failure on one file does not prevent the remaining files from being attempted. Download each successful output individually.

What to check before uploading

The browser currently handles supported JPEG, PNG, WebP and PDF inputs within its memory and time limits. Unsupported or larger files can fall back to edge/server processing in automatic mode, subject to account quotas. This is a queue of 50, not 50 simultaneous workers. It does not merge files or download a ZIP bundle.

Common questions

Is processing 50 files free?

Supported browser processing is free. Anonymous cloud fallback is limited to 5 files daily and signed-in Free fallback to 20; account and file-size limits still apply.

Why are only one or two files running at once?

A bounded worker count avoids exhausting browser memory. Files remain queued and begin as workers finish; slower devices use fewer workers.

Can one damaged file stop my whole batch?

Each file has its own result. A failed file is reported individually, while the queue continues unless you cancel it.

Other targets