FAQ
Does Imagizer cache images?
Yes, both original images and processed images are cached locally on Imagizer. Imagizer supports memory-based and disk-based caching. Caching is controlled by the Cache-Control header or through the Imagizer config.
How quickly can it be deployed?
Imagizer can be deployed and utilized in minutes.
What needs to be done to add Imagizer to an existing solution?
Imagizer supports two approaches to integration. Both approaches require all image requests to be routed through Imagizer. The first approach to integration provides for a global configuration of image compression and image format settings (settings will be applied to all images). This variety of integration is the easiest approach, which does not require changes to the client-side application. The second approach to integration allows for URL parameters which can be attached to image URLs to control image manipulation on an individual level. This type of integration requires modifications to the client-side application but provides fine tuning of the image manipulation, such as setting width and height constraints.
What image formats does Imagizer support?
Imagizer supports all major image formats including JPEG, PNG, GIF, WebP, AVIF, TIFF, and BMP. Imagizer can also automatically convert images to the most efficient format for each browser using the format=auto parameter.
Where can I store my images?
Imagizer works with multiple storage backends:
- Web Folder: Any publicly accessible URL, including your existing website
- Amazon S3: Both public and private buckets are supported
- Imagizer Storage: Free built-in storage backed by Amazon S3
How do I optimize images without changing my URLs?
Use the Default Parameters feature to apply optimization settings globally. You can configure compression, format conversion, and resizing to be applied automatically to all images without modifying any URLs on your website. See the Imagizer Cloud guide for setup instructions.
What is the format=auto parameter?
The format=auto parameter tells Imagizer to automatically select the best image format based on browser support. For example, it will serve WebP to browsers that support it, resulting in smaller file sizes and faster load times without any visible quality loss.
Can Imagizer resize images on the fly?
Yes, Imagizer processes images in real-time. Simply add width or height parameters to your image URL, and Imagizer will resize the image instantly. For example: https://your-source.imagizer.com/image.jpg?width=400
How does intelligent cropping work?
Imagizer can automatically detect faces and important objects in images to ensure they remain in frame when cropping. Use the crop=face parameter to enable face-aware cropping, which is particularly useful for profile photos and product images.
What deployment options are available?
Imagizer offers three deployment options:
- Imagizer Cloud: Fully managed service with pay-as-you-go pricing
- AWS Marketplace: Deploy on your own AWS infrastructure with hourly or monthly billing
- On-Premise: Run Imagizer in your own data center with support for VMware, QEMU, and other virtualization platforms
How do I scale Imagizer for high traffic?
For AWS deployments, use the CloudFormation template which includes auto-scaling, load balancing, and high availability across multiple availability zones. For on-premise deployments, Imagizer supports clustering with Consistent Hashing and Bounded Loads algorithm for distributing requests across multiple instances.
Is there an API for purging cached images?
Yes, you can purge individual images or clear the entire cache using the Admin API or the Imagizer Cloud dashboard. See the Admin API documentation for details on cache purging endpoints.
How do I monitor Imagizer performance?
Imagizer provides detailed statistics through the Admin API, including cache hit rates, request counts, response times, and system metrics. Integration with CloudWatch, Datadog, and Prometheus is also supported. See the Stats Reference for available metrics.
Can I upload images through Imagizer?
Yes, Imagizer supports image uploads to S3 backends and Imagizer Storage. You can also preprocess images during upload to automatically resize or optimize them before storing. See the Uploads Guide for more information.
What happens if my origin server is slow?
Imagizer caches both original and processed images locally. After the first request, subsequent requests are served from cache, eliminating the need to fetch from your origin server. You can also use async requests to pre-warm the cache before users request images.
How do I troubleshoot errors?
Check the Common Errors page for a list of error codes and their causes. For detailed debugging, you can access application logs through the Admin API or generate a debugging report to share with support.
Does Imagizer support HTTPS?
Yes, HTTPS is fully supported. On Imagizer Cloud, HTTPS is enabled by default. For AWS CloudFormation deployments, you can enable HTTPS with either a new certificate or an existing AWS Certificate Manager certificate.
Can I use my own domain name?
Yes, custom domains are supported on all deployment options. For Imagizer Cloud, configure a CNAME record pointing to your Imagizer endpoint. For AWS deployments, you can set up a custom domain through Route 53 during CloudFormation stack creation.