The quick answer
The official Grok usage guidance describes a shared weekly allowance for paid features including Chat, Imagine, Voice, and Build. Use the date and time in Settings → Usage for your personal reset, rather than inferring it from intervals between public events.
Free Chat and Voice allowances reset on their own schedule, separately from the paid weekly allowance. Do not apply the paid weekly reset time to a free-feature limit; check the affected feature and the message shown in your account. See what to do when you reach a Grok limit.
Choose your next step
- Find your time: open Settings → Usage and record the explicit reset date, time, and time zone.
- Plan work across features: check the shared pool before starting demanding tasks; billing renewal and public announcements do not establish your reset time.
- Set a countdown only for a known time: verify the converted date and return to Grok when it ends; the timer does not check your allowance.
What if no reset time is shown?
First confirm that you are viewing the same account and product that hit the limit. For a paid weekly pool, check Settings → Usage on grok.com or the mobile app; for free Chat or Voice, read that feature's own notice. An API error or Grok Bot announcement is not a substitute for either check.
If no date is available, do not calculate one from your first message, subscription renewal, or another user's screenshot. Save the notice and check again in the official product; contact support through the app or grok.com if the account information is missing or inconsistent. Until a concrete time is confirmed, skip the countdown. If a displayed time passes but the feature is still blocked, use the limit troubleshooting steps instead of repeatedly moving the timer.
Message counts are not usage amounts
Tasks consume different amounts of allowance. A short question cannot be compared with iterative coding or multimedia generation by counting messages alone. Long coding tasks and complex generation can consume more; this does not establish a fixed cost per message.
Use Settings → Usage to check current consumption and the reset time before planning demanding tasks.
How a shared pool affects task planning
Within the same allowance cycle, one feature's consumption can reduce what remains for other shared features. For example, extensive image experiments may leave less allowance for later coding tasks. This example does not imply a fixed Monday reset.
When you reach a limit, check the affected feature and the recovery or continuation options shown in your account. A weekly allowance cycle is distinct from billing renewal. Do not transfer an announcement's scope between Grok Bot, consumer interfaces, and API access.
Save a personal reset countdown
This site does not assume a universal five-hour or fixed weekly reset time for Grok:
- Read the explicit reset date, time, and time zone in the official settings. If no time is shown, record it as unknown.
- Enter the corresponding local time as requested by the site's form, checking the date and time after conversion.
- Return to Grok when the countdown expires to check your allowance. The timer records time; it does not monitor actual account recovery.
A time-zone example with explicit assumptions
Suppose the official screen explicitly says 2026-09-24 23:30 UTC, and your browser’s local time zone is UTC+08:00. Enter 2026-09-25 07:30 in the local-time form: the date changes as well as the hour. This is a calculation example, not a Grok reset announcement. If the screen gives no time zone, confirm it before converting; do not assume UTC.