What the family record covers
Google's model catalog groups Gemini 3 general-purpose variants alongside specialized audio, media, agent, and embedding models. The catalog explicitly distinguishes stable, preview, latest, and experimental names, making lifecycle state part of the technical decision.
A Gemini evaluation should preserve the full model string and endpoint. A rolling alias and a pinned stable model are not equivalent evidence, even when a UI presents both under the Gemini brand.
Documented access paths
- Gemini API model catalog
- Stable, preview, latest, and experimental naming channels with different lifecycle expectations
- Additional Google Cloud or product surfaces should be evaluated as separate deployments
Capabilities to verify
- Text, image, audio, video, or document handling needed by the actual workflow
- Structured response and tool behavior under the selected API method
- Latency and failure behavior for live or interactive use cases
- Migration behavior between preview, latest, experimental, and stable model names
Decision questions
- Does the workflow require a general model or a specialized media or live endpoint?
- Is a stable model ID required, or is the team prepared to retest a changing alias?
- Which Google product and governance boundary contains the deployment?
Evaluation cautions
- Gemini app, Gemini API, and Google Cloud experiences are not interchangeable test conditions.
- Preview, latest, and experimental identifiers carry different change expectations.
- Multimodal support must be tested on the exact input formats and failure cases you expect.
Related decisions
Move from a family name to the product, provider, workflow, comparison, or protocol that defines the real choice.
Sources checked
Open the original pages before relying on a time-sensitive product decision.