Free agency tools / WordPress Memory Estimator
How much memory does this WordPress site need?
"Allowed memory size exhausted" is the classic white-screen error. Estimate a sensible WP_MEMORY_LIMIT from what the site actually runs, and get the exact wp-config.php lines to set it.
How it works
- 1Pick the site type, roughly how many active plugins it runs, and whether it uses a page builder.
- 2We sum a baseline for WordPress core and the site type, ~2 MB per plugin and a page-builder allowance, then add headroom.
- 3The result is rounded up to a standard tier (128M / 256M / 512M / 1024M) with copy-ready wp-config.php code.
Frequently asked
What's the difference between WP_MEMORY_LIMIT and WP_MAX_MEMORY_LIMIT?
WP_MEMORY_LIMIT is the limit for normal front-end requests. WP_MAX_MEMORY_LIMIT applies to heavier admin and cron tasks (imports, updates) and is set higher — we suggest both.
Is more memory always better?
No. A limit far above what the site needs just masks a memory leak or a badly-behaved plugin and can let one request starve others. Size it to real need plus headroom, then fix the outlier if it climbs.
Where do I put this code?
In wp-config.php, above the line that says /* That's all, stop editing! */. If your host caps PHP memory below this at the server level, WordPress can't exceed it — you'll need a plan with a higher PHP memory_limit.
Is this exact?
It's an informed estimate, not a measurement — real usage depends on your specific plugins and traffic. Treat it as a sensible starting limit, then watch for exhausted-memory errors.
Related tools
PHP Upgrade Readiness CheckerGauge how ready a WordPress site is to move to PHP 8.3/8.4, with a risk plan.
WordPress Health ScannerVersion leaks, exposed files, security headers and a scored health report.