Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Web hosting

Hosting memory limits: PHP memory, process RAM and account limits are different

Published August 2026 · 2 min read · Updated 2026-09-05

Shared-hosting memory limits constrain the memory an account’s processes can consume on a multi-tenant node. Memory errors can be caused by PHP memory_limit, concurrent workers, large imports, image processing, plugins, cron, or per-account resource controls; the exact layer matters.

Identify PHP versus account/system memory limit

A PHP fatal “Allowed memory size exhausted” points to the per-process PHP memory_limit; a hosting resource fault may indicate aggregate account usage across processes. Read both application logs and hosting resource metrics.

Raising PHP memory_limit lets one process grow but can worsen aggregate pressure if many workers run concurrently.

Find the operation allocating memory

Large image manipulation, backups, CSV imports, report generation, page builders, plugins, and poorly bounded queries are common. Reproduce in a controlled window and profile the operation.

Process the dataset in batches where software supports it.

Reduce concurrency or per-process use

Tune PHP workers, plugin behavior, image sizes, caches, and cron concurrency. Remove abandoned plugins/themes and investigate memory leaks/repeated growth.

Keep enough memory headroom for normal spikes and system services.

Upgrade when healthy working set exceeds shared boundaries

A VPS provides a dedicated memory allocation but also transfers operating-system administration to the customer. Choose it when the application needs that resource/control boundary, not merely to avoid fixing a leak.

  • Locate the memory limit layer.
  • Profile the allocating task.
  • Bound concurrency and batch work.
  • Upgrade for sustained healthy demand.

Next step

Separate application memory settings from hosting-account and server RAM limits, then trace the actual memory error before upgrading or changing a PHP value.

Explore DotMoose web hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Virtualmin vs cPanel: Which Control Panel Should You Choose?

Virtualmin vs cPanel compared on licensing cost, account and site management, email, DNS, backups and migration, so you can pick the control panel that fits how you host.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

More web hosting guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move