Gemini 4 Hydrogen vs Argon: Speed, Price, Reasoning Compared

Google's newest speed play beat its own flagship by a point — and still isn't the model you want for your hardest bug. Gemini 4 Hydrogen launched globally on November 12, 2026 as the rapid-execution member of the Gemini 4 family, while Argon stays positioned for deep, long-horizon reasoning.

That split sounds clean until you see the Artificial Analysis number reported by Google: Hydrogen 51 at default high thinking versus 50 for Argon, and 54 at xhigh. The benchmark section below puts that single point in context, because the rest of the leaderboard points the other way.

Hydrogen beats Argon by 1 point, then loses the job Argon was built for

Google frames Hydrogen as built for rapid coding, agentic execution, multimodal synthesis, and everyday help across the Gemini API, AI Studio, Gemini app, Search, and Antigravity. Carbon makes architectural decisions; Hydrogen writes the code, runs tests, and verifies changes in parallel worker agents.

Price and speed first, because benchmarks won't pay your bill

Prices below match Google's launch post and the LLM Leaderboard pricing sheet, which cites AI Studio pricing.

Three billing details matter more than the headline rate:

1. Thinking tokens are billed as output. Running xhigh on everything erases the discount fast.
2. Pricing is flat across the full 1M context — no long-context surcharge tier on Hydrogen.
3. Worked example: 50M input + 10M visible output lists at roughly $150 on Hydrogen standard tier (75 + 75) versus $200 on Argon. If xhigh adds 20M thinking tokens at $7.50/1M, Hydrogen totals $300 — more than Argon for the same visible work.

Speed is where Hydrogen earns its name. Google claims 2.5x faster task completion than Gemini 3.8 Flash at default high (not versus Argon), 2x to 2.8x faster in partner graph/SQL workloads with 12% to 23% fewer tokens, and over 30% faster Sheets financial-model generation. An independent speed report cited on LLM Leaderboard puts Hydrogen at 198.2 tokens/sec versus 144.0 for Sonnet 5.5 and 136.6 for 3.8 Flash. No qualifying time-to-first-token figure exists yet, so treat first-byte latency as unverified.

What the benchmarks actually prove, and what they don't

Google's launch table (Hydrogen numbers generally pass@1 at max thinking; competitor figures largely provider-reported, full table in the launch post) is worth reading with the footnotes on:

Two caveats change how you should use these numbers. First, LLM Leaderboard lists independent xhigh reruns below Google's launch figures: Multimodal Knowledge Agent at 49.52% versus Google's 53.4%, and Terminal-Bench-Science at 49.52% versus 51.4%. Second, several "class-leading" claims never name the class.

What holds up across sources is narrower: Hydrogen is dramatically better than 3.8 Flash on agentic coding (57% vs 18.2% on Terminal-Bench 4.1), competitive with frontier models on automation breadth, and weaker on the hardest OSWorld-style computer-use and science reasoning where Sonnet 5.5 still leads.

Thinking levels are the real API setting

Hydrogen ships with four reasoning settings — low, medium, high, xhigh — with high as default and xhigh as the new maximum tier. Competitor coverage treats this as a footnote. For API callers it is the cost control.

Google advises selective xhigh because it increases wait time and billable thinking tokens and can overthink simple prompts. In practice: leave production agent loops on high and escalate only failed or high-value traces to xhigh — otherwise your "$1.50 model" invoices like a frontier one.

The Cursor docs expose the same idea as low-to-xhigh effort levels with model ID gemini-4-hydrogen, context limits, and agent-tool support. OpenRouter and Vercel AI Gateway both list hosted access with reasoning controls if you want a provider-neutral endpoint before wiring Google directly.

Access is messy right now: ID, limits, and quota quirks

The spec sheet is clean. The rollout isn't.

Official access as of November 12:

