Image Resizer API

🖼️ Image resizer API for batch image resizing

Image Resizer API resizes, compresses, and converts images from URLs, base64 data, or Apify key-value-store uploads. Use it when you need repeatable image processing for product photos, thumbnails, social assets, WhatsApp catalog images, or an API workflow that returns generated file URLs plus measured image facts.

• image resizer - resize batches of source images to custom dimensions or preset sizes.
• compress image - lower file sizes for JPEG, WebP, and AVIF outputs with quality and size-limit controls.
• resize image online - run image resizing from Apify Console, API calls, schedules, or integrations.
• image resizer free - test the shape with a small batch before adding larger image lists.
• resize image to 100kb - set an optional file-size target and check whether each generated file fits it.

✅ What this Actor does

• Accepts image URLs, base64 image data, and Apify key-value-store file keys.
• Saves one dataset row per successfully generated image.
• Saves generated files to Apify key-value storage and returns direct output.url links.
• Supports custom width and height up to 10000 pixels.
• Supports presets for e-commerce squares, website thumbnails, social squares, and WhatsApp carousel, catalog, and template images.
• Supports cover, contain, fill, inside, and outside resize behavior.
• Supports center, edge, and corner crop positions.
• Supports solid, blurred, and edge-extended padding for contained layouts.
• Converts images to WebP, JPEG, PNG, AVIF, GIF, TIFF, or the source format when supported.
• Strips metadata by default, with an option to preserve it.
• Skips failed image attempts from the dataset and keeps processing the rest of the batch when possible.

This Actor is a mechanical image processor. It does not generate new images with AI, add watermarks, discover images from web pages, edit private files, or require a third-party image-processing API key.

📦 Data you can export

Each output row represents one successfully generated image. Fields include:

• id - your optional image ID for matching output rows to input images.
• source - the submitted source type, URL, key-value-store key, and filename when available.
• original - source width, height, format, content type, and byte size.
• output - generated file URL, key, width, height, format, content type, and byte size.
• compressionRatio - byte-size reduction from source to output when it can be calculated.
• metadataPreserved - whether EXIF and other metadata were kept.
• fileSizeLimitMb - the applied size limit when you request one or use a preset with a limit.
• fileSizeWithinLimit - whether the generated file fits the applied size limit.

Open the dataset for rows you can export as JSON, CSV, Excel, XML, RSS, or HTML. Open the key-value store when you want to browse or download the generated image files directly.

🚀 How to run

1. Add one or more image sources in Images.
2. Choose Target size, or leave it on Custom size and set Custom width and Custom height.
3. Pick Resize fit, Padding style, and Output format.
4. Set Quality or Maximum file size when you need smaller output files.
5. Start the Actor.
6. Open the dataset for output rows, or open the key-value store for generated files.

For a quick first run, keep the prefilled sample image, leave Target size on Custom size, and use the default WebP output.

⚙️ Input

{
	"images": [
		{
			"url": "https://placehold.co/1200x800.jpg",
			"id": "sample-image"
		}
	],
	"targetPreset": "website_thumbnail",
	"fit": "contain",
	"paddingMode": "edge_extend",
	"outputFormat": "webp",
	"quality": 80
}

Use url for public HTTP or HTTPS image files, base64 for image bytes, or keyValueStoreKey for an uploaded image in the run key-value store. Add id or filename when you want stable matching in the output.

Enable combineImages only when you provide 2 or 3 source images and want one combined output image.

📄 Output example

{
	"id": "sample-image",
	"source": {
		"type": "url",
		"url": "https://placehold.co/1200x800.jpg",
		"keyValueStoreKey": null,
		"filename": "1200x800.jpg"
	},
	"original": {
		"width": 1200,
		"height": 800,
		"format": "jpeg",
		"contentType": "image/jpeg",
		"sizeBytes": 384212
	},
	"output": {
		"url": "https://api.apify.com/v2/key-value-stores/abc123/records/sample-image-website_thumbnail.webp",
		"key": "sample-image-website_thumbnail.webp",
		"width": 800,
		"height": 800,
		"format": "webp",
		"contentType": "image/webp",
		"sizeBytes": 72104
	},
	"compressionRatio": 0.8124,
	"metadataPreserved": false,
	"fileSizeLimitMb": null,
	"fileSizeWithinLimit": null
}

💳 Pricing

This Actor uses pay-per-event pricing. You are charged for each image that is successfully processed and saved with a downloadable output URL.

The local pricing event is image-processed at $0.0009 per successful processed image. Failed image attempts, skipped inputs, invalid image sources, and runs that do not save generated images do not create processed-image events.

🔌 Integrations

• Call the Actor through the Apify API when your app needs repeatable image resizing from URLs, base64 data, or uploaded files.
• Schedule recurring runs for product catalogs, campaign assets, or image batches that need the same output settings.
• Export dataset rows to JSON, CSV, Excel, XML, RSS, or HTML for review and reporting.
• Use webhooks to send generated output URLs and metadata to downstream storage, CMS, or automation tools.

❓ FAQ

Can I use this as an image resize API for many images?

Yes. Add up to 100 image sources in one run. Each successful image creates one generated file and one dataset row.

Can it compress image files as well as resize them?

Yes. Use JPEG, WebP, or AVIF output with the quality setting, and optionally set maxFileSizeMb. The output row reports the byte sizes, compression ratio, and file-size-limit result.

Can I resize image online without hosting files myself?

Yes. You can paste public image URLs, pass base64 image data, or upload images to Apify key-value storage and pass their keys. Generated files are saved in the run key-value store.

How does it compare with image resize API and cloud image processing API options?

It covers the common API workflow: submit image sources and settings, then read generated file URLs and metadata from Apify storage and the dataset. It does not require an external cloud image-processing account or API key.

Why not use the image source API?

Most image sources do not offer a single API for resizing, conversion, compression, and Apify dataset exports. This Actor processes the image bytes you provide and returns generated files plus structured metadata in one Apify run.

What are image resizer API alternatives?

Alternatives include hosted image CDNs, command-line tools such as Sharp-based scripts, online resize forms, or custom backend jobs. This Actor is useful when you want Apify runs, API calls, schedules, webhooks, exports, and generated file storage in one workflow.

What happens when one image fails?

The Actor skips that image, logs a warning, and continues with the rest of the batch. Failed images are not saved as dataset rows and are not charged as processed images.

📝 Changelog

• 1.0: Initial release.

🆘 Support

For issues, questions, or feature requests, file a ticket and I'll fix or implement it in less than 24h 🫡

🔗 Other actors

• Watermark Image API ↗ - Add text or logo watermarks to image URLs, uploads, KV files, or base64 data.
• Web Images Scraper ↗ - Extract image URLs and optional saved files from public webpages.
• Unsplash Image Scraper ↗ - Collect Unsplash image search results for design and content research.
• Craiyon AI Image Creator ↗ - Generate prompt-based images and save Apify download links.
• Font Detector ↗ - Detect fonts and font files from public web pages.

Made with ❤️ by Maxime Dupré