How to Tell If a Website Uses Ant Design

Ant Design (often called antd) is a comprehensive React UI library designed for enterprise applications, with an unusually strong set of data-dense components like tables, forms and date pickers. It leaves a distinctive footprint in the rendered DOM, so detecting it is straightforward: inspect any element and look for the ant- class-name prefix. This guide covers every reliable signal, the versioned styling architecture, the look-alikes to rule out, and what an Ant Design build tells you about the team.

What is Ant Design?

Ant Design, created by Alibaba's Ant Group and open-sourced in 2015, is a React component library built for enterprise-grade applications. Its hallmark is breadth and depth in data-display and data-entry components — powerful tables, complex forms, date and time pickers, transfer lists, tree selects and more — wrapped in a polished, consistent design language. It is one of the most popular component libraries globally and is especially prevalent in dashboards, admin panels, internal tools and B2B SaaS, as well as across the Chinese tech ecosystem where it originated.

For detection, the key context is the same as for other React UI libraries: Ant Design is a React library, so finding it tells you the site uses React, and it generates a recognisable ant- class-name footprint in the rendered HTML. Its presence signals a data-dense, enterprise-style application built by a team that wanted a complete, opinionated component set rather than building bespoke UI — usually indicating a real product or internal tool with significant engineering investment. The version (v4 with a static stylesheet versus v5 with CSS-in-JS tokens) offers an additional clue about how current the build is.

How Ant Design renders and styles components

Ant Design components render with the ant- class-name prefix throughout: ant-btn, ant-btn-primary, ant-row, ant-col, ant-table, ant-form-item, ant-input, ant-menu, ant-modal and so on. The pattern is ant-<component> with modifier classes like ant-btn-primary or ant-table-cell. This prefix is consistent across every Ant Design version, which makes it the most reliable signal regardless of how the styles are delivered.

The styling delivery, however, differs by version. Ant Design v4 and earlier ship a static stylesheet — antd.css or antd.min.css (often via the antd/dist/ path or a CDN) — so you will find a large CSS file with ant- rules. Ant Design v5 moved to CSS-in-JS with design tokens, generating hashed class names and css-var-/css-dev-only-do-not-override- style artefacts at runtime and injecting style tags into the head. So a v4 site shows a static antd stylesheet, while a v5 site shows runtime-injected styles — but both carry the ant- component classes. Knowing this — the ant- prefix plus the version-specific style delivery — makes detection both quick and informative about the version.

How to tell if a website uses Ant Design

Confirm at least two of the following.

1. Inspect a component. Right-click a button, table or form field and choose Inspect. An ant- prefixed class (ant-btn, ant-table, ant-form-item) is the definitive signal.

2. Search the DOM. In the Elements panel, search for ant- — many matches across components confirm Ant Design.

3. Check the styling delivery. Look for a static antd.css/antd.min.css stylesheet (v4) or runtime CSS-in-JS style tags with css-var-/css-dev-only artefacts (v5).

4. Confirm React. Because antd is a React library, verify React is present; Ant Design plus React is the expected pairing.

5. Note the data components. Rich tables, complex forms and date pickers in Ant Design's distinct style corroborate it, though the ant- classes are decisive.

What the Ant Design signals look like

<button type="button" class="ant-btn ant-btn-primary"><span>Submit</span></button>
<table class="ant-table"> … <td class="ant-table-cell"> … </td> … </table>
<div class="ant-form-item"> … <input class="ant-input"> … </div>
// v4: <link href="https://cdn.../antd@4/dist/antd.min.css">  |  v5: runtime CSS-in-JS style tags

The ant- prefixed classes across components are conclusive, and the style delivery indicates the version.

Ant Design versus other component libraries — avoiding false positives

Match the prefix to keep React component libraries distinct. Ant Design uses ant-; Material UI uses Mui-; Chakra UI uses chakra- and --chakra- variables; Mantine uses mantine-. The ant- prefix is unique to Ant Design, so it removes ambiguity instantly. Be aware that some sites use third-party Ant Design themes or derivatives, but they still carry the ant- prefix. Do not confuse Ant Design (a React component library) with a plain CSS framework like Bootstrap, which uses different, generic class names and provides no React components. The version distinction (static antd stylesheet vs CSS-in-JS) is about delivery, not identity — the ant- prefix confirms the library either way.

