Quick Answer (TL;DR)
"Unlimited websites" on a shared plan means unlimited domain slots, not unlimited server capacity. The limits that actually stop you are CPU, RAM, inode count, and hourly email volume — all typically published in a separate terms page rather than the pricing table. A plan allowing 100 websites is only useful if your sites collectively stay under those resource ceilings. For most small portfolios it does; for anything resource-heavy it doesn't.
Key Takeaways
- "Unlimited" refers to domains, not resources. You're buying permission to host more sites on shared infrastructure with fixed ceilings.
- Inodes are the hard stop. Every file and directory counts, and a single large site can consume a substantial share of a typical allowance.
- Email sending is capped separately. Unlimited mailboxes with an hourly send limit is a common combination.
- Cheap "unlimited" plans suit portfolios, not stores. Multiple small sites fit comfortably; one traffic-heavy site will hit CPU limits first.
- Backups are not unlimited anywhere. Storage for your own site files is separate from the storage you need to survive a failure.
What Does Unlimited Website Hosting Actually Mean?
The label describes a plan tier, not a technical capability. In practice, a plan sold this way gives you three things:
- Multiple domain slots. You can point several domains at one hosting account, sometimes dozens or hundreds.
- Multiple subdomains. Usually unlimited or a high fixed number.
- Multiple installations. Separate WordPress installs, separate databases, all under one billing account.
What it does not give you is a server that scales with the number of sites you add. Every site you install draws from the same fixed pool of CPU, memory, and disk. Adding a tenth site doesn't add capacity — it divides the existing capacity ten ways.
That distinction is the whole game. A plan with a 100-site allowance and a 1-core CPU limit is, functionally, a one-site plan for anyone running a database-driven site with real traffic.
The four numbers buried in the terms
Before any purchase, find these four figures. They appear on a terms or acceptable use page, not on the pricing table:
- Inode limit. The total count of files and directories on your account. Emails, cache files, and thumbnails all count.
- CPU and memory allocation. Sometimes stated as a share of a core, sometimes as a concurrent process limit.
- Hourly email send cap. Typically in the low hundreds per hour on shared plans, regardless of how many mailboxes you're given.
- Database size or table limits. Less commonly published, but frequently enforced.
What's Actually Unlimited — and What Isn't
The table below reflects the common pattern across published shared-hosting terms. Specific providers vary, sometimes significantly — confirm each line against the provider's current acceptable use policy.
| Resource | Usually marketed as | Actual typical status |
|---|---|---|
| Domains / websites | Unlimited | Genuinely open — high or no cap on domain slots |
| Subdomains | Unlimited | Usually open |
| Disk storage | Unlimited | Capped indirectly by inode limits and fair-use policy |
| Bandwidth | Unlimited | Capped indirectly by CPU and connection limits |
| Inodes (files + folders) | Rarely mentioned | Hard cap, often in the low hundreds of thousands |
| CPU / RAM | Not mentioned | Hard cap, enforced by throttling |
| Email accounts | Unlimited | Mailboxes open; sending is rate-limited per hour |
| Databases | Unlimited | Count usually open; size and concurrent connections capped |
| Backups | Included | Retention window limited; restores may be charged |
| SSL certificates | Free / unlimited | Genuinely free via Let's Encrypt on most providers now |
Read that table twice. The two rows people actually hit are inodes and CPU — and neither appears in the marketing copy.
Why Inodes Are the Real Ceiling
An inode is a file or a directory. Every image, every theme file, every plugin, every cached page, every email sitting in a mailbox on the server counts toward your total.
A clean WordPress install uses a few thousand inodes. Add a page builder, a caching plugin, an image library with multiple thumbnail sizes per upload, and routine backups stored locally, and a single site can climb into the tens of thousands quickly. Multiply by ten sites on an "unlimited" plan and you approach typical caps without doing anything unusual.
When you hit the limit, the failure mode is unpleasant: new uploads fail, plugins can't write files, and in some cases the account is suspended until you delete files. It's not a graceful degradation.
Practical mitigation: store backups off-server rather than in your hosting account, limit the number of image thumbnail sizes your theme generates, and clear cache and revision data on a schedule. Those three habits alone can cut inode usage substantially.
When "Unlimited Websites" Makes Sense — and When It Doesn't
Good fit
- Agency or freelancer portfolios. Several low-traffic client sites, each small, collectively modest in resource use.
- Multiple brochure sites for one business. Location pages, product microsites, campaign landing pages.
- Staging and development copies. A test install alongside the live one, same account, no extra billing.
- Personal projects. Side blogs and experiments that don't need guaranteed resources.
Poor fit
- Any online store taking transactions. A WooCommerce install with a product catalogue and real order volume will hit CPU limits during sales.
- Membership or LMS sites. Logged-in users generate uncacheable database queries — the most expensive kind.
- One high-traffic site plus several others. The busy site consumes the shared pool and the others suffer alongside it.
- Sites holding regulated customer data. Shared infrastructure rarely comes with the compliance documentation you need.
How to Test an Unlimited Hosting Claim Before You Buy
You can verify most of a provider's claims without spending money, and the rest inside the refund window.
- Open the acceptable use policy. Search it for "inode", "CPU", "memory", and "fair use". If those words appear with numbers attached, you've found the real limits.
- Check the pricing table footnotes. Renewal rates, term requirements, and "unlimited" disclaimers are usually there in small text.
- Look for a published status page. A provider that doesn't publish incident history is asking you to take uptime on faith.
- Buy the shortest term available. Monthly if offered, otherwise annual. Never prepay three years to test a claim.
- Upload a real site immediately, with your actual plugin set and image library — not a placeholder.
- Watch the resource meter in the control panel for a week. Many hosts publish live CPU and inode usage.
- Run a restore before the refund window closes. A backup you haven't restored is a hope, not a backup.
Unlimited Shared Plans vs the Alternatives
| Plan type | Site allowance | Resources | Renewal behaviour | Fits |
|---|---|---|---|---|
| Shared "unlimited websites" | High or open | Fixed pool, shared with neighbours | Sharp increase after initial term | Portfolios, brochure sites |
| Managed WordPress (multi-site tiers) | Often 1–5 per tier | Dedicated per-site resources | Usually stable, fewer promos | Business sites, service providers |
| Managed cloud | Depends on server size | Allocated, scalable on demand | Pay-as-you-go, no cliff | Growing sites needing headroom |
| VPS / unmanaged | As many as fit | Full server, your responsibility | Flat | Technical owners with dev support |
The honest summary: if you need more than five sites and none of them is resource-heavy, a shared unlimited plan is genuinely good value. If any single site carries real traffic, the site count is irrelevant — you need allocated resources, not more domain slots.
Where Backups Fit — the Limit Nobody Advertises
No hosting provider offers unlimited backups, and that's the gap most unlimited-plan buyers discover late.
Host-side backups typically run on the same infrastructure as your live sites, with a limited retention window — often somewhere between a few days and a month. They're designed to recover from a bad plugin update, not from account suspension, a billing dispute, a provider-wide outage, or a company changing hands. Restore fees are also common on budget tiers, which is an unwelcome discovery mid-emergency.
The working standard remains 3-2-1: three copies of your data, two media types, one off-site. For a multi-site account, that third leg means storing your own exports somewhere independent of the host — with separate credentials and separate billing.
GotBackup is one service in that category. The vendor advertises AES-256 encrypted storage, automated backup across Windows, Mac, iOS, and Android, and plans from 6 TB upward. I have not tested it, and to be precise about scope: it is an encrypted backup and storage service, not a web host — it holds your site exports and files, it doesn't serve your websites. If you want to see what the GotBackup encrypted storage plans currently include, the vendor publishes its tiers and terms directly.
What I Could Verify — and What I Could Not
Verified from published hosting terms
- That "unlimited websites" plans generally place no cap on domain slots while capping underlying resources.
- That inode limits, CPU allocation, and hourly email send caps are standard on shared plans and documented in acceptable use policies.
- That disk and bandwidth "unlimited" claims are constrained indirectly by those resource caps.
- That promotional entry pricing typically requires multi-year prepayment and resets on renewal.
- That backup retention windows are limited on shared tiers and restore fees are common.
Not verified — treat as open questions
- Exact inode, CPU, and memory figures for any named provider. These vary and change; check the policy directly.
- How aggressively throttling is enforced. Some hosts warn first, others suspend. Not publicly documented in most cases.
- Real-world performance across multiple sites. Requires live testing I did not perform.
- Actual uptime and restore success rates. Advertised percentages are claims, not measurements.
- Support responsiveness at different tiers and times of day.
- Current prices. Promotions shift weekly and vary by region.
Before-You-Buy Checklist
- Find the inode limit and estimate your total across all planned sites before buying.
- Locate the CPU and memory allocation. If it isn't published anywhere, treat that as a warning sign.
- Check the hourly email send cap if you'll use host mailboxes for customer correspondence.
- Confirm backup retention and whether restores carry a fee.
- Note the renewal price and calculate your three-year total, not your first-year total.
- Buy the shortest term available so you can leave if the plan doesn't hold up.
- Set up independent off-site backups on day one, before any site goes live.
Pros and Cons of Unlimited Website Hosting Plans
Pros
- Genuinely economical if you run several small sites — one bill covers all of them.
- No per-domain fees, which matters for agencies and multi-location businesses.
- Simple to manage: one control panel, one set of credentials, one renewal date.
- Free SSL and one-click installs are standard at this tier now.
- Low risk to trial, particularly inside a money-back window.
Cons
- The word "unlimited" obscures hard caps that decide whether your sites actually stay online.
- All sites share one resource pool, so one busy site degrades the rest.
- Renewal prices climb sharply after the promotional term.
- Backups are time-limited and restores may cost extra.
- Scaling means migrating to a different plan type entirely, not adding capacity.
Who Should Consider Unlimited Plans — and Who Should Avoid Them
Consider one if:
- You run several small, low-traffic sites and want one simple account.
- You're an agency hosting lightweight client brochure sites.
- You need staging copies and test installs without extra billing.
- You'll monitor resource usage and migrate the busy sites out as they grow.
Avoid one if:
- Any of your sites takes payments, bookings, or member logins.
- You expect seasonal traffic peaks that would hit CPU limits.
- You need a published SLA or compliance documentation.
- You'd rather not think about inode counts — allocated resources suit you better.
Frequently Asked Questions
Is unlimited website hosting really unlimited?
No. The "unlimited" label refers to the number of domains or websites you can host on one account. Storage, bandwidth, CPU, memory, inodes, and email sending all carry limits, usually documented in the acceptable use policy rather than the pricing page.
How many websites can I actually host on an unlimited plan?
Technically as many as your inode and CPU allowances support. A dozen small brochure sites may fit comfortably; two medium WordPress sites with large image libraries might exhaust the same allowance. The site count matters less than the total resource consumption.
What happens if I exceed an inode limit?
Typically uploads fail, plugins can't write files, and some hosts suspend the account until usage drops. Enforcement varies by provider and is usually described in the terms rather than demonstrated in advance. It's rarely a graceful warning-first process.
Does unlimited hosting slow down my site?
Not inherently, but shared plans place your site alongside others on the same server. When neighbouring accounts spike, your available CPU and memory can drop. That's why load times on shared hosting tend to be inconsistent rather than uniformly slow.
Can I run an online store on an unlimited website hosting plan?
You can install one, but it's a poor match. Ecommerce generates uncacheable database queries, and order volume produces exactly the CPU spikes that shared plans throttle. Managed or cloud hosting is the appropriate tier for stores handling live transactions.
Are unlimited email accounts actually usable?
Mailbox creation is usually unrestricted, but sending is rate-limited — commonly to a few hundred messages per hour across the account. That's fine for normal correspondence and unsuitable for newsletters or transactional email, which belong with a dedicated sending provider.
Do I still need separate backups on an unlimited plan?
Yes. Host backups are time-limited and live on the same infrastructure as your sites, so they don't protect against account suspension, billing disputes, or provider failure. An independent off-site copy is the only version you fully control.
Final Verdict on Unlimited Website Hosting
Unlimited website hosting is a fair deal for the right buyer and a misleading label for everyone else. If you're hosting a handful of small sites and you understand that the domain slots are open while the server resources are not, a shared unlimited plan delivers real value for a low monthly cost.
If any of your sites carries business weight — transactions, bookings, logins, seasonal peaks — the site allowance is irrelevant. What you need is allocated CPU and memory, a published uptime commitment, and a backup policy you've read. Those come with managed plans, and they cost more because they're a different product.
The practical move: buy the cheapest term available, check the inode and CPU figures before you install anything, keep your own off-site copies from day one, and plan to move your busiest site to allocated hosting as soon as it earns the upgrade. That approach treats "unlimited" as what it is — a marketing tier, not a resource guarantee.