FAQ
Questions, answered plainly
Short answers based on how Squeeze actually works today — including what runs in your browser versus what goes through the backend.
Yes, for compression. Single-file drag-and-drop, bulk upload, and URL fetch all send image data to the Squeeze FastAPI backend so it can hit an exact target size. Optional prep (crop, rotate, resize) runs in your browser first. URL modes also have the server download the remote image on your behalf, with SSRF protections. Nothing is kept as a permanent gallery after the response.
Common inputs work: PNG, JPG/JPEG, WEBP, BMP, GIF, and TIFF. Outputs are JPEG so Squeeze can reliably land on your target file size.
Single uploads, each file in a bulk upload, and URL-fetched images are limited to 15 MB per image. Bulk uploads are also limited to 50 MB combined, and URL fetches have a 10-second timeout.
Squeeze does not keep a permanent library of your uploads. Images are processed for the request and are not saved to a browsable gallery afterward. There is no account system. If you self-host, traffic stays on your own backend.
Portals, email systems, and app stores often enforce hard KB/MB caps. A vague “smaller” button can still fail those checks. Exact target size lets you aim for 150 KB, 200 KB, or whatever the form requires — and stop when you get there.
Yes. Squeeze is free to use with no signup and no paywall. Run it locally with the open frontend and FastAPI backend.
Want the product story? Read About or start compressing.