How reliable is each Ant Design signal?

The ant- class-name prefix is definitive — it is specific to Ant Design and appears across every component and version. The static antd.css stylesheet (v4) or the CSS-in-JS artefacts (v5) corroborate and reveal the version. The presence of React reliably accompanies Ant Design. The data-component visual style is suggestive but not decisive alone. There is essentially no false-positive risk once you see the ant- prefix in the rendered DOM. As a rule, a single ant- class confirms Ant Design immediately, and the style delivery tells you the major version.

What an Ant Design build reveals about a site

Finding Ant Design signals a data-dense, enterprise-style React application built with a comprehensive component library. It is especially common on dashboards, admin panels, internal tools and B2B SaaS, where its powerful tables and forms shine, and it is notably prevalent across the Chinese tech ecosystem and companies with ties to it. Its presence tells you the team prioritised a complete, polished, data-oriented component set over bespoke UI, and that the site is an application rather than a marketing page. If you sell developer tooling, design systems, or products aimed at React or enterprise-app teams, an Ant Design site marks a technical, application-focused buyer. The version (v5 CSS-in-JS versus v4 static CSS) hints at how recently the front end was built or upgraded.

What finding Ant Design means for sales, agencies and competitive research

For sales and prospecting, Ant Design marks an enterprise-style React application team — a fit for developer tools, design systems, data-grid and form products, and front-end infrastructure. The data-dense application nature qualifies it as a real internal tool or B2B product.

For agencies and consultants, finding Ant Design tells you the client runs a comprehensive React app, so engagements can focus on theming, performance, accessibility, or complex data-UI work. An older v4 install may also be an upgrade candidate to v5.

For competitive and market research, Ant Design adoption indicates an enterprise, data-oriented front-end approach, and its prevalence in particular regions can hint at a competitor's market or origins. Spotting it suggests a complete, polished component strategy, useful when benchmarking application depth.

Ant Design in the wider front-end stack

Ant Design sits at the centre of an enterprise React stack. It implies React, plus a build tool and often a meta-framework, state management, and a data layer feeding its tables and forms. Enterprise applications using antd frequently pair it with charting libraries (often Ant Design's own charts or ECharts, given the shared ecosystem), internationalisation, and authentication. For an auditor, the valuable details are the Ant Design version (CSS-in-JS v5 versus static v4), the degree of theming, the underlying framework, and the surrounding data, charting and auth tooling; together these reveal a data-dense enterprise application and the maturity of its front-end engineering.

A quick Ant Design confirmation walkthrough

Open the site with developer tools on the Elements panel and inspect a button, table or form field; look for an ant- prefixed class such as ant-btn or ant-table. Use Ctrl+F in the Elements panel to search for ant- and confirm many matches. Check whether styles come from a static antd.css stylesheet (v4) or runtime CSS-in-JS style tags (v5) to gauge the version. Optionally confirm React via React DevTools. The ant- prefix in the rendered DOM is enough to confirm Ant Design and indicate its major version.

A quick Ant Design detection checklist

• Inspect components for ant- prefixed classes (ant-btn, ant-table, ant-form-item) — conclusive.
• Search the Elements panel for ant- to confirm widespread usage.
• Check for a static antd.css stylesheet (v4) vs CSS-in-JS tokens (v5).
• Confirm React is present, since antd is a React library.
• Note rich data components (tables, forms, date pickers) as corroboration.
• Distinguish Ant Design (ant-) from MUI (Mui-) and Chakra (chakra-).

Detecting Ant Design at scale

Checking one site is quick, but mapping component-library adoption across many domains — to find enterprise React application teams — calls for automation. StackOptic detects Ant Design and thousands of other technologies from a real browser, reading the rendered DOM so it catches both static-CSS and CSS-in-JS deliveries. For related reading, see our guide to checking if a website uses React, Vue or Angular and the full Ant Design technology profile.