# Iminify

> Free online image compressor, converter and resizer, plus a page scanner that finds and compresses every image on a web page. No account, no watermark, up to 16 MB per image; the page scanner needs a free account.

Iminify runs on its own servers with jpegli, mozjpeg's jpegtran, pngquant, zopfli, cwebp, avifenc and gifsicle. Two compression levels search for the encoder quality per image, so the same level means the same visual quality across photographs. Smart keeps the lowest quality that reaches either 40 dB PSNR or a score of 80 on the SSIMULACRA 2 scale (where a picture cannot be told from the original side by side), raised until it scores at least 70; a screenshot or drawing is held to 80. Ultra keeps the lowest that reaches 34 dB, raised until it scores 50. These are targets, not guarantees: Smart's score of 80 applies to images up to 4 megapixels, the perceptual check to images up to 8 and the search to images up to 36, and a larger image, or one that reaches no target, is encoded at the level's quality ceiling (Smart: 90, Ultra: 75, and never above 75 for an upload that is already a lossy WebP). The search is for JPG, WebP and AVIF output: a PNG is quantised to a smaller palette, which at Smart has to score 80 for a screenshot or drawing up to 8 megapixels or the PNG keeps every colour, and a GIF is compressed at a fixed setting for the level. Lossless repacks a JPEG, PNG, GIF or lossless WebP without changing a pixel, except that a PNG or lossless WebP tagged with a wide-gamut colour profile is converted to sRGB; a lossy WebP has no repack step, so Lossless hands it back as it came and re-encodes it only for a resize, another format or a size limit it is over (at quality 75 at most, lower or smaller in pixels when a limit needs it; with Auto, another format's file of it is delivered when that is smaller), and a HEIC or TIFF always comes back in another format because Iminify writes neither. None applies only the resize, conversion or metadata setting chosen, and an upload with none of those comes back byte for byte. A file Iminify made at Smart or Ultra, sent again at that level (or an Ultra file at Smart) with no resize, no other format and no size limit it is over, comes back as it is (already-optimized, or completed with its metadata taken off when it carried some), since a second pass would cost it visible quality; Iminify keeps a keyed fingerprint of each such file, linked to no account, to know it.

## Pages

