You can move a running Cloud VM to a larger plan from Settings → Change Plan. The VM is briefly stopped, resources are upgraded in place, and it restarts on the new plan.
Settings tab availability. Change Plan is generally available. The Change OS, SSH Keys, and Hostname sub-tabs on the Settings panel show “This section is under development” today — they’re being rolled out. In the meantime, rebuild from a template (Change OS), add or rotate keys at the project level (SSH Keys), and set the hostname inside the guest (Hostname).
If only data is growing, attaching a block storage volume is usually a better fit than resizing the whole plan.
On the server detail page, open the Settings tab. Change Plan is selected by default.
The Current Plan card shows your existing vCPU, RAM, and disk — for example 2 vCPU · 8 GB RAM · 50 GB NVMe.
Open the Available Upgrades dropdown and select a plan. The dropdown lists each plan with its name and headline specs:
After selection, a Selected Plan summary appears confirming the new specs.
Read the Upgrade Process notice:
Click Upgrade Plan to start. The VM transitions through Stopping → Resizing → Starting → Running.
Most cloud images use cloud-initramfs-growroot and resize automatically on boot. If df -h / still shows the old size after resize, run:
Reboot if any tool reports the partition is busy.
In-console downgrades are not supported. To move to a smaller plan:
The dropdown is empty Your VM’s region only has plans equal to or smaller than the current plan. Check Regions and locations for plan availability.
Resize stuck
Open the Activity feed. A failed resize will surface as Operation Failed with a message; the VM will roll back to the original plan automatically.
Disk space didn’t grow
Run the growpart / resize2fs commands above. Some images don’t auto-extend on resize.