How Much Can You Actually Make With One Week of SuperGrok?

Grok recently replaced separate daily limits with a shared seven-day quota. When I first saw the change, my reaction was probably the same as everyone else's: I looked at the “36%” on the Usage page and asked a very basic question.

What does a full 100% actually buy me over one week?

xAI has not published a conversion table showing how much one image or one video deducts. So I went through the official rules, current generation options, and community tests that included before-and-after Usage readings, then ran the numbers again.

One important caveat: the figures below are not official guarantees from xAI. They are planning estimates built from community observations collected around July 2026. Backend weights, account tiers, and percentage rounding can all change, so your results may differ.

The short answer

If you spent the entire 100% weekly pool on one type of generation, a reasonable estimate would look like this:

Usage type	Approximate output per week
Speed images	700–800 images
Quality images	350–400 images
480p, 10-second videos	70–80 videos
720p, 10-second videos	45–50 videos
720p, 15-second videos	45–55 videos

Most people will mix tasks instead. A realistic heavy week might be:

• About 100 Quality images
• 20 videos at 480p
• 10 videos at 720p
• The remaining quota reserved for chat, retries, and failed generations

That is enough to support a fairly demanding weekly workflow for an individual AI image or video creator.

Why not budget around claims like “110 videos” or “unlimited images”? The calculation method below explains why.

How the seven-day shared quota works

First, there is an easy misunderstanding to clear up.

SuperGrok does not currently give you “500 images per week, 100 videos per week, plus a separate chat allowance.” According to the official xAI Grok FAQ, paid users receive one shared Weekly Usage pool that can be spent across Chat, Imagine, Voice, Build, and other Grok products. Different tasks draw different amounts depending on the compute they require.

Your Usage page may show something like this:

Weekly Usage
Used: 36%
Imagine: 29%
Chat: 5%
Other: 2%
Remaining: 64%

Images, videos, and chats all draw from the same 100%. A normal chat message is relatively light; a high-quality video or long coding task costs much more. The pool resets on the schedule shown under Settings → Usage.

That means the useful question is not “What is the video limit?” It is “What percentage does one video of a fixed specification consume?” Once you know that number, you can estimate a weekly total.

How I estimated the limits

I did not rely on a statement such as “I made 100 videos this week.” There are too many hidden variables. The person may also have used Chat, counted failed generations differently, or mixed resolutions and durations.

Tests with before-and-after Usage readings are more useful. For example, suppose an account starts at 0%, generates only one type of content, and ends at 19% after completing 15 videos.

The math is straightforward:

Cost per generation = Usage increase ÷ completed generations
Theoretical weekly total = 100 ÷ cost per generation

19% ÷ 15 ≈ 1.27%
100% ÷ 1.27% ≈ 79

That gives an average cost of about 1.27% per video and a theoretical maximum of roughly 79 videos. This is more informative than a standalone claim that someone “made about 100.”

The Usage meter is rounded, however, and xAI can adjust backend weights. That is why this article uses ranges instead of pretending the limits are exact to the last generation.

Video is what really burns the quota

Images were not my main concern. Video was, because video generation is where the pool disappears quickly.

480p, 10 seconds: budget for 70–80

One useful recent observation recorded 15 completed 480p, 10-second videos using 19% of the weekly allowance. That works out to about 1.27% each. If the whole weekly pool went into that single format, the theoretical output would be about 79 videos.

I record that as a range of 70–80, not exactly 79. Failed generations, chat activity, percentage rounding, and dynamic backend changes can all move the result.

Earlier users did report reaching approximately 110 videos at 480p before hitting the limit, which would imply only about 0.9% per video. That report may have been accurate for the account and week in question, but it does not match later observations. Other users have also reported higher consumption.

So, can you reliably plan on 100 480p videos every week? I would not. Budget for 70–80. If you reach 90 or 100 during a favorable week, treat that as upside rather than the default allowance.

720p, 10 seconds: budget for 45–50

For short-form video, 480p is useful for testing prompts. For content I might actually publish, 720p matters more.

Across several July 2026 community observations, a 720p, 10-second video commonly consumed about 2% of Weekly Usage. That figure also appears in r/grok reports about the new weekly system.

100% ÷ 2% = 50

For planning, I use “one 720p video is about 2%” and leave a little room for variation. That produces a realistic range of 45–50 videos.

Does a 15-second 720p video cost more?

The intuitive answer is yes: if 10 seconds costs 2%, then 15 seconds should cost 3%. Actual Usage readings have not been that tidy.

One set of repeated 720p, 15-second generations averaged around 1.8% each, which implies about 55 videos. I would not conclude that 15-second video is somehow cheaper than 10-second video. The Usage meter rounds percentages, and backend settings may differ by time and account.

For budgeting, I treat a 720p generation as roughly 2% regardless of duration. In other words, 45–50 videos remains the safer expectation; 45–55 is a wider theoretical range.

Image limits are more generous than they look

Images and videos operate on very different scales.

Speed images

The most repeatable estimate is about eight Speed images per 1% of Usage. If you spent the whole week on Speed mode, that would be roughly 800 images. Allowing for rounding and backend variation, 700–800 is a more realistic range.

That is more than 100 images per day, which is difficult to exhaust in a normal individual workflow.