• Developers: Gemini API and AI Studio; Android Studio paid tier
• Paid subscribers: Antigravity for Google AI Pro and Ultra
• Business: Gemini for business via API or model menu; Sheets for eligible subscriptions
• Everyone: Gemini app and Search globally; Sheets starting with Pro and Ultra
• Free app users: Hydrogen via automatic model selection, not always a manual picker choice

Core limits to wire into your client (model card, AI Studio model docs):

• Input context: 1,048,576 tokens, flat pricing across the window
• Default synchronous output cap: 65,536 tokens
• Long output: up to the remaining 1M context via background long decode
• Inputs: text, code, images, video, audio, PDFs, spreadsheets and Office docs; output is text
• Knowledge cutoff: March 2026
• Capabilities: function calling, structured output, code execution, file search, URL context, Search and Maps grounding, computer use, implicit caching; no audio/image generation or Live API

Launch-day threads report mixed availability: some users saw Hydrogen in one product but not another, and some saw it replace Flash as default.

"defaulted to Hydrogen instead of my normal Flash 3.8!" — u/fozzy71, r/GeminiAI launch thread

"It found new things that 3.8 missed." — u/Numerous-Cup1863, r/GeminiAI Hydrogen test thread

Two narrower reports are worth knowing before you trust early demos. In the web-search test thread, u/Healthy_Phone_3703 reported Hydrogen denying the new model names and claiming no live-search support. Separately, @FurkanGozukara reported Hydrogen testing worse than 3.8 Flash at audio understanding. Among the open questions users keep raising are Antigravity uptime and five-hour quota costs at each thinking level — Google's Orchestrator claim of 24% less quota and 19% faster completion on Terminal-Bench 4.0 is a single-benchmark result, not a quota guarantee.

If you ship this week: pin the model ID in config, handle 404/403 as "not enabled for this project/region" rather than retrying blindly, and don't hard-code assumptions about free-tier routing.

Which to call for your workload

Route by failure cost and loop volume — Hydrogen for verifiable volume, Argon for expensive failures (Carbon only as an optional planner above both):

• High-volume agent loops, test runners, verifier agents → Hydrogen on high. This is where 2.5x speed over Flash and $4.50 blended cost compound. Pair with Carbon as planner via Orchestrator if you already use Antigravity.
• Repository coding and debugging with room to verify → Hydrogen first, escalate to Argon on failure. Google claims targeted edits without rewriting unrelated files plus parallel file-read batching, which fits this loop when you can diff the result.
• Deep research, hard science, subtle architecture calls → Argon. Hydrogen's AutomationBench gap (76.14% vs 77.5%) and OSWorld/Science shortfalls matter most here.
• Sheets, Slides, Search-grounded docs and prototypes → Hydrogen. Sheets canvas generation over 30% faster and Search's upgraded fan-out favor iteration speed.
• Still on 3.8 Flash? → Migrate volume paths to Hydrogen, not Argon. Google positions Hydrogen as the fast execution tier covering Flash-era volume work (see the enterprise migration guide), with 5x fewer fabricated claims and better tool-failure recovery than 3.8 Flash. Keep Flash only where you need its proven quota behavior until Hydrogen quotas stabilize.

Related reading on this site: Gemini 4 Carbon vs Argon guide, Gemini 4 Argon API pricing and availability, Gemini 3.8 Flash pricing review.

Gemini 4 Hydrogen vs Argon FAQ

Can free-tier users pick Hydrogen manually?

Not reliably. Free Gemini app users get it via automatic selection; selectable access depends on plan, product, and rollout wave. API free tier lists access, but quotas differ from paid.

Does Hydrogen support 1M output in one call?

Only via background long decode. Default synchronous calls cap at 65,536 output tokens; the remaining context is reachable through long-decode mode.

The trade-off you can't prompt around: Hydrogen buys you speed and throughput at near-frontier quality for everyday agent work, but every xhigh escalation and every unverified quota assumption hands that saving back. Use it as your default worker, not your final judge.