Quick Answer
Replit has three different clocks. Core monthly credits reset at the billing cycle and do not roll over. Purchased credit packs expire six months after purchase. A subscription pause skips a payment and monthly grant but still bills Agent and hosting usage on a pay-as-you-go basis.
Pause is therefore not a spending freeze. Set usage controls and record pack expiry before using it.
Clock 1: Core monthly credits reset
Replit’s pricing and plans guide says Core credits reset at the start of each billing cycle and do not roll over. They are a cycle allowance, not a balance to save for a future client project.
The same page gives Pro a different rule: unused Pro credits carry over for two months before expiring. Do not apply that Pro behavior to Core, and do not infer the expiry of referral or promotional credits from either plan rule.
This article deliberately omits current subscription prices. Replit’s public pricing and help pages showed inconsistent annual Core arithmetic when checked on 28 August 2026. The live checkout is the source for the amount charged; the help page is the source used here for credit behavior.
Clock 2: a pack starts its own six-month timer
Replit’s Managing Your Spend page says:
- credit packs expire six months after the purchase date;
- unused pack credits do not roll over after expiry;
- packs do not automatically renew;
- credits are used from the pack that expires earliest first; and
- auto-reload purchases a new pack when the configured balance condition is met.
Each auto-reload is therefore a new purchase with its own clock. It does not extend the expiry of an older pack.
The spend page also documents a $0.01 usage limit for someone who wants usage to stop after purchased credits are exhausted. That limit is a hard-spend control, not a refund rule. Confirm the account’s budget and usage settings before starting an unattended Agent or deployment job.
Clock 3: subscription pause keeps the meter running
Replit’s subscription guide says only some subscribers are offered a one-month pause on the cancellation path. During that pause:
- the next payment is skipped;
- no monthly credits are granted;
- published projects remain live and collaborators retain access;
- eligible credits and credit packs remain usable; and
- Agent and hosting usage is still billed pay-as-you-go.
That last line controls the decision. Keeping a published app live can preserve service, but its usage can still create a bill. A remaining pack can also continue to be consumed.
The same page says a scheduled pause can be canceled before it starts, but an active pause cannot end early. It also says a subscription can be paused only once and resumes automatically on the displayed date.
Pause and cancel solve different problems
| Question | Pause, when offered | Cancel |
|---|---|---|
| Monthly plan charge | Next payment is skipped | Paid features remain until the current period ends |
| New monthly credits | None during pause | Current plan remains through the paid term |
| Published projects | Stay live | May go offline after the plan ends |
| Agent and hosting usage | Still pay-as-you-go | Previously incurred usage can still be billed |
| Reversal | Active pause cannot end early; one pause only | Return requires a later subscription decision |
Replit’s cancellation guidance warns that published apps may go offline, custom-domain connections may be removed, and storage can be reduced after the paid term. Download anything that must be retained before canceling.
The billing and refunds guide also explains why a charge can appear after cancellation: usage incurred earlier may reach a billing threshold later, or an earlier failed payment may be retried. Canceling a plan does not erase already measured usage.
Free Mode does not rewrite the pause rule
Replit’s Free Mode documentation describes a no-cost Agent allowance with its own five-hour and weekly limits. The official pages were not fully consistent about how they describe Starter eligibility when checked, so this guide does not create a new eligibility rule.
More importantly, the subscription guide does not say that a paused account’s Agent and hosting activity becomes free. It says those categories remain pay-as-you-go. Use that published pause rule for budgeting.
A three-ledger check
Before buying or pausing, write down:
- Monthly ledger: billing-cycle date and Core credits likely to expire at reset.
- Pack ledger: purchase date, six-month expiry, remaining balance, and auto-reload state.
- Usage ledger: Agent, deployment, hosting, storage, budget, and hard usage limit.
If pausing, also record the automatic resume date and confirm that an active pause cannot end early. If canceling, inventory live applications, domains, and files that depend on the paid plan.
The safe summary is short: the Core grant dies at the cycle, a pack dies six months after purchase, and pause does not stop usage billing.
Sources
- Replit pricing and plans — Core and Pro rollover behavior and plan-credit definitions; checked 28 August 2026
- Managing Your Spend — six-month pack expiry, earliest-expiry spending, auto-reload, and usage limits; checked 28 August 2026
- Replit subscriptions — pause eligibility, pause effects, one-use lock, cancellation consequences, and automatic resumption; checked 28 August 2026
- Billing and refunds — post-cancellation charges and usage-billing controls; checked 28 August 2026