Your files never leave your device. All processing happens locally in your browser.

Your files. Your device.
Your privacy.

Compress, convert and optimize 27 kinds of files right here — no uploads, no cloud, no signup.

Process files locally

Drop files here — they are validated and processed inside your browser. Nothing is uploaded.

Drop files here

Files are processed locally in your browser and never uploaded.

You can select multiple files. Drag and drop or use the file picker.

Batch status

0 total0 completed

Batch progress appears while jobs are active.

Job queue & results

No jobs yet. Add validated files to the queue to start processing.

How it works

  1. Choose a file

    Your browser reads the file locally and validates its real type with extension, MIME and magic-byte checks — before anything else happens.

  2. Process on your device

    The file's bytes are transferred into a Web Worker and processed by lazy-loaded engines. Your main browser tab stays responsive, and the bytes never reach a network.

  3. Download the honest result

    You get the real measured size change — including "it didn't get smaller", when that's the truth. Temporary resources are released right after download.

Frequently asked questions

Do my files get uploaded anywhere?
No. CompressKit has no upload step: your file is read by your browser, processed by JavaScript and WebAssembly running on your device, and the result is saved straight back to your disk. The architecture contains no server that could receive file data.
How can the tools be free with no signup?
Because there is no processing infrastructure to pay for — your own device does the work. A backend exists only for account and payment features; it never receives file bytes, file contents or filenames.
Which formats can CompressKit handle?
Every tool listed on this page is implemented and tested: PDF (compress, merge, split, extract), images (JPEG, PNG, WebP, SVG), archives (ZIP, gzip, TAR, Zstandard, 7-Zip), Office documents (DOCX, XLSX, PPTX, legacy XLS conversion), CSV, developer formats (JSON, HTML, CSS, JavaScript), audio (WAV/MP3 inspection, MP3 re-encode and MP3→WAV), video (MP4/WebM convert, trim, compress and inspect), EPUB optimization and font subsetting (TTF, WOFF2). Formats that are not yet tested are deliberately not advertised.
Does processing happen offline?
Once the page has loaded, the tools keep working even if your connection drops, because all processing is local. For heavy WASM-based operations the engine is loaded on demand from the site, but the file data itself never travels.
What are the size limits?
There is no artificial limit and no account tier gating — the practical limit is your device memory. Very large files are flagged with a warning before processing so you can decide.