{"id":2021353,"date":"2024-07-26T07:01:16","date_gmt":"2024-07-26T07:01:16","guid":{"rendered":"https:\/\/wpx.net\/blog\/?p=2021353"},"modified":"2025-02-21T11:47:42","modified_gmt":"2025-02-21T11:47:42","slug":"wordpress-memory-exhausted-error-a-simple-solution","status":"publish","type":"post","link":"https:\/\/wpx.net\/blog\/wordpress-memory-exhausted-error-a-simple-solution\/","title":{"rendered":"WordPress Memory Exhausted Error\u00a0– A Simple Solution"},"content":{"rendered":"\n

In this article, we will go through and uncover uncertainties in regards to memory limits in WordPress. There are two types of memory limit and it is important that we distinguish them properly. Most articles regarding the topic name them both the same way, however, they are completely different. Of course, we will go through the errors associated with reaching this limitation and offer different solutions on how to fix them.<\/p>\n\n\n\n

<\/span>What does WordPress Memory Limit Error mean and where can I find it?<\/span><\/h2>\n\n\n\n

In terms of breaking everything down in simpler terms, the Memory Limit is connected to the built-in PHP structure of WordPress itself and it is set by default for each website installation.<\/p>\n\n\n\n

The default settings for WP Memory Limit are quite low and sometimes may hinder your workflow and operations in the back end while working on your website. Usually, they can be viewed from each WordPress Dashboard.<\/p>\n\n\n\n

To do so, you will need to login your website and navigate to Tools <\/strong>(1) and select Site Health <\/strong>(2):<\/p>\n\n\n\n

\"wordpress<\/figure>\n\n\n\n

Once you have selected the tab, you will need to choose the section Info<\/strong>:<\/p>\n\n\n\n

\"site<\/figure>\n\n\n\n

From there, it will load up and provide dropdown options for each specific part of your website, including the resources for your PHP Memory Limit. To view the specific limit set for your website, you need to select Server<\/strong> (1) and see field PHP Memory Limit <\/strong>(2):<\/p>\n\n\n\n

\"PHP<\/figure>\n\n\n\n

That\u2019s it! The next step would be to set a higher limit to test if that fixes the error.<\/p>\n\n\n\n

<\/span>Fix WordPress Memory Exhausted Error<\/span><\/h2>\n\n\n\n

To fix the error, we will need access to the website files. You can use an external FTP client or our own built-in File Manager<\/strong><\/a> to handle the process without much effort.<\/p>\n\n\n\n

The file responsible for your WP Memory Limit is the wp-config.php <\/strong>file. To adjust the limit, you would need to navigate through the original path: public_html<\/strong> and you should be able to find it there:<\/p>\n\n\n\n

\"fix<\/figure>\n\n\n\n

Once you find the file, you simply need to double-click on it to load up the code inside and edit it freely. The final step of the process will require putting a certain code with a higher limitation for your WP Memory Limit.<\/p>\n\n\n\n

The code looks like this:

define( ‘WP_MEMORY_LIMIT’, ‘1024M’ );<\/em><\/p>\n\n\n\n

You can see that the code indicates that the WP Memory Limit should be set to 1024 MB instead of the previous setting by default to 384 MB.<\/p>\n\n\n\n

The code needs to be set right above the last possible text and do not forget to Save <\/strong> the changes made to the file:<\/p>\n\n\n\n

\"wp<\/figure>\n\n\n\n

Once that is done, you can check it by going to Site Health <\/strong>again from Step 1 and revisiting the information shown by WordPress:<\/p>\n\n\n\n

\"php<\/figure>\n\n\n\n

That\u2019s it! You have successfully changed the WP Memory Limit for your website.  <\/p>\n\n\n\n

<\/span>What\u2019s the difference between WP Memory Limit and Server Memory Limit?<\/span><\/h2>\n\n\n\n

As promised in the beginning, it is important to mention the difference between two types of memory limit. The first one, which we discussed in this topic is named either WP Memory Limit or PHP Memory<\/strong> Limit<\/strong>, strictly connected to your WordPress installation. <\/p>\n\n\n\n

The next one is Server Memory Limit or in other words RAM<\/strong>. That is the allocated server resource for each WordPress website you get per your hosting plan configuration. That limitation is fixed and can not be changed, unless you upgrade the plan itself to a higher one with more resources or vice versa. <\/p>\n\n\n\n

I hope that we cleared all the confusion in regards to the two types of memory and how it can be addressed. If you still receive the same error after making the needed changes, then we recommend contacting our WPX Support for further technical guidance.<\/p>\n\n\n\n

If you find this article useful, you should also read our blog posts on How to Fix WordPress Permalink Issues<\/a> and How to Fix LCP Issue in WordPress<\/a>!<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

In this article, we will go through and uncover uncertainties in regards to memory limits in WordPress. There are two types of memory limit and it is important that we distinguish them properly. Most articles regarding the topic name them both the same way, however, they are completely different. Of course, we will go through […]<\/p>\n","protected":false},"author":29,"featured_media":2021354,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"cybocfi_hide_featured_image":"","footnotes":""},"categories":[86],"tags":[138,145,161,139,121],"ppma_author":[150],"class_list":["post-2021353","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress","tag-guide","tag-how-to","tag-memory-exhausted-error","tag-step-by-step","tag-wordpress"],"blocksy_meta":[],"authors":[{"term_id":150,"user_id":29,"is_guest":0,"slug":"svetlozar-todorov","display_name":"Svetlozar Todorov","avatar_url":{"url":"https:\/\/wpx.net\/blog\/wp-content\/uploads\/2024\/07\/Profile-Picture.png","url2x":"https:\/\/wpx.net\/blog\/wp-content\/uploads\/2024\/07\/Profile-Picture.png"},"0":null,"1":"","2":"","3":"","4":"","5":"","6":"","7":"","8":""}],"_links":{"self":[{"href":"https:\/\/wpx.net\/blog\/wp-json\/wp\/v2\/posts\/2021353","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wpx.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wpx.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wpx.net\/blog\/wp-json\/wp\/v2\/users\/29"}],"replies":[{"embeddable":true,"href":"https:\/\/wpx.net\/blog\/wp-json\/wp\/v2\/comments?post=2021353"}],"version-history":[{"count":3,"href":"https:\/\/wpx.net\/blog\/wp-json\/wp\/v2\/posts\/2021353\/revisions"}],"predecessor-version":[{"id":2022049,"href":"https:\/\/wpx.net\/blog\/wp-json\/wp\/v2\/posts\/2021353\/revisions\/2022049"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wpx.net\/blog\/wp-json\/wp\/v2\/media\/2021354"}],"wp:attachment":[{"href":"https:\/\/wpx.net\/blog\/wp-json\/wp\/v2\/media?parent=2021353"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wpx.net\/blog\/wp-json\/wp\/v2\/categories?post=2021353"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wpx.net\/blog\/wp-json\/wp\/v2\/tags?post=2021353"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/wpx.net\/blog\/wp-json\/wp\/v2\/ppma_author?post=2021353"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}