Image tools

Image Compressor

Compress JPEG, PNG, WebP, and AVIF images to 100 KB, 200 KB, 1 MB, or another target size. Drop a file on this page, paste one from the clipboard, or browse for it. The tool shows the savings, then gives you the file or a CDN link you can put in a page. Social apps are strict about weight: WhatsApp wants a small absolute image, and a multi-megabyte PNG is a common reason a link card fails even when the meta tags are correct.

This page compressor is the browser tool. You bring the file. You pick how small it needs to be. You download the result or copy the CDN URL. It is the right step when you already have the artwork and the only problem is the byte size. It is not a substitute for a missing og:image. If the page has no image, or the image is a screenshot of the whole layout, generate a branded OG image first, then compress that file if the platform still rejects the weight.

When to compress, and when to check the tags

Use the compressor when the debugger reports a file that is too heavy, or when you know the destination has a tight cap. Meta's public guidance allows a much larger file than WhatsApp's preview docs. A single export can pass one network and fail another. Open the Open Graph debugger to see the content type, dimensions, and file size of the image a live URL already publishes. If the card is the wrong picture entirely, compressing it will not fix the preview.

Agents can compress a public image URL without this upload form. The MCP connector exposes compress_image. It takes an image URL, not a base64 blob, and returns a CDN URL plus the byte size, dimensions, and quality. Debug, compress, and palette work on a guest connector session. Image generation is separate and needs an account with an active plan. The browser tool on this page and the MCP tool are two ways into the same job: make the file small enough to unfurl.

Related tools

• Extract a color palette when you need hex values and contrast from a logo or photo. That tool stays in the browser.
• Read the API docs when the image itself should be created from a signed request, not only resized.
• Compare OG image APIs if the pipeline is generation plus hosting, not a one-file squeeze.
• WordPress and Carrd still need an image URL that platforms can fetch. Compress it before you paste it into the plugin or the share-image field.

Keep the visual at about 1200 by 630 when the file is an og:image. Shrinking the bytes should not crop away the headline or the logo. After you replace the file, fetch the page again in the debugger. Crawlers cache image bytes by URL, so a new file at the same address can keep showing the old, heavier image until the URL changes or the platform rescrapes it.