Image Optimizer — WebP / AVIF / JPEG / PNG Bulk Compress & Resize

Batch convert, resize and compress images to WebP, AVIF, JPEG or PNG — strip metadata, shrink file size, and drop the results straight into your pipeline.

What it does

Give it a list of image URLs and a target format. For every image it fetches the file, converts it to your chosen format, optionally resizes it down to a max width/height, compresses it at your chosen quality, and (by default) strips EXIF/IPTC/XMP metadata. Each optimized file is saved to storage with a direct download link, and you get a dataset row showing the original size, new size and percentage saved.

• Four formats — WebP, AVIF, JPEG, PNG.
• Smart resize — cap width and/or height without upscaling or distorting.
• Quality control — one dial from 1 (smallest) to 100 (best).
• Metadata stripping — remove GPS, camera and author data for smaller, more private files.
• Bulk — hundreds of images in one run.

Use cases

• The image step in your pipeline — the compress-and-convert stage in an n8n, Make or Zapier workflow. Feed in URLs, get back optimized files and a savings report.
• TinyPNG-style batch optimization — shrink a whole folder of images at once for the web, without an upload UI.
• Web performance — serve modern WebP/AVIF to cut page weight and speed up load times.
• CMS & e-commerce — normalise product and blog images to one format and size.
• Privacy — strip location and camera metadata before publishing user uploads.

Input

{
  "imageUrls": [
    "https://example.com/photo-1.jpg",
    "https://example.com/photo-2.png"
  ],
  "format": "webp",
  "quality": 80,
  "maxWidth": 1600,
  "maxHeight": 0,
  "stripMetadata": true
}

Field	Type	Description
imageUrls	array	Direct image URLs to optimize.
format	string	webp, avif, jpeg or png. Default webp.
quality	integer	Compression quality 1–100. Default 80.
maxWidth	integer	Max width in px; 0 keeps original.
maxHeight	integer	Max height in px; 0 keeps original.
stripMetadata	boolean	Remove EXIF/IPTC/XMP metadata. Default true.

Output

Each image produces one dataset row, and the optimized file is saved with a direct link (resultUrl).

{
  "url": "https://example.com/photo-1.jpg",
  "format": "webp",
  "origBytes": 482113,
  "newBytes": 91544,
  "savedPct": 81,
  "width": 1600,
  "height": 1067,
  "resultUrl": "https://api.apify.com/v2/key-value-stores/xxxx/records/img-0001.webp",
  "ok": true
}

Output schema

Field	Type	Description
url	string	The source image URL.
format	string	Output format.
origBytes	integer	Original file size in bytes.
newBytes	integer	Optimized file size in bytes.
savedPct	number	Percentage of size saved.
width	integer	Output width in px.
height	integer	Output height in px.
resultUrl	string	Direct link to the optimized file.
ok	boolean	Whether the image was optimized successfully.

FAQ

Which format should I use? WebP is the best all-round choice for the web. AVIF compresses even smaller but encodes slower. JPEG and PNG maximise compatibility with older tools.

Does resizing upscale small images? No — images are only ever scaled down to fit your limits, never enlarged, and aspect ratio is preserved.

What if one URL is broken? That image is skipped with ok: false and an error field; the rest of the run continues.

Can I automate it? Yes — via integrations on the Apify platform (n8n, Make, Zapier and more) and the Apify API.

Notes

Original clean-room implementation.