A self-hosted image compressor that never uploads your images
TinyPNG and its clones compress your images on their servers. SnapOtter runs the same job on yours, through a UI or a REST API, so the originals never leave your network.
What most teams do today
You drag images into an online compressor, wait, and download the smaller files. The originals sit on a third-party server for as long as that service chooses to keep them.
Why that's a problem for sensitive files
For public marketing assets that's usually fine. For product screenshots, ID scans, or anything with customer data in frame, you have handed a copy to a vendor whose retention you do not control. Free tiers also cap image count and size, so batch jobs stall.
How SnapOtter does it privately
SnapOtter's compress tool runs on your own instance. Point the UI at a batch or POST files to the API, get back optimized JPG, PNG, or WebP, and nothing leaves the box. The only limit is your hardware.
Self-host in one command
Process a file over the REST API
Last reviewed July 10, 2026. Commands match the current single-container image and REST API. Competitor references: TinyPNG
Frequently asked questions
- Does it upload my images anywhere?
- No. Compression runs inside your SnapOtter instance. If you deploy it inside your own network, the images stay there.
- Which formats does it handle?
- JPG, PNG, and WebP for compression, with the wider SnapOtter catalog available for conversion in the same deployment.
- Is there an API for batch jobs?
- Yes. POST files to /api/v1/tools/image/compress with an si_ API key, or chain compression into a pipeline for whole folders.
More self-hosted workflows
Deploying this across a team?
Audit trails, per-tool permissions, SSO, and air-gapped deployment for regulated environments. Talk to us about running SnapOtter as shared infrastructure.