Quality images

Quality mode consumes noticeably more. A useful reference point is about four Quality images per 1%. At that rate, the theoretical weekly output is 400 images. With a little safety margin, 350–400 is a sensible range.

That is approximately 50–57 images per day, still enough for most creators.

What is the difference between 1K and 2K?

This was the question I most wanted to answer, and the one where I ultimately chose not to invent a number.

xAI's API does price image output by quality and resolution. In the August 2026 Grok Imagine Image 2.0 API documentation, for example, a 1K Medium output is listed at $0.06 and a 2K Medium output at $0.08. Earlier documentation used different prices.

But the key point is that API pricing is not the same as SuperGrok Weekly Usage. xAI has never said that a 33% or 40% API price difference produces the same percentage difference in the consumer subscription meter. The systems cannot be converted directly.

I also could not find a sufficiently controlled test using the same account, time, prompt, and mode while changing only 1K versus 2K and recording enough generations to overcome percentage rounding. I would rather leave the number open than publish a precise-looking figure without evidence.

The same logic applies to video API pricing. It can show that higher-resolution video requires more compute, but it cannot tell us exactly how the SuperGrok subscription meter is weighted.

Mixed use is the real scenario

In practice, I am not going to make 800 images or 80 videos in isolation. A real week mixes tasks.

Here is one budget I calculated for myself:

Task	Estimate	Expected usage
100 Quality images	About 4 images per 1%	About 25%
20 480p, 10-second videos	About 1.27% each	About 25%
10 720p videos	About 2% each	About 20%
Total		About 70%

The remaining 30% covers prompt adjustments, chat, image reruns, failed videos, moderation, and unexpected requests. That is much closer to a real week than an absolute maximum.

If you only make videos

If Grok is primarily a video tool for you, use these planning numbers:

• Testing-heavy workflow: Mostly 480p, 10-second video; about 70–80 generations per week, or 10–11 per day.
• Final-output workflow: Mostly 720p, 10–15-second video; about 45–50 generations per week, or 6–7 per day.

If it takes three attempts on average to select one finished clip, then 50 ÷ 3 is about 16. In practical terms, your weekly output may be 15–20 satisfactory 720p clips. That is a more useful measure of production capacity than simply saying “50 videos.”

There is another limit to keep in mind. The official xAI FAQ says that 720p generations automatically fall back to 480p after an account reaches the 720p cap for its subscription tier. You may therefore have 35% of Weekly Usage remaining and still be unable to continue generating at 720p.

If you selected 720p but received a 480p result, it may be this separate quality cap rather than a bug.

If you only make images

For AI image creation, the allowance is much more comfortable:

• Speed images: about 700–800 per week, or more than 100 per day.
• Quality images: about 350–400 per week, or roughly 50 per day.

If every usable result requires four candidates on average, then 400 ÷ 4 = 100. That gives you approximately 100 strong selections per week, enough for most individual users.

My biggest takeaway: test cheaply before using 720p

The biggest lesson from these numbers is simple: image usage is not the main concern; video usage needs a plan.

One 720p video can consume close to 2%. Five videos use 10%, ten use 20%, and 25 can take half of the weekly pool. A single day spent testing ten 720p prompts may burn almost one-fifth of the entire week.

My workflow now looks like this:

1. Establish the visual style with images.
2. Test motion, camera behavior, and prompts at 480p.
3. Generate the 720p version only after the direction is validated.

That saves a meaningful amount of quota compared with starting every prompt at 720p.

Your results may be different

This needs to be explicit: SuperGrok Weekly Usage is not a transparent, fixed exchange system. xAI has not published a table saying that one Quality image equals 0.25%, one 480p video equals 1.27%, or one 720p video equals 2%.

The estimates in this article come from recurring community observations around July 2026, but even reports from the same period vary. The same 480p, 10-second task has appeared at approximately 0.9%, 1.27%, and higher consumption rates.

Treat these numbers as a budgeting baseline, not a permanent fixed allowance.

Want the real limit for your account? Test it

The most accurate method is to wait for Weekly Usage to reset, record the starting value, generate 10–20 items with identical settings, and record the ending value.

Cost per generation = Usage increase ÷ generation count
Theoretical weekly total = 100 ÷ cost per generation

For example, if 20 videos consume 25%:

25% ÷ 20 = 1.25% per video
100% ÷ 1.25% = 80 videos

For a cleaner result:

• Use the same account throughout the test.
• Complete the test within a relatively short period.
• Keep the mode, resolution, and duration identical.
• Do not mix in Chat, Voice, or Build activity.
• Record failed and moderated attempts as well.

That result will be more useful than any “latest Grok quota chart” you find online. SuperGrok currently behaves like a seven-day shared compute pool with dynamic costs for different tasks, not a package of fixed generation counts.

Final verdict

Based on July 2026 observations, SuperGrok's weekly allowance is generous if images are your main use case. If video is the priority, remember two numbers:

480p video: budget for 70–80 per week.
720p video: budget for 45–50 per week.

Use 480p for testing, reserve 720p for prompts you have already validated, and keep roughly 30% available for chat, failures, and unexpected work. That is the most practical baseline I have found for judging what one week of SuperGrok is actually worth.