How to Increase the WordPress Memory Limit

What the memory error means

Fix 1 — wp-config.php, the WordPress-level define:

1. Open cPanel → File Manager (enable Show Hidden Files) and edit wp-config.php in the site root.
2. Add this line above the 'That's all, stop editing' comment: define('WP_MEMORY_LIMIT', '256M');
3. Save and reload the failing page.

If the error persists, PHP's own cap is the ceiling and Fix 2 applies: MultiPHP INI Editor → memory_limit → 256M. The .htaccess fallback (Apache only) is php_value memory_limit 256M.

Reading the error first helps: 'Fatal error: Allowed memory size of X bytes exhausted' names the current limit — if X is already 256M, the hungry plugin (Query Monitor finds it) or the hosting cap is the real story. Standard sites sit fine at 128M; image-heavy WooCommerce wants 256M. The WordPress hosting tiers raise the caps with the plan, and the 500-error cousin covers the crash variant.

Fix 1: wp-config.php define

How this plays out with WP_MEMORY_LIMIT: settings that look cosmetic usually decide page speed and uptime under real traffic. The defaults WebJi® ships are tuned for Indian network conditions, and support can review your setup on request.

Fix 2: php.ini via cPanel

On WP_MAX_MEMORY_LIMIT, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Fix 3: .htaccess fallback

For “Fix 3: .htaccess fallback”, change one thing at a time and reload in a private window. Note the exact error text, the URL, and what you changed last — that is what support needs. If the site was fine before an update or a DNS edit, undo that edit first. Email support@webji.services (24/7, Hindi and English) or open a ticket at https://billing.webji.in/submitticket.php?step=2&deptid=10. A 2 a.m. fault goes to email, not to the phone line.

When the hosting cap wins

When the hosting cap wins. Do the change this heading names on one site first, then check it in a private browser window or in the mail client, depending on the topic. Change one setting at a time, and undo it if the result is wrong before you try the next. If you want the Jaipur desk to look with you, email support@webji.services — that mailbox is staffed 24/7 in Hindi and English. Phone +91 141 4941811 is business hours only.

Finding memory-hungry plugins

Update plugins and themes on a copy or straight after a backup, one at a time if the site is a shop. A white screen after an update is usually one plugin: rename its folder via the file manager to disable it. Remove plugins you do not use — they are unpatched code.

128M vs 256M guidance

On hosting-imposed memory caps, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.