Change history

Grok limit changes

Current and previous observations remain linked to their official sources. Detection date and effective date are kept separate when known.

Verified Aug 22, 20260 verified changes

Verified history

No verified historical change is recorded yet.
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Grok has never changed. Undated values are kept in the current baseline below instead of being presented as history.

Current monitored baseline

HyperObserve currently monitors 4 scoped observations for Grok. The baseline covers Grok 4.6 context, per-model rate dimensions, Files API upload size, Grok app file size. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.

ConstraintCurrent valueScopeVerified source
Grok 4.6 contextRequests above 200K context have separate documented pricing.500,000 tokensxAI API model grok-4.6xAIAug 22, 2026
per-model rate dimensionsThe per-second request limit is derived from the minute budget and prevents full-minute bursts.RPS and TPM vary by model and cumulative-spend tierPer xAI API teamxAIAug 22, 2026
Files API upload sizeThe API exposes separate initialize and chunk-upload operations.50 MB per filexAI Files APIxAIAug 22, 2026
Grok app file sizeDocuments, images, code, and audio use this general app allowance; behavior can vary by platform or subscription.Most supported files: up to 150 MB eachGrok website and appsxAIAug 22, 2026

Tracked constraints and impact

xAI model context, per-model RPS and TPM, Files API, and app uploads. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.

How a change is verified

  1. Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
  2. Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
  3. Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.

Official sources monitored

These first-party documents support the current Grok baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.

Grok 4.6 model

Context window and model-level rate limits

xAI API rate limits

Per-model RPS, TPM, spend tiers, and 429 handling

Upload files

Files API maximum upload size

Grok website and apps FAQ

Grok app file types and upload sizes

Related

Continue researching Grok