WordPress Fix: Fatal Error: Allowed Memory Size of 33554432 bytes exhausted
Fatal error: Allowed memory size of 33554432 bytes exhausted:
- Download, back up and open: wp-settings.php in wordpad/notepad
- Search for define(‘WP_MEMORY_LIMIT’, ’32M’);
- Change 32M to 64M : define(‘WP_MEMORY_LIMIT’, ’64M’);
- Enjoy

didn’t work for me
Try now. I had wp_cofig.php instead of wp_settings.php
sorry about that.
Hey,
Thanks for the advice.
It works!
Thank you for this solution!
Hello!
Very Interesting post! Thank you for such interesting resource!
PS: Sorry for my bad english, I’v just started to learn this language
See you!
Your, Raiul Baztepo
Hi all,
got the same problem. I haven’t tried this solution yet, but before, don’t you think that, by this way, we “delay” the problem for later ?
And then, in a few month or in a few years, we will reach the 64M limit again, and then be in front of a bigger problem ?
Flex you may be right. But the solution is equally applicable to Drupal too. And it seems to work pretty well. Let me know if you have any other solution.
Sur I will !
maybe we have to ask direct to the wordpress creators…
I have an other question : is this 64M yhe higher limit, or we can “go further” to 128M for example ?
On my specific problem, I can precise that I used a lot of times the uploader of wordpress, instead of a ftp program. I used to upload a lot of big PDF files that way.
But the website is globally not so big, only 500 articles, on a quite big host server. Far smallest than one of my other website with nearly 2.000 pages… same type of host, and still no problem.
I think that there is a corelation between this memory problem, and the fact to use a lot the uploader with big files.
Do you think I can be right ?
You may be right. But really, I am NOT the expert.
What I understand is with the regular WP, only 32 is fine. As soon as we start adding more functionality via numerous plugins, we start using more resources hence 64 M. I don’t know who came up with this number but it seems to work very well.
there are literally 100s of topics in WP forum with same question and same answer. Please let me know if you find out the root cause.
I tried to switch to 64M as suggested here, and the problem seems to be solved (for now).
it seems that as soon as one of your page exceed a certain size with 32M, it “launches” the problem, which can only be resolved by switching to 64M.
I would say : do not create too heavy pages with wordpress.
Well.
I am glad that your problem is at least solved (for now!). I would recommend that you delete old plugins and plugins that you don’t use anymore. I also found that there are some WP plugins that simply uses too much of MYSQL space such as “Recenly Popular” or “WP-Stats” plugins. Don’t use them if you don’t need them.
As I said before, the same 32 MB exceed problem occurs with Drupal too if you try to install too many MODULES at the same time.
I am glad that I don’t use Drupal. WordPress is way easier for non-tech person like myself!
Obrigado! tks.
Thanks for advice, good idea.
Thanks so much! I was so scared I had destroyed my site with a plugin….
Cool thanks !!!
Thanks! It worked.
It worked 4 me…..
I am confused….. my cpanel tells max limit to 32M
now i only changed in settings.php to 64M.
if wordpress was using 32M then it must be restricted on the server side itself ….
I guess?
Grand post about search engine optimization. I’m honestly dumfounded that it has not been stated earlier.
Hey,
this worked pefect for me, thank you very much….
Worked perfect for me!! Thanks.
Works! there is also a description here:
http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP
Thanks!
This did not work for me and gave a fatal error, so I had to roll back to my backed up wp-settings.php
Thanks so much for this. I was having a lot of trouble updating some of my blogs to the latest version of WordPress. This fixed the problem perfectly.
it works! thank U
Well done, worked perfectly, thanks for sharing.
Thanks
I stay having some broblems, but the majorety are resolved =)
Thanks so much….it worked!
By the way, for those folks that use VPS/Reseller hosting for multiple domains, be sure to go to the wp-settings.php file for each affected domain.