Show what happened
Formats, dimensions, bytes, duration, and real size changes belong beside every result - including when a resize or crop makes a file larger.
Small tool. Strong opinions.
A playful image tool that respects the boring details.
Tinify.dev started as a custom alternative to image tools that made a simple job feel needlessly complicated. The animated gradients, strange shapes, and original upload box are part of that identity - not decoration waiting to be replaced by a dashboard template.
Underneath, the goal is stricter: predictable processing, honest results, and an API whose behaviour can be understood before you send it a production image.
The point of view
Simple on the surface. Specific underneath.
Keep the simple path simple
The first interaction should still be the familiar Tinify box: drop in an image, choose what matters, and get the file back.
Make limits explicit
File, pixel, queue, and timeout limits turn overload into a clear answer instead of an endless spinner or a vague promise.
Behind the upload box
One public door. One private image pipeline.
The handoff is deliberately narrow. Each layer owns one decision and passes a verified job to the next.
- 01BrowserSelects files and reports progress without exposing image content.
- 02Kotlin gatewayValidates access, limits, quotas, and every public API response.
- 03Sharp workerProcesses core formats on an authenticated private connection.
Privacy is a product feature
Your image is input, not content.
- Results have a short download window and are cleaned up.
- The image worker is private behind the public API gateway.
- Analytics never receive image contents or filenames.
- A larger result is described as an increase, not a saving.
Designed and built by
Stian Larsen
I build Tinify.dev from the animated interface to the processing services behind it. It is deliberately personal, a little odd, and continuously sharpened by the images people actually bring to it.
More work at stianlarsen.com →Enough about the tool