imgcompress is fully self-hosted — your files are processed on your own server and never leave your infrastructure. No cloud storage, no third-party APIs, no tracking. Complete data sovereignty for privacy-conscious users and teams.
imgcompress runs entirely on your own server. When you upload an image, it goes to your Docker container, not to any cloud or third party. Only you (and anyone you give access to your server) can ever see your files.
Because imgcompress is self-hosted, the privacy model is straightforward: your files never leave your infrastructure.
For maximum privacy, you can block your Docker container from the internet entirely. imgcompress works fully offline. The only network call it makes is the optional version check described below.
Use Docker's network settings or your firewall to isolate the container. If you do, the version check simply won't run.
The built-in Heartbeat Check lets you confirm at a glance whether your container can reach the internet, without opening a terminal.
| Step | How it looks | What to do |
|---|---|---|
| 1 |  Open Storage Management | Storage Menu Open the "Storage Management" section in the app. |
| 2 |  Click Status Button | Check Status Click the "System & Connectivity Status" button. |
| 3 |  View Results | See your status Look at the results to see if you are online or offline. |
| Offline (isolated) | Online |
|---|---|
 Restricted status |  Online status |
I want you to know exactly what imgcompress does on the network. To make sure you never miss an important fix, I included a privacy-safe version check.
Update notification banner
The check only reads a version number (e.g. v0.6.0). No files, no IP logging, no identifiers of any kind are shared.
You can verify every line of code and every network call directly on the GitHub Repository.