These terms apply specifically to the compiled, ready-to-run version of Chrome and ChromeOS that most people download and use. The underlying source code is separately available under open source licenses, which have their own terms.
This analysis describes what Google's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
The terms establish that the executable binary version of Chrome and ChromeOS, which is what users install and run, is subject to these terms and the parent Google Terms of Service, while developers accessing the source code are subject to the distinct open source licenses listed at chrome://credits.
For everyday users, this distinction has no practical impact. For developers who build on or modify Chrome's source code, the applicable license terms are the open source licenses referenced at chrome://credits rather than this document.
Cross-platform context
See how other platforms handle Scope Limited to Executable Code Version and similar clauses.
Compare across platforms →Monitoring
Google has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
"These Google Chrome and ChromeOS Additional Terms of Service apply to the executable code version of Chrome and ChromeOS. Most source code for Chrome is available free of charge under open source software license agreements at chrome://credits.— Excerpt from Google's Google Chrome Terms of Service
(1) REGULATORY LANDSCAPE: The distinction between executable and source code licensing is a standard practice in software distribution and engages open source license compliance frameworks such as those administered under the GNU General Public License, BSD licenses, and similar regimes. No specific consumer protection regulation is directly implicated by this scoping provision. (2) GOVERNANCE EXPOSURE: Low for most organizations. Enterprise IT teams deploying the standard Chrome or ChromeOS executable are bound by these terms and the parent Google Terms of Service. Organizations that build custom Chromium-based browsers or ChromeOS forks based on the source code should conduct separate open source license compliance reviews using the credits listed at chrome://credits. (3) JURISDICTION FLAGS: Open source license compliance obligations apply globally and are not jurisdiction-specific. The distinction between executable and source code licensing is recognized in most major legal systems. (4) CONTRACT AND VENDOR IMPLICATIONS: Procurement teams that build or distribute software incorporating Chrome source code components should conduct an open source license audit against chrome://credits to identify applicable licenses, including any licenses with copyleft requirements that may affect proprietary software distribution. (5) COMPLIANCE CONSIDERATIONS: Organizations developing Chromium-based products should establish an open source compliance program that includes review of the chrome://credits license inventory. Standard executable deployments do not require additional open source compliance action beyond accepting these terms.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
The terms establish that the executable binary version of Chrome and ChromeOS, which is what users install and run, is subject to these terms and the parent Google Terms of Service, while developers accessing the source code are subject to the distinct open source licenses listed at chrome://credits.
For everyday users, this distinction has no practical impact. For developers who build on or modify Chrome's source code, the applicable license terms are the open source licenses referenced at chrome://credits rather than this document.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Google.