How to Resize Droplets for Vertical Scaling
Last verified 18 Nov 2026
DigitalOcean Droplets are Linux-based virtual machines (VMs) that run on top of virtualized hardware. Each Droplet you create is a new server you can use, either standalone or as part of a larger, cloud-based infrastructure.
Resizing a CPU Droplet changes the resources (CPU, RAM, and optionally disk) that the Droplet has. You cannot resize GPU Droplets.
When you resize a Droplet that uses a bundled plan, the Control Panel shows a Downscale anytime by keeping the storage size fixed checkbox. This checkbox controls whether the resize changes the disk:
-
Selected, CPU and RAM only: The resize increases or decreases the amount of CPU and RAM available to a Droplet, and the disk stays the same size. Because the disk doesn’t grow, you can resize the Droplet back down to a smaller plan later. Keeping the disk fixed doesn’t reduce the price of the plan.
-
Cleared, disk, CPU, and RAM: The resize increases or decreases the amount of CPU and RAM available to a Droplet and permanently increases the size of a Droplet’s disk. You cannot downscale the Droplet to a plan with a smaller disk afterward, because you cannot decrease the size of a Droplet’s disk.
The checkbox doesn’t appear for Droplets with a v5 configuration. For those Droplets, you set the vCPU, memory, and boot disk size directly.
Increasing a Droplet’s memory and CPU improves its performance. Increasing the size of its disk increases the amount of data you can store.
You can resize to any Droplet plan that has an equal or greater amount of disk space as the original Droplet.
Considerations Before Resizing
-
Allow for about one minute of downtime per GB of used disk space, though the actual time necessary is typically shorter. You can check the disk storage on the filesystem with
df / -h.Estimated downtime depends on disk usage even for resizes that don’t change the amount of disk space. This is because the Droplet may move to a new hypervisor, which transfers disk data over the network.
-
We strongly recommend taking a snapshot of the Droplet before resizing.
Droplets may change hypervisors during a resize, and any changes to a filesystem can lead to data loss if something goes wrong. We strongly recommend backing up the Droplet’s data before resizing. If you use snapshots, you can delete the snapshot after confirming that the resize was successful.
-
You cannot decrease the size of a Droplet’s disk.
Data is not always sequentially written in memory, so reducing the available space would risk data loss and filesystem corruption. For more flexibility, you can use volumes for additional data storage, which lets you detach or delete the volume if you no longer need the space.
-
You cannot resize between v5 configurations and bundled plans.
Droplets created with a v5 configuration resize only to other v5 configurations, and Droplets created with a bundled plan resize only to other bundled plans. When resizing a v5 Droplet, you can only select a configuration whose boot disk is equal to or larger than the current one.
Resizing Droplets with the Control Panel, API, or CLI
You can resize Droplets from the Control Panel, using the DigitalOcean API, or using doctl, the DigitalOcean CLI.
Using the Control Panel
Before you can resize a Droplet in the Control Panel, you need to power it off. We recommend you do this from the command line to avoid data corruption, so SSH to your Droplet and issue the shutdown command:
sudo shutdown -h nowNext, go to the DigitalOcean Control Panel. On the Droplets page, click the name of the Droplet you want to resize, then click the Settings tab. Click Edit next to Resize configuration. You can also click Actions and select Resize.
The resize section expands to show your current plan and available options.
The current Droplet plan is displayed at the top. For a bundled-plan Droplet, select Downscale anytime by keeping the storage size fixed if you want to resize only CPU and RAM and keep the option to downscale later. Then select a compute plan and choose the new Droplet size. If a plan is unavailable for resizing, the Control Panel displays the reason.
If the Droplet is still running, a Turn off this Droplet button appears at the bottom of the resize section. Click it to power down the Droplet from the Control Panel before you can click Resize Droplet. Because powering off from the Control Panel risks data corruption, we recommend shutting down from the command line first.
Once the resize is complete, power the Droplet back on. A Turn On Droplet button appears at the top of the detail page in place of the Web Console button. You can also use the Actions dropdown and select a power option, or power it on from the More menu on the Droplets list.
The new size is visible on the Settings tab next to Resize configuration. Once the Droplet is booted, you can begin verifying that your services are working as expected. If you took a snapshot of the Droplet before doing the resize, you can now delete the snapshot to avoid further billing for it.
Using the API
When resizing a Droplet via API, you need to specify the resize action type and specify a slug for size. To view a list of slugs, you can use the /v2/size API endpoint.
Resizing via API automatically powers down the Droplet first.
After the resize is complete, power on the Droplet.
Using the CLI
When resizing a Droplet via the CLI, you need to provide a slug to pass to the --size flag. To view a list of slugs, you can use doctl compute size list.
You also need to power off the Droplet by calling doctl compute droplet-action power-off before resizing.
After the resize is complete, power on the Droplet.
Verifying Disk Resizes
In certain cases, a disk resize fails to resize the Droplet’s partition or filesystem. If you rerun df -h after a disk resize and the output is unchanged, this usually indicates a problem. Use gdisk to get more information:
gdisk -l /dev/vdaThe output looks like this:
GPT fdisk (gdisk) version 1.0.3
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/vda: 104857600 sectors, 50.0 GiB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): C1E73477-225B-4585-8BB5-C9291E473CE4
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 52428766
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 227328 52428766 24.9 GiB 8300Some operating systems, like CentOS, don’t come with gdisk by default. You can either install gdisk using the package manager (for example, sudo yum install gdisk) or use fdisk:
fdisk -l /dev/vdaThe output looks like this:
Disk /dev/vda: 50.0 GB, 53687091200 bytes, 104857600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: dos
Disk identifier: 0x000b956b
Device Boot Start End Blocks Id System
/dev/vda1 * 2048 52428766 52426718 83 Linux
In both of the above cases, the partition is still 25 GB even though the disk is 50 GB. To resize the partition, use the growpart command. In this command, /dev/vda is the name of the disk, separated by a space, and followed by the number of the partition to resize, 1.
growpart /dev/vda 1The command to resize the filesystem depends on the filesystem type. If you don’t know what filesystem you’re using, check with df:
df -Th /dev/vda1You can see the filesystem type in the second column of the output. The following example output shows the filesystem type is ext4.
Filesystem Type Size Used Avail Use% Mounted on
/dev/vda1 ext4 50G 4.0G 45G 10% /
For ext3/4 filesystems, use resize2fs to resize the filesystem.
resize2fs /dev/vda1For XFS, use xfs_growfs to resize the filesystem.
xfs_growfs /dev/vda1If there is more than one partition on the disk, you may have to modify the above commands to more closely match the Droplet’s partition table. Partitions are numbered, so if you want to grow a specific partition, use its number in the growpart /dev/vda command. For example, growpart /dev/vda 2 grows the second partition.