How to Tell If a Website Uses imgix

imgix is a popular real-time image-processing CDN that resizes, reformats, compresses and optimises images on the fly and delivers them from the edge. Like other media CDNs it delivers straight from its own URLs, so detecting it is direct: look for assets served from a *.imgix.net domain, usually carrying query-string transformation parameters. This guide covers every reliable signal, the query-string architecture that distinguishes imgix from path-based CDNs, the look-alikes to rule out, and what an imgix integration tells you about the team.

What is imgix?

imgix, founded in 2011, is a developer-focused platform for real-time image processing and delivery. A site connects imgix to wherever its original images live — an Amazon S3 bucket, a Google Cloud Storage bucket, a web folder or another origin — via an imgix "source", and imgix then serves optimised, transformed variants on demand through its global CDN. As with Cloudinary, transformations are driven by the URL, but imgix puts them in the query string: appending ?w=800&auto=format&fit=crop to an image URL produces exactly that variant, cached at the edge. imgix is prized by engineering teams for its clean API, its responsive-image tooling, and its focus on doing one thing — images — extremely well.

For detection, the key context is that imgix is a developer-implemented, performance-focused choice, common in modern web apps, ecommerce, marketplaces and media sites where fast, responsive imagery matters. Its presence signals a technical team that has invested in automated image delivery rather than serving static files. Because media is served from imgix URLs (or a CNAME pointing at imgix), the integration is highly visible in the browser, making it one of the more straightforward technologies to confirm — provided you know to look at the query string.

How imgix delivers media

imgix delivery URLs take the form https://<source>.imgix.net/<path>?<parameters>, where the source subdomain identifies the imgix source connected to the site's origin, and the query-string parameters define the transformation. Characteristic parameters include auto=format,compress (automatically choose the best format and compression for the browser), fit=crop/fit=clip (resize behaviour), w= and h= (dimensions), dpr= (device pixel ratio for retina displays), q= (quality) and many more. Responsive implementations typically generate a srcset of the same image at several widths and dpr values, all on the imgix domain.

The query-string placement is the defining structural trait: where Cloudinary encodes transformations in the path as comma-separated codes, imgix encodes them after the ?. That single difference lets you tell the two apart instantly. Sites that want to mask the imgix host can configure a custom domain (CNAME), so images may load from a brand domain while still carrying the imgix query parameters — which is why those parameters are your most portable signal. Understanding this query-driven model makes every detection step below clear.

How to tell if a website uses imgix

Confirm at least one strong signal (a single asset URL usually suffices).

1. Inspect image sources. Right-click an image and copy its URL, or open the Network tab. A <source>.imgix.net/...?... URL is the definitive signal.

2. Look for query-string transformations. Even on a custom host, image URLs ending in ?auto=format&w=...&fit=...&dpr=... are highly characteristic of imgix.

3. Read the source subdomain. The subdomain in <source>.imgix.net identifies the imgix source configured for the site.

4. Check the Network tab for the host. Filter for imgix. Assets from *.imgix.net confirm the platform; a custom CNAME may need the query-parameter pattern to confirm.

5. View the page source. Search the HTML for imgix.net or imgix; src and srcset attributes frequently reference it directly, and some sites include the imgix.js client library.

What the imgix signals look like

<img src="https://acme.imgix.net/products/widget.jpg?auto=format,compress&w=1200&fit=max">
<img srcset="https://acme.imgix.net/hero.jpg?auto=format&w=400 400w,
             https://acme.imgix.net/hero.jpg?auto=format&w=800 800w" sizes="...">
// Custom domain: https://images.acme.com/hero.jpg?auto=format&fit=crop&w=1200

A *.imgix.net asset URL is conclusive on its own; the query-string transformation parameters confirm imgix even behind a custom host.

imgix versus other media CDNs — avoiding false positives

