“Unlimited storage.” “Unlimited bandwidth.” “Unlimited websites.” It’s the most common promise in shared hosting — and it can’t be literal. A server has a fixed amount of disk, memory and processing power, shared by hundreds of accounts.
So where are the limits? In the terms of service, the acceptable use policy and the help articles — and they’re more specific than the marketing suggests. This guide explains the seven limits that sit behind “unlimited”, shows what three of the largest hosts’ own documents say, and gives you a checklist to find the real numbers before you buy.
Table of Contents
Why “unlimited” can’t be literal
Shared hosting puts many accounts on one server. If “unlimited” meant unlimited, a single account could fill the disk, saturate the CPU and take down every other site on the machine. So “unlimited” in hosting has a narrower meaning: the host doesn’t meter that particular resource, as long as you use it the way a typical website does.
Most sites never notice. A small business site uses a tiny fraction of what any plan allows. The limits appear when a site grows, stores a lot of email, runs heavy plugins or sends newsletters — and that’s exactly when finding them in the fine print matters.
The seven limits behind “unlimited”
1. Files (inodes)
Every file, folder and email counts as one inode, and nearly every “unlimited storage” plan caps them. It’s the limit people hit most often, because it has nothing to do with gigabytes: a WordPress site with years of cache files, image thumbnails and a busy mailbox can reach it while using only a few GB of space.
How quickly do sites get there? We counted the files in WordPress and popular plugins — and our inode calculator estimates your own site’s total.
2. CPU and processes
Shared servers limit how much processing power each account may use, and how many processes it can run at once — often called entry processes, the number of simultaneous PHP requests. When a site hits it, visitors see an error instead of the page — on servers running CloudLinux, it’s the “508 Resource Limit Is Reached” page.
3. Memory
Each account gets a memory ceiling. A plugin or import that needs more simply fails, often with a PHP error rather than a clear message.
4. Disk speed (I/O)
Separate from storage size, many hosts limit how fast an account can read and write to disk. A backup plugin or a large import that runs into it slows the whole site down while it runs.
5. Email sending per hour
“Unlimited email accounts” doesn’t mean unlimited sending. Almost every shared host caps outgoing messages per hour — usually a few hundred. It’s why newsletters sent from a hosting account stall halfway through the list. Our comparison of email limits by provider shows how the caps at Gmail, Outlook, Yahoo and iCloud compare.
6. Databases
Limits on database size, the number of tables and simultaneous connections. A large WooCommerce store or a site with many plugins can reach them long before it reaches any storage limit.
7. The “fair use” clause
Most terms include a general clause that lets the host restrict any account whose usage it considers excessive or harmful to other customers. It’s the catch-all behind every “unlimited” promise — and it’s usually defined only loosely.
What the terms actually say: three examples
These are the limits published in each host’s own documents, as of September 2026:
| Host | What’s advertised | Files (inodes) | Other published limits | Source |
|---|---|---|---|---|
| HostGator | Unlimited storage and bandwidth on shared plans | 100,000 soft limit — above it, the account is left out of weekly backups; above 200,000, it violates the Acceptable Use Policy and may be suspended | Weekly backups only for accounts under 20 GB and 100,000 inodes | Inode Limits, Account Limits Summary |
| Bluehost | Unmetered bandwidth | One help article sets a maximum of 200,000 inodes per account; another describes a 50,000 soft limit, with a Terms of Service violation above 1,000,000 files | 500 emails per hour per domain; databases up to 5,000 tables or 10 GB in total, 5 GB per database; CPU limits on all shared accounts | Account Limits Summary, Server Resource Limitations, Hosting Inode Limit |
| GoDaddy | Unlimited bandwidth; some plans with unlimited disk space and websites | 250,000 inodes per Linux account; 500,000 files per Windows account | All plans limited to 100 GB of disk; 500 SMTP relays per hour; 30 concurrent MySQL connections | Hosting Agreement, Resource limits |
None of these hosts is unusual. Limits like these exist everywhere in shared hosting; these three are simply among the largest, and they publish enough detail to compare.
When the documents don’t agree with themselves
Two details show how hard the real limits can be to pin down.
GoDaddy’s hosting agreement says some plans offer unlimited disk space — and, in the same section on storage limits, that all plans are limited to no more than 100 GB of disk storage.
Bluehost’s help center gives two different inode figures: a 200,000 maximum in one article, and a 50,000 soft limit with suspension only above 1,000,000 files in another.
Neither is necessarily wrong — the documents may cover different plans or generations of service. But a customer reading them can’t tell which number applies. That’s the practical reason to ask the host directly, in writing, before you buy.
Why hosts sell “unlimited” anyway
Because it works for most customers. Shared hosting is priced on the fact that the typical site uses very little, so a server can hold many accounts. “Unlimited” is simpler to sell than a list of numbers — and in a comparison table, “unlimited” beats “50 GB” at a glance, even when 50 GB is more than the site will ever use.
The problem isn’t the model; it’s the word. A plan that says “50 GB, 250,000 files, 500 emails per hour” and a plan that says “unlimited” may have the same real limits — but only one of them lets you plan around them.
How to find the real limits before you buy
Search the terms. Open the host’s Terms of Service and Acceptable Use Policy, press Ctrl+F and look for: inode, files, CPU, processes, per hour, database, fair use, excessive. The limits are usually there, even when the sales page doesn’t mention them.
Check the help center. Articles with titles like “account limits” or “resource limits” often contain the numbers the terms leave vague.
Ask support five questions, in writing:
- What’s the file (inode) limit on this plan?
- How many emails can I send per hour?
- What are the CPU, memory and entry process limits?
- Is there a maximum database size or number of tables?
- What happens when I reach each limit — throttling, a warning, or suspension?
After you buy, watch the dashboard. In cPanel, the Statistics panel shows file usage, and the Resource Usage page on CloudLinux servers shows when the account hit its CPU, memory or process limits.
If the file count gets close to the limit, the usual culprits are cache files, old email kept on the server, and backup copies stored inside the account — deleting those is usually enough to bring it back down. Our inode count of WordPress and popular plugins shows where the files usually come from.
What happens when you hit a limit
It depends on the limit:
- Files: uploads may fail, email may stop arriving, and — at some hosts — the account stops being included in backups.
- CPU, memory or processes: the site slows down or shows a 508 error during peaks, then recovers.
- Email per hour: messages over the limit are held or bounced until the next hour.
- Sustained excessive use: a warning, a request to upgrade, or suspension under the fair use clause.
The first four are warnings, not disasters — they tell you the site has outgrown the plan. The right response is usually to clean up, or to move to a plan with stated, larger limits — often a VPS, where the resources are yours.
Send our support team the five questions above — files, email per hour, CPU, databases and what happens at each limit — and get the exact numbers for the plan you’re considering, in writing. And when a site outgrows shared hosting, a Copahost VPS gives you dedicated resources with the limits stated up front.
See hosting plans →Frequently asked questions
Is unlimited web hosting really unlimited?
No. “Unlimited” in shared hosting means the host doesn’t meter a particular resource — usually storage or bandwidth — as long as your usage is typical. The terms of service still limit files, CPU, processes, email sending and databases, and a fair use clause lets the host restrict excessive use.
What is an inode limit?
The maximum number of files and folders an account can hold — every file, folder and email counts as one inode. It’s the limit most often hit on “unlimited storage” plans, because a site can reach it while using only a few GB of space.
What’s the inode limit at HostGator, Bluehost and GoDaddy?
According to their own documents in September 2026: HostGator uses a 100,000 soft limit and considers accounts above 200,000 in violation of its policy; Bluehost’s help articles cite both a 200,000 maximum and a 50,000 soft limit; GoDaddy’s hosting agreement sets 250,000 inodes for Linux accounts. Check each host’s current terms, as these change.
How many emails can I send per hour on shared hosting?
Usually a few hundred. Bluehost publishes a limit of 500 emails per hour per domain, and GoDaddy of 500 SMTP relays per hour. For newsletters, a dedicated email marketing service is the reliable option.
What happens if I exceed a hosting limit?
It depends on the limit: CPU and process limits slow the site or show a 508 error during peaks; file limits can block uploads and email and, at some hosts, exclude the account from backups; sustained excessive use can lead to a warning, a required upgrade or suspension.
How do I find the real limits of a hosting plan?
Search the terms of service and acceptable use policy for words like inode, CPU, per hour and fair use, check the help center’s account limits articles, and ask support in writing for the file, email, CPU and database limits of the plan you’re considering.
Conclusion
“Unlimited” in shared hosting is a promise about metering, not about physics. The limits are real — on files, CPU, processes, email and databases — and they live in the terms of service and help articles, not on the sales page. HostGator, Bluehost and GoDaddy all publish them; so does almost every other host, if you know where to look.
None of that makes shared hosting a bad deal. Most sites never come near any of these numbers. What matters is knowing them before you need them: search the terms, ask support in writing, and watch the resource panel as the site grows. The day a limit starts to matter is the day to move to a plan where the resources are stated — and yours.
