Terms and Conditions Last updated: REPLACE_WITH_DATE

Terms and Conditions

The terms on which this site is offered. Written specifically for what this site publishes - technical figures that go stale and commands that change system settings - rather than assembled from generic boilerplate.

📝

Complete and review before publishing

These terms are a starting draft tailored to this site's content, not legal advice. Four placeholders need filling, and one decision needs making.

Replace Four placeholders

REPLACE_WITH_DATE, REPLACE_WITH_YOUR_EMAIL, REPLACE_WITH_SITE_NAME and REPLACE_WITH_JURISDICTION.

Decide Your content licence

Section 5 offers three options for what visitors may do with the site's text. Pick one and delete the other two.

Review Have a lawyer look

Limitation of liability and governing law in particular vary by jurisdiction, and some clauses are unenforceable against consumers in some places.

The short version

In plain English

Not a substitute for the sections below, but this is the substance.

🏢

Not Google

An independent reference. Nothing here is official, endorsed or reviewed by Google.

📉

Figures go stale

Benchmarks, prices and rankings change. Verify anything consequential against the primary source.

⌨️

Commands are yours to run

Some change system settings. Understand what they do before running them on a machine you care about.

📜

We don't licence the model

Gemma's licence comes from Google, not from us. Read it there.

Section 1

What this site is, and your agreement

REPLACE_WITH_SITE_NAME ("this site", "we") is an independent community reference documenting Google's Gemma family of open-weight AI models. By accessing or using this site you agree to these terms. If you don't agree with them, please don't use the site.

🏢
No affiliation with Google. This site is not operated, sponsored, endorsed, reviewed or authorised by Google LLC or Google DeepMind. Gemma, Gemini and Google are trademarks of Google LLC, used here only to identify and describe the subject matter - nominative reference, not a claim of association. For anything official, go to ai.google.dev/gemma.
Section 2

Accuracy, and why it decays

This site carries a large number of specific figures. Some of them will be wrong by the time you read them, and that's worth stating precisely rather than hiding behind "as is".

What goes staleHow fastWhat to do
PricingWeeks Check the provider's own pricing page before budgeting
Leaderboard rankingsWeeks Arena ranks decay as new models arrive; ours are dated
Model availability and IDsMonths Confirm against the live repository or provider
Runtime versions and flagsMonths Check the runtime's own documentation
The weights themselvesWithout warning Gemma 4's July 2026 refresh changed behaviour with no version bump - results before and after aren't comparable
Benchmark figuresPer release Ours state their evaluation settings; other sources may not

The content here is provided on an "as is" and "as available" basis, without warranties of any kind, express or implied, including as to accuracy, completeness, currency or fitness for a particular purpose. Some figures are computed or derived, and are labelled as such. Where sources disagreed we have said so rather than silently choosing one - but that doesn't make either figure authoritative.

Section 3

Commands, code and configuration

This is the clause that matters most on a site like this one.

⚠️
Some instructions here change system state, and one can hang your machine. The site documents commands that install software, alter GPU memory limits, modify service configuration and expose network endpoints. As one specific example, raising the macOS wired-memory ceiling with iogpu.wired_limit_mb can cause a kernel-level stall if set too high - the page documenting it says so, and that warning is part of the instruction, not decoration.

You run all of it at your own risk, on your own hardware, having satisfied yourself about what it does. We accept no liability for data loss, downtime, hardware issues, unexpected costs or security exposure arising from following anything published here.
🔓

Security configuration

Self-hosting guidance includes exposing inference endpoints. Deploy them behind your own authentication - an open endpoint is someone else's free GPU.

💸

Cost estimates

Cost figures are illustrative and based on rates at a point in time. They are not quotes and not a basis for a business case without your own verification.

🔑

Credentials

You are responsible for your own API keys and access tokens. The site never asks for them, and you should never send them to us.

Section 4

We do not licence Gemma to you

Nothing on this site grants you any rights in Gemma, Gemini or any Google model or software. Gemma 4 is distributed by Google under the Apache 2.0 licence, and Gemma 3 and earlier under the separate Gemma Terms of Use. Those licences come from Google and are the only source of your rights.

