Gemma licenses: choose the source for the exact model
“Gemma” is a model family name, not a single license page that should be assumed to govern every version. Google’s current Gemma Terms page says its terms apply to the models listed in that page’s Appendix and directs Gemma 4 readers to a separate license page. Google’s Gemma 4 model card identifies Gemma 4’s license as Apache 2.0. Start with the exact model and its official card, then follow the linked license. This page is a navigation and evidence guide, not legal advice or a substitute for reading the license that applies to your artifact.
Start with Google’s first-party documents
- Google’s Gemma license page: Apache License 2.0 — Google provides the Apache 2.0 license text here and points Gemma 4 readers to this license.
- Google Gemma Terms of Use — The page states that these terms apply to the model names in its Appendix and directs Gemma 4 to a separate license page.
- Google Gemma 4 model card — The card identifies the Gemma 4 license as Apache 2.0; use the card for the model-specific context and the license page for the license text.
A version-by-version source comparison
Use the table to find the right document, not to infer rights from the word “Gemma” alone. The exact model name and the source attached to the artifact matter. If a package combines model versions, conversions, adapters, or third-party files, review each component’s provenance and notices separately.
| What you have identified | Google source and what it says | Next verification step |
|---|---|---|
| Gemma 4 | The Gemma 4 model card lists Apache 2.0. Google’s Gemma license page provides that license text. | Read the model card and linked Apache 2.0 text for the specific Gemma 4 artifact. Check the package’s notices and any changes or additions made by its distributor. |
| A model named in the Gemma Terms Appendix | Google says the Terms apply to the models listed in that page’s Appendix. The Terms incorporate a Prohibited Use Policy by reference. | Confirm that the exact model name appears in the Appendix. Read the current Terms, the referenced policy, and the required distribution provisions; do not substitute the Gemma 4 page. |
| A derivative, conversion, adapter, or unclear package | A family label or a package filename alone does not establish which source terms apply to every component. | Trace the original model, the converted files, and any additional components to their publishers. Review each artifact’s model card, license file, and accompanying notices before deciding what applies. |
Example: an app package contains more than one model generation
Suppose a developer sees “Gemma” in an app manifest, an asset filename, and a model card. One file is identified as Gemma 4; another older asset has only a family nickname. The safe documentation task is not to copy the old Terms into both records. Create a small inventory that links each exact file or package to its original model name, official source, license text, and any notices. The Gemma 4 record should point to the Gemma 4 model card and Apache 2.0 source. The older model should be checked against the Appendix and the current Terms. If provenance is incomplete, keep that entry unresolved and ask the publisher or qualified counsel before making a distribution decision. This is an evidence workflow, not a legal conclusion about a particular Cove package.
- 1. Identify the exact model Record the full model name and version shown by the publisher, not just “Gemma.” Capture the artifact filename, source URL, publisher, revision or release identifier, and whether the file is original, converted, quantized, fine-tuned, or combined with other components. A quantized filename or an app-level display name may not tell you the upstream model identity by itself. If two records do not match, treat the mismatch as an open question rather than choosing the more familiar license.
- 2. Follow the model-specific official link For Gemma 4, open Google’s Gemma 4 model card and follow its license reference to the Apache 2.0 material. For a model listed in the legacy Gemma Terms Appendix, open the Terms page and verify that exact model is listed. Google’s Terms page itself distinguishes Gemma 4 and directs readers to the separate license. Save the official page and review date in the inventory so a later reviewer can repeat the check.
- 3. Compare the artifact with the source documents Check that the card, license file, package metadata, and any download or redistribution notice refer to the same model and version. For a derivative or conversion, find the upstream model and the converter’s additional files or notices; do not assume one family-level page answers every component’s licensing question. If the package includes software libraries, datasets, or tokenizer assets from another publisher, track those separately. Record uncertainty explicitly.
- 4. Preserve the evidence and route unresolved issues Keep the model card, license text, artifact identifier, source URL, date checked, and applicable NOTICE or attribution files together with release documentation. If the model identity, rights, redistribution conditions, or relationship between a derivative and its source is unclear, pause the release decision and seek clarification from the publisher or qualified legal counsel. Do not replace missing evidence with a statement that all Gemma models share one license.
Documentation acceptance criteria
Before marking a model entry as verified, check that the record is specific enough for another person to reproduce the lookup. These criteria test the evidence trail; they do not decide anyone’s legal rights.
- Model identity: The record names the exact upstream model and version, not just a family name or product label.
- Official source: The record links to the model-specific first-party card and its stated license source, with a date checked.
- Distribution materials: The relevant license file, attribution, NOTICE, modifications, and other package components have been identified for review.
- Scope is stated: The record distinguishes what the source establishes from unresolved provenance or interpretation questions and has an owner for follow-up.
Frequently asked questions
Do the Gemma Terms of Use govern Gemma 4?
Google’s Terms page says it applies to the models listed in its Appendix and specifically directs Gemma 4 readers to a separate license page. Google’s Gemma 4 model card lists Apache 2.0. Use those linked sources for Gemma 4; do not present the Appendix Terms as a blanket license for the full Gemma family.
Where can I verify Gemma 4’s license?
Open Google’s Gemma 4 model card and check its license field, then read the Apache 2.0 text linked from Google’s Gemma license page. Keep both sources with the exact artifact record. This page summarizes the navigation path; the official documents control and should be reviewed directly for the intended use.
Does the Gemma Prohibited Use Policy automatically apply to Gemma 4?
The current legacy Gemma Terms incorporate a Prohibited Use Policy and state that those Terms apply to Appendix-listed models. The Terms page sends Gemma 4 readers to a separate license. This page does not claim that the legacy policy governs Gemma 4; consult the current Gemma 4 source and any other applicable product or service terms for your use.
Does using a Cove app mean I have accepted the Gemma Terms?
This page does not determine whether a user accepted any agreement or which agreements govern a particular app interaction. That can depend on the applicable license, product terms, notices, and the facts of use. Read the relevant official documents and product terms; seek qualified legal advice when the answer matters to a release or business decision.
This page is general source navigation for model-license research, not legal advice. Google’s current model-specific documentation and license text are the primary sources. A model-family name, app label, or this summary cannot determine the terms for an unidentified or mixed-provenance artifact.