How to Think About Storage on a Small VPS: Avoid Overpaying

A practical framework for sizing your VPS disk correctly, plus specific Hostinger plan guidance so you buy only what you need.

TL;DR

Start with 10-20GB on a cheap Hostinger VPS and monitor. SSDs are fast but finite. Most small sites (WordPress, APIs, tools) need under 20GB for code, database, and logs. Keep backups off-server. Upgrade only when disk usage consistently exceeds 80%. Check Hostinger VSS plans and pick the smallest plan that covers your current needs plus 6 months of growth headroom.

Storage Is Not "Just Space"

Think about storage in layers:

Base OS (~2-4GB for a minimal Ubuntu/Debian install)
Applications and dependencies (~500MB - 2GB depending on stack)
Codebase (your app, themes, assets — often 50-500MB)
Database (critical: 500MB for 10k WP posts, grows with content)
Logs (rotate them or they'll fill your disk)
Temporary files (uploads, cache, build artifacts)
Backups (store these off-server, not on the same VPS)

Overestimating storage leads to overpaying. Underestimating leads to downtime when your disk fills. The goal is to start small and expand as needed.

Hostinger VPS Storage Tiers Explained

Hostinger's VPS plans (as of 2026):

VPS 1: 10GB SSD — enough for a small WordPress blog or personal API
VPS 2: 20GB SSD — comfortable for most small SaaS prototypes
VPS 3: 30GB SSD — suitable for medium WordPress sites or multiple small apps
VPS 4+: 40GB to 200GB — for media-heavy sites or multiple projects

All use NVMe SSD, no HDD option. I/O is consistently fast (500MB/s+ read/write).

Practical Estimation Method

Don't guess numbers — calculate:

# On an existing similar server, check current usage:
du -sh /var/www
du -sh /var/lib/mysql
du -sh /var/log
df -h
            

If you're starting fresh:

WordPress + MySQL: allocate 5GB for install + 1GB per 2k posts
Node.js/Python API: 1-2GB for app + 1GB per GB of database
Docker deployments: each container adds 200-500MB, plus volumes

Add 30% headroom. If your calc says 12GB, pick the 20GB plan.

Step-by-Step: Right-Size Storage

List your components: OS, app, code, DB, logs, uploads.
Find current sizes (use a similar server) or estimate conservatively.
Pick the smallest Hostinger VPS that fits today's needs + 6 months of growth (30% buffer).
Set up monitoring: install netdata or use df -h in cron alerts.
When disk usage hits 80%, upgrade via Hostinger panel (in-place, no migration).
Keep backups off-server using Backblaze B2 or Wasabi at $5/TB/month.

⚠️ Never store backups on the same VPS. If the disk fails, both your live data and backups are gone. Use rclone or restic to push daily backups to S3-compatible storage. This costs pennies and saves you from disaster.

Frequently asked questions

How much storage do I really need on a small VPS?

Most small projects (blogs, small APIs, personal tools) run comfortably on 10-20GB. Count your codebase (~100MB), database (~500MB for 10k posts), logs (rotate them), and backups (keep 2-3 off-server). Start small on Hostinger's $1.99 VPS and upgrade if needed.

Does Hostinger VPS use SSD or HDD?

Hostinger VPS uses SSD storage exclusively across all plans. There's no HDD option. SSDs provide 10-100x faster I/O than HDD, which matters for databases and boot times. The storage size varies by plan (10GB on entry-level to 200GB on high-end).

Can I add more storage to my Hostinger VPS later?

Yes, you can upgrade your VPS plan to increase storage. This is done through the control panel with no migration needed (storage expands in-place). Downgrades that reduce storage may require data removal, so plan conservatively upward.

Should I store backups on the same VPS?

No. Off-server backups are essential. Use external storage like Backblaze B2, Wasabi, or rsync to another VPS. Storing backups on the same disk defeats the purpose (single point of failure).

What eats storage on a Linux VPS without me noticing?

Common culprits: (1) Unrotated logs in /var/log (can grow to GBs), (2) Docker images and volumes (each layer persists), (3) Package caches (apt/yum), (4) Core dumps, (5) Orphaned files from uninstalled packages, (6) Database dumps left behind. Set up logrotate and periodic cleanup.

Disclosure: This post contains affiliate links. If you click through and purchase hosting, we may earn a commission at no extra cost to you. This helps support our research and keeps the site running. We only recommend services we've tested and believe provide real value. See our full disclosure policy for details.