Generated title card reading "Gemini 4.0 or Gemini 4?" with the subtitle "One model, two spellings, and the vendor writes it without the dot". Two labelled cards sit beneath it: the left card reads "Vendor writes — Gemini 4 / Gemini 4 Argon" and the right card reads "API identifier — gemini-4-argon", over a footer line reading "Vendor forms verified against Google's own model page, announcement post and API model list, 2026-10-14."
Guides & Insights

Gemini 4.0 or Gemini 4? Why the Dotted Spelling Is the Same Model

Author

Rowan Sterling

Date Published

Latest models · 20View all models →
Benchmarks: Artificial Analysis · updated daily
Back to all posts

G​oogle's flagship is called G​emini 4 Argon, and the generation it belongs to is called G​emini 4. G​oogle has not written G​emini 4.0 anywhere — not on its model page, not in the announcement post, and not in the one identifier its API publishes for the model, which is gemini-4-argon and carries no dot. So the dotted form is not a second model, not a minor release and not a version bump inside the line. A reader who types it arrives at exactly the same thing a reader who types the plain form arrives at. The dot comes from somewhere real, though: G​oogle shipped a G​emini 2.0 Flash line and an image model it sells as Imagen 4.0, and both of those carry the .0 in the name the company sells them under. Anyone who learned G​emini's version numbers from that generation, or who has met the imagen-4.0-generate endpoint, has a reasonable expectation that the numbering continued. It did not. If what you want is the model itself rather than its name, the page to read is our G​emini 4 Argon explainer; this page is only about the number.

Two spellings, one subject — and how you can tell

The honest way to settle a spelling question is not to argue about it but to measure it, and the measurement points one way. When our query data is collapsed by flattening out spaces and dots, the dotted term and the plain term land in the same bucket: every query that reads gemini 4.0 resolves onto the same subject as the queries that read gemini 4. When the two are kept separate, they do not overlap at all. That combination — identical when you normalise, disjoint when you do not — is the signature of one subject written two ways, not of two subjects that happen to look alike. Across our own G​oogle Search Console window ending 2026-10-12, the dotted family took 2,915 impressions and 57 clicks over 15 queries. The bare term gemini 4.0 took 1,006 impressions and 34 clicks over 4 queries, which is a better click rate than most of the stem manages. This is a spelling people are looking for on purpose, not a typo tail. It is worth saying what the dotted family is not, because that absence is itself a finding: unlike the Argon stem, where misspellings such as agron, argom and aragon make up a measurable tail of their own, the dotted spelling has no misspelling tail at all. Conventions have followers. Typos have variations of themselves. The dotted form has the first and none of the second.

What the dotted form is not

Three readings are wrong, and each is worth one line because each is a thing a reader might reasonably have assumed.

• It is not a different model. There is no second G​emini 4 that the plain spelling does not reach. The saturation on G​oogle's own material is total: the model page, the announcement post and the API model list agree on the name, and the name does not contain a dot.

• It is not a minor release, the way a point release sits under a major version in ordinary software numbering. G​oogle's published 4-series identifier set has exactly one member, and it is gemini-4-argon. There is no gemini-4, there is no gemini-4.0, and there is no gemini-4.1 — the last of those has been checked separately on this blog and the answer did not change.

• It is not a version bump that G​oogle quietly applied and then documented under a different form. If the company had shipped a 4.0 and then renamed it, the identifier would have moved with the name, the way identifiers always do in the G​emini API's model list. It has one entry for the generation, and the entry is Argon.

None of which makes the dotted spelling ignorant. It makes it early. The .0 form was correct for the previous generation in exactly the place readers learned it, and conventions outlive the versions that taught them.

Where the dot actually comes from

This is the part the demand rows make legible, so it is worth being precise about the two precedents rather than gesturing at them.

A screenshot of Google's Gemini API models documentation page, captured 2026-10-14. A section headed "Gemini 4" is marked Stable and contains a card headed "Gemini 4 Argon" described as Google's flagship reasoning model with a unified 1M context window, with its Endpoint field reading gemini-4-argon — no dot in the identifier. The list continues below with the Gemini 3 family, headed by Gemini 3.8 Flash.

The first precedent is the G​emini 2.0 line. G​oogle's own model documentation lists G​emini 2.0 Flash and G​emini 2.0 Flash-Lite under its previous-models heading, with the endpoints gemini-2.0-flash and gemini-2.0-flash-lite. That is the only major G​emini line the page writes with a .0. Every other generation it lists is numbered the way G​emini 4 is: 3.8, 3.6, 3.5, 3.1, 2.5. So the dotted form is not a rule readers invented. It is a rule G​oogle applied once, to the 2.0 generation, and then stopped applying.

The second precedent sits outside G​emini entirely but inside the same API surface, which is what makes it sticky. G​oogle's generative-media model list includes imagen-4.0-generate. A developer who has that string in a config file has, quite reasonably, a memory of a versioned G​oogle model whose number is written 4.0. Put the two memories together and the dotted form stops looking like a mistake and starts looking like something you are supposed to be able to type.

You can type it. It just does not resolve to a dotted name, because there is no dotted name to resolve to.

The one 4-series identifier G​oogle publishes

