A TinyPNG alternative with room for bigger files

TinyPNG is a good tool, and it made image compression something anyone could do. Iminify takes larger files for free, reads formats TinyPNG doesn't, and tells you what each compression level is measured against. Try it below. No account needed.

  • 16 MB a file as a guest
  • HEIC, TIFF and GIF accepted
  • You decide when files go
Compression Level
None
No compression, only apply settings on image
Lossless
Without any visual change in the image quality
Ultra
Max compression with some quality loss
Smart
Balance between the image quality and compression
Change Format Will allow you to convert images to different extensions
Resize Will allow you to change the width, height or scale of images
Keep EXIF Will allow you to preserve meta data in images
Maximum file size is 16 MB per image and supported formats are: PNG, JPG, JPEG, WEBP, GIF, HEIC, HEIF, TIFF, TIF
Guests get 10 images a day, 10 left today. A free account gets 40 a day.
Delete this image?
The image and its optimized copy will be removed from storage. This cannot be undone.

Rename this image
Choose the name the optimized image downloads with. Its format stays the same.

Uploaded as

Rename the selected images
Each image gets this name and a number, counted in the order they were uploaded. Their formats stay the same.

Share this image
Choose the compression level that suits your images
Level What it promises What happens Pick it when
Lossless
Not one pixel changes in a JPEG, PNG or GIF The file is repacked, never re-encoded. JPEGs get an optimised Huffman table and progressive scan, PNGs a tighter deflate pass, GIFs a lossless gifsicle run. A lossy WebP has no repack step, so it is re-encoded at the highest quality the level allows. A sideways phone JPEG is rotated losslessly on the way through and keeps its colour profile. The one exception to the promise is a PNG or WebP tagged with a wide-gamut profile such as Display P3: its colours are converted to sRGB, so the values change but the picture doesn't. Logos, line art, anything you'll edit again, or when the file is evidence.
Smart
No visible change, targets 40 dB PSNR and a perceptual score of 70 A quality search runs per image and stops at the lowest quality that still clears the PSNR target. That answer is then scored on the SSIMULACRA 2 scale, because an average over every pixel lets a mostly flat picture through at a quality its detail doesn't deserve, and when it falls under 70 the search moves back up until it doesn't. Photos and graphics end up at different qualities because they need different ones; an image that cannot reach the targets inside the quality ceiling is encoded at the ceiling. Almost everything on a website. This is the default for a reason.
Ultra
Smallest file, targets 34 dB PSNR and a perceptual score of 50 The same two-stage search with lower targets. Fine texture softens a little; edges and text stay sharp. Thumbnails, backgrounds, email images, anything shown small or blurred anyway.
None
No compression at all Only the resize, conversion or metadata setting you chose is applied. An untouched upload comes back byte for byte. You only wanted to resize or convert, and quality is someone else's decision.

Side by side

Iminify and TinyPNG, by the numbers they publish

The TinyPNG column is taken from tinypng.com. Where its pages don't state something, the cell says so; we haven't guessed.

What Iminify TinyPNG
Free file size limit 16 MB as a guest, 32 MB with a free account 5 MB each
Free volume 40 images a day with a free account, 10 without one Up to 20 images at once
Free format conversion Every image, within the daily count Up to 3 images
Input formats JPG, PNG, WebP, GIF, HEIC, TIFF JPEG XL, AVIF, WebP, JPG, PNG and APNG
Output formats WebP, AVIF, PNG, JPG, or Auto (the smallest wins) AVIF, JPEG XL, WebP, JPEG, PNG
Compression levels Lossless, Smart and Ultra, each defined by a PSNR and a perceptual target Not stated
Resize in the same pass Yes, by pixels or percent Not stated for the free web tool
How long your files are kept Until you delete them. Every result has a delete button that removes the upload and the optimized copy for good. A guest can reach their results only while the browser session lasts, about two hours after the last request; after that the files stay in storage until we remove them, and an email to [email protected] gets one deleted. A maximum of 48 hours, then permanently deleted
Paid plan Pro: $36 a year or $5 a month, 90 MB files, no daily caps Web Pro and Web Ultra subscriptions

TinyPNG's figures were read from its own site on September 20, 2026, and they may have changed since. Source: tinypng.com.

The differences that matter

Where the two tools part ways

Retention first, because it cuts both ways. TinyPNG deletes your uploads within 48 hours. Iminify keeps an upload and its optimized copy until you delete them, so with an account your results are still there next week and you can compress the same original again with different settings. As a guest you can reach them only while your browser session lasts, about two hours after your last request, and the files stay in storage after that. If you'd rather nothing stayed on a server, that's a point for TinyPNG. Here, the delete button on each result is how a file goes, and it goes for good.

Then size. A 5 MB limit stops most photos straight from a current phone or camera. Iminify takes 16 MB with no account and 32 MB with a free one.

