Web hosting limits are the caps a hosting plan places on what your account can use, and every plan has them, including plans marketed as unlimited. Hosts enforce limits on storage, bandwidth, files, CPU, memory, concurrent processes, and email sending. This guide defines the seven limits that matter, gives their typical thresholds on shared plans, and shows you where to find them before you buy.
Why Do Hosting Plans Have Limits?
Hosting plans have limits because servers have finite resources that many customers share. A shared server splits one machine's CPU, memory, and disk across hundreds of accounts, so the host caps each account to stop one busy website from slowing down its neighbors. Limits protect you as much as they restrict you: on a well-run server, the account next to yours cannot consume the resources your site needs.
Limits also define the upgrade ladder. Shared plans carry the tightest caps, VPS plans reserve fixed CPU and RAM for you alone, and cloud plans lift caps in exchange for usage-based billing.
What Are the Seven Hosting Limits That Matter?
The seven hosting limits that matter are storage, bandwidth, inodes, CPU, memory, entry processes, and email sending. Each one can take your site offline or degrade it when exceeded.
Storage
Storage caps the total disk space your files and databases occupy. Shared plans commonly include 10 GB to 100 GB. A typical WordPress site with moderate media uses under 5 GB, so storage is rarely the first limit you hit unless you upload video files or keep old backups on the server.
Bandwidth
Bandwidth caps the data transferred between your server and visitors each month. Budget plans sometimes cap bandwidth at 100 GB to 1 TB per month, while many shared plans advertise it as unmetered. A page weighing 2 MB served to 50,000 visitors consumes roughly 100 GB, which shows how a modest traffic increase can approach a low cap.
Inodes
An inode count caps the number of individual files and folders in your account, and it is the limit beginners discover last. Shared plans commonly cap inodes at 250,000 to 500,000. Caches, email storage, and abandoned staging copies inflate inode counts quietly, and hosts often stop backing up accounts that exceed the cap before they suspend them.
CPU
CPU limits cap how much processor time your account uses, usually expressed as a percentage of one core. Shared plans commonly allow 100% of a single core with throttling beyond it. When you exceed the cap, the host slows your site rather than taking it offline, which appears to visitors as pages that hang for several seconds.
Memory
Memory limits cap the RAM your scripts use, commonly 768 MB to 2 GB per account on shared plans. Heavy page builders, large WooCommerce carts, and unoptimized plugins exhaust memory first, producing "allowed memory size exhausted" errors in PHP.
Entry Processes
Entry processes cap how many PHP requests run at the same moment, commonly 20 to 40 on shared plans. This limit, together with PHP workers on managed platforms, decides how many visitors your site serves simultaneously. When concurrent visitors exceed the cap, extra visitors see 503 errors even though the plan's bandwidth and CPU sit well below their limits.
Email Sending
Email limits cap outbound messages, commonly 100 to 500 per hour on shared plans, to protect the server's sending reputation. A newsletter to 2,000 subscribers exceeds an hourly cap immediately, which is why hosts and email specialists both recommend sending bulk mail through a dedicated email service instead of the hosting server.
What Does Unlimited Actually Mean in Hosting?
Unlimited in hosting means the host does not publish a number, not that no limit exists. Every unlimited plan carries a fair-use or acceptable-use policy that lets the host throttle or suspend accounts using excessive resources, and the host defines excessive. A plan that publishes exact caps for storage, inodes, and CPU gives you something you can verify and compare. Treat a published 50 GB cap as more trustworthy than an unpublished unlimited claim.
How Do You Check a Plan's Limits Before Buying?
Check a plan's limits in three places before buying: the plan comparison table, the terms of service, and the knowledge base. Firstly, read the plan table's footnotes, where hosts disclose inode and email caps in small print. Secondly, search the terms of service or acceptable-use policy for the words "inode", "CPU", and "fair use". Thirdly, search the host's knowledge base for "resource limits", because support articles often state the exact LVE limits that marketing pages omit. Ask pre-sales support for any number you cannot find, and treat a refusal to give numbers as a warning sign.
What Should You Do When You Keep Hitting Limits?
Move up one hosting type when you hit the same limit repeatedly after cleanup. Clear caches, delete unused files, and offload media first, because many limit problems are housekeeping problems. If the warnings continue, a VPS plan reserves dedicated CPU and memory for your account alone, and a cloud plan scales resources with your traffic instead of capping it.
Browse the HostVeritas shared hosting, VPS hosting, and cloud hosting directories to compare providers at each level. HostVeritas is a non-affiliate directory, so no listing pays to rank above another.