Storage is the line item price-conscious buyers scrutinize least, yet it is where hosting invoices quietly diverge. The same 100 GB can cost almost nothing as part of a flat plan, a few dollars as a block volume, or a few cents as object storage – with very different performance and rules attached. This guide compares the three ways you actually pay for storage and shows when each one wins.<\/p>\n\n\n\n
Entry-level plans bundle storage into a fixed price. Converting that into a per-gigabyte figure reveals how much you are effectively paying:<\/p>\n\n\n Included storage is fast (local NVMe or SSD), but it is finite and priced per plan. When you outgrow it, you do not buy more gigabytes at that rate – you jump a plan tier or bolt on a separate volume.<\/p>\n\n\n\n Block volumes attach to an instance like a second disk and are billed per gigabyte per month, typically in the $0.08-$0.20 range, often with performance tiers that raise the price for higher IOPS. They are the right tool for growing databases and application data that need local-grade latency, and they usually survive instance rebuilds. The catch is that a volume you forget to detach keeps billing even after the instance is gone.<\/p>\n\n\n\n Object storage is roughly an order of magnitude cheaper per gigabyte than block storage, which is why it is the standard target for backups and media libraries. The trade-off is that you pay per API request and per gigabyte transferred out, so a badly designed setup that reads the same object thousands of times can erase the per-gigabyte saving.<\/p>\n\n\n\n Every snapshot is data on a disk somewhere, and on many plans it consumes your included quota. Two or three weekly snapshots of a 40 GB disk can occupy more space than the live site. Check whether the provider charges for snapshot storage separately, and whether backups count against the plan quota – it is one of the most common sources of unexpected overage.<\/p>\n\n\n\n For cold data – backups, archives, finished media – object storage wins by a wide margin. For data an application reads and writes constantly, the request and egress fees on object storage can close the gap, and local block storage stays the better choice.<\/p>\n\n\n\n The split is the decisive step: a site with 200 GB of data may only need 20-30 GB on the instance, with the rest in object storage at a fraction of the cost. Estimate the hot portion first, size the plan to it, and let cold data scale independently instead of forcing you onto a larger, more expensive tier.<\/p>\n\n\n\nPlan price<\/th> Included storage<\/th> Effective $\/GB\/mo<\/th><\/tr><\/thead> $3.50<\/td> 25 GB<\/td> $0.14<\/td><\/tr>\n $5.00<\/td> 40 GB<\/td> $0.125<\/td><\/tr>\n $7.00<\/td> 60 GB<\/td> $0.117<\/td><\/tr>\n $12.00<\/td> 80 GB<\/td> $0.15<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n 2. Block Storage Add-Ons<\/h2>\n\n\n
3. Object Storage<\/h2>\n\n\n
Property<\/th> Block volume<\/th> Object storage<\/th><\/tr><\/thead> Typical $\/GB\/mo<\/td> $0.08-$0.20<\/td> $0.005-$0.023<\/td><\/tr>\n Latency<\/td> Local SSD-class<\/td> Milliseconds over HTTP<\/td><\/tr>\n Ideal for<\/td> Databases, live app data<\/td> Backups, media, static assets<\/td><\/tr>\n Hidden fees<\/td> IOPS tiers, snapshots<\/td> Request charges, egress<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n Snapshots and Backups Are Storage Too<\/h2>\n\n\n
Effective Cost: A Worked Comparison<\/h2>\n\n\n
Data volume<\/th> On block storage<\/th> In object storage<\/th> Cheaper option<\/th><\/tr><\/thead> 50 GB<\/td> ~$6\/mo<\/td> ~$0.60\/mo<\/td> Object<\/td><\/tr>\n 250 GB<\/td> ~$30\/mo<\/td> ~$3\/mo<\/td> Object<\/td><\/tr>\n 1 TB<\/td> ~$120\/mo<\/td> ~$12\/mo<\/td> Object<\/td><\/tr>\n<\/tbody><\/table><\/figure>\n\n\n When Each Option Wins<\/h2>\n\n\n
How to Estimate Your Real Storage Need<\/h2>\n\n\n
du -sh<\/code> across your top-level directories.<\/li>Five Ways to Cut the Storage Line Item<\/h2>\n\n\n