Fastly Image Optimizer

Overview

Fastly Image Optimizer is a cloud service for transforming and delivering images through Fastly’s edge network. It best suits teams running image-heavy sites or apps that need on-demand variants without maintaining a separate stored copy for every size or format.

Its strongest case is configurable processing paired with cached delivery; the trade-off is a request-based meter that makes traffic volume central to the cost decision.

Key features

Image Optimizer can resize, crop or trim, adjust quality, change orientation and convert images when a request arrives. Developers set those choices through query parameters and configuration, rather than creating each variant in advance. That can simplify variant management for teams with many placements, while leaving teams that need fixed, pre-generated assets with less reason to add a request-time processing layer.

Processed images are cached and reused, so later requests can be served with minimal latency. Supported formats are WebP, AVIF, JPEG and PNG. Configurable defaults cover WebP and JPEG quality, resizing filters, upscaling, animated GIF-to-video handling and which file types are processed, giving teams control over common behaviors without making every choice ad hoc.

The service works with existing asset pipelines and CMS platforms, so teams can keep their current image sources. It can be enabled in the Fastly control panel or through the API; Compute SDK access is available through a beta program. Every request sent to Image Optimizer, including one through the SDK, counts as a billable image request, so using a different integration path does not avoid the usage meter.

Fastly says its global edge network is designed for high-throughput image delivery to media sites, ecommerce platforms and SaaS applications. Its stated security and compliance credentials include ISO/IEC 27001:2022 certification, SOC 2 Type 2 audit, audits against key GDPR requirements and relevant HIPAA sections, and PCI DSS Level 1 compliance. Fastly was founded in 2011 and is headquartered in San Francisco.

Pricing

There is a free allowance of 100,000 image requests per month at 0.00 USD per free. It gives smaller projects a way to use the service without an initial paid request tier, but the allowance is a monthly request cap, not an unlimited free plan.

Above that, the listed usage rates are billed per 10,000 Image Requests per month: 0.50 USD for 100,000–10 Million image requests; 0.15 USD for 10 Million–50 Million; 0.07 USD for 50 Million–150 Million; 0.03 USD for 150 Million–500 Million; 0.02 USD for 500 Million–1 Billion; 0.02 USD for 1 Billion–5 Billion; and 0.01 USD for Beyond 5 Billion image requests. These are most relevant to teams able to estimate monthly image-request volume: the per-unit rate falls at larger tiers, while the total bill still depends on the number of billable requests. The listed paid-from amount is 1500 /mo, so buyers should reconcile that figure with the request-volume tiers before budgeting. Pricing is also described as on request.

Platforms

Fastly Image Optimizer supports API, Linux and web environments. It is deployed in the cloud. Teams can deploy through the Fastly CLI, control panel, GitHub Actions, Terraform or APIs; API access is supported. The broader runtime offering names Rust, JavaScript, Go, C++, Python and other WASI-supporting languages, though Compute SDK access for Image Optimizer is in beta.

Who it's for

This is a strong fit for media publishers, ecommerce platforms and SaaS teams serving many image variants, particularly when they want to keep existing sources and let request parameters control output. Caching helps when optimized versions are requested repeatedly. It is less compelling for low-volume projects that do not need dynamic variants or for teams that need predictable costs without tracking request counts.

Pros and cons

• Pro: Request-time resizing, cropping, quality changes and format conversion avoid maintaining a separate pre-generated variant for each use.
• Pro: Cached optimized images are reused, supporting low-latency delivery on repeat requests.
• Pro: Existing asset pipelines and CMS platforms can remain in place, with control through query parameters, configuration or the API.
• Con: Every request, including SDK requests, is billable, so broad use can increase costs with traffic.
• Con: The free allowance stops at 100,000 image requests per month, and the stated paid-from amount of 1500 /mo warrants careful budgeting against the usage tiers.
• Con: Compute SDK access is still in beta, which may not suit teams seeking a fully established SDK workflow.

Alternatives

For teams whose priority is image compression software rather than edge delivery and request-time transformations, compare options in the Image Compression Software category. For broader delivery infrastructure, the CDN Software category is a more relevant starting point.

BunkerWeb is worth considering when a free, self-hosted option is preferable: its open-source plan is 0.00 USD per free under an AGPLv3 license. Wallarm API Security may fit teams looking for API security with a free tier, which allows up to 500,000 requests per month and three users per company, but excludes vulnerability assessment and API Abuse Prevention. Gcore WAAP offers a free tier for one domain and 0.5M requests, plus a Start plan at 25.00 EUR per month for five domains and 1M requests; choose it when those stated domain and request allowances suit the need. Cloudflare WAF is a more relevant comparison for teams shopping for a WAF: its free tier includes one rate-limiting rule, while its Pro plan is 20.00 USD per month, billed annually. F5 BIG-IP APM is another alternative to compare for access management. Oracle Cloud Infrastructure Secret Management, BitNinja and OWASP Coraza WAF are additional options to assess for other infrastructure or security needs.

Verdict

Choose Fastly Image Optimizer if your site or app serves many image variants and you want configurable edge transformations with cached reuse, while keeping your existing asset pipeline. Its key drawback is the billable-request model: the free monthly cap is limited, and higher traffic demands close attention to tier pricing and the stated paid-from amount.