As your workload grows or shrinks, resizing your VPS plan is usually straightforward — without needing to rebuild your server from scratch. This guide covers the process and what to expect.
Signs You Need to Upgrade
- Load average consistently above your vCPU count
- Available RAM regularly near zero with active swap usage
- Disk usage consistently above 80–85%
See How to Check VPS Resource Usage (CPU, RAM & Disk) to confirm these signs before upgrading.
Signs You Could Downgrade
- Resource usage consistently well below your current plan's limits, over an extended period (not just a quiet week)
- You've migrated part of the workload elsewhere
Step 1 — Determine Your New Target Specs
See How to Choose the Right VPS Plan for Your Workload for sizing guidance based on your actual usage patterns.
Step 2 — Back Up Your Data First
Before any resize operation, take a fresh backup or snapshot — see How to Set Up Automated VPS Backups. While resizing is generally safe, having a recent backup is standard precaution before any infrastructure change.
Step 3 — Request the Upgrade/Downgrade
In your client area, navigate to your active VPS service and look for an Upgrade/Downgrade or Change Plan option. Select the new plan and confirm.
Step 4 — A Reboot Is Typically Required
Most CPU/RAM resizing operations require a brief reboot to apply — expect a short period of downtime (usually under a few minutes) during the process.
Step 5 — Verify the New Resources
free -h
nproc
df -hConfirm the new RAM, CPU core count, and disk size are correctly reflected after the resize completes.
Important: Disk Downsizing Limitations
While RAM and CPU can usually be adjusted in both directions, reducing disk storage is often not supported (or requires manual data migration to a smaller volume) since existing data must physically fit — check your provider's specific policy before assuming a downgrade includes disk reduction.
Billing Adjustments
Plan changes typically result in a prorated charge or credit for the remainder of your current billing cycle — check your invoice after the change to confirm the adjustment was applied correctly.
Alternative: Migrating to a New VPS Instead of Resizing
If your provider doesn't support in-place resizing, or you're changing regions/providers entirely, see How to Migrate a Database to a New VPS for the data migration process, which applies more broadly to full application migrations as well.
Common Errors
Service doesn't come back online after resize — wait a few minutes for the reboot to complete; if it persists, check your provider's status page or contact support.
Resources show old values after resize — a reboot may not have completed correctly; try rebooting again from your control panel.
Best Practices
- Always back up before resizing, even though the operation is generally safe
- Schedule the resize during a low-traffic maintenance window
- Verify resources and test your application immediately after the change
Related Articles
- How to Choose the Right VPS Plan for Your Workload
- How to Check VPS Resource Usage (CPU, RAM & Disk)
- How to Set Up Automated VPS Backups (rsync, cron & Off-Site Storage)
