What web hosting is not for: backups, file storage and bulk email
Three things people routinely use hosting for that it is explicitly not sold for — and in each case the account suspension arrives without much warning.
Key takeaways
- "Unlimited storage" is sold for website files. Using it as a backup drive breaches nearly every host's terms.
- Hosting backups are not backups — they sit on the same machine as the thing they are backing up.
- Bulk or marketing email from a shared host will fail on deliverability before it fails on policy.
- Enforcement is usually suspension first, explanation second, and inodes often catch you before the terms do.
- The correct alternatives are cheap: object storage, a backup service, a transactional email provider.
An unlimited-storage hosting plan at $3 a month looks like the cheapest cloud storage on the market. It is not storage, and the three ways people try to use it as storage all end the same way.
Worth being clear about the framing: this is not hosts behaving badly. Shared hosting is priced on the assumption that a website uses modest resources continuously, which is very different from a file archive that consumes disk and bandwidth in bursts. The terms exist because the pricing depends on them.
1. Backup and file storage
Why people try it
Unlimited storage for a few pounds a month, against a dedicated backup service charging per terabyte. The arithmetic looks unanswerable.
Why it does not work
The terms prohibit it. Nearly every shared host's acceptable use policy explicitly excludes using the account primarily for file storage, archiving or backup of material not part of a website. This is not buried — it is a named clause, because it is the most common form of abuse.
Inodes stop you first, usually. As covered in what "unlimited" means, hosts cap the number of files regardless of size. A photo archive is exactly the shape that hits an inode limit — enormous file counts, moderate total size. You will often break the account before anyone notices the policy breach.
It is not a backup anyway. This is the important one. A backup needs to be somewhere separate from the original. Files on your hosting account share a fate with your hosting account: if it is suspended for non-payment, hacked, or you have a billing dispute, you lose the site and the backup together. That is precisely the scenario a backup exists for.
The tooling is wrong. No versioning, no incremental sync, no client, no encryption at rest that you control, no restore testing. Recovering anything means FTP and hope.
What to use instead
Object storage — the S3-compatible services from the major cloud providers and several independents — costs a few dollars per terabyte per month, is built for exactly this, and has real tooling. For personal backups, a consumer backup service handles versioning and scheduling for a flat fee.
For backing up the website itself: keep a copy somewhere that is not your host. Your host's own backups are for their convenience and are the first thing you lose in an account dispute.
2. Bulk and marketing email
Why people try it
The plan includes unlimited email accounts. A mailing list is email. It looks included.
Why it does not work
Deliverability fails before policy does. Shared hosting mail servers carry the reputation of every account on them. One spammer degrades the IP for everyone. Sending marketing mail from a shared host means much of it lands in spam folders regardless of how legitimate it is — and you get no feedback, so you conclude the campaign performed badly rather than that it was never delivered.
Sending limits are low. Hosts cap outbound mail per hour, often in the low hundreds, specifically to contain spam. A list of a few thousand simply will not send.
Bulk sending is usually prohibited outright, and being flagged as a spam source can get the account suspended immediately — taking your website down with it, since they are the same account.
What to use instead
A dedicated email service. Marketing platforms handle list management, opt-outs and compliance; transactional providers handle order confirmations and password resets. Both maintain sender reputation as their core business, and both have usable free tiers at small volume.
This is worth doing even for a small site's contact form. Transactional email sent through a proper provider actually arrives, which is a low bar that shared hosting mail frequently fails to clear.
3. Media hosting for other sites
Why people try it
Unmetered bandwidth, so why not serve video, large images or downloads from the hosting account and embed them elsewhere?
Why it does not work
"Unmetered" describes billing, not capacity. Serving large media consumes I/O and connections continuously, and hosts apply fair-use clauses to exactly this pattern. Using an account as a CDN for content displayed on other domains is specifically named in most acceptable use policies.
Practically, it is also slow. A single shared server in one location serving video to a global audience performs poorly compared with a CDN, which is inexpensive and sometimes free.
What to use instead
A video platform for video — you get transcoding, adaptive bitrate and a player, none of which you get from a file on a web server. Object storage plus a CDN for other large files. An image service for responsive images.
How enforcement actually happens
Rarely a warning followed by a conversation. The common sequence is automated detection, then suspension, then an explanation when you open a ticket.
That ordering matters because your website goes down at the same moment. Whatever you were doing with the storage, the consequence lands on the site — and if the account is terminated rather than suspended, data recovery is at the host's discretion.
Hosts are generally reasonable about genuine misunderstandings on first offence. But the enforcement is automated and the appeal is manual, which means the site is down for however long support takes to reply.
What hosting is for
Serving website files, running the application that generates pages, storing the database behind it, and the media that is part of the site. That is a well-defined job and shared hosting does it cheaply and well.
The general principle: if a file is not served as part of a web page, it probably does not belong on web hosting. The alternatives are all inexpensive, purpose-built, and will not take your website offline when misused.
If you answer "backup / bulk file storage" in the finder, it recommends VPS/cloud with a caveat attached — that category has the most expandable storage of the four, but dedicated object storage is a better answer than any of them. That reasoning is documented on the methodology page.
Further reading
- What "unlimited" means — inodes and fair-use clauses in detail.
- Choosing a hosting type — picking the right category to begin with.
- Migrating hosts — including keeping a backup that is not on either host.