Droplet resizing limits hinder cost‑optimization for low‑traffic workloads

Answer: Use a snapshot‑based rebuild to change Droplet size

Yes – you can move a nano Droplet to a micro (or any other plan) only by detaching any attached block storage, taking a snapshot, destroying the original Droplet, and creating a new Droplet from that snapshot with the desired plan. Direct in‑place resizing is blocked by the same‑family rule and the inability to shrink disk size.

Confirmed facts from the platform

• Resizing is allowed only between Droplets that share the same family (e.g., nano → micro, but not nano → small).
• You cannot reduce the disk size during a resize; the target plan must have equal or greater disk capacity.
• Nano Droplets are excluded from automated backups and snapshots, so a manual snapshot is required for any plan change.
• Attached block storage prevents any resize operation; the storage must be detached first.

Step‑by‑step workaround

1. Detach any block storage volumes from the nano Droplet (via the control panel or doctl compute volume-action detach).
2. Create a snapshot of the Droplet (doctl compute droplet-snapshot create).
3. Destroy the original nano Droplet (doctl compute droplet delete).
4. Create a new Droplet from the snapshot, selecting the micro plan (or another plan that meets your disk‑size requirement).
5. Re‑attach the block storage volume to the new Droplet (doctl compute volume-action attach).
6. Verify that services start correctly and update any DNS or floating IP references if needed.

Before proceeding, confirm the used disk space on the nano Droplet. If the used space exceeds the disk capacity of the target plan, the snapshot‑based downgrade will fail and you will need to clean up data or choose a plan with sufficient storage.