Hosting Resource Limits: CPU, RAM, Inodes, and Traffic Explained

Hosting resource limits are the real terms of a hosting plan, and they rarely appear on the pricing page. "Unlimited" storage and traffic always sit on top of concrete ceilings: CPU seconds, memory, file counts, and transfer rules buried in an acceptable-use policy. Sites do not get suspended for using too much "unlimited"; they get suspended for hitting a specific number nobody showed them.

This guide explains each limit in plain terms and how to find yours. Read how to choose a web host if you are still picking a plan, and our migration guide if a limit has already forced your hand.

Where hosting resource limits hide

Look past the pricing grid to three places: the acceptable-use policy, the terms of service, and the plan comparison footnotes. That is where hosts define what "unlimited" means in practice for 2026 plans.

Before you buy, ask pre-sales for the actual numbers: CPU allowance, memory, inode cap, and what happens when you exceed each. Keep the written answer with your account notes.

The CPU limit on shared hosting

A CPU limit caps how much processor time your account can use, usually measured in seconds of CPU or a percentage of one core. Hosting plans enforce it quietly: your pages slow down or return errors during busy moments while the host's status page stays green.

Repeated throttling is the most common reason a healthy site feels slow on paper-cheap plans. It is also the limit hosts are least eager to publish.

Memory and process caps

Memory limits decide how much RAM your scripts can use at once, and process caps decide how many things can run simultaneously. Hit either and visitors see errors during traffic spikes, form submissions, or plugin updates.

These caps matter more than storage for dynamic sites. A WordPress site with a heavy page builder can exhaust memory long before it fills a disk.

The inode limit explained

An inode is roughly one file or folder, so an inode limit is a cap on how many files your account can hold, independent of their size. Caps in the hundreds of thousands sound generous until email, cache files, and image thumbnails quietly multiply.

Going over it often blocks backups before it blocks the site, which is the worst possible order. Clear old caches, unused themes, and stale mail regularly.

The counts climb faster than intuition suggests. Upload one photo to a typical CMS and it generates several thumbnail sizes, so a 2,000-image gallery can occupy 10,000 inodes before you count a single cache file. Hosted email is the other quiet consumer: every message and attachment is a file, and a mailbox nobody prunes can outgrow the website it sits beside.

Bandwidth and "unlimited" traffic

A bandwidth limit caps total data transferred to visitors in a month. Most small sites never approach it, but image-heavy pages, podcast files, and video multiply it quickly.

A CDN, a network that serves cached copies of your files from locations near visitors, offloads most of that transfer. Cloudflare's explanation of CDNs covers the mechanics: Cloudflare's explanation of CDNs.

How to check your current usage

Open your control panel's resource or statistics page and note CPU, memory, inode, and bandwidth usage against the caps. cPanel and similar panels chart all four; five minutes a month is enough.

Record the numbers when the site is behaving normally. A baseline turns "the site feels slow" into "CPU throttling started Tuesday," which is a solvable problem.

When limits mean it is time to move up

Hitting one limit occasionally is a cleanup job. Hitting the same limit monthly means the plan no longer fits, and the fix is an upgrade path rather than another round of pruning. We cover the options in our guide to scalable hosting.

Upgrade for the resource you actually exhaust. Buying more storage because CPU throttling made the site slow solves nothing.

Keep a record of the numbers

Save the plan's stated hosting resource limits and your monthly usage snapshot in the same note. When support says you exceeded a limit, you can check the claim against your own history instead of taking it on faith.

Bottom line

Hosting resource limits, not the word "unlimited," define what a plan can handle. Learn your CPU, memory, inode, and bandwidth ceilings, watch your usage monthly, and upgrade for the specific resource you keep exhausting.

Frequently asked questions

What happens when I hit my inode limit?

New files stop being created, which can break uploads, caching, email delivery, and often backups. Most hosts warn near the cap, then suspend accounts that stay over it. Deleting cache files, old mail, and unused plugins usually recovers headroom quickly.

Is a bandwidth limit the same as a traffic limit?

Effectively yes. Bandwidth is measured in data transferred, so the practical cap depends on page size: heavy pages spend it faster than lean ones. Compressed images and a CDN stretch the same allowance across far more visitors.

How do I find my plan's hosting resource limits?

Check the control panel's resource-usage page for live numbers, then the acceptable-use policy for the official caps. If the two disagree or the policy is vague, ask support to state the limits in writing.

Can bot traffic push me over CPU limits?

Easily. Crawlers and scrapers request uncached pages at machine speed, and every request spends CPU your plan counts against you. A caching plugin absorbs most of it, and blocking abusive bots at the server or CDN level handles the rest. If throttling starts without any growth in human traffic, check the access logs for bots before blaming the plan.