The fast-resize down will allow you to resize down to the original size that the droplet was created at, but not lower as that would require shrinking the drive partition.

Thanks

It's not that much hustle to make a backup, boot up a new droplet and select the backup in question, destroy the old one?

@Robin J.

It would have a new IP though, would it not?

If i remember well that was an option in the past but now i see its gone. It was a great option.. i used it to go from 512mb to 1gb then 2gb(ram) and then i downgraded back to 1gb because it was better (my usage was lower) . Please DO do it back.

The correct way to downgrade would be to take a snapshot of your droplet, and boot up a new instance with your snapshot. Shouldn't be anything else to it.

If we could downgrade using the API the same droplet that would be awesome because we could use a script that checks the resources, if there is a spike the script would upgrade the droplet, if spike is gone then the script would downgrade.
We could start big projects on small droplets, once the project grows automatically it will resize the droplet to make sure it has everything it needs.

To downgrade by creating a snapshot and then using it to create a new droplet doesn't make sense either - the IP address will be different, right? That's not a downgrade, that's a new droplet/"host".

Why is it possible to downgrade in my account? Is that because it's a very new account?

yeah.. I agree.. I do upgrade and downgrade depends on usage. can we please get this option?

Even if it was just an button that automated the shutdown - > snapshot -> deletion -> recreation from snapshot with the same IP.

I think part of the issue is that upgrades don't actually change the amount of allocated space you receive, which is incredibly annoying. So downgrading would essentially mean free space.

Currently you need to create a Snapshot, destroy and recreate... I second this.

What there really should be is a "slow resize" option which might take a little longer but allows you to upgrade/downgrade to any size.

That way there are less steps and less frustration when you have to do a real upgrade/downgrade that the fast upgrade option doesn't support.

I wonder why you have to do this twice in step b and c: "create a new droplet from the snapshot image" ?

I agree about downgrade option, as far as it (as upgrade) only touch the CPU and RAM.

Resizing (down) filesystems implies to front with corner cases, file mounts, etc...

I like the idea of being able to downgrade but lets say if i upgraded my hard disk and then downgraded, would i loose data? Also i like the idea of being able to upgrade/downgrade via the api.

Or, how about a way to port a snapshot to a new Droplet (with, perhaps, a warning to the User that this will only work if the Droplets have the same architecture profile.

Addendum to my last comment: The ability to port a snapshot to a new Droplet would, actually, be a great way to transition during a downgrade. The original Droplet could stay live, while the Downgrade Droplet is tested, then change the DNS nameserver records to finalize.