Hosting · Guide
How to Read a Hosting Plan's CPU and RAM Limits
Short answer
Read a hosting plan by separating four numbers: CPU cores, CPU seconds, PHP workers, and RAM per request. Cores and workers set how many uncached requests run at once, CPU seconds set how much processor time you can use over an hour or day, and RAM sets how much memory each request can hold. Compare those four numbers across plans, then check your current use in your host panel and in WordPress Site Health.
Key takeaways
- CPU cores and PHP workers set how many uncached requests can run at the same time.
- CPU seconds measure total processor time used, so a busy hour can hit the limit even with few visitors.
- WordPress asks for 40 MB of memory on a single site and 256 MB in the admin by default.
- Hostinger lists 1 CPU core and 2 GB of RAM on Premium and 2 cores and 3 GB on Unlimited, as of November 2026.
- SiteGround lists 768 MB of RAM per process and CPU-second limits that rise with each shared plan.
- Kinsta splits one memory pool between PHP threads, so more memory per thread means fewer threads.
What do CPU and RAM limits mean on a hosting plan?
A CPU limit caps how much processor work your site can use, and a RAM limit caps how much memory its running code can hold at one time.
CPU does the work of building pages. Each uncached visit runs PHP code, asks the database for content, and builds HTML before the page reaches the visitor.
RAM holds the working data for that job. A PHP request keeps its code, query results, and image data in memory while it runs, then frees that memory when it ends.
A plan limit is a cap on one of those two resources. When you reach it, new requests slow down, wait in a queue, or fail with an error.
What is the difference between CPU cores, CPU seconds, and PHP workers?
Cores set how much work runs at once, CPU seconds set how much total work you can use, and PHP workers set how many uncached requests run at the same time.
A CPU core is one processing unit. A plan with 2 cores can do about twice as much simultaneous work as a plan with 1 core, if the rest of the server keeps up.
A CPU second is 1 second of full use of 1 core. A task that uses half a core for 4 seconds costs 2 CPU seconds, so short tasks add up across a busy day.
A PHP worker, also called a PHP thread, is one PHP process that handles one request at a time. Kinsta's docs say each thread handles one incoming request at a time, and cached content bypasses PHP threads (PHP performance).
| Measure | What it counts | What runs out first when it is too low |
|---|---|---|
| CPU cores | Simultaneous processing power | Slow pages during traffic peaks |
| CPU seconds | Total processor time over an hour or day | Limits hit after a busy period |
| PHP workers | Uncached requests running at once | Queued requests and timeouts |
| RAM per request | Memory one PHP request can hold | Memory errors and 500 errors |
How much RAM does WordPress need per request?
Most small WordPress sites run well with 256 MB per PHP request, while shops and page builders often need 512 MB.
WordPress sets its own memory request with two constants. The WordPress PHP guide states that WP_MEMORY_LIMIT defaults to 40 MB on a single site and 64 MB on multisite (PHP optimization).
The same guide states that WP_MAX_MEMORY_LIMIT defaults to 256 MB for admin screens. Admin work such as imports, updates, and image processing needs more room than a normal page view.
PHP also has its own ceiling, called memory_limit. The WordPress guide describes it as the maximum amount of memory that PHP is allowed to use per page render, and WordPress cannot raise it above the server value if the host blocks the change.
Kinsta sets a useful floor for shops. Its docs say that WooCommerce sites should keep memory per thread at 128 MB or more, and lower values can cause downtime and errors (PHP performance).
How do you find the limits on a plan page before you buy?
Open the host's pricing page, then its limits or parameters page, and write down cores, RAM, PHP workers, CPU seconds, and inodes for each plan.
Start on the pricing page and note the plan names in order. Prices change with term length, so note the term next to each price and check the renewal price as of November 2026.
Then open the host's own limits page. Hostinger publishes a parameters page that lists CPU cores, RAM, PHP workers, inodes, and database limits for each current plan (Parameters and limits).
Look for four gaps that pricing pages often hide. Check whether the plan lists CPU seconds, a per-process RAM cap, a PHP worker count, and an inode count.
Follow these steps for each plan you compare:
- Note the CPU cores and total RAM in the plan table.
- Note the PHP worker or thread count, if the host publishes one.
- Note any CPU-second limit per hour, day, or month.
- Note the inode limit, which counts files, folders, and email messages.
- Note the storage type and size, since slow disk can look like a CPU problem.
Allow about 15 minutes for a 3-plan comparison. If a host does not publish a number, treat that as missing data, not as an unlimited resource.
How do you check the limits you already have?
Open WordPress Site Health for the PHP memory limit, then open your host panel for CPU, RAM, and worker use over the last 7 days.
Start inside WordPress. Go to Tools, then Site Health, then Info, then Server, and read the PHP memory limit and PHP version listed there.
WordPress.org recommends PHP 8.3 or greater, plus MariaDB 10.11 or greater or MySQL 8.4 or greater, with HTTPS support (Requirements). A host on an older PHP version is a separate problem from a low memory limit.
Then open your host panel and find its resource usage page. Hostinger places it under Hosting Plan, then Resource Usage, and its support guide says a red line on each graph marks the plan limit (Fix the 503 error).
Follow these steps to read the graphs:
- Open the resource usage page in your host panel.
- Switch the view to the last 7 days, so one spike does not mislead you.
- Read CPU, memory, PHP workers, and processes in turn.
- Note the time of each peak and what happened on the site then.
- Compare each peak with the red limit line for your plan.
To confirm the fix worked after a change, repeat this check after 7 days. Peaks should sit below the limit line, and the error should not return at the same time of day.
How do Hostinger, SiteGround, and Kinsta limits compare?
Hostinger publishes cores and RAM per plan, SiteGround publishes CPU seconds and a per-process RAM cap, and Kinsta publishes a shared memory pool split between PHP threads.
Hostinger lists clear per-plan numbers as of November 2026. Premium has 1 CPU core, 2 GB of RAM, 40 PHP workers, and 400,000 inodes, while Unlimited has 2 cores, 3 GB of RAM, 60 PHP workers, and 600,000 inodes (Parameters and limits).
Cloud Startup steps up to 4 cores, 4 GB of RAM, 100 PHP workers, and 2,000,000 inodes on the same Hostinger page. The jump from Premium to Unlimited adds a second core, which matters more for CPU-bound sites than the RAM rise alone.
SiteGround uses a different unit. Its fair-use page lists 1,000 CPU seconds per hour, 10,000 per day, and 300,000 per month on StartUp, rising to 2,000, 20,000, and 600,000 on GrowBig, and 4,000, 40,000, and 800,000 on GoGeek (Fair use).
The same SiteGround page says it allocates up to 768 MB of RAM per process. That page was last updated on 12 October 2021, so ask SiteGround support to confirm the current values for your plan before you rely on them.
| Host and plan | CPU | RAM | PHP workers or threads |
|---|---|---|---|
| Hostinger Premium | 1 core | 2 GB | 40 workers |
| Hostinger Unlimited | 2 cores | 3 GB | 60 workers |
| Hostinger Cloud Startup | 4 cores | 4 GB | 100 workers |
| SiteGround StartUp | 1,000 CPU seconds per hour | 768 MB per process | Not published |
| SiteGround GrowBig | 2,000 CPU seconds per hour | 768 MB per process | Not published |
| Kinsta Single 35k | Not published as cores | 512 MB pool, 256 MB per thread | 2 threads |
Kinsta splits one pool between threads. Its docs give a 2 GB pool as an example: 4 threads at 512 MB each, or 8 threads at 256 MB each, so raising memory per thread cuts the thread count (PHP performance).
Kinsta also sells a PHP performance add-on at $10 per extra 500 MB per month, as of November 2026. The maximum memory limit per thread is 1,024 MB, so the add-on cannot push one thread past that cap.
If you need help picking between hosts, read our guide on how to choose WordPress hosting. It covers the wider choice, while this guide covers only the resource numbers.
What happens when you hit a CPU or RAM limit?
CPU limits cause slow pages and queued requests, while RAM limits cause memory errors, 500 errors, and failed tasks such as imports.
When PHP workers run out, new uncached requests wait. Visitors see slow pages first, then timeouts if the queue does not clear.
When RAM runs out, PHP stops the request with a memory error. Kinsta notes the common message as “Allowed memory size of 268435456 bytes exhausted”, and 268,435,456 bytes equals 256 MB (PHP threads vs PHP memory limit).
When CPU seconds run out on a shared plan, the host may slow or stop the account until the period resets. The exact response differs by host, so read the fair-use or terms page for your plan before you assume a limit is soft.
Hostinger's support guide links a 503 error to maxed-out CPU, RAM, or disk space, and tells owners to check the Resource Usage page first (Fix the 503 error). A 503 after a traffic spike points at a resource cap more often than at a broken plugin.
How do you lower CPU and RAM use without upgrading?
Cache full pages, cut uncached work, and remove heavy plugins, then recheck the usage graphs after 7 days.
Caching is the largest saving. A cached page skips PHP and the database, so it uses almost no CPU, RAM, or PHP workers.
Logged-in pages, carts, and checkout pages bypass most page caches. Those pages run PHP on every view, so a shop or course site uses more CPU per visit than a blog with the same traffic.
Try these cuts in order, one at a time:
- Turn on full-page caching and check that logged-out pages are served from cache.
- Replace WP-Cron with a real server cron job if your host offers one, so scheduled tasks do not run on random visits.
- Limit image sizes before upload, since resizing large images on the server uses CPU and RAM.
- Remove or replace plugins that run on every page load, especially ones that add remote requests.
- Reduce the number of posts shown per page and the number of widgets that query the database.
Our guide on how to speed up WordPress walks through caching and plugin checks in more detail.
Keep a backup before you change caching or cron settings, as described in how to back up WordPress.
When should you upgrade instead of optimising?
Upgrade when peaks sit near the limit after caching and cleanup, when logged-in traffic keeps growing, or when one task always needs more memory than a single request allows.
A single spike after a post goes live is not a reason to upgrade. A peak that returns at the same time each day, after caching is on, is a sign the plan is too small.
Count the cost of the next tier against the cost of the slowdown. A shop that loses checkouts during a queue is paying more in lost sales than the price gap between plans, as of November 2026.
Choose the upgrade that fixes the number you hit. More PHP workers help queued uncached requests, more RAM per request helps memory errors, and more cores help a site that is busy all day.
A CDN can cut bandwidth and some static load, but it does not raise your PHP worker or RAM limits. Read how much a CDN costs for WordPress before you buy one for a resource problem.
What mistakes should you avoid?
Do not judge a plan by storage, visits, or the word unlimited, and do not raise a WordPress memory constant past the server ceiling.
Storage and visit counts tell you little about CPU or RAM. A plan with 100 GB of storage and 1 CPU core still queues uncached requests when traffic peaks.
The word unlimited on a plan page means the host has not set a simple number for that item. CPU, RAM, PHP workers, and inodes still have caps, so read the limits page for the real numbers.
Do not set WP_MEMORY_LIMIT above the PHP memory_limit and expect it to work. The WordPress PHP guide says WordPress will raise the PHP limit to its constants only if it has permission, and it will not lower a higher server value (PHP optimization).
Do not add PHP workers without checking memory per worker. On Kinsta, more threads from the same pool means less memory per thread, so a shop can trade a queue problem for a memory problem.
Do not compare hosts on one number alone. A host that lists 4 cores and a host that lists 4,000 CPU seconds per hour are measuring different things, so compare the full table in the section above.
A comparison of two shared hosts shows how the same numbers can differ in practice. See our SiteGround vs Hostinger speed test for that side-by-side view.
Frequently asked questions
How much CPU and RAM does a small WordPress blog need?
A small blog with caching on usually runs well on 1 CPU core, 2 GB of RAM, and 256 MB per PHP request. Logged-out pages served from cache use little CPU or RAM, so the plan matters most for admin work, imports, and traffic peaks. If peaks stay below the limit line for 7 days, the plan is enough.
Is 256 MB of PHP memory enough for WooCommerce?
Yes, 256 MB per PHP thread is a sound starting point for many WooCommerce stores, and Kinsta notes that WooCommerce should keep at least 128 MB per thread. Large catalogs, page builders, and many plugins can push a single request past 256 MB. If you see memory errors during checkout or imports, raise the per-request limit before adding more workers.
What is the difference between RAM and PHP memory limit?
RAM is the total memory on the server or in your plan, while the PHP memory limit is the maximum memory one PHP request can use. A plan can have 3 GB of RAM and still fail a request that needs more than its 256 MB PHP limit. Check both numbers: total RAM sets the size of the pool, and the PHP limit sets the size of each request.
Why does my site hit CPU limits with low traffic?
Low traffic can still use a lot of CPU if most visits bypass the cache. Logged-in users, cart and checkout pages, search pages, and admin work all run PHP on every view. Bots, cron jobs, and uncached image resizing also add CPU seconds without adding real visitors. Check which hours peak, then cache more pages and cut the heaviest uncached tasks.
Can I raise the CPU or RAM limit without changing plans?
Sometimes, but only within the host's rules. Kinsta sells a PHP performance add-on that raises the memory pool, and some hosts let you change the PHP memory limit in the panel. CPU cores and CPU-second caps usually change only with a plan upgrade. Ask support what can change on your current plan before you pay for an add-on.
Do I need more CPU cores or more PHP workers?
You need more PHP workers when uncached requests queue and wait, and more CPU cores when the server is busy even with free workers. Workers set how many requests run at once, while cores set how fast that work finishes. If pages are slow but workers are free, the work itself is heavy and needs cores, caching, or lighter code.
Sources
- Requirements WordPress.org
- PHP Optimization WordPress Developer Resources
- Editing wp-config.php WordPress Developer Resources
- Parameters and limits of hosting plans in Hostinger Hostinger
- 503 Service Unavailable: causes and how to resolve it Hostinger Support
- What is a Fair Use of SiteGround Web Hosting Services? SiteGround
- PHP Performance Kinsta Docs
- PHP threads vs PHP memory limit: the difference Kinsta
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
