Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Accepted Answer
Ok, so I spoke to the support team and found out that although you’re not using the “empty” space on the droplet it gets snapshotted as well. The file size is not compressed. So if you’re running a 20 gb droplet, the unused space gets added to the snapshot. I think it’s better to switch to alternative backup methods. You don’t want to end up with more than a dozen snapshots weighting at 19 gb’s each in the end.
Are you sure you’re not just using that space even though you deleted the files? Files that are still being used by programs will stick around when deleted until those programs stop using them. They contribute to filesystem size that way.
I’m having the same issue. My latest snapshot is huge compared to the one just created a couple of days ago. 18.14 GB vs 2.65 GB. I’m running a basic LEMP setup with WordPress. Looking at my “/” directory as root with du -sh / it’s only showing 2.1G. Where are all these huge files?