Gemini API prepaid billing: what's changing and by when

Google has started emailing developers about a change to how the Gemini API is paid for. The short version: billing is moving from postpay to prepay, and the deadline is October 12, 2026. Since PhotoCaptioner AI runs on your own Gemini key, it’s worth knowing what this is — even though, for most people reading this, the answer is “nothing to do.”

First: does this affect you at all?

Probably not. Here’s the quick test.

• You use Gemini 3.6 Flash on the free tier. Nothing changes. The free tier is untouched by this, you have no billing account to migrate, and you don’t need to enter a card. You can stop reading here. (Not set up yet? Get a free Gemini API key.)
• You’ve set up billing — for Gemini 3.1 Pro, for Google Search grounding, or just to lift the free tier’s daily limit. This applies to you, and there’s a deadline.

What’s actually changing

Until now, paid Gemini API usage worked like a utility bill. You used the API all month, Google tallied it up, and charged your card afterwards. That’s postpay: you spend first and pay later.

Prepay flips it around. You buy a balance of credits up front — the minimum is $10 — and your API calls draw down against it in near real time. When the balance runs low you top it up, either manually or automatically. Google’s own description is “increased spend predictability and a simplified workflow,” which for once is a fair summary.

That’s the whole change. Same API, same keys, same models, same prices per request. Only the payment plumbing is different.

The deadline

Google’s notice is explicit: developers using paid Gemini API features need to move to prepay and purchase credits before October 12, 2026. If you don’t, your paid API access is interrupted until you do.

Google is notifying affected accounts by email, so check the inbox tied to your Google Cloud billing account. The switch itself is done on the Billing page in Google AI Studio, and it takes a couple of minutes.

Why this is genuinely good news

It reads like a chore, but for the kind of person who uses PhotoCaptioner AI — someone captioning their own photo library, not running a company on the API — prepay is the better deal in almost every respect.

Your balance is a hard ceiling. This is the big one. Under postpay, the worst case was always theoretical but real: a runaway process, a misunderstanding about grounding, a batch far larger than you meant, and a bill you didn’t expect. Under prepay, the API simply cannot spend money you haven’t already put in. Load $10 and $10 is the absolute maximum exposure. The failure mode changes from a surprise charge to captioning pauses until you top up — a much better kind of problem.

It replaces a fiddly workaround. Postpay users were advised to set a monthly spend cap in AI Studio to protect themselves. That cap worked, but it was an experimental feature, it only applied to billing-enabled keys, and because Google measures usage with about ten minutes of latency, you could still tip slightly over. Prepay makes the protection structural instead of a setting you have to remember to configure correctly.

You can see what you’re spending as you spend it. Rather than waiting for a month-end statement to find out what captioning actually cost you, the balance ticks down visibly. For anyone who’s ever been vaguely nervous about leaving billing enabled, watching a large batch cost eleven cents is oddly reassuring.

It lowers the barrier to trying paid features. Plenty of people never turn on billing at all, because handing a card to a metered API feels like signing a blank cheque. Buying $10 of credits is a much smaller psychological commitment than authorising open-ended charges — and $10 goes a very long way at Gemini’s per-request prices. A large batch on Flash typically costs a few cents.

Auto-reload is there if you don’t want interruptions. If a paused batch would annoy you more than an automatic charge, you can turn on auto-reload, which tops the balance up when it runs low. Crucially, it has its own monthly limit that you set — so it takes over the job the old spend cap was doing, without the latency caveat.

The worst case stops being a bill you didn’t expect. It becomes captioning that pauses until you decide to continue.

The fine print worth knowing

Prepay is better, not perfect. A few details are worth having in your head before you buy credits:

• Credits expire twelve months after purchase, and they’re non-refundable. Don’t pre-load $200 “to be safe” — buy what you’ll plausibly use in a year. For most photo libraries, the $10 minimum is more than enough.
• The balance is per billing account, not per key. When it hits zero, every API key on that billing account stops at the same moment. If you’ve got other projects sharing one billing account, they all pause together.
• The minimum purchase is $10 and the maximum balance is $5,000.
• Prepay isn’t offered for invoiced or offline accounts, which won’t apply to most individuals but matters if you’re billed through a company.
• You aren’t stuck with it. Google says that once an account has a consistent payment history and higher usage, it can opt back into standard postpaid billing.

What to do, if it applies to you

1. Open Google AI Studio and sign in with the account that owns your Gemini key.
2. Go to the Billing page and switch the plan to Prepay.
3. Purchase credits — $10 is the minimum and a sensible starting point.
4. Optionally turn on auto-reload, and set its monthly limit to an amount you’re comfortable with.
5. Do it before October 12, 2026 so nothing is interrupted.

That’s it. Your existing key keeps working, and PhotoCaptioner AI needs no changes at your end — the key in Settings → API Keys stays exactly as it is.

What PhotoCaptioner AI is doing about it

An upcoming update makes the app fluent in the new billing model. Most of it is wording — everything that used to say “enable billing on your Google Cloud project” now points at the AI Studio billing page and prepaid credits, so the instructions match what you’ll actually see on screen.

The more useful part is a new error message. When a prepaid balance runs out, Google returns the same generic “quota exceeded” response it uses for half a dozen unrelated limits, which would have left you staring at a message about waiting for tomorrow’s daily reset — advice that would never have worked, because no amount of waiting refills a credit balance. The app now recognises that specific case and tells you plainly that your credits are depleted and where to add more.

If you’re on the free tier, none of this will ever appear. It’s just there for the people who’ve moved past it.

The bottom line

A mandatory billing migration with a deadline is nobody’s favourite email. But strip away the admin and this is Google replacing an open-ended arrangement with one where you decide the maximum in advance. For hobbyists captioning their own photographs, that’s the right way round — and if you’re on the free tier, it costs you nothing but the two minutes it took to read this.