| Unlimited storage hosting does not remove your storage limit, it moves it. Shared plans cap the number of files you can store, called inodes, and apply a fair use clause in the terms of service. Most small sites never reach either limit, but mailboxes and stored backups reach them fast. |
Unlimited storage is one of the oldest phrases in hosting, and it is also one of the most misread. No provider owns infinite disks. What the phrase describes is a billing model: you are not charged per gigabyte, and no counter stops you at 50GB. The limits still exist. They are simply written in a different unit, and they live in the acceptable use policy rather than on the pricing table. The pattern repeats across the industry, exactly as it does with monthly bandwidth allowances.
This guide explains the three limits that really bind an unlimited plan, shows you how to measure your own usage in two minutes, and sets out the point at which unlimited stops being the right answer.
What unlimited storage hosting really means?
A hosting provider sells space on a server with a finite disk. When a plan is advertised as unlimited, the provider is making a statistical bet rather than a technical promise. Most sites on a shared hosting server use very little space, so uncapped gigabytes can be offered to everyone while the average stays low.
That bet works because normal websites are small. A brochure site with 30 pages and 200 optimised images rarely passes 2GB. A busy WordPress blog with several years of posts often sits under 10GB. The model only breaks when a handful of accounts behave nothing like the average, and the fair use clause exists precisely to manage those accounts.
So the honest reading is this: unlimited means uncounted in gigabytes, and capped in other ways.
The three limits that actually apply
| Limit | What it counts | Where it is written | Who hits it |
| Inode limit | The number of files and folders, not their size | Plan feature list, WHM package, knowledge base | Mail heavy accounts, large plugin stacks, cached sites |
| Fair use clause | Disk used for material unrelated to a live website | Acceptable use policy in the terms of service | Accounts used as file storage, media libraries or archives |
| Backup exclusion | How much of your data the provider will include in its own backups | Backup policy page or JetBackup settings | Any account that grows past the backup ceiling |
Of the three, the inode limit surprises people most, because it has nothing to do with how big your website is.
What an inode is, in plain terms?
An inode is a record on the filesystem, used by ext4 and similar Linux filesystems to track a single item. Every item on your account consumes one, whatever its size.
- One HTML page uses one inode. One 40MB video file also uses one inode.
- One folder uses one inode, even when it is empty.
- One received email message uses one inode, because IMAP mailboxes in Maildir format store each message as a separate file. Attachments travel inside that file.
- A WordPress core installation contains several thousand files before you add anything. Individual plugins commonly add several hundred more.
- A node_modules folder from a JavaScript build can hold tens of thousands of tiny files by itself, which is why build folders should never be uploaded to a hosting account.
This is why an account can sit far below its disk usage and still be refused new files. A small business running five mailboxes with ten years of correspondence can hold hundreds of thousands of tiny files totalling under 3GB. Measured in gigabytes that account is trivial. Measured in inodes it is one of the heaviest on the server.
How to check your own usage in two minutes?
In cPanel, open the statistics panel on the right of the main dashboard. Disk Usage shows gigabytes. File Usage shows inodes. Read the second number, not the first, because the second is the one that stops you.
With SSH access, two commands answer the question directly.
| # total inodes used by the current account find . -xdev | wc -l # the ten folders holding the most files for d in */; do echo “$(find “$d” | wc -l) $d”; done | sort -rn | head |
Run the second command from your home directory. In most accounts near a limit, the top result is the mail folder, a cache folder, or an old staging copy that nobody deleted after launch.
When unlimited genuinely does not matter?
It is worth saying plainly, because most hosting content will not: for the majority of buyers, unlimited storage is a real and useful feature. If you run a company website, a portfolio, a local service business or a blog, you will never approach an inode ceiling, and paying more for a metered plan with a printed gigabyte figure buys you nothing.
The feature becomes a problem only in specific patterns of use.
| Site pattern | Storage risk | What to do |
| Brochure or business site | Very low | Unlimited shared hosting is the correct fit |
| WordPress blog with images | Low | Serve WebP, keep the plugin count lean, purge old revisions |
| Store with thousands of product photos | Medium | Offload media to object storage or serve it through a CDN |
| Five or more busy mailboxes | High, inode driven | Archive mail locally, or move email to a dedicated mail plan |
| Stored backups kept on the account | High | Move backups off the server, which is also safer |
| Media library or file sharing use | Breaches fair use | Use object storage, not web hosting |
The last row is the one that ends accounts. A fair use clause is not aimed at websites that grew, it is aimed at accounts being used as a hard drive. Storing a video archive on a hosting plan because the plan says unlimited is the clearest way to trigger a suspension notice. Hosting large video from your own server also consumes bandwidth at a rate that dwarfs everything else on the account.
Backups are the limit nobody reads
Most providers, Bisup included, run automated backups on shared servers, commonly through JetBackup or a comparable system. Backup platforms almost always carry a size ceiling of their own, because copying a very large account every night is expensive in disk and in time. Our post on why backup is necessary covers the wider failure patterns.
The result is a gap that appears only when you need it most. Your account is allowed to grow past the backup ceiling, so it does. Then the site breaks, you open a ticket, and you learn the last automated copy excluded your account for being oversized. Unlimited storage and unlimited backup are not the same promise, and they are rarely on the same page of the website.
Keep your own copy. A weekly download, or an offsite copy to storage you control, costs almost nothing and removes the dependency entirely.
Five questions to ask before you buy
- What is the inode limit on this plan, as a number?
- Is there a soft warning threshold before the hard limit, and where is it shown?
- Does email count towards the same inode pool as the website?
- What is the maximum account size the automated backup will include?
- What does the acceptable use policy say about non-website files, and what notice is given before action?
A provider that answers all five in writing is telling you the truth about the plan. A provider that answers only the first is selling you the word rather than the service. Apply the same test to the rest of the pricing table using how to choose a hosting plan without overpaying.
When to move up from shared hosting?
Storage is rarely the first reason to leave shared hosting, but it is a reliable early signal. Move when two or more of these are true.
- You sit within roughly 20 percent of the inode limit and the number keeps climbing.
- Your account is too large for the automated backup to include.
- You have already offloaded media and cleared old staging copies, yet the number has not fallen.
- You need control of the filesystem itself, for example cron driven archiving or custom retention.
At that point a cloud VPS is the honest answer, because you get a defined disk you can size and grow rather than an undefined disk with hidden edges. If those conditions do not hold, stay where you are. Compare hosting types on workload instead of on storage claims, and check Bisup plans or VPS options on CPU, memory and support quality, which are the numbers that decide your experience.
Frequently asked questions
No. It is a billing model rather than a technical claim. You are not charged per gigabyte and no counter stops you at a set size. The real limits are the inode count and the fair use clause, both published rather than hidden, although rarely on the pricing page.
An inode limit caps the number of files and folders on your account rather than their total size. Every file, folder and stored email message consumes one inode. A small account can hold hundreds of thousands of tiny files and reach the limit while using only a few gigabytes.
On most shared plans, yes. Mailboxes sit on the same account filesystem as the website, and Maildir format stores each message as a separate file, so every message consumes an inode from the same pool. Heavy email use is the most common cause of exhaustion.
No. Acceptable use policies restrict the account to files supporting a live website. Storing video archives, personal media or general backups is the usual trigger for a fair use warning, even when disk space is technically available.
In cPanel, read the File Usage figure in the right hand statistics panel rather than Disk Usage. Over SSH, run find . -xdev | wc -l from your home directory. Compare the result against the inode figure your provider publishes for the plan.
