Platform hub

Grok limits

xAI model context, per-model RPS and TPM, Files API, and app uploads. Values below are scoped rather than flattened into one misleading platform-wide number.

Verified Aug 22, 2026Official docs
Quick answer:  Grok has multiple independent constraints. Match the exact plan, model, runtime, invocation mode, or server configuration shown in each row.

Current documented limits

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

How to apply Grok limits safely

The monitored baseline covers Grok 4.6 context, per-model rate dimensions, Files API upload size, Grok app file size. Treat these as separate constraints rather than one platform-wide capacity number: a workload can fit one row and still fail another because the plan, model, endpoint, runtime, region, invocation mode, or account scope differs.

  1. Match the production workload to the exact scope printed beside each value and confirm it in the active Grok console, configuration, or response headers.
  2. Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
  3. Check every adjacent layer—client, SDK, gateway, proxy, queue, database, and downstream service—for a smaller effective limit before changing architecture.

Specific limit pages

These pages exist because the constraint has a distinct implementation or troubleshooting intent. Closely related keyword variations stay consolidated.

Compare alternatives

Official sources

View Grok change history