Google Chrome
About this Google Chrome profile
UA Hub lists Google Chrome as a tools and productivity browser profile maintained by Google LLC. This page brings together the profile's reference labels and compatibility context so an engineer can compare a browser identity before reproducing a request or testing a user-agent rule.
The current reference tags cover Web browser, Chromium, Cross-platform sync, Fast engine, Google ecosystem. They describe the profile taxonomy only and are not operational measurements. A real request may vary by operating system, release channel, embedded browser host, privacy settings, and account configuration.
- Compare browser family and platform labels before debugging a routing or analytics rule.
- Use the visible profile signals to choose a representative compatibility fixture.
- Verify important behavior with feature detection and current request data.
How to use this Google Chrome reference
Start with the browser family and platform context, then compare the exact User-Agent value from the request you are investigating. The profile helps you choose a reproducible fixture for a compatibility test, analytics review, support ticket, or server-log investigation. It does not prove which features are available in every release or embedded host.
A request identified as Google Chrome may come from a desktop installation, a mobile build, a custom tab, or an in-app browser. The operating system, release channel, privacy settings, extensions, and host application can change storage, navigation, media, and Client Hints behavior while the browser family remains the same.
For a reliable test, record the route, timestamp, raw header, major version, operating system, and expected behavior. Reproduce the same journey in the affected context and a known baseline browser. Prefer feature detection and server-side controls over a User-Agent-only rule when the decision affects access, security, payments, or account flows.
Keep the raw request and test context beside this profile when a result matters. Update a fixture when a vendor release, privacy change, parser update, or host-application change alters the evidence behind the browser label.
- Preserve the raw header beside the normalized browser label.
- Test embedded contexts separately from the system browser.
- Document evidence, scope, date, and confidence for important decisions.