Can I reduce the size of my VPS?
CPU, memory and disk reductions have different requirements. A smaller plan must still meet peak demand and application limits. Disk reduction is especially sensitive because shrinking a virtual block device before its data layout is prepared can destroy data.
Instructions
1. Measure the minimum workable capacity
Record busy-period CPU use, working memory, disk usage, growth and recovery space. Leave room for updates, logs and temporary operations rather than selecting a size equal to current used bytes.
free -h
df -hT
lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTSThese read-only views help identify current usage and storage layers; they do not prove a shrink operation is supported.
2. Confirm the provider and filesystem constraints
Ask whether the plan supports an in-place reduction and whether it requires shutdown or migration. Some storage configurations cannot shrink safely in place. A fresh smaller instance with an application-aware migration may be the appropriate supported route.
3. Validate before retiring the larger service
Test the application and data on the reduced allocation or replacement instance under representative load. Confirm billing and cancellation through the service process; shutting down the original VPS is not the same as terminating its subscription.
Check the result
- The reduced allocation supports the measured workload with appropriate headroom.
- Data and application behaviour are validated before the previous service is retired.
Troubleshooting
- Used disk space fits but shrinking is unsupported
- Capacity alone does not establish layout compatibility. Use a supported migration path.
- The reduced RAM causes failures
- Check application memory limits and sustained demand; restore an appropriate allocation through the approved service change.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.