By David Russell · Official documentation checked November 4, 2026.
Affiliate disclosure: We may earn a commission when you purchase through our Namecheap link, at no extra cost to you.
Find the limit before choosing an upgrade.
Compare CPU, RAM, entry processes and file-count limits across Stellar, Stellar Plus and Stellar Business.
Compare current Namecheap plans →View resource limits ↓Stellar Plus
Compare this tier when memory or included tools matter. Its published base CPU allocation matches Stellar.
Review Namecheap hosting options →Stellar Business
Shortlist this when the documented resource increase fits measured demand. Confirm the full package and renewal cost.
Explore Business at Namecheap →Buttons open Namecheap’s current offers through our affiliate link. Select the relevant product there; prices and eligibility are confirmed at checkout.
Quick answer
Namecheap hosting resource limits are more useful than a website-count headline when diagnosing slowdowns. Read the account’s resource history, identify the metric reaching its ceiling and compare the specific increase offered by the next tier. Upgrading storage alone does not establish that a CPU problem will improve.
Namecheap hosting resource limits at a glance
| Published base allowance | Stellar | Stellar Plus | Stellar Business |
|---|---|---|---|
| CPU | 0.5 core | 0.5 core | 1 core |
| Physical memory | 1 GB | 2 GB | 2 GB |
| Entry processes | 20 | 30 | 40 |
| I/O | 50 MB/s | 50 MB/s | 50 MB/s |
| Inodes | 300,000 | 300,000 | 600,000 |
Sources: Namecheap’s base-resource comparison, resource policy and inode guide. Check the limits shown in your own account and ask support about any mismatch.
Base allocations are separate from temporary burst allowances. These figures describe account capacity, not a measured traffic limit or a guaranteed speed result.
What changes when you move between Stellar plans?
The published table shows a useful distinction: Plus increases physical memory and entry-process capacity over Stellar, while the base CPU remains the same. Business increases base CPU and entry capacity over Plus, but the published memory figure remains 2 GB. All three list the same I/O rate in the resource policy.
That makes the reason for upgrading important. If an account repeatedly runs out of memory, compare the memory increase. If CPU is the constraint, compare CPU. If neither metric is near its limit, investigate application behavior and other causes before assuming a larger hosting package will fix the issue.
A package may still be worth buying for its backup tools or other included services. Keep that purchase reason separate from a performance claim. See our Stellar plan comparison for the broader decision.
How to check resource usage in cPanel
Namecheap documents a Resource Usage screen under cPanel’s Metrics section. Review the period when the problem happened rather than relying only on a quiet moment’s dashboard reading. Its LVE and resource-usage guide explains the charts and limit indicators.
- Record the time, affected URL and visible error.
- Open Resource Usage and choose a matching time range.
- Compare usage peaks with the account’s limits and fault indicators.
- Check recent deployments, background tasks and traffic around that period.
- Save the evidence and ask support which process or metric needs attention.
A daily average can hide a short interruption. Equally, one brief peak does not prove the site needs a permanent upgrade. Look for recurring faults that line up with a business problem, such as failed checkout requests or unusually slow administration pages.
What a 508 resource-limit error tells you
Namecheap associates 508 errors with the entry-process limit. It distinguishes these from other error categories in its server error guide. A process limit should not be converted into a universal visitor-count rule: request duration and workload matter.
Several long-running requests can occupy capacity differently from a larger number of short cached requests. Record which action fails: opening a normal article, searching, submitting a form or loading a store page. That narrows the investigation more effectively than saying the entire site is always slow.
Do not diagnose every 500 or 503 as the same problem. Configuration errors, application failures and resource pressure need different checks. Preserve the error message and timestamp, review available logs and get support’s interpretation before changing unrelated settings.
Compare the resource that your site actually needs
Use the account’s charts and support findings alongside the current plan details.
Check Namecheap plan options →Reduce avoidable work before paying for more capacity
Namecheap’s overusage troubleshooting guide recommends checking recent changes, resource history and traffic. Start with a small, reversible change tied to the evidence. For a WordPress site, use a safe test copy when a change could affect forms, orders or membership access.
Review expensive searches, repeated external requests and background jobs. Check whether backups, scans and imports run at the same time. Schedule non-urgent tasks so they do not all compete with your busiest period. Keep necessary monitoring active while working through the cause.
Cache public pages where appropriate and optimize oversized media. Review duplicate plugin functions, but avoid disabling essential checkout or security features simply to make a graph fall. After each change, test the affected action and compare another representative traffic window.
Keep an independent backup and know the recovery path before significant changes. Our Namecheap backup guide explains the separate backup considerations.
File-count limits are separate from storage and backups
Namecheap counts filesystem objects toward an inode allowance. Its guide lists 300,000 for Stellar and Stellar Plus, and 600,000 for Stellar Business. A collection of many small files or mail messages can consume that allowance even when disk usage looks modest.
Review old cache folders, unused test installations, redundant local archives and mailbox housekeeping. Identify what owns a folder before removing it, and preserve a recoverable copy of anything important. A cleanup should reduce unnecessary objects without deleting active site content.
The hosting inode ceiling and backup eligibility rules are different checks. Being under a hosting file-count limit does not by itself prove a fresh automated backup exists. Review both in the dashboard instead of treating one healthy indicator as confirmation of the other.
When an upgrade is the reasonable next step
An upgrade belongs on the shortlist when recurring legitimate workload reaches a resource ceiling after sensible optimization, and the proposed package increases that specific allowance. Ask support to confirm the bottleneck, the destination allocation and the expected migration process.
For several sites sharing one account, investigate the account as a whole. Namecheap notes that resource overuse by one domain can affect other domains in the same account. An apparently quiet site may experience symptoms caused by another workload under the same account.
Compare the full recurring cost, migration work and operational needs. A busy store may need a different hosting architecture rather than the next shared tier. This guide does not establish a maximum visitor count or promise that one upgrade will produce a particular page-speed score.
Before seasonal promotions, review our renewal-cost guide, migration checklist and Shared Hosting vs EasyWP comparison. Verify the actual offer and renewal terms before paying.
Frequently asked questions
Does unmetered storage mean unlimited CPU?
No. Storage, CPU, RAM and process capacity are separate parts of the hosting package. Compare the relevant resource allowance.
Will Stellar Plus double my base CPU allocation?
The published comparison lists the same base CPU for Stellar and Stellar Plus. Plus changes other allowances and features.
Is an entry process the same as one website visitor?
No. The relationship depends on requests and how long they run. Avoid translating the process allowance into a fixed traffic promise.
Should I upgrade after one resource spike?
First check whether the spike matches a recurring problem. Investigate the cause, test reasonable fixes and compare the next package’s relevant limits.
Buy capacity for a measured need
Confirm the limiting metric, choose the appropriate package and keep a record of its renewal cost.
Review current Namecheap plans →Editorial method: Based on official Namecheap product and support documentation checked November 4, 2026. We did not run an independent load test or performance benchmark. Illustrations represent hosting concepts.
