Upgrading or Downgrading Storage

The Drive Add-on is built to be resized. Start at 1 TB, fill it, bump to 5 TB. Realise you don't need all of it, clean up and drop to 2 TB. There's no penalty for adjusting. You pay for what you have at any given moment, prorated correctly when you change.

This guide covers the resize flow, what happens to billing when you change size, and the safety rule that prevents you from downgrading below your current usage.

Where to resize

In the dashboard, go to Plans (or Billing → Plans). Find the Drive Add-on section. If you have an active Add-on, you'll see a card showing your current size with a Resize button.

Click Resize and the slider opens at your current size. Drag it to the size you want. The slider snaps to supported tiers (250 GB, 500 GB, 1 TB, 2 TB, 5 TB, 10 TB, 20 TB, 50 TB, 100 TB).

The price preview updates as you drag, showing both the new monthly/yearly price and the prorated difference for upgrades.

Upgrading (going to a bigger tier)

Upgrades take effect after payment is confirmed. Once payment is confirmed:

• The new larger capacity becomes available
• Stripe charges the prorated difference for the rest of the current billing cycle
• The next renewal will be at the new larger price

How proration is calculated

Stripe's prorated math is straightforward. If you upgrade midway through your billing cycle:

• They calculate the cost-per-day for your new tier and multiply by the days remaining in the cycle
• They subtract what you've already paid (cost-per-day of your old tier × days remaining)
• They charge the difference now

A worked example using the current ladder: you're on 1 TB monthly at $11.20/month. On day 15 of a 30-day cycle, you upgrade to 5 TB monthly at $56/month.

1 TB cost-per-day:  $11.20 / 30 = $0.3733
5 TB cost-per-day:  $56.00 / 30 = $1.8667

Days remaining in cycle: 15

Already paid (for the 15 remaining days at the old rate):
  15 × $0.3733 = $5.60

What you should have paid (at the new rate):
  15 × $1.8667 = $28.00

Prorated charge now:
  $28.00 - $5.60 = $22.40

You're charged $22.40 immediately, and your next renewal (at the start of the next cycle) is $56 for 5 TB.

You don't have to do this math. It's shown in the resize confirmation dialog before you commit. We're walking through it because customers often ask "where did this number come from?"

Yearly proration

Yearly subscriptions prorate the same way, just over 365 days instead of ~30. Upgrading 6 months into a year-long 1 TB subscription to 5 TB will charge you the prorated difference for the remaining 6 months.

Currency stays locked

Upgrade preserves your existing currency. A USD subscription upgrading from 1 TB to 5 TB stays in USD. You can't switch currencies via resize.

White Label Lite discount carries through resizes

If your account has White Label Lite, a resize selects the current 10%-off ladder. The prorated upgrade math uses those prices. The 1 TB → 5 TB example above with White Label active uses $10.08/month and $50.40/month instead of $11.20 and $56:

1 TB cost-per-day (White Label):  $10.08 / 30 = $0.336
5 TB cost-per-day (White Label):  $50.40 / 30 = $1.68

15 days remaining × ($1.68 - $0.336) = $20.16 charged immediately

For a yearly resize, the current 5 TB prices are $504 with White Label and $560 standard. This release does not bulk-reprice untouched existing subscriptions; a purchase or resize is the event that selects the current account-aware Stripe Price.

Downgrading (going to a smaller tier)

The resize dialog lets you choose one of two timings:

• Apply now. The smaller capacity starts today. Stripe puts the prorated price difference on the next Drive Add-on invoice as a credit.
• Apply at next renewal. You keep the current capacity through the paid period. The smaller size and new price start at renewal, with no charge or credit today.

The dialog shows the timing you chose and the next billing date.

The usage-fits check

Downgrades require a usage-fits check: does your current usage fit in the new size? If you have 4.2 TB of pooled storage in use and try to downgrade to 1 TB, the dialog blocks the change with:

Your account is currently using 4.2 TB. Downgrading to 1 TB would put you 3.2 TB over the new limit. Free up space first, or pick a larger target.

This applies because TrekMail does not promise an additional 30-day cleanup period after a smaller paid storage tier takes effect. You should reduce usage before scheduling or applying a downgrade.

If you really do want to downgrade despite usage being over the target, the workflow is:

1. Delete files to bring usage under the target
2. Empty Trash (deleted-but-trashed bytes still count)
3. Wait for the storage card to update to reflect the lower usage
4. Try the resize again

Canceling a scheduled downgrade

You can change your mind. If you've scheduled a downgrade and decide you want to keep the larger size, click Cancel scheduled change on the Add-on card. The downgrade is canceled and you continue at the current larger tier.

You can also override a scheduled downgrade with an upgrade, if you scheduled "5 TB → 1 TB at end of cycle" and a week later realise you actually need 10 TB, click Resize and pick 10 TB. The pending downgrade is cleared and the immediate upgrade charge runs.

Choosing the timing

Use Apply now when you are comfortable reducing capacity today and want the pricing change reflected by a prorated credit on the next invoice. Use Apply at next renewal when you want to keep the current capacity through the period you already paid for.

What happens to your data

Resizing affects your capacity (how many bytes the pool can hold), not your content (the bytes already there).

• Upgrading: files stay where they are; you just have more headroom for new uploads.
• Downgrading and you fit: files stay where they are; you have less headroom for new uploads.
• Downgrading and you do not fit: the change is blocked or storage-dependent features may be restricted until you reduce usage or choose a larger tier.

Downgrade overage handling

This is an edge case worth being clear on. If you scheduled a downgrade from 5 TB to 1 TB and you're at 1.2 TB on the change date, the smaller tier may not be allowed to take effect, or the account may be treated as over quota.

What happens:

• New uploads may be blocked.
• New incoming email may bounce as the pool fills further.
• The dashboard may ask you to free up space, empty Trash, choose a larger target, or keep the current size.
• TrekMail does not provide or promise a separate 30-day grace period for downgrade overage.

The cleanest way to avoid this entirely: clean up before requesting a smaller tier, empty Trash, confirm your usage fits, and then resize.

When you'd resize

A few scenarios from real customer patterns:

Quarterly cleanup, then downsize. End of Q3, you do your usual housekeeping, delete old project files, archive completed deliverables, empty Trash. Realise you've gone from 8 TB use to 3 TB. Schedule a downgrade from 10 TB to 5 TB at end of cycle.

One-time large project, then downsize. Took on a video-editing client for two months. Bought 20 TB to handle the raw footage. Project wraps, you archive what you need elsewhere, and downsize back to 1 TB.

Growth surprise, upgrade now. You hit your storage cap on day 12 of the month and need it sorted today. Upgrade to the next tier; after payment is confirmed, capacity increases and Stripe prorates the charge.

Switching to yearly mid-cycle. Realised you're going to keep this subscription long-term. Currently on monthly. The system doesn't directly switch billing periods via resize. You'd cancel the current monthly subscription and resubscribe at yearly. The cleanest moment to do this is just before a renewal date so you don't lose much money on the unused part of the monthly cycle.

What's next

• Subscribing to the Drive Add-on, if you don't have one yet.
• Canceling Drive Add-on, full cancellation, not just downsize.
• Drive Add-on Pricing & Plans, the price ladder.
• Pooled Storage Quotas Explained, usage you're trying to fit under your target size.