Designed around a queue
The batch queue limits worker concurrency and avoids decoding an entire collection at once.
A Squoosh Alternative for Batches and URLs
Compare CompressByURL and Squoosh for browser-local compression, batch work, target sizes and URL image optimization.
Local processingBatch readyIndividual or ZIP download
Settings
Upload and compress images
Drop or paste images here
JPEG, PNG, WebP or static AVIF. Add one file or a whole batch.
- JPEG
- PNG
- WebP
- AVIF
Local files never leave your device.
Keep local processing; change the shape of the workflow.
Squoosh is a strong browser-local image lab. CompressByURL is the alternative when the job is a repeatable queue, an explicit byte ceiling, a direct image URL or a webpage image audit.
- Shared strength
- Browser-local image compression
- CompressByURL focus
- Batch, target-size and URL workflows
- Review date
- September 14, 2026
Different control philosophy
Squoosh exposes deep codec choices. CompressByURL uses restrained presets first and keeps advanced controls available when needed.
Evidence review · September 14, 2026
CompressByURL vs Squoosh
Both products process local images in the browser. The useful choice is between Squoosh's detailed per-image codec workspace and CompressByURL's queue, byte-target and URL-oriented workflow.
| Workflow | CompressByURL | Squoosh |
|---|---|---|
| Local processing | Local file decode, encoding, previews, naming and ZIP generation happen in the browser. | The official repository says image compression happens locally and images are not sent to a server. |
| Working style | A bounded worker queue processes multiple images with shared settings and ZIP output. | The official app is organized around a detailed image comparison and codec settings workspace. |
| Format controls | Supports JPEG/JPG, PNG, WebP and static AVIF behind one consistent settings model. | The official repository describes numerous formats and exposes codec-specific controls. |
| URL workflows | Includes direct public image URL intake and bounded single-page image discovery. | This comparison makes no claim that Squoosh lacks an equivalent URL workflow. |
Sources reviewed: Squoosh web app, official Squoosh repository, official Squoosh FAQ (last edited 2021). Features and limits can change; verify the linked product before making a decision.
How it works
Local files remain on the device in both products according to the reviewed first-party evidence. CompressByURL's network access begins only when you deliberately choose an Image URL or Website URL mode.
Add a file or batch
Drop a supported static image or a batch into the shared browser-local queue.
Choose repeatable settings
Apply one preset across the queue, or use resize, quality, format and target-size controls.
Inspect and export
Review measured bytes and dimensions, then download individual results or a ZIP.
Useful for
- Apply the same settings to several website assets.
- Search for the highest tested quality under a fixed KB ceiling.
- Move from a webpage image audit into a local optimization queue.
Questions about a squoosh alternative for batches and urls
Is CompressByURL more private than Squoosh?
No. Both keep local image processing in the browser. CompressByURL is aimed at repeatable batch, target-size and URL/page workflows; Squoosh is especially useful when you want to explore detailed codec controls on an image.
Does Squoosh upload the image itself?
The Squoosh repository says it collects basic visitor information and before/after image-size values through analytics. It also says the image itself is not sent to a server. Review the current privacy disclosures for your needs.
When is target-size mode useful?
Use target-size mode when a form or CMS imposes a byte ceiling. CompressByURL searches a bounded quality range and can offer proportional Smart Fit dimension reduction when quality alone cannot meet the target.