User uploads, optimized before they hit your CDN
If your product lets users upload images, you inherit their 8 MB phone photos. Optimagio’s API compresses, converts, and resizes every upload on the way in — with SSRF-safe URL handling and idempotent batches so it’s safe to put in front of real users.
- Optimize user uploads via the API in real time
- SSRF-safe URL mode for user-supplied links
- Cache-aware billing and self-hostable stack
Real product capability — not a placeholder.
User-generated images are a performance and safety liability
Accepting image uploads means accepting whatever users send: huge dimensions, legacy formats, and occasionally malicious payloads. Serving those raw inflates your bandwidth bill and slows every screen that renders them. Optimizing on intake fixes both.
Safe to expose to user input
Optimagio’s URL optimization allows only http/https, blocks private and internal IP ranges, and caps source size — so a user-supplied URL can’t be turned into a server-side request forgery. A pixel-count guard blocks decompression bombs. Batches are per-item, so one bad upload is rejected on its own while the rest succeed.
Production-grade by default
Real-time intake
Compress/convert/resize on upload so your storage and CDN only ever hold optimized bytes.
SSRF protection
URL mode blocks internal ranges and caps source size — built for untrusted input.
Idempotent batches
Safe retries with idempotency keys; changed payloads on a used key return 409.
Cache-aware
Identical inputs don’t double-charge your monthly quota.
Your storage
Stream results through the API backed by disk or any S3-compatible bucket you own.
Self-host option
Run the Go API, worker, Postgres, and Redis on your own Docker infrastructure.
Scale throughput as you grow
Pro handles 50,000 images/month at 1,000 RPM; Business handles 100,000 at 3,000 RPM. Scale is custom for high-volume products with contract limits and 10 team seats.
Frequently asked questions
Is it safe to optimize user-supplied image URLs?
Yes. Optimagio’s URL optimization allows only http/https, blocks private and internal IP ranges, and caps downloaded source size, which prevents server-side request forgery (SSRF) from user input. A decompression-bomb guard also protects against malicious files.
How does Optimagio handle one bad file in a batch?
Batches are per-item: invalid, oversized, or checksum-failed files are listed separately as rejected while every accepted file keeps processing. A single bad upload never fails the whole batch.
Can we run it on our own infrastructure?
Yes. The stack runs on Docker Compose — Go API, dedicated image worker, PostgreSQL, and Redis — with disk or S3-compatible storage for optimized results.
Start optimizing your images today
Try the free public tool now, then upgrade for higher limits, bulk batches, the API, storage, and reports.
Free tier available · No card required to start · Cancel anytime