Many shared hosting plans are sold as “unlimited”, yet one day your site shows a “Resource Limit Is Reached” error or your host emails you about inode usage. That is because every shared hosting account works within limits, even when the plan does not highlight them. In this guide, you will learn what inodes, bandwidth, CPU, RAM and the other CloudLinux limits mean, how to check them in cPanel, and what to do when you hit them.
Why shared hosting has limits at all
On shared hosting, hundreds of websites can run on the same physical server. If one site suddenly uses all the CPU or memory, every other site on the server slows down. To prevent this, most cPanel hosts use CloudLinux OS, which places each cPanel account inside its own LVE (Lightweight Virtual Environment). Each LVE has a fixed ceiling for CPU, memory, processes and disk activity. Your site can use resources freely up to that ceiling, but not beyond it.
Think of it like a housing society water connection. Every flat gets water, but a limiter on each pipe ensures one flat filling a swimming pool does not leave others with dry taps.
What “unlimited” really means: fair use
When a plan says “unlimited disk space” or “unlimited bandwidth”, it normally means the provider does not set a hard number for that particular item, as long as you use it in a normal way for a website. This is covered under a fair use or acceptable use policy in the terms of service. Typical restrictions include:
- Using the account mainly for a website, not as file storage or a backup dump
- No hosting of large media files for download or streaming beyond normal use
- Staying within CPU, memory and process limits, which are almost never unlimited
- Staying under an inode limit, which many hosts set even on “unlimited” plans
Always read the fair use section of your provider’s terms. It tells you what “unlimited” means in practice for your plan.
The main resource limits explained
| Limit | What it measures | What happens when you hit it |
|---|---|---|
| CPU (SPEED) | Processor time your account can use, often shown as a percentage of one CPU core | Site slows down because processes are throttled |
| PMEM | Physical memory (RAM) used by all your processes together | Processes are stopped; visitors may see 500 or 503 errors |
| EP (Entry Processes) | Number of simultaneous connections running PHP or other scripts | Visitors see a “508 Resource Limit Is Reached” error |
| NPROC | Total number of processes running in your account, including cron jobs, SSH and email | New processes cannot start; errors similar to EP faults |
| IO | Disk read/write speed (throughput) | Disk operations are slowed down |
| IOPS | Number of disk read/write operations per second | Disk-heavy tasks slow down |
| Inodes | Number of files and folders in your account | You cannot create new files, emails or uploads |
| Bandwidth | Data transferred from your site to visitors each month | Site may be suspended or show an error until the next cycle |
CPU
The CPU limit controls how much processing power your account can use. On CloudLinux, 100% usually means the equivalent of one full CPU core. When your site reaches its CPU limit, it is not switched off. Instead, it is slowed down, so pages take longer to load. Heavy plugins, unoptimised database queries, bots crawling your site and missing page caching are common causes.
PMEM (physical memory)
PMEM is the RAM your account can use at one time. Every PHP request, cron job and email process uses some memory. If the total goes over the limit, CloudLinux stops processes to protect the server, and visitors may see a 500 Internal Server Error or 503 error. Large WordPress sites with many plugins, page builders and WooCommerce can use a lot of memory per request.
EP (Entry Processes) and NPROC
Entry processes are the number of PHP scripts or similar requests your account can run at the same moment. It is not the number of visitors to your site. A page that loads in half a second only holds an entry process for that half second. Problems start when requests are slow, because each one holds a slot longer and the slots fill up. When all slots are busy, new visitors see the 508 Resource Limit Is Reached error.
NPROC is broader. It counts every process in your account, including entry processes, cron jobs, SSH sessions, IMAP connections for email and background tasks.
IO and IOPS
IO limits how fast your account can read from and write to the disk, while IOPS limits how many separate read or write operations happen per second. Backups, large imports, image optimisation plugins and sites with many small files can hit these limits. When that happens, those tasks slow down rather than fail.
Inodes
An inode is a record for one file or one folder. A single email, a cached page, a thumbnail image or a PHP file each uses one inode. A WordPress site can easily have tens of thousands of files once you add plugins, themes, cache and image sizes. Email accounts with years of stored messages are another big source. When you reach your inode limit, you cannot upload images, receive new email or update plugins.
Bandwidth
Bandwidth, more accurately called data transfer, is the total data sent from your server to visitors over a month. Each page view, image and download adds to it. Most small sites use only a small portion of what is allowed. Large videos or downloadable files hosted directly on your account use bandwidth quickly.
How to check your resource usage in cPanel
On servers with CloudLinux, cPanel includes a dedicated Resource Usage tool. In the Jupiter theme, follow these steps:
- Log in to cPanel for your domain.
- Scroll to the Metrics section, or type “Resource Usage” in the search box at the top.
- Click Resource Usage. The dashboard tells you whether your account has hit any limits recently.
- Click Details or open the Current Usage view to see graphs for CPU, physical memory, entry processes, number of processes, IO and IOPS.
- Look for “faults”, which show how many times a limit was reached in the selected period. Change the time range to spot patterns, such as faults every night at the same time.
The right-hand Statistics panel on the cPanel home page also shows quick figures such as Disk Usage, File Usage (inodes), Bandwidth, CPU Usage, Entry Processes and Physical Memory Usage, depending on your server setup.
Tip: If you do not see Resource Usage in cPanel, your server may not run CloudLinux, or the host has hidden the feature. Ask your provider which limits apply to your account.
Common problems and fixes
“508 Resource Limit Is Reached” error
- Install a page caching plugin so most visitors get a static page without running PHP.
- Block bad bots and aggressive crawlers using your security plugin or a CDN.
- Find slow plugins and replace or remove them.
- Check for spikes in traffic to
wp-login.phporxmlrpc.php, which often indicate brute-force attacks.
High inode usage
- Clear old cache files and remove unused themes and plugins.
- Delete old backups stored inside
/home/username/and keep them on your computer or cloud storage instead. - Empty email trash and spam folders, and archive or delete old messages.
- Use the Disk Usage tool in cPanel to find folders that are unusually large.
Memory errors in WordPress
- Reduce the number of active plugins, especially heavy page builders and statistics plugins.
- Use the latest supported PHP version through MultiPHP Manager or Select PHP Version, as newer versions are often more efficient.
- Run heavy tasks such as imports or backups at night when traffic is low.
Frequently asked questions
Is “unlimited bandwidth” really unlimited?
Not in an absolute sense. It means there is no fixed monthly cap for normal website use, but fair use rules still apply, and CPU or memory limits will usually restrict you long before bandwidth does.
How many visitors can my shared hosting plan handle?
There is no fixed number. It depends on how fast your pages are generated. A well-cached site can serve far more visitors within the same entry process and CPU limits than a slow, uncached one.
Do emails count towards my inode limit?
Yes. Each email message is stored as a file, so a mailbox with thousands of messages uses thousands of inodes.
Will my site go down if I hit the CPU limit?
Usually not. Hitting the CPU limit slows your site down. Hitting the entry process or memory limit is more likely to cause visible errors.
Conclusion
Shared hosting limits exist to keep every site on the server fast and stable. Once you understand CPU, PMEM, entry processes, NPROC, IO, IOPS, inodes and bandwidth, the errors and warnings start to make sense. Check the Resource Usage page in cPanel regularly, fix the common causes like missing caching and old files, and upgrade to a bigger plan or VPS only when your optimised site still needs more room.
