GUIDE
Need a no-upload alternative to TinyPNG-style batch?
Short answer: Upload compressors send originals to someone else’s servers. If you care about privacy or folder-scale batches, use BulkCrunch in the browser and download a ZIP. Free-web count or size claims from competitors are per their own pages. BulkCrunch has no that kind of web quota; the real ceiling is device memory and the browser.
1. Upload vs local
Upload path: handy for a few public assets; files leave the device. Local path: read, encode, and ZIP in this tab—better for client work, unreleased products, or large packs. See local batch compress (no upload).
2. What BulkCrunch offers
On-device JPG/PNG/WEBP re-encode, quality and optional max edge, singles or ZIP. Encoding is in-browser. The goal is local, batch-friendly, honest limits—not cloning one cloud optimizer’s ratio.
3. How to choose
- A few files and upload is fine: follow the other product’s current docs.
- Batch + originals stay on device: BulkCrunch; split if memory is tight—“no web quota” is not a fake “unlimited” promise.
- Format and upload size: JPG/PNG/WEBP · compress for upload limits.
- After compress, strip location or watermark: Metastrip · Stampdrop.
FAQ
Is local always smaller? Not guaranteed. Compare workflow and privacy.
Login? No.