- [Image optimization](https://www.iminify.com): upload JPG, PNG, WebP, GIF, TIFF or HEIC; choose Lossless, Smart or Ultra; convert to WebP, AVIF, PNG or JPG, or let Auto pick the smallest; resize by pixels or percentage; fit each file under a size in KB, made smaller in pixels when quality alone can't get it there; keep or strip EXIF; compare a result with its original as a slider, side by side, or as a pixel difference map with its PSNR; compress a result again with different settings from its own copy of the original; rename results, one at a time or numbered in a batch, before downloading them singly or as a zip; on a paid plan, upload a whole folder, or a zip that the browser opens and uploads image by image, and get the zip back in the same folders, and get each image at several widths (480, 768, 1200 and 1600 pixels by default, never enlarged) with an <img srcset> to paste; share a result on a public page at an unguessable link, where anyone can see the optimized copy, compare it with the original where a browser can draw it, download either, or compress the original again with their own settings, until the link is switched off; AI alt text, on by default, writes a one-sentence description and suggests a file name for each image in one of 23 languages (Anthropic's Claude, from a small copy of the image), to copy or apply to the download.
- [Page optimization](https://www.iminify.com/scan): enter a page URL; the scanner opens the page in a browser on our servers, collects every image the page loads, compresses them all and hands back one zip that keeps each image in the folders of its address, with a manifest.csv mapping each image address it fetched to its file. Each scan also reports how the page shows its images: oversized files (more than twice the size they are shown at), images without width and height, lazy loading in the first screen or missing below it, missing alt text (with an AI alt text suggested for each image shown without one, on by default), and the largest contentful paint, for every image address on the page. On a paid plan the report can be shared at a public link (read only, with thumbnails of the compressed images, kept out of search and paused while the account is not on a paid plan) and downloaded as a CSV of every image or a PDF. On a paid plan, a site crawl takes a sitemap or a list of pages on one site, scans each page the same way, compresses an image the pages share once, and gives one report for the whole site and one zip with a folder and a manifest for each page; and a crawled site can be checked every week: Iminify crawls it again, compresses only the images that are new or changed, and emails a link to a zip of them.
- [Pricing](https://www.iminify.com/pricing): the guest, free, Pro and Max plans side by side, how the paid plans are paid for, and the billing questions.
- [AI agents](https://www.iminify.com/ai-agents): the MCP server that lets Claude, ChatGPT, Cursor and other AI apps compress, convert and resize images and optimize pages on an Iminify account, which apps connect, and what it costs.
- [Blog](https://www.iminify.com/blog): notes on image compression, formats and page speed from Mozex, who runs the tool. Append .md to a post address, or ask for text/markdown, for the post as plain markdown.
- [Terms of service](https://www.iminify.com/terms-of-service)
- [Privacy policy](https://www.iminify.com/privacy-policy)

## Tools

Each page below opens the image tool already set up for one job. Any of them, and the home page, also takes `?format=` (webp, avif, png, jpg or auto), `?level=` (lossless, smart, ultra or none) and `?target=` (a file size in KB to fit each image under) to open on those settings, for example https://www.iminify.com?format=avif&level=ultra or https://www.iminify.com?target=150.

- [JPG to AVIF](https://www.iminify.com/jpg-to-avif): The smallest file a photo can get in a current browser.
- [PNG to AVIF](https://www.iminify.com/png-to-avif): Big savings on screenshots and graphics, with transparency kept.
- [HEIC to JPG](https://www.iminify.com/heic-to-jpg): iPhone photos as JPGs that open anywhere, the right way up.
- [PNG to WebP](https://www.iminify.com/png-to-webp): Lossless or lossy, transparency kept, every browser supports it.
- [JPG to WebP](https://www.iminify.com/jpg-to-webp): Smaller photos for the web, with the exceptions shown honestly.
- [TIFF to JPG](https://www.iminify.com/tiff-to-jpg): Scans and exports as JPGs a fraction of the size.
- [WebP to JPG](https://www.iminify.com/webp-to-jpg): For the image you saved from the web that nothing will open.
- [GIF to WebP](https://www.iminify.com/gif-to-webp): Animated GIFs as animated WebP: every frame, far fewer bytes.
- [Compress PNG](https://www.iminify.com/compress-png): Smaller PNGs that stay PNGs, transparency and all.
- [Compress JPEG](https://www.iminify.com/compress-jpeg): Lossless repacking, or a quality measured for each photo.
- [Compress WebP](https://www.iminify.com/compress-webp): Re-encode oversized WebP files, with the caveats stated.
- [Compress Nano Banana](https://www.iminify.com/compress-nano-banana-image): Gemini's API saves at JPEG quality 100. See what its files shrink to.
- [Compress to 20 KB](https://www.iminify.com/compress-image-to-20kb): A photo or a signature small enough for a strict form.
- [Compress to 50 KB](https://www.iminify.com/compress-image-to-50kb): ID and profile photos under the most common middle limit.
- [Compress to 100 KB](https://www.iminify.com/compress-image-to-100kb): The limit job sites, visa forms and inboxes ask for most.
- [Compress to 200 KB](https://www.iminify.com/compress-image-to-200kb): A full-size web photo under a page weight budget.
- [TinyPNG alternative](https://www.iminify.com/tinypng-alternative): Limits, formats and file retention, side by side.
- [iLoveIMG alternative](https://www.iminify.com/iloveimg-alternative): A focused compressor next to a broad image toolkit.

## API

Everything the website does is also a JSON API at https://www.iminify.com/api/v1, for any account with a verified email address, on the same daily and per-minute allowances as the website: compress, convert and resize an image, or fit it under a size in KB, sent as a file or fetched from a URL (with an AI alt text and a suggested file name, on by default), poll it, download it or a zip of several (on a paid plan, each in the folder it was sent with), have it made at several widths with an <img srcset> (paid plans), rename, share, recompress, retry, cancel or delete it, ask for its alt text later or in another language, send one image in an upload group and get every size and format a site keeps of it made from it (cropped as WordPress crops), counted as one image and a file per output against a daily allowance of files (https://www.iminify.com/docs/upload-groups), scan a page for every image it loads, share its page report or download it as CSV or PDF (paid plans), crawl several pages of one site from its sitemap or a list, with one report and one zip for the whole site (paid plans), have a crawled site checked every week, compressing only its new or changed images (paid plans), and read the plan and usage. An account on Pro or Max can also have each image and scan that finishes or fails sent to its own server as a signed webhook, set up in Settings > Webhooks (https://www.iminify.com/docs/webhooks). The Iminify GitHub Action (https://github.com/mozex/iminify-action, open source) compresses the PNG, JPG, WebP and GIF files a pull request adds or changes through the API, with a token kept as a repository secret, commits the smaller files to the pull request's branch and comments with the savings (https://www.iminify.com/docs/github-action). Requests carry a personal access token from Settings > API Tokens as a Bearer token. The OpenAPI 3.1 description, with code samples in cURL, Python, PHP and JavaScript, is at https://www.iminify.com/api/v1/openapi.json.

- [Iminify API](https://www.iminify.com/docs): Compress, convert and resize images over HTTP with the Iminify API. Upload a file or send a URL, poll the result, download it. Samples in cURL, Python, PHP and JavaScript.
- [API authentication](https://www.iminify.com/docs/authentication): How to create an Iminify API key, send it as a Bearer token, keep it safe and replace it, and which accounts can use the API.
- [API compression settings](https://www.iminify.com/docs/compression-settings): The levels, formats, resize options and metadata switch the Iminify API takes, what each one does to an image, and requests for common jobs.
- [API rate limits and quotas](https://www.iminify.com/docs/limits): Requests a minute, compressions a minute, images and page scans a day, file size and batch size for each Iminify plan, and how to handle a 429.
- [API errors](https://www.iminify.com/docs/errors): Every error the Iminify API answers with: the JSON shape, the HTTP status, each error code and what to do about it.
- [API webhooks](https://www.iminify.com/docs/webhooks): Get a signed request on your own server when an Iminify image or page scan finishes: the events, the body, checking the signature, and retries.
- [Iminify MCP server](https://www.iminify.com/docs/mcp): Connect Claude, ChatGPT, Cursor or VS Code to Iminify's MCP server and let an AI agent compress, convert and resize images and scan pages for you.
- [Iminify GitHub Action](https://www.iminify.com/docs/github-action): Compress the images a pull request adds with the Iminify GitHub Action: it commits the smaller files to the branch and comments with what each one saved.
- [Iminify PHP client](https://www.iminify.com/docs/php): Compress images from PHP with the open source Iminify client, with typed errors, a fake for your tests and an optimizer for Spatie's image packages.
- [Iminify for Laravel](https://www.iminify.com/docs/laravel): Optimize Media Library conversions and uploads through Iminify in a Laravel app, with a facade, a fake for your tests and a webhook route.
- [Images API](https://www.iminify.com/docs/images): Compress an image from a file or a URL, poll it, download it, rename it, share it, run it again or delete it. Every images endpoint with samples.
- [Upload groups API](https://www.iminify.com/docs/upload-groups): Send one image and get every size and format your site keeps made from it, counted as one image. Open a group, send its source, poll it and download the files.
- [Page scans API](https://www.iminify.com/docs/page-scans): Scan a web page for every image it loads, compress them all, and download them as one zip. Every page scans endpoint with samples.
- [Site crawls API](https://www.iminify.com/docs/site-crawls): Crawl several pages of one site at once, from its sitemap or a list, with one report and one zip for the whole site. Every site crawls endpoint with samples.
- [Weekly site checks API](https://www.iminify.com/docs/site-checks): Have a crawled site crawled again every week, compressing only its new or changed images, with an email and a zip when a check finds some. Every weekly site checks endpoint with samples.
- [Account API](https://www.iminify.com/docs/account): Read your Iminify plan, its limits and how much of the day's images and page scans are used, from the account endpoint.

## MCP server

AI agents (Claude, ChatGPT, Cursor, VS Code and any client that speaks MCP over streamable HTTP) can use Iminify through its MCP server at https://www.iminify.com/mcp, signing in with OAuth or sending an API key as a Bearer token. Its tools compress, convert and resize images, or fit them under a size in KB, or on a paid plan make them at several widths with an <img srcset>, from URLs, one-time upload links or small inline files, each with an AI alt text and a suggested file name, write the alt text of an image that has none, scan a page for every image it loads, share the page report of a scan or hand it over as CSV or PDF (paid plans), crawl several pages of one site at once and have one checked every week (paid plans), answer each result with signed download links, and rename, share or delete results, on the same allowances as the website and the API. What it does: https://www.iminify.com/ai-agents. Setup for each client: https://www.iminify.com/docs/mcp.

In Claude (Chat and Cowork, on web, desktop and mobile), Iminify is listed in the Connectors Directory, and one connection covers both: https://claude.ai/directory/iminify.

The server alone handles local files wherever the agent runs commands next to them (Claude Code, Cursor, Claude in Cowork with a folder connected). The optional Iminify plugin (https://github.com/mozex/iminify-plugin, open source) packs the server with three skills: optimize-images finds the images in a project or a folder, compresses them through upload links and writes the smaller files back in place; image-seo writes alt text for the images a project's pages show without any and gives files descriptive names, with the user's approval; fix-core-web-vitals scans a published page, reads its image report and fixes the images behind its largest contentful paint and layout shift in the project (priority, lazy loading, width and height, files larger than their space). It is in Anthropic's plugin directory: install it in Claude Code with /plugin install iminify@anthropic-plugin-directory (or by hand from GitHub with /plugin marketplace add mozex/iminify-plugin, then /plugin install iminify@iminify); in Claude, it is in the plugin directory under Customize, Plugins, where one install covers Chat and Cowork and includes the connector; with both installed, Claude shows one set of tools, since they share one address.

## Blog posts

- [Does compressing an image change what Gemini reads? Full-colour JPEG quality 95 to 40 didn't, shrinking to 600 pixels did](https://www.iminify.com/blog/37-does-compressing-an-image-change-what-gemini-reads-full-colour-jpeg-quality-95-to-40-didnt-shrinking-to-600-pixels-did): Gemini 3.8 Flash read two text sheets the same at full-colour JPEG quality 95 and 40; shrinking them to 600 pixels wide cost about 15 of 192 fields.
- [Background remover PNG too big? One cutout went from almost 7 MB to 356 KB as WebP](https://www.iminify.com/blog/36-background-remover-png-too-big-one-cutout-went-from-almost-7-mb-to-356-kb-as-webp): remove.bg's 6,731,926-byte sample cutout became a 356,282-byte WebP at Iminify's default level, transparency unchanged. WebP, AVIF and PNG measured.
- [Does Wix compress images? Yes, and on JPG images its AVIF is a median 16 percent smaller than its WebP, not 50](https://www.iminify.com/blog/35-does-wix-compress-images-yes-and-on-jpg-images-its-avif-is-a-median-16-percent-smaller-than-its-webp-not-50): Does Wix compress images? Yes: on JPG images Chrome's AVIF was a median 3.1% of the media file, and Wix's AVIF a median 16.4% smaller than its WebP, not 50%.
- [How many pixels does an AI print need? 300 per inch, and at 16x20 our PNG is over Etsy's download limit](https://www.iminify.com/blog/34-how-many-pixels-does-an-ai-print-need-300-per-inch-and-at-16x20-our-png-is-over-etsys-download-limit): AI print size in pixels at 300 DPI: what 4096 px Gemini and 2048 px Midjourney images cover, four shops' file limits, and PNG vs JPEG sizes.
- [Convert your existing WordPress images to WebP without a plugin: what regenerate breaks](https://www.iminify.com/blog/33-convert-your-existing-wordpress-images-to-webp-without-a-plugin-what-regenerate-breaks): Convert existing WordPress images to WebP with a filter and wp media regenerate. On WordPress 7.1.4 we found what the default run breaks, and how to avoid it.
- [Next.js static export images: the default loader breaks them and unoptimized ships the original](https://www.iminify.com/blog/32-nextjs-static-export-images-the-default-loader-breaks-them-and-unoptimized-ships-the-original): Next.js static export image optimization, measured in Chrome: unoptimized sent a phone 2.4 MB for five photos and 55.2 MB for five 4K files. Fixes compared.
- [Should you compress images before your CDN re-encodes them? Measured through Next.js, wsrv.nl and Photon](https://www.iminify.com/blog/31-should-you-compress-images-before-your-cdn-re-encodes-them-measured-through-nextjs-wsrvnl-and-photon): Compress images first, or let the CDN? In our Next.js test a lossless repack changed nothing and a lower quality beat a lossy first pass at no more bytes.
- [Why does a transparent PNG turn black as a JPG? The colour hiding underneath](https://www.iminify.com/blog/30-why-does-a-transparent-png-turn-black-as-a-jpg-the-colour-hiding-underneath): Converting a transparent PNG to JPG fills its see-through pixels with black, white or the colour stored under them. We tested five converters.
- [Does compression remove the AI tag Merchant Center asks for? 10 tools, WordPress and Iminify tested](https://www.iminify.com/blog/29-does-compression-remove-the-ai-tag-merchant-center-asks-for-10-tools-wordpress-and-iminify-tested): Four of ten tools keep the IPTC AI tag Merchant Center asks for by default; Iminify drops it when it compresses. One ExifTool command restores it.
- [Why is my WebP bigger than the JPG? Measured on 40 JPEGs and 4 PNGs](https://www.iminify.com/blog/28-why-is-my-webp-bigger-than-the-jpg-measured-on-40-jpegs-and-4-pngs): In our tests a WebP made from a JPEG saved at 80 was bigger from about quality 90 up, and scored lower. Where it flips, why, and which file to keep.
- [Do AI images hurt SEO? What Google's pages say, and what a 2K Gemini picture did to a page](https://www.iminify.com/blog/27-do-ai-images-hurt-seo-what-googles-pages-say-and-what-a-2k-gemini-picture-did-to-a-page): Do AI images hurt SEO? Google's pages we read don't mark AI images down. A 2K Gemini file took 20.3 s in Lighthouse mobile, 1.4 s resized and compressed.
- [What image quality does Next.js ship? WebP 75, AVIF 47 if you list it, and by default a 90 becomes 75](https://www.iminify.com/blog/26-what-image-quality-does-nextjs-ship-webp-75-avif-47-if-you-list-it-and-by-default-a-90-becomes-75): In next/image, quality 75 is WebP 75, or AVIF 47 if you list it. A 90 is served as 75 unless listed. Bytes and scores for 864 images on Next 16.4.3.
- [Why is red text blurry in JPG and WebP? Chroma subsampling, measured](https://www.iminify.com/blog/25-why-is-red-text-blurry-in-jpg-and-webp-chroma-subsampling-measured): Red text goes dull in JPG, WebP and AVIF when colour is stored at a quarter of the detail. Seven images, six settings: what 4:4:4 and sharp_yuv cost.
- [How much does lossless JPEG compression save? 25 files, every pixel checked](https://www.iminify.com/blog/24-how-much-does-lossless-jpeg-compression-save-25-files-every-pixel-checked): Lossless JPEG compression saved 0 to 16.3 percent on 25 JPEGs (9.5 percent in total) with every pixel unchanged. Progressive scans were the biggest step.
- [Can ChatGPT read HEIC? What five AI tools list, and what three APIs did with an iPhone photo](https://www.iminify.com/blog/23-can-chatgpt-read-heic-what-five-ai-tools-list-and-what-three-apis-did-with-an-iphone-photo): ChatGPT's and Claude's format lists leave out HEIC; Gemini's API image page and Grok's FAQ name it. What three AI APIs did with an iPhone HEIC, and the fix.
- [Does Squarespace compress images? What it sent Chrome for 621 images](https://www.iminify.com/blog/22-does-squarespace-compress-images-what-it-sent-chrome-for-621-images): Squarespace compresses images: resized JPEGs at quality 85, WebP to Chrome on 84 of 85 sites, none over 2,500 px, PNG photos sent to Chrome lossless.
- [Why is my JPG file so large? What 11 real JPEGs are made of](https://www.iminify.com/blog/21-why-is-my-jpg-file-so-large-what-11-real-jpegs-are-made-of): JPG too large? In 11 real JPEGs the picture was 89.7 to 99.9% of every file and nothing else in them passed 729 KB. A lower quality setting shrank all 11.
- [Does compression remove Content Credentials? Two signed Gemini images through 13 tools](https://www.iminify.com/blog/19-does-compression-remove-content-credentials-two-signed-gemini-images-through-13-tools): Compressing broke C2PA Content Credentials in our c2patool tests: every file 13 tools changed lost the manifest or kept an invalid copy.
- [Why is my GIF so big? What each fix did to four real GIFs](https://www.iminify.com/blog/13-why-is-my-gif-so-big-what-each-fix-did-to-four-real-gifs): A GIF stores every frame losslessly in at most 256 colours, which is why it gets so big. We measured the usual fixes on four: WebP cut a 555 KB GIF to 154 KB.
- [Stop your iPhone saving HEIC, and convert the photos you already have](https://www.iminify.com/blog/12-stop-your-iphone-saving-heic-and-convert-the-photos-you-already-have): Turn off HEIC on iPhone: Settings > Camera > Formats > Most Compatible. In our table, three iPhone photos came out 24% smaller to 61% bigger as JPGs.
- [Image too large to upload? Each fix, measured on a phone photo](https://www.iminify.com/blog/11-image-too-large-to-upload-each-fix-measured-on-a-phone-photo): A 6.5 MB phone photo too large to upload: halving its width and height gave 1.33 MB at quality 90; at full size, getting under 2 MB took quality 61.
- [Does WordPress compress images? What WordPress 7.1 does to your upload](https://www.iminify.com/blog/10-does-wordpress-compress-images-what-wordpress-71-does-to-your-upload): WordPress 7.1 doesn't compress your upload: it stores it byte for byte and re-encodes the resized copies. A 2x screen can still download the original.
- [ComfyUI PNG to JPG loses the workflow. WebP and AVIF can keep it](https://www.iminify.com/blog/20-comfyui-png-to-jpg-loses-the-workflow-webp-and-avif-can-keep-it): ComfyUI's own loader can't read a workflow from a JPG. A WebP or AVIF with it in EXIF can, at about a tenth of the PNG's size. Ten example images, tested.
- [How to find large images on a website: three tools gave us three different lists](https://www.iminify.com/blog/9-how-to-find-large-images-on-a-website-three-tools-gave-us-three-different-lists): To find a page's large images, scroll to the bottom and sort Chrome's Network panel by size. Lighthouse's phone run missed a real page's two heaviest.
- [Does a JPEG lose quality every time you save it? We saved five photos 100 times](https://www.iminify.com/blog/18-does-a-jpeg-lose-quality-every-time-you-save-it-we-saved-five-photos-100-times): Does re-saving a JPEG lose quality? At the same setting, no later save cost as much as the first, but one-pixel crops kept costing. 100 saves, measured.
- [Improve image delivery in Lighthouse: what it replaced and how it counts savings](https://www.iminify.com/blog/8-improve-image-delivery-in-lighthouse-what-it-replaced-and-how-it-counts-savings): Lighthouse's "Improve image delivery" replaced four audits, "Serve images in next-gen formats" among them. Its savings are arithmetic on bytes and pixels.
- [How many tokens is an image? Claude, GPT and Gemini, measured on seven real files](https://www.iminify.com/blog/17-how-many-tokens-is-an-image-claude-gpt-and-gemini-measured-on-seven-real-files): GPT-5.6 at default detail counts a 12.5 MP photo at 14,746 tokens, Claude Opus 5.5 at 4,743 and Gemini 3.8 Flash at 1,102, each on the vendor's own counter.
- [Why is my PNG file so large? Four causes, measured](https://www.iminify.com/blog/7-why-is-my-png-file-so-large-four-causes-measured): In our tests a photo as PNG was 5.7 to 9.3 times its JPEG at quality 90. Extra pixels, 16-bit colour and light compression add size too. The fix for each.
- [Image exceeds 5 MB maximum? Claude counts the base64, not your file](https://www.iminify.com/blog/16-image-exceeds-5-mb-maximum-claude-counts-the-base64-not-your-file): Claude's 5 MB image limit on Bedrock counts base64, so a 4,309,090-byte JPEG is too big. Six files measured against each image limit, and the fixes.
- [How big is a Nano Banana image? 52 files measured, from 512 px to 4K](https://www.iminify.com/blog/15-how-big-is-a-nano-banana-image-52-files-measured-from-512-px-to-4k): Nano Banana image size, measured on 52 API images: a detailed picture from Nano Banana 2 or Pro is about 1 MB at 1K and 10.45 to 12.13 MB at 4K, as a JPEG.
- [Does converting PNG to WebP lose quality? Five files, every pixel checked](https://www.iminify.com/blog/6-does-converting-png-to-webp-lose-quality-five-files-every-pixel-checked): Lossless WebP kept every 8-bit pixel of five PNG files and made them 28.6% to 77.3% smaller. What quality 100, a JPG and the compress-PNG button really cost.
- [Why do images save as WebP? What 12 sites sent Chrome, and how to get the JPG](https://www.iminify.com/blog/14-why-do-images-save-as-webp-what-12-sites-sent-chrome-and-how-to-get-the-jpg): Why do images save as WebP? Many sites pick the format from a line your browser sends. We tested 12: 9 sent WebP or AVIF, and all 9 gave us a JPEG.
- [AVIF vs WebP file size: ten images, one quality score, and where WebP still wins](https://www.iminify.com/blog/5-avif-vs-webp-file-size-ten-images-one-quality-score-and-where-webp-still-wins): AVIF vs WebP file size on ten images at one quality score: AVIF a third smaller, WebP ahead on lossless and, alpha matched, on our one transparent image.
- [JPEG 80 is not WebP 80: what quality means in four encoders](https://www.iminify.com/blog/2-jpeg-80-is-not-webp-80-what-quality-means-in-four-encoders): WebP quality 80 isn't JPEG quality 80. Matching mozjpeg at 80 on six photographs took a median of cwebp 87.5, jpegli 83.5 and avifenc 72.
- [SSIMULACRA 2 scores in practice: what 50, 70 and 90 cost in kilobytes](https://www.iminify.com/blog/1-ssimulacra-2-scores-in-practice-what-50-70-and-90-cost-in-kilobytes): What a SSIMULACRA 2 score costs in kilobytes: an 832 KB photo clears 70 at 311 KB through jpegli, and 90 at 847 KB. Ten public images, three encoders.
- [How many KB should a website image be? Measured at four widths](https://www.iminify.com/blog/3-how-many-kb-should-a-website-image-be-measured-at-four-widths): How big a website image should be in KB: Lighthouse budgets a sixth of a byte per pixel, 10 KB at 300x200, 256 KB at 1536x1024. Ten real images, measured.
- [What AVIF quality setting should you use? The answer changed in March 2026](https://www.iminify.com/blog/4-what-avif-quality-setting-should-you-use-the-answer-changed-in-march-2026): Which AVIF quality number to type: libavif 1.4.0 changed what it means, so -q 60 gives one file on Debian 13 and another on 1.4.2. Ten images, measured.

## Limits and storage

- Maximum 16 MB per image without an account, 32 MB with a free account, 90 MB on the paid Pro plan and 90 MB on the paid Max plan, and 64 megapixels on every plan.
- Images a day: 10 without an account, 40 with a free account, 1,000 on Pro and unlimited on Max.
- Page scans a day: none without an account, 3 with a free account at up to 20 images a scan, 50 on Pro at up to 150 images a scan, and unlimited on Max at up to 150 images a scan.
- Site crawls (Pro and Max): 3 a day of up to 10 pages each on Pro, and 10 a day of up to 100 pages each on Max.
- Sites checked weekly (Pro and Max): up to 3 at once on Pro and 25 on Max; on a plan that checks fewer than an account has set up, the oldest keep running and the rest pause; a weekly check counts against no daily site crawls, page scans or images.
- Pro: $36 a year ($3 a month) or $5 month to month, paid by card, PayPal, Apple Pay or Google Pay through Lemon Squeezy.
- Max: $96 a year ($8 a month) or $12 month to month, unlimited, paid the same way.
- Changing plans: a subscriber moves between Pro and Max, or between monthly and yearly, on Lemon Squeezy's own page, opened from the plan page.
- Pro trial: a new account gets 7 days of Pro once its email is verified, and an older account that never had a plan starts it with the trial button on the website, once per person, with no card: 300 images and 300 AI alt texts a day, 10 page scans a day at up to 150 images a scan, 10,000 upload group files a day, one site crawl a day, and the rest of Pro. It then drops to the free plan by itself.
- AI alt texts a day: 10 without an account, 40 with a free account, 1,000 on Pro and 2,000 on Max, where it stops before the images.
- Files a day in the API's upload groups (each output in each format is one file, and the group counts one image): 1,500 with a free account, 30,000 on Pro and unlimited on Max; a group makes at most 30 outputs, each from the one image it sends.
- Each daily count runs for 24 hours from the first image, scan, crawl, alt text or group file it counts, not from midnight.
- Input formats: PNG, JPG, JPEG, WEBP, GIF, HEIC, HEIF, TIFF, TIF. Output formats: WebP, AVIF, PNG, JPG, or Auto.
- Uploaded and optimized files are kept so results stay available; a delete button on each result removes the image and its optimized copy from storage for good. An image or upload group sent through the API as ephemeral is deleted about a day after it finished.

## Support

- Questions and account requests: support@iminify.com.