Our summaries of those licences are written carefully and are, to the best of our knowledge, accurate - but they are summaries. They are not legal advice, and if a licensing question is material to what you're building, read the licence text and take proper advice.

⚖️
One distinction we make repeatedly, restated here. The licence position differs across the family: Gemma 4 is Apache 2.0, while Gemma 3, Gemma 3n and most specialised variants including ShieldGemma remain under the older Gemma Terms of Use with obligations that propagate downstream. Don't rely on a general impression that "Gemma is Apache 2.0" - check the specific model.
Section 5

Using this site's own content

Choose one of the three below and delete the others. Option B is a reasonable default for a community reference.

Option A

All rights reserved

The text, layout and original diagrams on this site are copyright REPLACE_WITH_SITE_NAME. You may read and share links, but may not republish substantial portions without written permission.

Most restrictive. Fine if you want control over reuse.

Option B - suggested

Attribution licence

Original text and diagrams are made available under Creative Commons Attribution 4.0. You may copy, adapt and republish, including commercially, provided you credit REPLACE_WITH_SITE_NAME and link back.

Suits a reference site: encourages the material spreading while keeping credit.

Option C

Public domain

Original content is dedicated to the public domain under CC0. Use it however you like, with or without credit.

Maximum reuse, no obligations on anyone.

📋
Whichever you choose, it covers only our own words. Benchmark figures, model names, specifications and quoted material originate with Google and others and are reproduced here for reference and commentary. Your chosen licence cannot grant rights in material we don't own, and code snippets illustrating third-party tools are governed by those tools' own licences.
Section 6

Acceptable use

Fine

Please do

  • ✅ Read, bookmark, share and link to any page
  • ✅ Use the calculators and selectors for your own planning
  • ✅ Quote figures with attribution and a link
  • ✅ Report corrections - genuinely welcome
Not fine

Please don't

  • ⚠️ Scrape at a rate that degrades the site for others
  • ⚠️ Present the content as official Google documentation
  • ⚠️ Republish substantial portions in breach of section 5
  • ⚠️ Attempt to interfere with the site or its hosting
  • ⚠️ Use it in a way that breaks the law where you are
Section 7

The playground and calculators

The playground connects to software running on your own computer at localhost. We do not operate that software, receive your prompts, or have any visibility into what it produces. Whatever you run locally is yours to configure and yours to be responsible for.

The VRAM calculator, runtime selector and model comparator produce estimates from published figures and stated assumptions. They are planning aids, not guarantees - actual memory use and performance vary with runtime, configuration and hardware. Where a figure is computed rather than measured, the tool says so.

Section 9

Limitation of liability

To the fullest extent permitted by law, we exclude liability for any loss or damage arising from your use of, or reliance on, this site - including loss of data, loss of profits, business interruption, hardware damage, unexpected infrastructure or API costs, and security incidents. This includes losses arising from inaccurate or outdated information and from following instructions published here.

Nothing in these terms excludes liability that cannot lawfully be excluded - including, in many jurisdictions, liability for death or personal injury caused by negligence, or for fraud. If any provision is found unenforceable, the remainder continues to apply.

🧾
Consumer protection varies. Broad exclusions like the one above are limited or unenforceable against consumers in a number of jurisdictions. This clause should be reviewed against the law where you operate rather than assumed to hold as written.
Section 10

General

Changes to these terms

We may update these terms as the site changes. The date at the top will be revised, and continued use after a change constitutes acceptance. Material changes will be noted rather than made silently.

Availability

The site is offered free of charge and without any guarantee of availability. It may be changed, suspended or withdrawn at any time, and pages may be removed or rewritten as the underlying subject matter changes.

Governing law

These terms are governed by the laws of REPLACE_WITH_JURISDICTION, and the courts of that jurisdiction have exclusive jurisdiction over any dispute - except where mandatory local law gives you the right to bring proceedings elsewhere.

Privacy

How the site handles data is described separately in the privacy policy, which forms part of these terms.

Contact

Questions about these terms, or notices under them, go to REPLACE_WITH_YOUR_EMAIL. Corrections are better sent through the contact page.

Questions about any of this?

The contact page reaches us; the about page explains what this site is and how it's sourced.

Contact us Privacy policy About this site