Who Uses i18next? 1,500+ of the World's Top Websites

i18next turns 15 this year, with nearly 15 million weekly npm downloads. One question we get a lot is who actually uses it in production. So instead of guessing, we measured.

We scanned the top 100,000 websites and checked each one for i18next fingerprints in its delivered HTML, its JavaScript bundles, and its network requests. At least 1,534 of them run on i18next.

The "at least" matters: this is a lower bound (method below). The real number is higher.

It's the top of the web, not the long tail

i18next isn't fringe adoption. It's densest among the most-visited sites and thins out as you go down the ranking:

Most of what we found is react-i18next and next-i18next, which tracks with where the JavaScript ecosystem has gone. And 264 of these sites render i18next on the server (Next.js and friends), exactly the kind of usage a naive client-only check misses entirely.

You know a lot of them

A sample of the sites detected using i18next, the open-source library:

XApple App StoreGitLabMicrosoft Power BIXiaomiSnowflakeMSNNBC NewsBuzzFeedWorld Economic ForumDeezerFreepikElsevierGuggenheim BilbaoEventbriteGoFundMeTradingViewCoinMarketCapKrakenCrypto.comCash AppRakutenStravaUEFADeepLBurberryCartierMercedes-BenzMarks & SpencerGroupon

How we measured this (and where it's fuzzy)

It's only fair to show our work:

• What counts as a hit: the i18next runtime, a binding (react-i18next / next-i18next / others), the http-backend /…/locales/{lng}/{ns}.json load path, or the i18next language-detector cookie, found in a site's HTML, its first-party bundles, or its requests.
• It's a lower bound. Around 9% of the top 100k blocked automated requests or wouldn't respond, and sites that inline their translations with no runtime marker are invisible to this method. Those are undercounted, not counted.
• It's automated, so it can include the occasional false positive. The data is from July 2026, based on the Majestic top-100k ranking. See something wrong about your site? Let us know and we'll correct it.

Search the full list

Every domain we detected, searchable: