A practical migration checklist
- Inventory URLs and features.
Collect representative image paths, parameters, signatures and delivery domains. Flag AI, video and unsupported effects before you plan a switch.
- Connect your existing origin.
Create an Imgexo source with the approved HTTPS base URL. Test a real relative image path. Confirm origin authentication and source limits.
- Map the supported parameters.
Core options include
w,h,fit,crop,q,fm,autoanddpr. Focal-point, background and implemented effects have explicit limits. Unknown transform parameters are rejected. - Review signing separately.
An Imgix
ssignature does not authorize an Imgexo request. For signed-only sources, generate Imgexo HMAC URLs server-side using the source’s current signing configuration. - Validate images and cache behavior.
Compare dimensions, crop position, format, transparency and visual quality. Different encoders do not guarantee identical bytes. Test both cold and warm requests.
- Roll out with a fallback.
Switch a small cohort, watch errors and delivery costs, then expand. Retain the old URL builder until representative production traffic has been validated.
Choose the right URL shape
Use the shared imgexo.com/{source-slug}/{path} route, configure a verified custom subdomain, or set up a fixed first-party proxy path on your own server. DNS alone cannot proxy a path. Existing *.imgix.net hostnames remain under Imgix control.