{"id":4358,"date":"2026-10-13T07:09:32","date_gmt":"2026-10-13T07:09:32","guid":{"rendered":"https:\/\/www.wpchatsupport.com\/blog\/?p=4358"},"modified":"2026-10-13T07:14:42","modified_gmt":"2026-10-13T07:14:42","slug":"fix-wordpress-memory-exhausted-error","status":"publish","type":"post","link":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/","title":{"rendered":"How to Fix the WordPress Memory Exhausted Error"},"content":{"rendered":"<h2>Introduction<\/h2>\n<p>Your site stops part way through loading. Perhaps the dashboard goes white. Perhaps an upload fails for no clear reason. Then you find a line like this in your log or on screen:<\/p>\n<pre><code>Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 20480 bytes)<\/code><\/pre>\n<p>That is the WordPress memory exhausted error. The wording looks alarming, but the meaning is simple. PHP was given a fixed amount of memory for that one page. It used all of it before finishing. So it stopped.<\/p>\n<p>Nothing is broken in the usual sense. No files are damaged. Your content is safe. The site simply ran out of room to work in, and the fix is to give it more room or ask it to do less.<\/p>\n<p>This guide covers the whole job. You will learn the signs that point at memory rather than something else, what is really eating the budget, and a fix for every cause in a safe order. The last section shows you how to stop it returning.<\/p>\n<p>The usual triggers are easy to name. A new plugin. A page builder. A big import. A large image. A host that caps memory lower than you expected. We cover each one below.<\/p>\n<p>If your page is blank with no message at all, you may be looking at a different fault. Our guide to <a href=\"https:\/\/www.wpchatsupport.com\/blog\/fix-500-internal-server-error-wordpress\/\">the 500 internal server error<\/a> covers the server-level version of that.<\/p>\n<h2>Signs That Point to the WordPress Memory Exhausted Error<\/h2>\n<p>Memory faults have a recognisable shape. Work through the checks below before you change any settings, because they separate this fault from the ones that look like it.<\/p>\n<p>The clearest sign is the phrase itself. Look for &#8220;Allowed memory size of&#8221; followed by a number, then &#8220;bytes exhausted&#8221;. The number is your limit in bytes. Divide it by 1,048,576 to get megabytes. So 67108864 bytes is 64MB, and 134217728 is 128MB. That tells you immediately what you are working with.<\/p>\n<p>The second sign is where it happens. Memory faults usually hit the heaviest screens first. The dashboard, the plugins screen, the media library, a page builder, or an import. The front end often keeps working for a while, because it does far less per request. If your public pages are fine and only admin screens break, memory is a strong suspect.<\/p>\n<p>Third, look for a cut-off page rather than an error page. Memory exhaustion stops PHP mid-sentence. You often get half a page, or a layout that ends abruptly, rather than a tidy error screen. Viewing the page source shows HTML that simply stops.<\/p>\n<p>Fourth, note whether the fault follows an action rather than a page. If it only appears when you upload a large image, run a backup, or import a file, the budget is being used up by that one heavy job. The rest of the site is fine.<\/p>\n<p>Fifth, check whether it started after a change. A new plugin, a theme switch, a page builder, or a host moving you to a new plan all change how much memory a request needs. The last change you made is the strongest clue you have.<\/p>\n<p>Finally, rule out the lookalikes. If the page hangs for a long time and then fails, you may have hit a time limit instead, which our guide to the <a href=\"https:\/\/www.wpchatsupport.com\/blog\/how-to-fix-the-maximum-execution-time-exceeded-error-in-wordpress\/\">maximum execution time exceeded error<\/a> covers. If only the dashboard is slow but nothing fails, read our guide to a <a href=\"https:\/\/www.wpchatsupport.com\/blog\/fix-a-slow-wordpress-admin-dashboard-issue\/\">slow WordPress admin dashboard<\/a> instead.<\/p>\n<h2>Reasons Why the WordPress Memory Exhausted Error Happens<\/h2>\n<p>Every page load gets a memory budget. The error appears when the work needed is larger than the budget allowed. Below are the real causes, and what each one does.<\/p>\n<p><strong>The server&#8217;s PHP memory limit caps everything.<\/strong> Your host sets a value called memory_limit for PHP. This is the hard ceiling. WordPress cannot go above it, no matter what you put in your own files. On cheap shared plans this is often 64MB, which is tight for a modern site.<\/p>\n<p><strong>WordPress&#8217;s own default was never raised.<\/strong> WordPress tries to set its own limit at startup. The default target is 40MB for a single site and 64MB for a multisite network, as the official <a href=\"https:\/\/developer.wordpress.org\/advanced-administration\/wordpress\/wp-config\/\" target=\"_blank\" rel=\"noopener\">WordPress wp-config.php handbook<\/a> explains. If nobody ever raised it, that is what you are running on.<\/p>\n<p><strong>The dashboard needs more memory than the front end.<\/strong> Admin screens do heavy work. They check for updates, build lists, and process images. WordPress allows a separate, higher limit for the admin area through a second constant. If only that one is missing, your public pages stay fine while your dashboard breaks.<\/p>\n<p><strong>The constant sits in the wrong place in wp-config.php.<\/strong> Memory constants only work if they are read before WordPress finishes loading. Added below the &#8220;stop editing&#8221; line, they are read too late and do nothing at all. The setting looks correct in the file but never applies.<\/p>\n<p><strong>One heavy plugin is eating most of the budget.<\/strong> Some plugins load a large amount of code on every single request. Security scanners, page builders, analytics suites and multi-purpose toolkits are common offenders. One badly behaved plugin can take more memory than the rest of the site combined.<\/p>\n<p><strong>Your theme or page builder loads too much per request.<\/strong> Multi-purpose themes often load every feature they own, whether your pages use them or not. Page builders add another layer on top. The result is a baseline memory cost before your content is even considered.<\/p>\n<p><strong>Large images and media processing.<\/strong> When you upload an image, WordPress loads the whole thing into memory to make the smaller sizes. A very large photo from a modern camera can use a surprising amount on its own. Add a theme that registers many extra image sizes and one upload can exhaust the budget.<\/p>\n<p><strong>Imports, exports and backups run in a single request.<\/strong> These jobs try to handle a lot of data at once. Memory use climbs steadily as they run, and the failure often comes near the end. That is why a backup can fail at ninety per cent and succeed on a smaller site.<\/p>\n<p><strong>A plugin conflict or a runaway loop.<\/strong> Occasionally code calls itself over and over without stopping. Memory fills in seconds rather than gradually. This is rarer than the other causes, but it is the one that raising the limit will never fix.<\/p>\n<h2>How to Fix the WordPress Memory Exhausted Error (Step by Step)<\/h2>\n<p>Work through these in order. They move from the quickest safe change to the deeper investigation. Stop as soon as the error clears.<\/p>\n<h3>Step 1: Find Your Real Limit and Raise It at Server Level<\/h3>\n<p>This step covers the server&#8217;s PHP memory limit, the hard ceiling above everything else. Nothing you set in WordPress can exceed it. If your host caps PHP at 64MB, setting 256MB in wp-config.php achieves nothing. So this is the first thing to establish.<\/p>\n<p>Confirm your real figure before changing anything. If you can reach your dashboard, open the Site Health screen and look at the server information section. It reports the PHP memory limit your site is actually running with. If the dashboard is down, read the number from the error itself and convert it from bytes, as described in the signs section above.<\/p>\n<p>There is no risk in simply looking. Raising the server limit is also low risk, but it is a server-wide change, so make it through your host&#8217;s own tools rather than by guesswork.<\/p>\n<p>Most hosting control panels have a PHP settings or PHP options screen where memory_limit can be changed. Set it to 256M if your plan allows. If you cannot find the option, ask your host to raise it for your account. Most will do it on request, and many do it instantly. Some hosts allow a php.ini or .user.ini file in your root folder instead.<\/p>\n<p>Reload the screen that was failing. If the error has gone, you are done, though step 5 is still worth reading to find out why you needed so much. If your host refuses to go higher, note the ceiling you have and move on, because the remaining steps reduce what your site needs rather than raising what it gets.<\/p>\n<h3>Step 2: Raise the WordPress Memory Limit in wp-config.php<\/h3>\n<p>This step covers WordPress&#8217;s own default, which is low and often never changed. WordPress aims for 40MB on a single site and 64MB on a multisite network. Even when your server offers more, WordPress will not reach for it unless you say so. This is the single most common fix.<\/p>\n<p>Check whether this applies to you first. Open wp-config.php and search it for WP_MEMORY_LIMIT. If the constant is not there at all, you are running on the default and this step is for you. If it is already there, note the value and compare it with the server ceiling you found in step 1.<\/p>\n<p>This step edits wp-config.php, and a mistake in that file takes the whole site offline. Download a copy before you change anything so you can put it straight back. Take a full backup too if you can still reach your dashboard, using a tool such as <a href=\"https:\/\/www.wpchatsupport.com\/blog\/how-to-backup-wordpress-using-updraftplus\/\">UpdraftPlus<\/a>. Use a staging copy first if your host offers one.<\/p>\n<p>Open wp-config.php over FTP or in your host&#8217;s file manager. Add this line above the comment telling you to stop editing:<\/p>\n<pre><code>define( 'WP_MEMORY_LIMIT', '256M' );<\/code><\/pre>\n<p>Save the file and reload the screen that was failing. If it loads, the fix worked. If nothing changes, check the Site Health screen again. Should it still report the old figure, your server ceiling is lower than the value you set, which sends you back to step 1.<\/p>\n<h3>Step 3: Give the Dashboard a Higher Limit of Its Own<\/h3>\n<p>This step covers the admin area needing more memory than the front end. WordPress supports a second constant for exactly this. Admin screens check for updates, build long lists and process images, all of which cost more than displaying a page to a visitor.<\/p>\n<p>Confirm this is your case with one observation. Does the public site load perfectly while the dashboard, the plugins screen or the media library fails? That pattern points straight at the admin limit. If the front end is breaking too, step 2 matters more than this one.<\/p>\n<p>You are editing wp-config.php again, so keep the copy you downloaded in step 2 to hand. The same warning applies. A typo here takes the site down.<\/p>\n<p>Add this line in the same place, above the &#8220;stop editing&#8221; comment. The handbook notes that it must be set before wp-settings.php is included, which that position guarantees:<\/p>\n<pre><code>define( 'WP_MAX_MEMORY_LIMIT', '256M' );<\/code><\/pre>\n<p>Save and reload your dashboard. If the admin screens come back, this was your cause. Keep both constants in place, because they do different jobs. If the dashboard still fails, your problem is the amount being used rather than the amount allowed, so continue.<\/p>\n<h3>Step 4: Check the Constant Is in the Right Place<\/h3>\n<p>This step covers a setting that looks correct but never runs. Memory constants are only honoured if PHP reads them before WordPress finishes starting up. Placed below the &#8220;stop editing&#8221; line in wp-config.php, they are read too late and are simply ignored. People often conclude the fix does not work, when in truth it never ran.<\/p>\n<p>Confirm this before anything else. Open wp-config.php and find the line reading that this is all, stop editing. Now look at where your memory lines sit. If they are below that line, you have found your problem. Another confirmation is a Site Health screen that keeps reporting the old value no matter what you set.<\/p>\n<p>You are moving lines in wp-config.php, so keep your downloaded copy safe. Moving a line is lower risk than writing a new one, but the file is still unforgiving.<\/p>\n<p>Cut both memory lines from wherever they are and paste them above the &#8220;stop editing&#8221; comment. Keep them near the other define lines. Save the file.<\/p>\n<p>Reload your site and open Site Health again. The memory limit shown should now match what you set. If it does, the setting is finally live. If the number still refuses to move, your host is enforcing a lower ceiling and step 1 is where to go.<\/p>\n<h3>Step 5: Find the Plugin That Is Using the Memory<\/h3>\n<p>This step covers one heavy plugin eating most of the budget. Plugins load inside the same PHP request as WordPress, so their cost is added to every page. Security scanners, analytics suites, page builders and large all-in-one toolkits are the usual heavy users. One of them can easily take more than everything else combined.<\/p>\n<p>Confirm plugins are involved before you start. If raising the limit helped but the site still feels close to the edge, something is using an unreasonable amount. A healthy result at the end of this test is a site that loads comfortably with all plugins switched off.<\/p>\n<p>Switching plugins off changes what visitors see, so pick a quiet hour or use a staging copy. Take a backup first. Your settings stay in the database when a plugin is switched off, so you will not lose configuration.<\/p>\n<p>If your dashboard loads, turn all plugins off from the plugins screen. If it does not, rename the plugins folder inside wp-content over FTP, which switches them all off at once. Then turn them back on one at a time, reloading the screen that was failing after each. The plugin that brings the error back is your heavy user.<\/p>\n<p>Once you know which it is, you have choices. Find a lighter replacement. Check whether an update exists, since memory leaks are often fixed. Or keep it and raise the limit to suit, if the plugin genuinely earns its cost. If no single plugin is responsible, the weight is spread across your theme, so continue.<\/p>\n<h3>Step 6: Test Your Theme or Page Builder<\/h3>\n<p>This step covers a theme or builder that loads too much on every request. Multi-purpose themes often load every feature they ship with, used or not. A page builder adds its own layer on top. Together they can set a baseline cost that leaves little room for anything else.<\/p>\n<p>Check this cause before switching. If the error survived turning every plugin off in step 5, the remaining weight is WordPress plus your theme. That narrows it considerably. Note also whether the fault began after a theme change or a redesign.<\/p>\n<p>Switching theme changes how your site looks, and some widget placements and theme settings will not survive the round trip. Back up first and use a staging copy if you have one. If you cannot, choose a quiet hour.<\/p>\n<p>Activate a default theme such as Twenty Twenty-Four from the themes screen. With no dashboard, rename your active theme&#8217;s folder over FTP, making sure a default theme is present. WordPress falls back to a default theme when the active one disappears.<\/p>\n<p>Reload the failing screen. If it works on a default theme, your theme or builder is the cost. Check for an update, turn off features you do not use in the theme options, or move to something lighter. Our guide to <a href=\"https:\/\/www.wpchatsupport.com\/blog\/how-to-fix-page-speed-issues-in-wordpress-easily\/\">fixing page speed issues in WordPress<\/a> covers trimming that weight properly.<\/p>\n<h3>Step 7: Tame Large Images and Media Processing<\/h3>\n<p>This step covers memory spent on images. When you upload a photo, WordPress loads the entire image into memory uncompressed to create the smaller sizes. A large modern photo is far bigger in memory than its file size suggests. Themes that register many extra image sizes multiply that work.<\/p>\n<p>Confirm this is your cause with a simple test. Does the error appear only when you upload, and only with big files? Try a small image. If that uploads cleanly while a large one fails, the problem is image processing and not your site as a whole.<\/p>\n<p>There is little risk in this step, since you are changing what you upload rather than how the site runs. If you later remove registered image sizes in code, back up first and work on staging.<\/p>\n<p>Start by resizing images before you upload them. Few sites need anything wider than about 2,000 pixels. Save as JPEG or WebP at sensible quality rather than uploading straight from a camera or phone. For bulk work, resize on your computer first.<\/p>\n<p>Reload the media library and try the upload again. If the upload fails with a message about a missing temporary folder rather than memory, that is a different server fault, covered in our guide to the <a href=\"https:\/\/www.wpchatsupport.com\/blog\/fix-missing-a-temporary-folder-error-wordpress\/\">missing a temporary folder error<\/a>. If it succeeds, you have your answer. For a longer-term fix, review how many image sizes your theme and plugins register, and remove the ones nothing uses. If uploads still fail with small files, the cause is elsewhere.<\/p>\n<h3>Step 8: Run Imports, Exports and Backups in Smaller Batches<\/h3>\n<p>This step covers heavy jobs that try to do everything in one request. Imports, exports and backups accumulate data in memory as they work. The further they get, the more they hold. That is why these jobs so often fail near the end rather than at the start.<\/p>\n<p>Check whether this is your cause by looking at when the failure happens. If normal browsing is fine and only a long job fails, you have found it. Note how far it reaches before stopping, because a consistent stopping point confirms a budget being used up rather than a random fault.<\/p>\n<p>These jobs touch a lot of data, so take a backup before retrying anything that writes to your site. If an import failed half way, check what it already created before running it again, or you may end up with duplicates.<\/p>\n<p>Split the work. Import a few hundred rows at a time rather than thousands. Most backup plugins have settings to lower how much they process per batch, often described as chunk size or request size. Lower that value and let the job take longer. Some tools can also run over the command line, which avoids the web request limit entirely.<\/p>\n<p>Run the job again and watch whether it completes. If it does, keep the smaller batch size as your normal setting. If it still fails at the same point regardless of batch size, something is holding memory that should have been released, which the last step addresses.<\/p>\n<h3>Step 9: Look for a Runaway Loop in the Log<\/h3>\n<p>This step covers a plugin conflict or code that calls itself endlessly. Here memory fills in seconds rather than climbing gradually. Raising the limit only buys a moment before the same failure. This is the cause that makes people think the fix did not work.<\/p>\n<p>Confirm it by the shape of the failure. Does the error appear almost instantly, and does raising the limit change nothing at all? Does the log show the same function or file repeated over and over before the fatal line? Both point at a loop rather than genuine demand.<\/p>\n<p>Reading the log is safe, but turning debugging on means editing wp-config.php, so keep your backup copy to hand. Never leave debugging switched on afterwards on a live site.<\/p>\n<p>Add these lines above the &#8220;stop editing&#8221; comment, as set out in the <a href=\"https:\/\/developer.wordpress.org\/advanced-administration\/debug\/debug-wordpress\/\" target=\"_blank\" rel=\"noopener\">WordPress debugging documentation<\/a>:<\/p>\n<pre><code>define( 'WP_DEBUG', true );\r\ndefine( 'WP_DEBUG_LOG', true );\r\ndefine( 'WP_DEBUG_DISPLAY', false );<\/code><\/pre>\n<p>Reload the failing screen once, then open debug.log in your wp-content folder. Read the lines just before the fatal error. A long repetition of the same call is your loop, and the file path names the plugin or theme responsible. Turn that extension off, send the log line to its developer, and set WP_DEBUG back to false.<\/p>\n<p>If the log shows nothing unusual and you have worked through every step above, the demand is real rather than faulty. At that point the honest answer is more memory or a lighter site, and a <a href=\"https:\/\/www.wpchatsupport.com\/blog\/emergency-wordpress-support-site-breaks\/\">WordPress support team<\/a> can read the log with you and say which.<\/p>\n<h2>Best Practices to Prevent the Memory Exhausted Error in Future<\/h2>\n<p>Each cause above has a habit that keeps it away. Put these in place once and memory stops being something you think about.<\/p>\n<p><strong>Set a sensible limit from day one.<\/strong> This prevents the default-limit cause. Put WP_MEMORY_LIMIT and WP_MAX_MEMORY_LIMIT in wp-config.php when you build the site, above the &#8220;stop editing&#8221; line, and ask your host what the server ceiling is so you know your real headroom.<\/p>\n<p><strong>Check Site Health now and then.<\/strong> It reports your actual memory limit rather than what you think you set. A quick look every few months catches a host change or a setting that silently stopped applying.<\/p>\n<p><strong>Audit plugins for weight, not just count.<\/strong> This prevents the heavy-plugin cause. Before installing anything, check when it was last updated and what it loads. Remove plugins you no longer use rather than leaving them switched off, and prefer one focused tool over an all-in-one suite.<\/p>\n<p><strong>Choose a lean theme.<\/strong> A theme that loads only what your pages use leaves room for everything else. If you are on a multi-purpose theme, go through its options and switch off the features you never touch.<\/p>\n<p><strong>Resize images before uploading.<\/strong> This prevents the media cause outright. Set a house rule for maximum width, and keep an eye on how many image sizes your theme registers.<\/p>\n<p><strong>Schedule heavy jobs sensibly.<\/strong> Run backups and imports outside peak hours, in batches, and let them take longer. A slow job that finishes beats a fast one that dies.<\/p>\n<p><strong>Keep PHP current.<\/strong> Newer PHP versions use memory more efficiently, so the same site often needs less. Check your version on Site Health a few times a year and upgrade on staging first.<\/p>\n<p><strong>Keep the log habit.<\/strong> Know how to switch WP_DEBUG_LOG on and where debug.log lives. When something fails, reading beats guessing, and memory errors always leave a clear line.<\/p>\n<h2>Conclusion<\/h2>\n<p>The WordPress memory exhausted error is one of the more honest faults you will meet. It tells you the limit, it tells you what was being attempted, and it points at where to look. The signs are a cut-off page, admin screens failing before public ones, and a message naming a size in bytes.<\/p>\n<p>The causes come from a short list. A server ceiling you cannot see. A WordPress default nobody raised. A missing admin limit. A constant in the wrong place. A heavy plugin, a heavy theme, a large image, a long job, or a runaway loop.<\/p>\n<p>The fix follows the same order each time. Find your real limit and raise it at server level. Set the WordPress limits and check they are in the right place. Then reduce demand. Test plugins, test the theme, tame images, batch the heavy jobs, and read the log for a loop. Back up before touching wp-config.php, and use staging when you can.<\/p>\n<p>Then build the habits. Sensible limits from the start, a lean plugin list, resized images, and a glance at Site Health now and then. If you have worked through all nine steps and the error still appears, do not keep raising the number. Send your debug log to your host, or hand it to a support team who reads these every day.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Introduction Your site stops part way through loading. Perhaps the dashboard goes white. Perhaps an [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4379,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[287],"tags":[538,539,389,366,343],"class_list":["post-4358","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress-error","tag-memory-limit","tag-php-memory","tag-wordpress-errors","tag-wordpress-support","tag-wordpress-troubleshooting"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.8 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>How to Fix the WordPress Memory Exhausted Error Fast<\/title>\n<meta name=\"description\" content=\"Hit the WordPress memory exhausted error? Find your real PHP limit, raise it safely, then cut what your site uses, with 9 causes and 9 clear fixes.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Fix the WordPress Memory Exhausted Error Fast\" \/>\n<meta property=\"og:description\" content=\"Hit the WordPress memory exhausted error? Find your real PHP limit, raise it safely, then cut what your site uses, with 9 causes and 9 clear fixes.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/\" \/>\n<meta property=\"og:site_name\" content=\"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting &amp; Tutorials\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-13T07:09:32+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-13T07:14:42+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/WordPress-Memory-Exhausted-Error.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2560\" \/>\n\t<meta property=\"og:image:height\" content=\"1440\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"James\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"James\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"17 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-memory-exhausted-error\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-memory-exhausted-error\\\/\"},\"author\":{\"name\":\"James\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#\\\/schema\\\/person\\\/42bec463c3b7b14c88f4c787a7009730\"},\"headline\":\"How to Fix the WordPress Memory Exhausted Error\",\"datePublished\":\"2026-10-13T07:09:32+00:00\",\"dateModified\":\"2026-10-13T07:14:42+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-memory-exhausted-error\\\/\"},\"wordCount\":3836,\"publisher\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-memory-exhausted-error\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/WordPress-Memory-Exhausted-Error.png\",\"keywords\":[\"memory limit\",\"PHP memory\",\"WordPress Errors\",\"WordPress support\",\"WordPress Troubleshooting\"],\"articleSection\":[\"WordPress Error\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-memory-exhausted-error\\\/\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-memory-exhausted-error\\\/\",\"name\":\"How to Fix the WordPress Memory Exhausted Error Fast\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-memory-exhausted-error\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-memory-exhausted-error\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/WordPress-Memory-Exhausted-Error.png\",\"datePublished\":\"2026-10-13T07:09:32+00:00\",\"dateModified\":\"2026-10-13T07:14:42+00:00\",\"description\":\"Hit the WordPress memory exhausted error? Find your real PHP limit, raise it safely, then cut what your site uses, with 9 causes and 9 clear fixes.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-memory-exhausted-error\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-memory-exhausted-error\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-memory-exhausted-error\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/WordPress-Memory-Exhausted-Error.png\",\"contentUrl\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/WordPress-Memory-Exhausted-Error.png\",\"width\":2560,\"height\":1440,\"caption\":\"WordPress Memory Exhausted Error\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/fix-wordpress-memory-exhausted-error\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Fix the WordPress Memory Exhausted Error\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/\",\"name\":\"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#organization\",\"name\":\"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/logo__1_-removebg-preview.png\",\"contentUrl\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/logo__1_-removebg-preview.png\",\"width\":600,\"height\":226,\"caption\":\"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials\"},\"image\":{\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/#\\\/schema\\\/person\\\/42bec463c3b7b14c88f4c787a7009730\",\"name\":\"James\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g\",\"caption\":\"James\"},\"description\":\"James is an experienced WordPress and WooCommerce specialist with over 10 years of practical experience. At WPChatSupport, he creates clear guides that help website owners fix WordPress issues, improve speed, secure their sites, and manage WooCommerce stores with confidence. His expertise includes store setup, plugin configuration, theme customization, payment gateway integration, and website troubleshooting. Through simple and helpful content, James supports users in solving technical problems and following best practices for online business growth.\",\"sameAs\":[\"https:\\\/\\\/blog.wpchatsupport.com\"],\"url\":\"https:\\\/\\\/www.wpchatsupport.com\\\/blog\\\/author\\\/24x7wpsupport\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Fix the WordPress Memory Exhausted Error Fast","description":"Hit the WordPress memory exhausted error? Find your real PHP limit, raise it safely, then cut what your site uses, with 9 causes and 9 clear fixes.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/","og_locale":"en_US","og_type":"article","og_title":"How to Fix the WordPress Memory Exhausted Error Fast","og_description":"Hit the WordPress memory exhausted error? Find your real PHP limit, raise it safely, then cut what your site uses, with 9 causes and 9 clear fixes.","og_url":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/","og_site_name":"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting &amp; Tutorials","article_published_time":"2026-10-13T07:09:32+00:00","article_modified_time":"2026-10-13T07:14:42+00:00","og_image":[{"width":2560,"height":1440,"url":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/WordPress-Memory-Exhausted-Error.png","type":"image\/png"}],"author":"James","twitter_card":"summary_large_image","twitter_misc":{"Written by":"James","Est. reading time":"17 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/#article","isPartOf":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/"},"author":{"name":"James","@id":"https:\/\/www.wpchatsupport.com\/blog\/#\/schema\/person\/42bec463c3b7b14c88f4c787a7009730"},"headline":"How to Fix the WordPress Memory Exhausted Error","datePublished":"2026-10-13T07:09:32+00:00","dateModified":"2026-10-13T07:14:42+00:00","mainEntityOfPage":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/"},"wordCount":3836,"publisher":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/#primaryimage"},"thumbnailUrl":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/WordPress-Memory-Exhausted-Error.png","keywords":["memory limit","PHP memory","WordPress Errors","WordPress support","WordPress Troubleshooting"],"articleSection":["WordPress Error"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/","url":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/","name":"How to Fix the WordPress Memory Exhausted Error Fast","isPartOf":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/#primaryimage"},"image":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/#primaryimage"},"thumbnailUrl":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/WordPress-Memory-Exhausted-Error.png","datePublished":"2026-10-13T07:09:32+00:00","dateModified":"2026-10-13T07:14:42+00:00","description":"Hit the WordPress memory exhausted error? Find your real PHP limit, raise it safely, then cut what your site uses, with 9 causes and 9 clear fixes.","breadcrumb":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/#primaryimage","url":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/WordPress-Memory-Exhausted-Error.png","contentUrl":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2026\/10\/WordPress-Memory-Exhausted-Error.png","width":2560,"height":1440,"caption":"WordPress Memory Exhausted Error"},{"@type":"BreadcrumbList","@id":"https:\/\/www.wpchatsupport.com\/blog\/fix-wordpress-memory-exhausted-error\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.wpchatsupport.com\/blog\/"},{"@type":"ListItem","position":2,"name":"How to Fix the WordPress Memory Exhausted Error"}]},{"@type":"WebSite","@id":"https:\/\/www.wpchatsupport.com\/blog\/#website","url":"https:\/\/www.wpchatsupport.com\/blog\/","name":"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials","description":"","publisher":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.wpchatsupport.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.wpchatsupport.com\/blog\/#organization","name":"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials","url":"https:\/\/www.wpchatsupport.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.wpchatsupport.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2025\/07\/logo__1_-removebg-preview.png","contentUrl":"https:\/\/www.wpchatsupport.com\/blog\/wp-content\/uploads\/2025\/07\/logo__1_-removebg-preview.png","width":600,"height":226,"caption":"WP Chat Support Blog \u2013 WordPress Help, Troubleshooting & Tutorials"},"image":{"@id":"https:\/\/www.wpchatsupport.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.wpchatsupport.com\/blog\/#\/schema\/person\/42bec463c3b7b14c88f4c787a7009730","name":"James","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/2279ad7c06143ec3d9993f3a47410189667d39a1d3d3ba17932e370f594894df?s=96&d=mm&r=g","caption":"James"},"description":"James is an experienced WordPress and WooCommerce specialist with over 10 years of practical experience. At WPChatSupport, he creates clear guides that help website owners fix WordPress issues, improve speed, secure their sites, and manage WooCommerce stores with confidence. His expertise includes store setup, plugin configuration, theme customization, payment gateway integration, and website troubleshooting. Through simple and helpful content, James supports users in solving technical problems and following best practices for online business growth.","sameAs":["https:\/\/blog.wpchatsupport.com"],"url":"https:\/\/www.wpchatsupport.com\/blog\/author\/24x7wpsupport\/"}]}},"_links":{"self":[{"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/posts\/4358","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/comments?post=4358"}],"version-history":[{"count":2,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/posts\/4358\/revisions"}],"predecessor-version":[{"id":4378,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/posts\/4358\/revisions\/4378"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/media\/4379"}],"wp:attachment":[{"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/media?parent=4358"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/categories?post=4358"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wpchatsupport.com\/blog\/wp-json\/wp\/v2\/tags?post=4358"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}