Image A TinyPNG alternative that never uploads your images
The same class of compression the popular upload based services use, running inside your browser instead of on their servers.
Drag files here, or
JPEG, PNG, WebP, AVIF and GIF. Decoded on your device, never uploaded.
Encodes at quality 76, tuned to be indistinguishable from the original at normal viewing size. This is the setting to use when you just want the file smaller.
Optional. Height follows automatically.
Ready. Runs locally on your device.
Your files stay on your device. The tool works directly in your browser, using your device to process your files. Nothing is sent to our servers, and we never receive, store, or see your files or figures.
Share result
Cite
Cite this page
Reembun. (2026, July 31). A TinyPNG alternative that never uploads your images. https://reembun.com/tinypng-alternative
How to use it
Drop the images in
As many as you like. They are compressed by your own browser, so there is no upload, no queue and no monthly limit.
Choose how hard to compress
Smart picks a sensible quality, By quality gives you the slider, and To a file size works backwards from the limit you have been given.
Pick the format
PNG keeps transparency and sharp edges. WebP and AVIF usually beat both PNG and JPEG on size, which is where the real saving is.
Compare and download
Every image lists the before and after size. Nothing leaves your device at any point, including the originals.
What actually differs
The compression itself is not the interesting part. Both approaches use the same two techniques, because those techniques are simply what works: reduce a PNG to a colour palette, and encode a JPEG with a quality focused encoder rather than a stock one.
What differs is where that happens.
| This tool | Upload based services | |
|---|---|---|
| Where it runs | Your browser | Their server |
| Your image | Never leaves the device | Copied to a third party |
| Batch limit | None | Capped on free tiers |
| File size limit | Your device’s memory | Capped on free tiers |
| Works offline | Yes, after first load | No |
| Account needed | No | Sometimes, for the API |
| Cost | Free | Free tier, then paid |
For most images this distinction is academic. For some it is the whole point: a client’s unreleased product photography, a scanned passport for a visa application, an internal screenshot with customer data on it, a medical image. Those should not be sitting in a queue on someone else’s machine, however briefly and however trustworthy the operator.
What “tiny” compression actually is
The marketing name obscures a fairly simple idea, and it is worth understanding because it tells you when it will work spectacularly and when it will not.
A normal PNG stores 24 bits of colour per pixel, enough for about 16 million distinct colours. Almost no real PNG needs that. A screenshot of a spreadsheet might use 40 colours. A logo might use 6. Quantisation finds the colours actually present, builds a palette, and stores one small index per pixel instead of three full bytes. On a flat graphic this routinely removes 70% of the file with no visible change whatsoever, because no information was thrown away.
On a photograph it is a poor fit. Photographs genuinely do use thousands of colours, especially across skies and skin, and forcing them into 256 produces visible banding. This is why every compressor of this kind performs miraculously on some images and disappointingly on others, and why converting a photographic PNG to JPEG or WebP will always beat quantising it.
The Smart preset here reads your image before deciding. If it already contains 256 colours or fewer, it uses exactly that many, which is mathematically lossless and still much smaller. Only richer images get reduced.
If you searched for tinyjpg, tinywebp or tinyavif
Those queries usually mean one thing: compress this format well, without thinking about settings. Choose the format at the top of the tool and leave it on Smart.
Worth knowing what each is good for:
JPEG is encoded with the same class of quality focused encoder that sits behind the better JPEG tools. Against your browser’s built in one it saves roughly 20% at matched quality, mostly through progressive encoding and better quantisation tables.
WebP is the pragmatic default in 2026. Every current browser supports it, it is meaningfully smaller than JPEG, and unlike JPEG it keeps transparency, so it can replace PNG for graphics too.
AVIF compresses hardest, often 40% below JPEG, but encodes slowly, especially on phones. For one hero image it is worth the wait. For a batch of fifty it usually is not.
When the upload based services are still the better choice
Being honest about this is more useful than pretending otherwise.
If you are compressing photographic PNGs where smooth gradients matter, their quantiser handles the transition between colours more gracefully than ours does, and the difference is visible. If you need compression as an automated step in a build pipeline or a CMS, they sell an API and this tool deliberately has no server to call. If you are processing hundreds of large images and your machine is modest, their servers are faster than your laptop.
If none of those apply, and for most people none do, there is no reason to send the file anywhere.
Common questions
Is this the same as TinyPNG?
No, and it is not affiliated with it. TinyPNG and TinyJPG are products of Voormedia. This is a separate tool that uses the same underlying compression techniques, a reduced colour palette for PNG and a quality focused encoder for JPEG, with one difference that matters. The work happens in your browser rather than on a server, so the image is never transmitted anywhere.
Is the compression as good?
For PNG, very close. Both reduce the image to a colour palette, which is where nearly all of the saving comes from. Our quantiser is a little less sophisticated in how it handles smooth gradients, so a photographic PNG may show slight banding where theirs would not. For flat graphics, screenshots and logos, which is what most PNGs actually are, the results are hard to tell apart. For JPEG both are doing the same thing, and the results match closely.
What is the file size or batch limit?
There is none. The upload based services have to cap batch size and file size because every image consumes their bandwidth and CPU. Nothing here touches a server, so the only limit is your own device's memory. Very large images will simply take longer.
I searched for tinyjpg, tinywebp or tinyavif. Is this the right tool?
Yes. Those searches almost always mean "compress this image type the way TinyPNG compresses PNGs". Pick your output format at the top and use the Smart preset. JPEG is handled by a quality focused encoder, while WebP and AVIF are handled by your browser's own, which are already the best available for those two formats.
Does it work offline?
Yes, once you have loaded the page once. The compression code is cached on your device, so you can add this page to your home screen and use it on a plane or with no signal. An upload based compressor cannot do this by definition.
Do you keep or see my images?
We cannot. There is no upload step to intercept. Your image is read by the page, decoded, re-encoded and handed back, all inside the browser tab. You can verify this by opening your browser's network tab while compressing, or by disconnecting from the internet entirely and watching it still work.
Last reviewed