Match the host and URL pattern to keep image services distinct. imgix uses *.imgix.net with query-string parameters; Cloudinary uses res.cloudinary.com with path-based comma-separated codes; Contentful uses ctfassets.net (its Images API also uses query parameters, but on the ctfassets host); Sanity uses cdn.sanity.io; Shopify uses cdn.shopify.com. The clearest discriminator between the two leading dedicated image CDNs is parameter placement — query string (imgix) versus path (Cloudinary). The main subtlety is custom domains hiding the imgix host; there, the auto=format/fit/dpr query parameters are the reliable signal. A general CDN (Cloudflare, Fastly) delivering images does not impose this transformation-query structure, so do not confuse the two.

How reliable is each imgix signal?

A *.imgix.net asset URL is definitive and reveals the source. The query-string transformation parameters (auto=format, fit, w, dpr, q) are equally strong and survive custom hosting. The source subdomain reliably identifies the configuration. The weakest situation is a site that proxies imgix through a brand domain and uses minimal parameters — uncommon, but there you rely on the query-string pattern and any imgix.js reference. Because images load on essentially every page, a single inspection usually settles it. As a rule, the host or the characteristic query parameters confirm imgix immediately.

What an imgix integration reveals about a site

Finding imgix signals a developer-led, performance-focused team that has invested in real-time image delivery. It skews toward modern web apps, ecommerce, marketplaces and media sites with engineering resources, and its developer-oriented positioning means its users tend to be technically sophisticated. The parameters in evidence refine the read: heavy use of auto=format and responsive srcset indicates a modern, Core-Web-Vitals-conscious implementation. If you sell performance, media, or developer tooling, an imgix site marks a technical team that already values image optimisation and pays for specialised infrastructure. The source subdomain can also reveal the origin storage (some sources are named after S3 buckets), offering a small additional clue about the site's infrastructure.

What finding imgix means for sales, agencies and competitive research

For sales and prospecting, imgix marks a technical, performance-focused team — a fit for developer infrastructure, performance tooling, media services and modern hosting. Its developer-oriented nature suggests an engineering buyer who values clean APIs and measurable performance gains.

For agencies and consultants, finding imgix tells you the client takes image performance seriously, so engagements can focus on advanced responsive imagery, Core Web Vitals, or media-workflow optimisation rather than basics. It signals a technically capable client.

For competitive and market research, imgix adoption indicates a sector that values performance and has engineering depth. Spotting a competitor on imgix tells you they deliver optimised, responsive imagery automatically, useful when benchmarking speed and visual quality.

imgix in the wider stack

imgix usually sits within a modern, performance-conscious engineering stack. It pairs with cloud storage (S3, GCS) as the image origin, a modern framework (React, Next.js, Vue), edge hosting (Vercel, Netlify or a cloud provider), and frequently a broader CDN handling non-image assets. Media and publishing sites may combine it with a headless CMS. For an auditor, the valuable details are the source subdomain (and any origin hints it reveals), whether auto=format and responsive srcset are in use, whether a custom domain is configured, and the surrounding framework and storage; together these reveal a technically mature, performance-focused team with imgix as its image layer.

A quick imgix confirmation walkthrough

Open the site with developer tools on the Network panel and reload, then look at where images load from. An <source>.imgix.net/...?... URL confirms imgix; click one and read the source subdomain and the query parameters. If images load from a brand domain, check for the characteristic auto=format/fit/w/dpr query parameters, which confirm imgix behind a CNAME. View the source and search src/srcset attributes for imgix.net, and look for an imgix.js library reference. A single imgix.net asset URL — or the query-string transformation pattern — is enough to confirm imgix and identify the source.

A quick imgix detection checklist

• Inspect image URLs for a *.imgix.net host — conclusive.
• Look for query-string parameters: auto=format, fit, w, h, dpr, q.
• Read the source subdomain to identify the imgix configuration.
• Check for a custom domain hiding the imgix host (rely on the query parameters).
• Distinguish imgix (query-string params) from Cloudinary (path-based params).
• Note the surrounding framework and storage to map the media stack.

Detecting imgix at scale

Checking one site is quick, but mapping image-CDN adoption across many domains — to find performance-focused, developer-led businesses — calls for automation. StackOptic detects imgix and thousands of other technologies from a real browser, including custom-domain setups, so you can build a list of technically mature, media-conscious sites. For related reading, see our guide to telling if a website uses Cloudflare or another CDN and the full imgix technology profile.