Llama 4 Scout and Maverick: What Meta Released and What to Check

Published · Updated • articles
MetaOpen Weights

Correction, 21 October 2026: This page previously described Llama 4 as an upcoming release in 2026. Meta released Scout and Maverick on 5 April 2025. The earlier predictions about native audio, near-zero long-context latency and planned AI Mastery benchmark testing were unsupported and have been removed.

Meta's release announcement introduced Llama 4 Scout and Maverick as downloadable, natively multimodal models using a mixture-of-experts architecture. Behemoth was described as a teacher model still in training at that announcement. A preview description is not a downloadable checkpoint.

The official model card is the reference for supported inputs, model configuration and usage restrictions. Read it alongside the exact checkpoint you intend to deploy. This article is a deployment assessment, not an AI Mastery performance benchmark.

Separate active parameters from memory requirements

Meta reported 17 billion active parameters per token for both Scout and Maverick, with 16 and 128 experts respectively. Active parameters describe the computation selected for a token; they do not mean the entire stored model occupies the memory of a dense 17B model. In its announcement, Meta distinguished Scout on one H100 with Int4 quantization from Maverick on an H100 host.

For capacity planning, start with the actual weight files and quantization. Then budget separately for the KV cache, runtime buffers, image processing and concurrent requests. A model that loads with a short prompt can still fail under your intended context length. The hardware ROI tool can help compare a proposed deployment's costs, but its output is not proof that a checkpoint fits.

Evaluate the configuration you will actually serve

Before committing to a deployment, record these decisions:

DecisionEvidence to retainFailure it helps diagnose
Checkpoint and quantizationRepository revision, filenames and runtime versionA result from a different model or conversion
Context and concurrencyPrompt lengths, parallel requests and peak memoryA server that loads but runs out of memory under use
Multimodal inputYour image types, resolutions and expected answersText success being mistaken for image-task reliability
Application behaviorTask success, invalid outputs, latency and failuresA public benchmark being substituted for your workload
LicenseThe license and acceptable-use terms for the checkpointDownload access being mistaken for unrestricted usage

What the launch does not establish

A maximum context specification does not establish reliable retrieval throughout that context, or constant latency as it grows. Likewise, downloadable weights do not eliminate hosting, maintenance or evaluation costs. Compare the full cost of an acceptable answer, including failed attempts and operational work, with an API alternative.

Use a small set of real tasks with expected outcomes before expanding the trial. Keep failed cases rather than reporting only successful examples. That produces a deployment decision you can revisit when the model, quantization or runtime changes, without treating a launch headline as an operating guarantee.

Free interactive tools for the decisions this piece raises.

Related Reading