Is Unlimited Hosting Really Unlimited? Where the Limits Start
What is unlimited hosting, and is it really unlimited?
Unlimited hosting is a shared hosting plan that sets no fixed cap on items such as disk space, bandwidth or the number of websites. However, it is not truly unlimited. Every server has finite CPU, memory and disk speed, so the provider still caps usage through fair use terms and hidden resource limits.
We are Talha Aslan and team, a digital marketing and web design team, not a hosting company. So we do not praise or criticise any provider in this guide. Our goal is simple: to show you what to check when a plan page says "unlimited". We base the technical part on the official documentation of common platforms such as CloudLinux. For the advertising part, we point to published regulator guidance.
In short, "unlimited" is a marketing frame rather than a product feature. The numbers that really decide your capacity often sit in the small print, or nowhere at all. Once you know those numbers, you can tell much more clearly whether a plan fits your site.
Why can no server be physically unlimited?
Every shared hosting account eventually runs on a real physical server or on a virtual machine that slices one. That machine has a fixed number of CPU cores, a fixed amount of RAM and disks with a fixed capacity. Therefore, the combined usage of hundreds of accounts on one server can never exceed what the hardware delivers.
Disk space follows the same logic. Larger disks cost more, and backups take up space too. On the traffic side, the server's network uplink also has a maximum speed. We explain what bandwidth actually means for hosting in our hosting bandwidth guide.
Moreover, the limit does not stop at total capacity. A disk can only handle a certain number of read and write operations per second. In other words, even with free space on the disk, everyone slows down when many sites read files at the same moment. For that reason, providers set per-account ceilings so one account cannot choke the rest. Those ceilings stay in place even when the plan page says "unlimited".
Why do hosting providers use the word "unlimited"?
The unlimited hosting business model relies on statistical sharing of resources. Most sites on a shared server are small business pages, personal blogs and low-traffic projects. These sites use only a small slice of the disk and traffic available to them. As a result, a provider can place more accounts on the same hardware than the raw capacity would suggest on paper.
That approach is not wrong in itself; it is what keeps prices low. The problem lies in how providers communicate it. In practice, "unlimited" means an average site will rarely hit a ceiling. On the day your site stops behaving like an average site, though, the hidden limits kick in.
On the other hand, the "unlimited" label also makes comparison harder. If two plans both promise "unlimited disk", the real difference comes down to CPU, memory and concurrent process limits. A plan page that hides those values hides the most useful information. We list the criteria worth comparing in our guide on how to choose web hosting.
What does a fair use policy actually mean?
A fair use policy is the contract clause that explains when the provider will restrict a resource it calls "unlimited". You usually find it in the terms of service or in the acceptable use policy. The wording tends to rely on broad phrases such as "usage that harms server performance" or "usage outside the purpose of the plan".
That vagueness matters, because it leaves the decision with the provider. A clause without a concrete threshold means you cannot know in advance where the provider will step in. So when you read a fair use clause, check three things:
- A measurable threshold: Does the clause mention a percentage, a file count or a process count?
- A defined purpose: Does it rule out file storage, backup archives or media hosting in plain words?
- A notice process: Will the provider warn you before it restricts the account, or suspend it straight away?
If those three answers stay vague, "unlimited" in practice means "at the provider's discretion". That alone does not prove poor service. Still, it makes planning much harder for you.
Which hidden limits apply to unlimited hosting plans?
On unlimited hosting plans, account-level resource limits decide your real capacity. The official CloudLinux limits documentation defines these values one by one, and CloudLinux is common on shared servers. In summary, these items matter most:
- SPEED (CPU): The processing power your account may use, expressed relative to a single core.
- PMEM (physical memory): The total RAM that processes in your account can use.
- IO and IOPS: Disk throughput, plus the number of read and write operations per second.
- EP (entry processes): According to the docs, this usually represents concurrent connections.
- NPROC: The maximum number of processes your account can run at once.
- Inodes: The count of files and folders your account holds.
Each of these limits deserves its own article, so here we only touch on how they relate to the "unlimited" label. If you want to know how providers isolate accounts from each other, read our piece on CageFS account isolation. The key point stays the same: even under "unlimited disk", these six values decide your site's real speed and resilience.
What is an inode limit, and why is "unlimited disk" not enough?
An inode is the record a Linux file system keeps for every file and folder, and it is where many unlimited hosting plans quietly draw a line. Every image, every cache file and every stored email in your account uses one inode. So even with "unlimited" disk space, your plan can still cap the number of files.
In practice, that difference matters a lot. For example, a large WordPress site can generate tens of thousands of small cache files through caching plugins. Those files take little space, yet they fill the inode counter quickly. Old mailboxes that nobody cleans up do the same, because the server stores each message as a separate file.
Once you approach the inode limit, you cannot create new files. As a result, a plugin update may fail halfway, new emails may bounce, or a backup job may stop with an error. That is why one of the first questions on any "unlimited disk" plan is whether an inode limit exists and what it is. Your control panel usually shows your current inode count in its statistics area. Checking that number regularly prevents unpleasant surprises.
How does an email sending limit affect your website?
Many unlimited hosting plans that promise "unlimited email accounts" still cap how many messages you can send per hour or per day. The reason is simple. Bulk mail from a shared server can land the server's IP address on blocklists, and then every account on that server suffers. Hosting control panels also let administrators set an hourly sending cap per domain.
This cap matters most for online stores and membership sites. Order confirmations, password resets and form notifications all draw from the same quota. For instance, if you send a newsletter on a campaign day, order emails may sit in the queue during that same hour.
So we recommend that you do not send bulk newsletters from your hosting server. For transactional email, a verified SMTP service keeps you under the cap and also improves deliverability. We cover the WordPress setup in our WP Mail SMTP guide. Sender reputation is the topic of our email deliverability guide.
Which MySQL limits show up on shared plans?
"Unlimited databases" usually refers to the number of databases, not their capacity. What really affects your site is how many connections you can open at once and how many resources your queries consume.
MySQL has system variables such as max_user_connections that cap concurrent connections per user. On shared servers, the administrator sets such values for all accounts, and you cannot change them. In addition, long-running queries also draw on your CPU and IO limits. A slow query can therefore hit database limits and account limits at the same time.
In practice, watch for these signs: "too many connections" errors at busy hours, a sudden slowdown in the admin area, and search pages that time out. Query tuning and caching remove many of these symptoms. Still, if you run a database-heavy application, a shared plan offers only limited room to grow.
What restrictions apply to backups and stored files?
Many unlimited hosting terms of service ask you to use hosting space for website files only. Personal archives, large video files or backups from other servers may count as a breach of the fair use clause. Therefore, "unlimited disk" does not mean "store any file you like without limit".
You will see similar restrictions on backups. Some providers leave accounts above a certain size or file count out of automatic backups. Others count backups against your own quota. Moreover, a provider backup is often a goodwill extra rather than a guarantee.
So do not leave your backups to the provider alone. A copy in a separate location keeps your data within reach even if the provider suspends the account. We walk through the full plan in our website backup strategy guide.
Where do you find "unlimited" in the terms of service?
The plan page gives a summary. The binding text, however, is the service agreement and the policies attached to it. You usually find these documents in the site footer under labels such as "terms of service", "terms and conditions" or "acceptable use policy".
Your browser's search function makes the reading much faster. Search for these words one by one:
- "unlimited": Is there a footnote or an exception right next to the word?
- "fair use" or "reasonable use": Does the text say when restrictions start?
- "inode" or "file count": Does the plan carry a separate file ceiling?
- "suspend" or "terminate": Does it state when the provider may stop the account and how much notice you get?
- "email" and "per hour": Does it mention a sending cap?
- "backup": Does it describe the scope and retention of automatic backups?
If these searches return no clear numbers, ask the provider in writing before you buy. A written answer is the strongest record you can hold if a dispute ever comes up.
What happens when you hit a limit: throttling or suspension?
The outcome depends on which limit you hit. According to the CloudLinux documentation, the system does not kill processes at the CPU and IO limits; it throttles them instead. Your site still loads, but pages take noticeably longer. Visitors simply experience a slow site.
When you exceed the entry process (EP) limit, the docs say the server returns a 508 "Resource Limit Reached" error. At memory or process limits, visitors may see 500 or 503 errors, because the server cannot run the script. At the IOPS limit, read and write operations wait until the current second ends.
Suspension, on the other hand, is an administrative decision rather than an automatic technical response. A provider may stop your account if it decides your usage keeps straining the server or breaches the terms. Some providers send a warning first, while others act right away. Reading the suspension procedure in advance is the easiest way to avoid a nasty surprise on a launch day. We cover other server-side causes in our article on why a website is slow.
How can you tell that you are hitting a limit?
The first clue is irregular behaviour. If the site runs fast at night but slows down at lunchtime or after a social post, you are probably touching a resource ceiling. Also, a 508 error points almost directly at the entry process limit.
On cPanel servers with CloudLinux, the panel usually includes a resource usage screen. It shows which limits you reached in recent days and how often. You can read that data like this:
- Frequent CPU or IO faults: Start with caching, image optimisation and a plugin clean-up.
- Frequent EP faults: Too many requests arrive at once, so check bot traffic and uncached pages.
- Memory faults: A heavy plugin or a long-running task may be filling up memory.
If that screen is missing, ask support for a recent limit report. It also helps to confirm which server your domain points to with our DNS lookup tool and to include that detail in your ticket.
Why do sales and launch days test unlimited hosting first?
The hidden limits of unlimited hosting rarely show on ordinary days, because average traffic stays below the ceilings. The trouble starts when traffic multiplies within minutes. A discount campaign, a TV spot or a viral social post can send hundreds of visitors to your site in the same minute.
In those moments, the entry process limit usually gives way first. CPU throttling and the database connection cap follow. In other words, "unlimited bandwidth" may describe your monthly data transfer correctly, yet it says nothing about how many visitors the plan can serve at once.
So before you spend an ad budget on a campaign, ask the provider about your limits and test your caching. Otherwise, the clicks you pay for may land on a page that does not load. In our Google Ads management work, we add a load check of the landing site to the pre-launch list. We cover preparation for traffic spikes in a separate article in this series.
How do limits differ between shared hosting and a VPS?
On shared hosting, you split resources with other accounts and the provider sets the limits. A VPS, by contrast, states your virtual cores, memory and disk up front. As a result, you will rarely see "unlimited" on VPS plans, because the product itself comes defined in numbers.
That difference gives you a real planning advantage. On a VPS, your own monitoring shows which resource will run out and when, and you can scale just that resource. That freedom, however, also hands you security updates, backups and server software maintenance.
Put simply, a VPS removes the "unlimited" ambiguity but replaces it with management responsibility. If your site regularly outgrows a shared plan and you have technical people, the move can make sense. Without such a team, a managed VPS or a higher-limit shared plan is often the safer step. Our VPS, VDS and cloud server comparison explains the options.
What do advertising rules say about unlimited hosting claims?
We have not found a regulation written specifically for hosting, but advertising regulators have looked closely at the word "unlimited". In the UK, the Advertising Standards Authority publishes advice on "unlimited" claims for broadband and telecoms services.
According to that advice, "unlimited" claims are likely to be acceptable if legitimate users face no extra charge or suspension for exceeding a fair use threshold. It also says any provider-imposed limits should be moderate only and clearly explained in the ad. That guidance targets telecoms, not web hosting. Still, it shows how a regulator reads the word: as a promise the average customer can rely on.
Rules differ by country, and this section is general information, not legal advice. If you think a hosting ad misled you, speak to a lawyer or to your local consumer protection body about the right route.
Which questions should you ask a provider before you buy?
Clear written questions turn the "unlimited" ambiguity into concrete numbers. You can paste the list below into a support ticket or a sales email as it stands:
- What are the per-account CPU, physical memory and IO limits on this plan?
- What are the entry process (EP) and process count (NPROC) limits?
- Is there an inode or file count ceiling?
- What is the hourly and daily email sending limit?
- Do you cap database size or connections per user?
- How often do you take automatic backups, and which account sizes fall outside them?
- Do you warn customers before you throttle or suspend an account?
- Can I move to a higher plan instantly, and will that cause downtime?
A provider that answers clearly knows its product and works transparently. If the answers stay at the "unlimited, don't worry" level, that tells you something too. We describe the upgrade process itself in our guide to upgrading a hosting plan without downtime.
Unlimited hosting vs a plan with clear limits
The table below compares two ways of writing a plan, not any specific company. The point is to show how the same information, presented two ways, changes your decision.
| Item | Plan labelled "unlimited" | Plan with clear limits |
|---|---|---|
| Disk space | Unlimited, subject to a fair use clause | States a fixed value |
| File count (inodes) | Often missing from the plan page | States a clear ceiling |
| CPU and memory | Usually not stated | States the core share and memory |
| Entry processes (EP) | Usually not stated | States a number |
| Email sending | Says "unlimited accounts"; the sending cap sits in the terms | States an hourly sending cap |
| Result of hitting a limit | At the provider's discretion | Defines a warning and an upgrade path |
| Ease of comparison | Low; key values stay hidden | High; values sit side by side |
When you use the table for your own comparison, fill each row with the provider's written answer. Empty cells show you which questions remain open. For example, if one provider lists EP and inode values while another only says "unlimited", weigh the price gap against that missing information. The cheaper-looking plan can create migration costs later.
In short, the plan with clear limits may seem to promise less, but it gives you a basis for planning. An unlimited hosting plan can suit an average site well, yet you only learn where its ceiling sits by hitting it.
Which type of website really needs unlimited resources?
The honest answer is none. No website needs unlimited resources. Every site needs a certain amount, and you can measure that amount. The right question is not "is it unlimited?" but "how much does my site need, and what happens when it grows?"
You can think about site types roughly like this:
- Company brochure site: Few pages and low traffic; an entry-level shared plan is usually enough.
- Blog or content site: Traffic comes in waves, so caching and inode tracking matter.
- Online store: Database-heavy, with concurrent sessions and email caps playing a critical role.
- Web app or SaaS: Runs its own processes, so shared hosting is often a poor fit.
We discuss store hosting criteria separately in our WooCommerce hosting guide.
How do you plan your own resource needs?
Resource planning starts with your own site data instead of trust in an "unlimited" label. If your site already exists, your panel's usage history, monthly traffic and file count make the best starting point.
As a sample calculation, think of it this way. First, note the inode count your site uses today and the entry process value on your busiest days. Then estimate how much your content or product count will grow over the coming period, and scale those values by that rate. This rough sum is not a guarantee, yet it shows in advance which plan will feel tight.
When you run that calculation, look at your peak day, not just the average. After all, you hit limits at peak moments, not on quiet days. Also factor in how media files, product images and mailboxes grow over time. Checking these values every six months tells you whether your plan still fits.
For a new site, similar sites offer a rough guide. Here too, the safest route is a plan that upgrades easily, so you can scale up instead of moving house. A fast, lean build also cuts resource needs from day one. That is why we plan performance at the design stage in our web design projects.
When should you leave the work to your hosting provider?
On shared hosting, you have no access to server settings anyway; the administrators set the limits. Reading limit reports is your job, but changing server-side settings belongs to the provider. Keeping that line clear saves time and prevents risky changes.
Hand the issue straight to the provider in these cases:
- The provider suspended your account and the reason is unclear.
- The limit report points to overall server load rather than your own site.
- Email sending stopped because of a blocklist and the IP reputation suffered at server level.
- The database server does not respond at all.
Site-side optimisation, by contrast, stays with you: plugin clean-up, caching, image sizes and unnecessary cron jobs. Moving to your own VPS is a separate decision. If you are not ready to take on security and maintenance, a managed shared plan remains the more sensible choice. If you wonder how CloudLinux licensing works, see our CloudLinux license guide.
Summary: read the limits table, not the label
In hosting, "unlimited" is marketing language, not a capacity figure. Hardware has limits, and providers enforce them through fair use terms and account-level resource caps. That model keeps prices low, but without transparency it makes planning hard.
When you decide, follow this order. First, measure what your site needs. Next, search the terms for "unlimited", "fair use", "inode" and "suspend". After that, send your written questions to the provider and place the answers in a comparison table. That way, you put real values side by side instead of plan labels.
Finally, the advertising section above is general information, not legal advice. On the technical side, an unlimited hosting promise does not protect you on its own; measurable limits, regular backups and an easy upgrade path do.
