All image tools: compress, resize, convert, and crop

Compress, resize, or convert: which image tool

Do not collect tools. Collect outcomes. If the page is heavy, start at compress image. If the layout is a 640-pixel column and the file is a 24-megapixel export, resize first - compression cannot invent a correct width. If the CMS still serves JPEG everywhere, convert a WebP or AVIF sibling and keep JPEG as the last source in a picture tag.

Marketers usually need a size a platform already defined. That is the marketer lane: social presets, watermarks, favicons, palettes, borders for catalogs, blur for a background plate. Developers usually need facts and markup. That is the developer lane: inspector, metadata strip, Base64 for the tiny stuff, srcset from a real master.

Order to prepare images for a website

1. Inspect type, pixels, and weight.
2. Crop extra background, then resize to the largest size you will serve.
3. Compress or convert to WebP. Keep JPEG for Open Graph.
4. Remove EXIF on phone photos that will be public.
5. Copy a picture tag if the template needs more than one width.

Image tools API (JSON catalog)

There is a catalog at /api/tools if you want to list these URLs from a script. It is the same list as this page. Filter with ?audience=marketers, developers, or most-used. Image bytes never go to that endpoint.

fetch('/api/tools?audience=developers')
  .then((res) => res.json())
  .then((data) => {
    data.tools.forEach((tool) => {
      console.log(tool.name, tool.url);
    });
  });

What we will not add just to look complete

A fake "AI upscaler" that hallucinates jewelry on a product. A background remover that ships your photo to a model you did not choose. A meme generator. Those products exist. They are not how you make a homepage faster or a feed crop less embarrassing. If a tool does not help an image survive the web, it does not belong in this toolkit.