Compare
A TinyPNG alternative that keeps the photo here.
TinyPNG compresses images on its servers. The Image Compressor here re-encodes them in your browser tab. That difference matters for some photos and not for others, and for PNG files TinyPNG usually gets them smaller.
Last updated 28 October 2026
The short answer
Yes, for JPG and WebP photos, and for PNG if you accept a different trade-off. The Image Compressor here decodes and re-encodes the image inside the tab, and no request carries it. TinyPNG's FAQ says uploaded images are retained for up to 48 hours and then permanently deleted. TinyPNG reduces the number of colours in a PNG, which this site does not do, so for a PNG that has to stay a PNG, TinyPNG will usually produce the smaller file.[1][3]
Claims about TinyPNG checked on 28 Oct 2026. Sources are listed at the end.
Compressing an image, side by side
- Where the image is processed
- TinyPNGUploaded to TinyPNG and kept for up to 48 hours.[1]
- StaysLocalIn this browser tab. No request carries the image.
- Free limits
- TinyPNGUp to 20 images at a time, 5 MB each.[2]
- StaysLocalUp to 50 MB per image. The Batch Optimizer takes many images and returns a ZIP; the tool sets no count limit.
- PNG
- TinyPNGLossy: similar colours are combined, often into an 8-bit palette.[3]
- StaysLocalLossless re-encode only. A large saving means converting to WebP or JPEG.
- Metadata
- TinyPNGRemoved. The developer API can keep copyright, location and creation date.[5]
- StaysLocalRemoved on re-encode, including GPS location. No option to keep it.
Where TinyPNG is the better choice
PNG is the clearest case. TinyPNG combines similar colours, which turns a 24-bit PNG into a much smaller 8-bit one with little visible change. The compressor here re-encodes PNG losslessly, so a screenshot or an illustration that must stay a PNG will usually come out smaller from TinyPNG.[3]
TinyPNG also handles formats this site does not write, JPEG XL and AVIF among them, as well as animated PNG. Its developer API lets a build pipeline compress images automatically, and can keep copyright and creation-date metadata that a re-encode here always drops. The work runs on TinyPNG's servers rather than on your device's processor, which matters on a slow machine with a large batch.[1][4][5]
Where keeping the photo in the tab matters
A phone photo carries more than pixels. Its EXIF data often includes the GPS coordinates of where it was taken, which for most personal photos means a home address. Here, that photo never leaves the device on its way to being made smaller, and the re-encode strips the location from the copy you download.
There is also no retention window to think about. TinyPNG states its own clearly: 48 hours, with only you able to access the images. Processing in the tab means there is no copy to retain at all. And the size cap is set by what a tab can safely decode, not by an upload limit, so a 20 MB camera JPEG is fine.[1][2]
What the compressor here does
It gives you a quality slider and shows the before and after file size as you move it, so you can stop where the picture still looks right. For most photographs that is somewhere between 75 and 85; above 90 the file grows quickly for detail nobody sees. It does not pretend a JPEG can get smaller with no loss: JPEG is lossy, and the honest goal is a loss you cannot see.
For a folder of images, the Batch Optimizer applies one quality and format setting to every file and hands back a single ZIP, one image at a time so the tab does not run out of memory.
Check it yourself
You do not have to take this page's word for any of it. Open your browser's developer tools, switch to the Network tab, and run the compressor on a photo. Look for a request that carries it: there is none. Then switch the network off and run it again. It still works, because nothing was being sent in the first place.
The same check works on any other tool, including the ones compared here. It is the quickest way to find out where a file actually goes, whatever a page says about it.
The tools compared here
Sources, checked on 28 Oct 2026
Every statement above about TinyPNG comes from one of these. Products change; if one no longer matches, the date says when it was last true.
- [1]
TinyPNG's FAQ says only you have access to the images you upload, and that it retains them for a maximum of 48 hours, after which they are permanently deleted.
TinyPNG home page FAQ · Stated on their page · Checked on 28 Oct 2026
- [2]
TinyPNG's web compressor says it takes up to 20 images at a time, with a maximum of 5 MB each, for free users.
TinyPNG home page · Stated on their page · Checked on 28 Oct 2026
- [3]
TinyPNG's FAQ says it compresses PNG files by combining similar colours, a technique it calls quantization, so 24-bit PNG files can become much smaller 8-bit indexed-colour images.
TinyPNG home page FAQ · Stated on their page · Checked on 28 Oct 2026
- [4]
TinyPNG's FAQ lists support for JPEG XL, AVIF, WebP, JPG, PNG and APNG (animated PNG).
TinyPNG home page FAQ · Stated on their page · Checked on 28 Oct 2026
- [5]
TinyPNG's FAQ says it removes unnecessary metadata, and that its developer API can keep some metadata, such as copyright, location and creation date.
TinyPNG home page FAQ · Stated on their page · Checked on 28 Oct 2026