Switch with a clear plan

New image infrastructure.
Familiar URL parameters.

Keep your image origin. Map the supported transformation contract. Make the change with representative tests and a controlled rollout.

Before · illustrative Imgix URLexample.imgix.net/catalog/shoe.jpg?w=800&fit=clip&q=75
After · illustrative Imgexo URLimgexo.com/shop/catalog/shoe.jpg?w=800&fit=clip&q=75

A practical migration checklist

  1. Inventory URLs and features.

    Collect representative image paths, parameters, signatures and delivery domains. Flag AI, video and unsupported effects before you plan a switch.

  2. 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.

  3. Map the supported parameters.

    Core options include w, h, fit, crop, q, fm, auto and dpr. Focal-point, background and implemented effects have explicit limits. Unknown transform parameters are rejected.

  4. Review signing separately.

    An Imgix s signature does not authorize an Imgexo request. For signed-only sources, generate Imgexo HMAC URLs server-side using the source’s current signing configuration.

  5. 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.

  6. 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.

Big on images.
Light on everything else.

Let’s build a simpler image pipeline for your next million requests.

Enterprise image optimization. Built for scale.