Free
$0
- 100% local compression, no image uploads
- Up to 50 images per batch
- Keeps nested folder structure in the ZIP
Swiftiny
Compress WebP images online, on your device
Drop WebP files or folders. Swiftiny re-encodes them in your browser so already-converted assets can get smaller still. Nested folders stay in the ZIP. Nothing is uploaded.
Why compress WebP hereExports that are already WebP are not always well compressed. A second local pass can cut weight on a design folder or CMS dump without sending files out.
Drop images or folders here
Supports PNG, JPG, WebP, and AVIF. You can choose files or folders, and folder paths are kept in the zip.
Selected0 image(s)
Original size0 B
Output size0 B
Savings0%
Select or drop multiple images, then start compression. By default, the tool aims to reduce size while preserving visual quality, and you can compare sizes after processing.
Compression settings
Re-compress WebP batches privately
If your pipeline already outputs WebP, you may still want a smaller quality/size tradeoff before deploy. Swiftiny does that in the browser, with the same folder-preserving ZIP as PNG and JPG.
Use the quality slider and Deep mode when you need more savings. Switch output to JPG or PNG only if a tool downstream cannot read WebP.
Free use processes up to 50 images per batch. Pro removes the cap with a one-time purchase.
Frequently Asked Questions
Do you upload WebP files to compress them?
No. WebP encoding runs locally in your browser.
Can I mix WebP with PNG and JPG in one batch?
Yes. Swiftiny accepts PNG, JPG, and WebP in the same folder. Set output to Keep original format or convert everything to one format.
Will compressing WebP again ruin quality?
Re-encoding can add generation loss. Start at quality 82 and compare. If the file does not get smaller, enable “keep original when compression gets larger.”
Pricing
Free to try. Pro when batches get big.
Compression still happens on your device. Pay once for unlimited images per batch — Creem handles checkout, cards, and tax.