← Back to all deprecations

Migrating off Llama 4 Scout

Llama 4 Scout (Groq) — retired 2026-07-17. Source · Verified 2026-08-08.

Groq decommissioned Llama 4 Scout on 2026-07-17. If you're reading this because a bookmarked pricing page or an old integration guide 404'd, this is the retirement record — the model is no longer callable on Groq, full stop.

What actually changes

Llama 4 Scout
Blended $/M
Context window10,000,000 tokens
Max output32,768 tokens
Modalitiestext, vision
Tokens / secunchanged / not measurednot measured

Pricing from our live pricing registry; speed from our benchmark leaderboard where measured.

Gotchas

  • Scout's headline feature was its 10M-token context window — nothing in our current catalog matches that. Gemini 3.1 Pro's 2M-token window is the largest we route to now; if your use case genuinely needed 10M tokens of context, no current model in our catalog is a direct replacement.
  • Scout was a Meta open-weight model served via Groq at Groq pricing. Its intended successor, Muse Spark 1.1, is a proprietary first-party Meta model on a different API — not an open-weight download you can self-host as a fallback.
  • Any code that hardcoded the `llama-4-scout` model id now fails outright rather than returning stale results — check server logs for 4xx errors on that id if a workflow silently broke around 2026-07-17.

Alternatives beyond the obvious successor

Gemini 3.1 Pro$4.50/M blended

Largest current context window (2M tokens) if long-document handling was the priority.

Qwen 3.8 30B$1.20/M blended

Groq-hosted multimodal replacement, far smaller context but similar speed profile.

Grok 4.20 Reasoning$3.00/M blended

1M-token context with strong document analysis, off Groq.

FAQ

Is Llama 4 Scout being shut down?

Yes — it was retired on 2026-07-17. Source: https://console.groq.com/docs/deprecations.

What should I switch to from Llama 4 Scout?

There is no direct 1:1 successor — see the alternatives section for cross-provider options.

Will switching cost more or less?

See the pricing comparison table below for exact numbers.

Run the old prompt against both models, side by side

The only real way to know if a migration is safe is to test it. One workspace, both models, your actual prompts.

Try It Free