The Reported ChatGPT Pro-to-Plus Downgrade Trap: Usage May Not Reset

OpenAI documents when a lower-tier plan takes effect, but its public guidance does not explain how an in-flight Codex or ChatGPT Work usage window is handled when the tier changes. Several users report that their existing window did not reset and that usage recorded while they were on Pro left them at or above the smaller Plus allowance.

Those are case reports, not a published rule or service-level promise. The safe conclusion is not “downgrades never reset usage.” It is: a plan change may not align with the usage reset shown in your account, so plan the cutover around both clocks.

Before changing tiers, open Settings → My Plan and Settings → Usage. Record the billing date and the displayed usage-reset timestamp. Prices, multipliers, and reset behavior can move; your account is the operational source of truth.

What OpenAI documents—and what it does not

As of 28 August 2026, OpenAI’s Pro-tier help article lists two Pro options: $100 for 5x the Plus usage allowance and $200 for 20x. It says an upgrade takes effect immediately and starts a new billing cycle, while a move to a lower tier takes effect at the next renewal; cancellation leaves the current plan active through the paid period.

That settles the billing clock. It does not settle the quota clock.

The article does not say that a downgrade, renewal, or cancel-and-resubscribe action resets a weekly Codex window. It also does not document any linear formula for re-scoring past Pro usage against a Plus allowance. Do not infer either behavior from the plan multipliers.

OpenAI separately documents banked Codex resets. An eligible banked reset is a one-time refresh of the five-hour and weekly Codex windows, changes the weekly reset day, and is distinct from purchased credits. Eligibility, availability, and expiry depend on the offer, account, and region. The same article says Support does not provide manual or courtesy banked resets. That is narrower than saying Support never resets any ChatGPT limit.

What users reported

One r/codex user reported moving from the $100 plan to the $20 plan on the renewal date after seeing 78% remaining the night before, then landing at 0% with three days until the displayed reset. In a follow-up, the same user said letting the old subscription lapse before resubscribing did not reset the window. This is a single-account report, not official documentation.

An OpenAI Developer Community thread contains two related reports:

• One user said a Pro renewal left the usage indicator at the same 2% remaining rather than refilling it.
• Another said a window opened on 12 August while the account was on Pro, Pro ended on 16 August, Plus was purchased on 17 August, and the window reset on its original schedule on 19 August. The user described about 2.5 days without agent capacity.

A separate Codex GitHub issue reports Plus quota appearing exhausted immediately after a downgrade because requests made on Pro remained visible in the weekly window. The issue has no official resolution that turns the observation into a product rule.

The reports are mutually consistent, but they do not establish how every account, product surface, or future billing implementation behaves. They justify a conservative cutover plan, not a universal mechanism claim.

Treat two clocks as a cutover risk

The risky sequence is easy to understand:

1. Pro remains active until the paid-through date.
2. A multi-day usage window starts before that date.
3. Plus begins at renewal.
4. The account’s usage window may continue until its separately displayed reset.

If that happens, the invoice has changed while the meter has not yet refreshed. The public documentation does not promise a new Plus bucket at step 3.

Do not model this as “40% of a 5x Pro plan becomes 200% of Plus.” That arithmetic is a hypothetical illustration, not documented quota math. The only reliable values are the status and reset time shown in the account after the plan change.

A conservative downgrade procedure

Read both clocks before changing the plan. Record the Pro paid-through date and the usage reset timestamp. If Plus would begin before the displayed reset, reserve that interval as a possible reduced-capacity period.

Do only the real work you already planned. You keep Pro until the lower tier takes effect, so ordinary work continues under the current plan. Do not create tasks merely to consume quota, and do not assume that unused or used Pro allowance will be recalculated in any particular way after the change.

Keep deadlines outside the uncertain interval. The 2.5-day report is an anecdote, not a forecast. Still, a client launch or incident response should not depend on an undocumented reset at checkout. Move the tier change or prepare another documented execution path.

Prepare documented fallbacks. OpenAI’s Codex pricing page says Plus and Pro users can buy additional credits after reaching included limits, use Luna to extend available usage, or use an API key for additional local tasks billed at API rates. An eligible banked reset is another option when it is already present on the account.

Check Usage before scheduling work on Plus. If the account shows no remaining usage and a later reset time, follow the options displayed in the product. Do not assume another checkout will repair it.

Do not cycle plans to force a reset

Do not upgrade and downgrade repeatedly to try to manufacture a fresh allowance. OpenAI does not document tier cycling as a reset method, and the effect on billing and usage windows is not promised.

Use the paths OpenAI does document: wait for the displayed reset, buy credits if available, switch to Luna where appropriate, use API-billed local tasks, or apply an eligible banked reset already offered to the account. A billing workaround is a poor substitute for capacity planning.

Confirm current before the cutover

On the day you change tiers:

• Read the current ChatGPT pricing page and Pro-tier help article.
• Screenshot My Plan and Usage, including the timezone and reset timestamp.
• Keep the possible gap clear of delivery-critical work.
• After Plus starts, check the actual allowance before launching an agent task.
• Treat every community report as a warning to verify, not as a promise that your account will behave the same way.

As of 28 August 2026, official documentation still does not explain quota inheritance across a Pro-to-Plus change. Until it does, the responsible advice is to allow for a non-resetting window without claiming that the behavior is universal.