If you are writing code rather than reading prose, the answer is shorter than this page: the string is gemini-4-argon. It is listed as Stable, it is described on the same page as a reasoning model with a unified 1M context window, and it is the only member of the generation that appears anywhere in the model list. That is the identifier to put in a request, and no dotted variant of it exists.

What the model is — what G​oogle attached to the name, how it is positioned, and what was and was not published alongside it — is a separate question with its own page, and this one deliberately does not re-answer it. Our G​emini 4 Argon explainer carries that. If your actual question is which rung of the line Argon occupies and why no Ultra appears beside it, that reading lives in our G​emini 4 Argon tier positioning piece.

Where each dotted query goes next

Three qualified spellings make up most of the dotted family, and none of them is a naming question. Each has a different home, and the useful thing this page can do is point rather than duplicate.

• gemini 4.0 argon — 1,509 impressions and 12 clicks, the largest single row in the dotted family. That reader already has the right name and wants to know what is behind it. The G​emini 4 Argon explainer is the page for that, and the naming question does not need to be walked through there.

• gemini 4.0 pro — 154 impressions and 9 clicks. This is a tier question wearing a spelling, not the other way round. It belongs to the page that defines what a Pro rung is in a line G​oogle announced as a single model; it is not answered here, and answering it here would only put two of our own pages in front of the same reader.

• gemini 4.0 release date — 165 impressions and 2 clicks. The timeline reading has its own page, and using this one to restate it would be the second time we told that story rather than the first time we answered this one.

The pattern across those three rows is the argument for this page existing at all. A reader who types the dotted form is not asking a different question about the model. They are asking about the number, and until now nothing we published answered that in one screen.

What you will not find here

OrcaRouter serves no model id matching gemini-4 under any spelling, in either direction — not the plain form, not the dotted form, not the identifier G​oogle actually publishes. We checked our own live model list on 2026-10-14 and there is nothing on that stem to route, so there is no price to quote and no endpoint to describe. What we do serve from the same vendor is the shipping workhorse generation: google/gemini-3.8-flash and the rest of the 3.x line, all reachable through one API across more than 200 models with no markup on the provider's list price, so a vendor price change reaches you the same day rather than on our schedule. That is a statement about the models we carry, not about the one this page is named after.

A screenshot of the Artificial Analysis page for Gemini 4 Argon, captured 2026-10-14, showing the model named as Gemini 4 Argon (High) and labelled a Google proprietary model released September 2026, with its Intelligence Index score shown as 53, a 1M token context window, pricing of $2.00 per 1M input tokens and $10.00 per 1M output tokens, and a cost of $1.99 per Intelligence Index task.

It is worth noting what that independent page demonstrates about the naming question, because it is evidence rather than decoration. A third party that measures the model writes the name the same way G​oogle does: G​emini 4 Argon, undotted. Across the vendor's own material, the vendor's own API list and a measurement house with no interest in G​oogle's branding, there is one form and no dotted variant of it. That is as close to a tiebreak as a spelling question gets.

The convention to use going forward

Write G​emini 4 for the generation and G​emini 4 Argon for the model, and put gemini-4-argon in anything that has to execute. If you are the sort of reader who types the dotted form out of habit, nothing breaks — you have been landing on the right model the whole time. What you should stop doing is assuming the dot carries information, because in this generation it does not. It does not mark a point release, it does not mark a smaller variant, and it does not mark anything G​oogle has shipped.

Both spellings will keep appearing in search results, and for two reasons that have nothing to do with anyone being careless. The first is the precedent: gemini-2.0-flash is still a live string in the previous-models list and imagen-4.0-generate is still a live endpoint, so the dotted idiom is still current in the same documentation set, one page away. The second is how search engines treat punctuation, which is loosely enough that a page written either way can surface for either query. The result is that the dotted query keeps being asked, and the useful answer to it is the one this page gives: same model, no dot in the name, and here is where each of the qualified versions actually goes.

A generated reference card headed "What each spelling resolves to", listing four rows: "Gemini 4 — the generation, as Google writes it", "Gemini 4.0 — the same generation; no dotted form exists", "gemini-4-argon — the one published API identifier", and "gemini-4 — not published, and not served by OrcaRouter", over a footer line reading "Forms verified against Google's model page, announcement post and API model list on 2026-10-14; OrcaRouter availability checked against our own live model list the same day."

One closing note on sourcing, since this page is mostly a set of negatives. Every claim about which form G​oogle uses was checked on 2026-10-14 against G​oogle's own material: the model page, the announcement post and the API model list, which is where the single 4-series identifier comes from. The claim about the 2.0 line and about imagen-4.0-generate comes from the same documentation set, which is what makes it a statement about G​oogle's conventions rather than about this one model. The demand figures are our own first-party Search Console impressions and clicks, and they describe what people type and nothing else. And the availability line was checked against our live model list the same day rather than carried over from an earlier draft, because a confident availability claim that has gone stale is worse for you than no claim at all.

A naming question is also a good moment to check what has gone wrong before: the documented AI incidents and agent failures around models of this class are collected in the OrcaRouter AI Incident Archive , where each entry carries its own sources, severity, confidence grade and disputed flag.