How to troubleshooting smart compressor
- Step 1Check the tier limit — Free tier caps every input at 50 MB. If your file is larger you'll see a tier-limit error before processing starts. Pro raises this to 500 MB; Pro+Media to 2 GB.
- Step 2Verify the input format — Run /archive-tools/auto-format-detector on the file. It reads the first bytes and reports the true format — sometimes a renamed file (a .zip that's actually a .rar) is the cause of failure.
- Step 3Rule out browser extensions — Chrome's "A listener indicated an asynchronous response" warning in DevTools is a sign that an extension intercepts page messages. Disable extensions in Incognito and retry. WebAssembly init can stall when extensions touch worker channels.
Frequently asked questions
Why does it stay on "Processing…"?+
If processing exceeds 30 seconds the tool now throws a clear timeout error. If you're stuck at "Processing…" with no error, you may be on an old cached build — hard-refresh (Ctrl+Shift+R) to load the latest chunk.
Why does my file fail to compress?+
Check the format with the Archive Format Detector. A common cause is a corrupt central directory — try the Corrupted ZIP Repair Tool to recover what's salvageable.
Why is the output smaller / larger than expected?+
Compression ratios vary widely: text and source compress to 15-25% of original, JPEG/MP4/MP3 barely shrink (already entropy-dense), and re-zipping an existing ZIP is a no-op. Use the Compression Ratio Calculator for a per-file breakdown.
What error codes might I see?+
"Tier limit exceeded" — file too big for your plan. "Unsupported format" — magic bytes don't match a recognised archive. "WASM init timeout" — browser blocked WebAssembly; disable extensions. "CRC mismatch" — file is corrupt; try the repair tool.
Privacy first
Every JAD Archive tool runs entirely in your browser using fflate, @zip.js/zip.js, and the libarchive WASM bridge. Your archives never leave your device — verified by zero outbound network requests during processing.