New Chrome extension: Design inspiration in every new tab →
A1 Gallery

What is this website built with?

See the builder or framework behind any website, plus its hosting, libraries and analytics. Free, no sign-up.

Or try an example: , ,

a1.gallery is a Next.js site, plus 3 other tools

a1.gallery is built with Next.js

Next.js is Vercel’s React framework for production apps, with built-in optimisations, dynamic HTML streaming, and the App Router using React Server Components.

How we know: found /_next/static in the page

Browse Next.js sites →Next.js website ↗

Also on the page (3)

  • CloudflareHosting and CDN
  • ReactFrameworks and libraries
  • Google AnalyticsAnalytics

No CMS or fonts found

How to find out what a website is built with

Every builder and framework leaves marks in the pages it makes. The checker reads them for you. It takes a few seconds, and you don’t need a browser extension.

  1. Paste the link

    Paste any page’s address into the field above and press Check site. The homepage is the best place to start. A product page or a blog post can show tools the homepage doesn’t load.

  2. Read the answer at the top

    The headline names the builder or framework. The checker knows 51 of them, from Webflow and Framer to WordPress, Shopify and Next.js. You get the version and the theme when the page states them. “How we know” is the mark we found, so you can check it in the page source yourself.

  3. Look through the rest of the stack

    Under the answer is everything else the page loads, in groups: hosting, libraries, animation, CMS, payments, analytics, ad pixels, chat and cookie banners. Each tool has one line that says what gave it away. Press Copy summary to paste the whole list into a brief or a message.

  4. See more sites built the same way

    When A1 lists the technology, the sidebar shows hand-picked sites built with it. Open one to see how far the tool can go. Then get the same site’s typefaces with the font finder and its colours with the colour palette tool.

Frequently asked questions

Paste the link above. The checker fetches the page and reads its HTML, CSS and response headers. Builders and frameworks leave marks there: an asset host, a script path, a generator tag. You get the builder first, then the hosting, libraries and analytics around it.

Framer sites name Framer in their generator tag and load files from framerusercontent.com. Webflow sites carry a data-wf-site attribute and load assets from website-files.com. The checker looks for both, so you get the answer in a few seconds. Then browse Framer sites or Webflow sites in the gallery.

Paste the link. A CMS that builds the whole site, like WordPress, Ghost, Drupal or Shopify, shows as the headline. A headless CMS behind a custom front end, like Sanity, Contentful, Prismic or Storyblok, shows under “CMS and plugins”. It’s found by the host the site’s images load from.

WordPress pages load files from /wp-content/ and /wp-includes/, and many name WordPress in their generator tag. The checker reads both. When the page states them, it also shows the WordPress version, the theme folder, and plugins like Elementor, WooCommerce, Yoast SEO and WP Rocket.

Yes, when the page names it. For WordPress it’s the folder the theme’s files load from. For Shopify it’s the theme name every storefront prints in its code. A custom theme shows the name its maker gave it, which is often the brand’s own name.

51 of them. Website builders: Webflow, Framer, Squarespace, Wix, Shopify, Cargo, Readymag, Carrd, Tilda and Bubble. CMSs: WordPress, Ghost, Drupal, Joomla, Craft CMS and HubSpot CMS. Frameworks and site generators: Next.js, Nuxt, Astro, SvelteKit, Gatsby, Remix, Hugo, Jekyll, Eleventy and Docusaurus. Around them it spots 181 tools, like Vercel, Tailwind CSS, GSAP, Stripe, Plausible and Intercom.

The page has none of the marks the checker knows. Big companies often run their own platform, so apple.com and airbnb.com come back like this. It also happens when a site is hand-coded, when it blocks automated requests, or when it builds the whole page with JavaScript after loading.

The builder is right almost every time. It’s the same detector that tags every site in the A1 gallery. Each tool is matched on something a site can’t have by accident, like a vendor’s script host or a response header, never on a word in the copy. The list is what one page load shows, so a tool that only loads after you accept cookies can be missed.

Partly. A site can strip its generator tag or serve its files from its own domain. Most don’t bother, and frameworks leave marks that are hard to remove, like the /_next/ folder on a Next.js site.

Yes. No account, no browser extension, no ads, and we don’t keep the links you check. The only limit is 10 checks a minute. A1 has more free tools for the same job, like the website font finder and the design token extractor.

More free tools

All tools →