Supported browsers and platforms

Important note: For apps running on devices that do not support a system browser or that have limited input capabilities, such as TVs, game consoles, cameras, or printers, see Sign-In on TVs and Limited Input Devices.

The JavaScript client library for Sign In With Google and Google One Tap is designed to be compatible with most common browsers and platforms. It is not guaranteed to work on all browsers or platforms.

Due to security risks the JavaScript client library is only supported on the latest two versions of each browser.

Compatibility

The Sign In With Google button works with the following browser and platform combinations:

Browser / Platform	Android	iOS ^1	macOS	Linux	Windows 10
Chrome
Edge
Firefox
Safari	N/A			N/A	N/A

N/A means the browser is not available on the platform.

Note: ^1.Due to Intelligent Tracking Prevention (ITP), the Sign In With Google button on iOS requires redirect UX mode.

Google One Tap works with the following browser and platform combinations:

Browser / Platform	Android	iOS	macOS	Linux	Windows 10
Chrome		^2
Edge
Firefox	^2		^2	^2	^2
Safari	N/A	^2	^2	N/A	N/A

N/A means the browser is not available on the platform.

Note: ^2. Extra configuration is required to enable the upgraded One Tap UX on browsers that support Intelligent Tracking Prevention (ITP).

Third-party cookies

Privacy Sandbox for the Web and Chrome's planned removal of third-party cookies introduce significant changes to Google Identity Services (GIS) and user sign in.

As a participant in the W3C FedID community group working on FedCM, Google Identity Services has been working to increase user privacy and security while also minimizing the changes to existing websites and preserving ease of use for our users. The GIS JavaScript library now supports the proposed FedCM API.

As of August 2022, Google Identity Services has conducted a limited FedCM origin trial. Approximately 20 websites and 300K users successfully signed in using FedCM APIs and GIS.

We’re pleased to say early feedback has demonstrated that for most websites, switching to a more private and secure sign-in process without third-party cookies can occur transparently through backward compatible updates to the existing GIS library. Minimal to no changes to existing user flows and websites was required. This is a critical point as widespread adoption of FedCM APIs depends greatly upon an easy rollout for existing deployments.

Based upon this preliminary feedback, GIS currently plans to expand participation in testing GIS with FedCM.

During trials these issues were discovered and may require some web sites to take action when FedCM is adopted by GIS:

• Browser rendered dialogs eliminate the existing ability for sites to use style attributes or intermediate iframes to control sign-in dialog positioning. This may obscure existing site content, some of which may be helpful or critical for users to see before signing in.
• Although not yet widely deployed, some sites may use CSP and COOP. In these cases sites may have to make changes to direct browsers to allow popups and to load cross-site resources.