--- title: "Browser support specifications" slug: "browser-support-specifications" updated: 2026-07-01T12:38:43Z published: 2026-07-01T12:38:43Z canonical: "usercentrics.com/browser-support-specifications" --- > ## Documentation Index > Fetch the complete documentation index at: https://usercentrics.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Browser support specifications `loader.js` is the script that initializes the Usercentrics Web CMP on your site. Because the loader is fetched and executed directly in each visitor’s browser, it must be compatible with that browser. The desktop and mobile browser versions listed below define our minimum supported baseline. > [!NOTE] > **Note**: Browsers older than the stated versions aren’t officially supported and may show reduced or inconsistent behavior. For optimal performance, security, and accessibility, we recommend using the latest stable browser releases. > [!WARNING] > Note: Only the browsers listed below are officially supported. In-app browsers (e.g TikTok, Snapchat, Instagram) are **not supported. See the** [**In-App browsers**](/v1/docs/browser-support-specifications#inapp-browsers) **section below.** ## Desktop browsers | Browser | Version | | --- | --- | | Google Chrome | 124 | | Edge | 124 | | Firefox | 125 | | Safari | 17.4 | ## Mobile browsers | Operating System | Browser | Version | | --- | --- | --- | | Android | Google Chrome Firefox | Android 14+ Android 14+ | | iOS | Safari Chrome Firefox | iOS 17.0 iOS 17.0 iOS 17.0 | ## In-App browsers > [!WARNING] > In-app browsers - such as those used by TikTok, Snapchat, Instagram, and other social media apps when users open links within the app - are **not officially supported**. **Why are in-app browsers not supported?** In-app browsers are proprietary, custom browser environments that fall outside standard web browser specifications. A legal assessment concluded that supporting them poses compliance risks. Ongoing support would additionally require: - Compatibility work specific to each individual in-app browser implementation - Continuous monitoring and re-testing with every new in-app browser version release - Potential changes to the analytics pipeline > **What happens when a user opens your site via in-app browser?** > > Consent is captured correctly. However, analytics interaction events may fall back to NO_INTERACTION — our default fallback value — rather than reflecting the user's actual interaction. This is a known limitation of unsupported environments. > > > > For full functionality and accurate analytics, we **recommend** directing users to open links in a **supported** standard browser.