Costs & renewals
How to plan a SiteGround downgrade without losing what your site needs
Check capacity, features, prepaid credit, and the next renewal quote before choosing a smaller SiteGround hosting plan.
A SiteGround downgrade can lower your hosting commitment if your remaining sites fit the smaller plan. Check that fit before selecting the downgrade option. Website count and storage are only the starting point; staging, backups, client access, resource usage, and the treatment of prepaid time can change the decision.
This is a planning and acceptance guide based on SiteGround’s current documentation. It is not a report of a downgrade performed in a customer account. Use it to prepare the request and confirm the result shown in your own Client Area.
Where is the downgrade option?
SiteGround’s downgrade instructions direct customers to Services → Hosting → Manage, then the plan’s Settings and three-dot menu, where the Downgrade option appears. If the option is unavailable for your service, ask support which changes your particular plan supports.
Before confirming an action, record the current plan, the requested replacement, the effective date, and the resulting renewal details. A screenshot of the quote and a short list of the features you expect to retain are more useful than simply remembering that you selected a cheaper name.
A Cloud resource change and a move from one shared-hosting tier to another are not necessarily the same operation. Describe the exact source and target service in your support request. Ask whether any migration, interruption, or manual configuration work is involved.
Check four kinds of fit
| Check | Evidence to collect | Reason to pause |
|---|---|---|
| Sites and capacity | Active sites, required storage, mail usage, and file counts. | The destination cannot hold the required workload with room to operate. |
| Recurring demand | Usage history including scheduled backups, imports, and busy periods. | A smaller allocation would recreate a recurring resource problem. |
| Workflow features | Staging, restore options, access permissions, and deployment tools actually used. | An essential feature would disappear without a replacement. |
| Billing | Effective date, treatment of prepaid time, and next invoice. | The offered change does not deliver the expected saving or commitment. |
The current public plan comparison lists StartUp for one website, while GrowBig and GoGeek support multiple websites. It also distinguishes features such as staging and on-demand backups by tier. Check the current specifications against the plan you actually hold, particularly if it is an older offering.
Do not remove live files simply to make a usage number look smaller. First identify what is taking space: an obsolete staging copy, redundant local backup archives, media you still use, or email history. Each has a different owner and retention requirement. Keep an independent backup before changing the inventory.
Prepaid time is not necessarily a cash refund
SiteGround explains that shared-to-shared downgrades can convert the fee difference into prorated time on the hosting account. The documented treatment describes an adjusted service period, not an automatic promise of money returned to your payment card.
Ask for the new expiration date and the next renewal amount. This distinction matters if your goal is to reduce next month’s spending: extending a prepaid account may have value without producing an immediate cash saving. If you need a refund, ask about refund eligibility as a separate question.
For example, suppose a provider credits the equivalent of two months of the smaller service. You have gained service time, but your bank balance has not changed. That is an illustrative accounting distinction, not a claim about the credit any particular SiteGround account will receive.
Choose an appropriate time to change
A quieter business period gives you room to notice problems. Avoid combining the downgrade with a theme replacement, a large plugin update, and a DNS change. If several things change at once, it becomes harder to identify the cause of a new failure.
Record a few representative checks before the change: public pages, admin access, form delivery, scheduled tasks, and important logged-in workflows. If the site handles payments, agree an appropriate verification method with the person responsible for the store. Keep the checks focused on the functions your business actually uses.
- Before Keep a backup, inventory the workload, and save the quoted billing outcome.
- During Make the agreed plan change in a suitable business window.
- After Check site functions, resource use, features, and the next renewal date.
Verify the result beyond the homepage
Confirm that the intended plan is active and the expected websites remain attached to it. Review access for any collaborators and check the tools you use for staging or restoration. Then run the business checks you recorded before the change.
Watch the next occurrence of a task that creates a resource peak. A site can look normal during a quiet afternoon and struggle during an overnight import. Keep enough context to tell support when the problem occurred and what work was running, rather than reporting only that the site feels slower.
If the smaller plan does not fit, ask about returning to the previous service and its billing consequences. An application backup restores content and configuration; it does not automatically restore hosting entitlements or reverse a subscription change.
When a downgrade is the wrong saving
Keep the current tier when the features you would lose cost more to replace, or when the workload is already close to its relevant limits. Consider a different host when the basic service model no longer fits, but include the move itself in that comparison.
Read the SiteGround renewal price guide for account discounts and term comparisons. If you are weighing a move, use the migration budget to account for email, overlap, and one-time work. The smallest plan is useful only when it can support the site you intend to keep running.