i18n Detective: Translation Key Finder & Localization QA

Select a broken translation on any page and instantly see the translation key behind it and where it comes from: which frontend dictionary, which micro-frontend, or which backend endpoint. Translation bugs waste hours of ticket ping-pong. QA files "wrong text on checkout page", three teams reply "not ours". i18n Detective ends the argument by naming the exact source file or endpoint. Think git blame for translations. FIND THE KEY AND ITS SOURCE Select text or Alt+click an unselectable element. See the translation key, which dictionary defines it, and whether the value came from the frontend or the backend. AUDIT THE WHOLE PAGE One click scans forraw translation keys, empty or untranslated entries, and wrong-locale strings, highlighting every issue in red. CHECK LANGUAGE COVERAGE Pulls the site's other-language dictionaries and shows which keys are missing or empty in each locale. No manual language switching. ZERO SETUP No code changes, no exposed globals, no framework config. i18n Detective observes the dictionaries and API responses your page already loads. WORKS WITH React apps using i18next, react-i18next, next-i18next, react-intl or next-intl, whether the dictionaries load over the network or ship inside the JS bundle (live instances are read after hydration). Vue apps with vue-i18n, micro-frontend architectures with per-team dictionaries, server-rendered apps that embed translated strings in page state, and backend-driven strings over REST or WebSocket. Sites without any i18n library work too when they fetch locale JSON over the network. Built for QA engineers, localization managers and frontend developers doing internationalization (i18n) and localization QA on multi-team web apps. All processing happens locally in your browser, and captured data never leaves the tab. The only requests the extension makes itself are the dictionary downloads for the coverage check, sent to the site you are inspecting without cookies.