And formats in. TinyPNG reads JPEG XL and AVIF, which Iminify doesn't. Iminify reads HEIC from iPhones, TIFF from scanners and animated GIF, which TinyPNG's list leaves out. Pick the tool that reads the files you have.

We haven't published a compression benchmark against TinyPNG, so this page makes no claim about whose files come out smaller. Run the same image through both and compare. Iminify's Compare view gives you the PSNR and a pixel difference map to judge with.

What survives

What you get here

  • Levels that mean something

    Smart aims for 40 dB PSNR and a perceptual score of 70 against your upload; Ultra for 34 dB and 50. Lossless changes no pixel in a JPEG, PNG or GIF, apart from converting a wide-gamut PNG to sRGB.

  • Compress, convert and resize in one encode

    One pass, one generation of loss, not three tools chained together.

  • A whole web page at once

    With a free account the page scanner finds every image a page loads, compresses them all and hands back a zip.

  • No JPEG XL and no plugins yet

    TinyPNG has a WordPress plugin, an image CDN and JPEG XL support. Iminify has none of those today. Both have a developer API.

How to

Try the same image in both

  1. 1

    Drop an image above

    Use one you've already run through TinyPNG, so you have something to compare against.

  2. 2

    Leave it on Smart

    Smart is the closest match to an automatic setting.

  3. 3

    Compare size and pixels

    Check the saving, then open Compare for the PSNR and the difference map.

Questions

Questions about switching

From the blog

What we've measured so far

We run the encoders on real photos and screenshots and publish the numbers: when WebP beats AVIF, what quality 80 means in each encoder, and how many kilobytes an image on a web page should weigh.

All posts
Bar chart of the resized files WordPress 7.1.2 made on the server and in Chrome: 691 and 640 KB for a 1800 px photo, 1,942 and 2,193 KB for its 6000 px version, 553 and 651 KB for a PNG screenshot.

Does WordPress compress images? What WordPress 7.1 does to your upload

We uploaded the same photo to a fresh WordPress 7.1.2 site twice, both times from Chrome. The file we sent, 832 KB, was stored byte for byte both times. From it WordPress made five resized copies at JPEG quality 82. Through Media > Add Media File those copies came to 691 KB. Through the Upload button on an Image block they came to 640 KB, because in 7.1 that button has the browser make the copies instead of the server. So does WordPress compress images automatically? Not the file you upload, which is stored byte for byte. It re-encodes the resized copies it makes, the JPEG ones at quality 82. In our test a phone and a standard laptop screen downloaded copies of this photo, but a 2x laptop screen got the untouched original, so compressing it is still your job. Since 7.1, which program makes the copies depends on the button you press and the browser you press it in.

8 min read
ComfyUI's Flux Dev example render of a fox-eared girl in a maid dress holding a cake, captioned: 1,215,064-byte PNG to 125,684-byte WebP, and the workflow still loads in ComfyUI.

ComfyUI PNG to JPG loses the workflow. WebP and AVIF can keep it

ComfyUI's Flux Dev example image is a PNG of 1,215,064 bytes, and the two text chunks holding its prompt and workflow take 12,240 of them. The rest is 1024x1024 pixels stored without loss. Across the 92 PNGs in ComfyUI's examples repository that carry a workflow, the text was no more than 3.32 percent of any file, with a median of 0.62 percent. Converting to JPG shrinks the file, but ComfyUI's own loader can't read a workflow back out of a JPG. A WebP or AVIF can keep it, at about a tenth of the size. We took the text-to-image examples of ten models from ComfyUI's examples repository, made smaller copies several ways, and dropped the copies back onto ComfyUI 0.37.0's canvas to see which ones still held the workflow.

6 min read
Bar chart of mozex.dev's image bytes at Lighthouse's phone size: 63.7 KB in 2 files before scrolling, 653.5 KB in 9 files after, and a worked-out 107.1 KB with its own images resized and re-encoded for the phone and the hidden one skipped.

How to find large images on a website: three tools gave us three different lists

On 22 September 2026 we loaded mozex.dev, the site of Mozex Labs, which runs Iminify, at the phone size Lighthouse emulates, and listed its images three ways: Chrome's network log, Lighthouse and a console snippet. Before any scrolling, Chrome had fetched 2 image files, 63.7 KB. After we scrolled to the bottom, it had fetched 9 files, 653.5 KB. Lighthouse's phone runs requested 7 and never the two heaviest, 340.8 KB between them. The browser's own timing data put one image at 0 bytes. So the list you can trust comes from Chrome's Network panel, taken after a scroll. Every method here works on one page at a time, so run it on the pages you care about most.

8 min read

Run one of your images through it

A side-by-side test on your own file tells you more than any comparison page.

Compress an image Open the full tool