As of March 27, 2026, Nano Banana Pro does not have one single public rate-limit number anymore. If you mean the Gemini app, the current official answer is the Redo images with Nano Banana Pro daily cap by plan: up to 50/day on Google AI Plus, 100/day on Google AI Pro, and 1,000/day on Google AI Ultra, with no Basic entitlement on the current Gemini Apps limits page. If you mean the Gemini API, Nano Banana Pro is Google's gemini-3-pro-image-preview, and the public rate-limits documentation now gives you a quota framework based on RPM, TPM, RPD, per-project enforcement, and usage tiers rather than one guaranteed universal active RPM table.
That split is the real reason this keyword still feels messy. Old launch coverage, old quota guides, and even some newer blog posts keep acting like Nano Banana Pro is one standalone consumer product with one clear cap. Google's own current pages answer through two different surfaces instead: a Gemini app feature table on one side and Gemini API quota rules on the other.
The safe way to use this article is simple. First, identify whether you are hitting a limit in Gemini Apps or in the Gemini API. Second, use the right official rule set for that surface. Third, ignore any page that mixes late-2025 launch-era numbers, current app caps, and API assumptions into one neat table without telling you which surface each number belongs to.
TL;DR
| If you mean... | Best current answer | Why it matters |
|---|---|---|
| Gemini Apps on Basic | You get Nano Banana 2 generation, not Nano Banana Pro redo entitlement | The current support table shows up to 20 images/day for Nano Banana 2 on Basic, but no Nano Banana Pro redo lane |
| Gemini Apps on paid plans | Nano Banana Pro redo limits are currently up to 50/day on Google AI Plus, 100/day on Google AI Pro, and 1,000/day on Google AI Ultra | This is the cleanest official answer for consumer users |
| Gemini API | Nano Banana Pro means gemini-3-pro-image-preview, and active limits depend on your project tier in AI Studio | Google's public docs explain the framework, but live active project limits are shown in AI Studio |
| Daily reset timing | Gemini app image limits reset daily; Gemini API RPD resets at midnight Pacific time | Readers usually need this before deciding whether to wait or reroute work |
| Why numbers still conflict | Because page one still mixes launch coverage, old model surfaces, and current docs | The model launched on November 20, 2025, and older image-model assumptions became stale after later product changes |
The practical rule is this: if you are clicking around inside Gemini, treat the current support page as your source of truth. If you are building with code, treat the API rate-limits page, the pricing page, and your AI Studio project dashboard as your source of truth.
Current Gemini app Nano Banana Pro limits by plan
The current official consumer answer lives on the Gemini Apps limits page, and it is more nuanced than most ranking pages admit. Google now frames image usage in two separate rows:
Image generation & editing with Nano Banana 2Redo images with Nano Banana Pro
That means the old shorthand answer of "Nano Banana Pro gives X images per day" is no longer precise enough. The current support table is really telling you which plans get the base Nano Banana 2 generation quota and which plans also unlock the higher-end Nano Banana Pro redo lane.
| Gemini app plan | Nano Banana 2 generation & editing | Nano Banana Pro redo images | What that means in practice |
|---|---|---|---|
| Basic | Up to 20 images/day | No listed Nano Banana Pro redo entitlement | You still have a daily image lane, but not the paid Pro redo lane |
| Google AI Plus | Up to 50 images/day | Up to 50 redo images/day | Paid entry point for current Nano Banana Pro redo access |
| Google AI Pro | Up to 100 images/day | Up to 100 redo images/day | Best current consumer middle tier for heavier Gemini app use |
| Google AI Ultra | Up to 1,000 images/day | Up to 1,000 redo images/day | Highest official Gemini app cap on the current support table |
Two caveats on that same official page matter just as much as the raw numbers.
First, Google says Gemini Apps limits may change, access may be limited based on testing or availability, and limits are distributed throughout the day. That is the current official explanation for why users can feel like the product is "throttled" even when a blog post keeps repeating a headline cap.
Second, Google says image-generation limits reset daily. The help page also says Gemini will notify you when you are close to your limit and again when you reach it, including when it will refresh. So if you are a Gemini app user, the product behavior Google wants you to rely on is no longer "guess from an old blog table." It is "watch the in-product notification and use the current support page as the limit anchor."
The most important correction for this keyword is therefore conceptual, not numerical. Current Gemini app limits are no longer well described as a single Nano Banana Pro generation quota. The official wording now separates:
- the broader Nano Banana 2 generation lane
- the Nano Banana Pro redo lane layered on top of paid plans
That is why older pages that still lead with "Free gets 2, Pro gets 100, Ultra gets 1,000" now feel outdated. They are answering the old consumer framing, not the current 2026 one.
If your problem is actually access rather than quota, the next useful read is Nano Banana Pro not showing in Gemini, because a missing feature and a quota cap are different problems even when users describe them the same way.
Current Gemini API quota rules for Nano Banana Pro
For developers, the right official answer starts by dropping the nickname. In the API, Nano Banana Pro is the model gemini-3-pro-image-preview. Google's current models page and image-generation guide position it as the professional image lane for 4K output, complex layouts, strong text rendering, Google Search grounding, and more demanding visual work.
The current API rate-limits page does not give one public "every project gets this exact RPM" table for the model. Instead, Google currently states that rate limits are measured across:
- RPM: requests per minute
- TPM: tokens per minute
- RPD: requests per day
The same page also says three things that most ranking pages still bury:
- limits are applied per project, not per API key
- RPD resets at midnight Pacific time
- active limits depend on the project's usage tier and are viewed in Google AI Studio
| API rule | Current official answer | Why readers keep getting confused |
|---|---|---|
| Official model name | gemini-3-pro-image-preview | Many pages never make the nickname-to-model mapping explicit |
| Quota dimensions | RPM, TPM, RPD | Users expect one simple per-day image cap |
| Scope | Per project, not per API key | People assume switching API keys changes the quota pool |
| Reset rule | RPD resets at midnight Pacific time | Many posts still repeat local-time assumptions or app-reset rules |
| Where active limits live | Google AI Studio | Public docs explain the framework, but current active values live in the signed-in dashboard |
| Guarantee level | Specified rate limits are not guaranteed; actual capacity may vary | Old blog posts present one-size-fits-all numbers as if they were fixed promises |
Google does still publish some model-specific quota information in public, but it is now strongest on the Batch side rather than the live active RPM side. For gemini-3-pro-image-preview, the current public Batch API enqueued-token caps are:
- 2,000,000 on Tier 1
- 270,000,000 on Tier 2
- 1,000,000,000 on Tier 3
The current usage-tier ladder also matters because it explains why one developer's project limit may be meaningfully different from another's. Google's public page currently says:
- Free: active project or free trial
- Tier 1: active billing account linked
- Tier 2: paid account with $100 plus 3 days from first successful payment
- Tier 3: paid account with $1,000 plus 30 days from first successful payment
One more operational detail belongs here because rate-limit searches often hide a cost question underneath them. On the current Gemini pricing page, gemini-3-pro-image-preview has no free-tier pricing row, and the paid output-image prices are currently:
- $0.134 per 1K or 2K image
- $0.24 per 4K image
That does not directly answer "what is my RPM," but it does answer the second question most developers ask after discovering there is no easy public one-size-fits-all quota number: is there a free API lane for the Pro image model? Right now, the public pricing page says no.
If you are building against this model directly, the next useful companion page is Nano Banana Pro API, because setup mistakes and quota misunderstandings usually arrive together.
Why conflicting Nano Banana Pro limit numbers are still everywhere
The contradictions are not random. They are the residue of a real product transition.
Google's release notes say gemini-3-pro-image-preview launched on November 20, 2025 as the next iteration of the Nano Banana line. That launch is what taught the broader market the Nano Banana Pro nickname in the first place. Launch coverage, including a November 2025 TechCrunch article, explained the new model in consumer terms and described limited free use plus fallback behavior in early rollout language.
That launch-era framing stuck in search results. Then the product surface changed.
By March 2026, Google's own support answer is no longer centered on one "Nano Banana Pro generation" row for everyone. Instead, it centers:
- Nano Banana 2 generation and editing caps
- Nano Banana Pro redo-image caps
- daily refresh behavior
- warnings that limits may change and are distributed throughout the day
At the API level, Google's current public documentation also moved away from the older blog-friendly habit of publishing one universal active quota table that everyone could copy into an explainer. The docs now emphasize the framework and point you to AI Studio for the live project-specific answer.
That is why page one still feels noisy even when the official docs are current. The exact query is still driven by the Nano Banana Pro nickname, but the trustworthy answers now live in documents that assume you already understand the product split.
Community friction confirms that the confusion is real. A current Reddit thread literally asks for clarification on the latest Nano Banana Pro daily limits for the Pro plan and what happens after the cap. A Google AI Developers Forum thread from December 2025 also shows Google acknowledging that free-tier limits were lowered as demand shifted compute toward Gemini 3 Pro and Nano Banana Pro. Those community threads are not authoritative policy, but they are strong evidence that the problem is still live for real users.
So the correct editorial move is not to shout a cleaner number than everyone else. It is to explain why the number depends on the surface, and why old pages still sound more certain than current official docs do.
What to do when you hit the limit
If you are in Gemini Apps, the default next move is usually one of these:
- Wait for the daily refresh if the work is not urgent. Google's current support page says image-generation limits reset daily and that Gemini will tell you when the limit refreshes.
- Upgrade your Google AI plan if you regularly run into the current redo cap and the app workflow is otherwise working for you.
- Stop assuming the cap is "wrong" just because a blog shows a bigger number. Google's own page explicitly says limits may change and are distributed throughout the day.
If you are in the Gemini API, the right next move is different:
- Check AI Studio, because the live active quota answer is now project-specific.
- Verify which project is actually making the requests, because quotas are per project, not per API key.
- Check your current usage tier, because that is what governs how much headroom you can reasonably expect.
- Handle 429s as quota signals, not as a mystery outage. If you need the error-handling side, read Nano Banana Pro 429 error.
The most common bad move is to mix the two worlds. Gemini app daily caps do not tell you your API project quota. API tier improvements do not magically raise your Gemini app redo cap. If you do not separate those two systems first, every next step gets more expensive and more confusing.
There is also a planning rule buried in the current docs that deserves to be made explicit. Do not build production commitments around a copied blog RPM number alone. Google's current public rate-limits page says specified rate limits are not guaranteed and actual capacity may vary. That means your operational truth is the combination of:
- the public quota framework
- your usage tier
- your project's current AI Studio view
That answer is less satisfying than an old "100 RPM" headline, but it is more accurate.
Should you stay in Gemini Apps or move to the API?
The right path depends less on the raw cap and more on the kind of work you are doing.
| Surface | Best for | Main limit shape | Best next move when capped |
|---|---|---|---|
| Gemini Apps | Casual creation, quick redos, interactive use inside Gemini | Daily feature caps by plan | Wait for refresh or upgrade the Google AI plan |
| Gemini API | Product builds, automation, batch work, quota observability | RPM + TPM + RPD by project tier | Check AI Studio, tier status, and project usage |
Stay in Gemini Apps if:
- you are mostly working manually
- you do not need per-request observability
- your workload fits comfortably inside the current daily cap
Move to the API if:
- you are building with code
- you need project-level quota visibility
- you need a cost model tied to images and tiers rather than a consumer plan bundle
- your usage pattern is bursty enough that manual app caps keep getting in the way
The key decision rule is simple. If the important question in your head is "how many more can I do today inside Gemini?", you are in the app lane. If the important question is "how much throughput does my project tier have and how should I back off?", you are in the API lane.
For cost planning, the adjacent page you likely need after this is Nano Banana Pro price, because rate-limit confusion and pricing confusion usually come as a pair.
FAQ
Does Basic still get Nano Banana Pro?
Not in the current Gemini Apps limits table as a listed redo images with Nano Banana Pro entitlement. Basic currently shows up to 20 images/day for Nano Banana 2 generation and editing, but the Nano Banana Pro redo row starts on paid plans.
When do Gemini API daily quotas reset?
Google's current rate-limits page says RPD resets at midnight Pacific time.
Why doesn't Google just publish one active RPM number for Nano Banana Pro?
Because the current public documentation frames API limits as project-tier-dependent and tells users to view their active limits in Google AI Studio. The public page explains the framework, not one universal live project value.
Is there a free API tier for gemini-3-pro-image-preview?
The current public pricing page does not list a free-tier pricing row for Gemini 3 Pro Image Preview. That is different from the current Gemini app world, where paid plans unlock Nano Banana Pro redo access inside Gemini.
Why do older pages still say Nano Banana Pro has one simple daily limit?
Because they are usually carrying over the launch-era consumer framing from late 2025 or mixing app and API answers into one table. Google's current official pages now answer the query through a more split surface model.