Paid Grok access draws from a unified weekly pool across Chat, Imagine, Voice, and Build coding capabilities. Official Grok usage documentation details how feature usage aggregates into a shared quota. Learn how this shared pool behaves and when your Grok reset time occurs.
Message counts differ from compute consumption
Different tasks demand vastly different compute resources. A short text inquiry cannot be equated to an iterative coding build or high-resolution video generation. Official guidelines explicitly treat intense programming tasks and complex generation as drawing heavier allocations from your weekly balance.
Under Settings → Usage, Grok reports your current consumption breakdown alongside your scheduled reset timestamp. Track this timestamp to plan resource-intensive tasks effectively.
Shared weekly pool dynamics and recovery checkpoints
Because coding and generation draw from the same balance, creative experimentation during the weekend can directly reduce the tokens available for software tasks on Monday.
When limits are reached, the system pauses high-draw features until the active weekly cycle concludes. Always confirm whether an announcement relates to consumer interfaces or API endpoints before interpreting its impact on your account.
Setting your personal Grok reset countdown
Because Grok does not impose arbitrary rolling windows like other platforms, relying on third-party estimates is imprecise. Instead:
- Navigate to your account settings and copy the exact reset timestamp displayed.
- Input the timestamp into our local browser timer, which converts the time to your local zone.
- Once the timer reaches zero, inspect the native Grok interface to confirm that your balance has fully recovered.
Keep your reset time in view.
Enter the time your account shows. Everything stays in this browser.
Your reset clock →