How to Fix WordPress Image Upload Error Post-Processing of the Image Failed.
Why Am I Getting the Fix the Post-Processing of the Image Failed Error in WordPress?
As you probably know, you get the above error when you try to upload an image in WordPress. In my case, this appeared overnight, and while I know something had to have changed or updated, I couldn’t tell you what it was. The trouble was the image I was uploading was most definitely meeting the sizing criteria listed in the error. It was only 1100px wide. So something else was going on.
It turns out when you get this error it’s because your PHP settings have maxed out.
Now if you’re not technical, don’t let that spook you. It just means that the coding language that runs your website needs more room to operate on the server. Think of it as needing more elbow room to do it’s thing.
Here are the step-by-step instructions on how to use cPanel, the interface that comes with your hosting package, to fix the error.
If you’re not technical you can always just call your hosting company and ask them to “set your PHP settings to their maxes” and that will get you this same result.
Here’s How to Fix the Post-Processing of the Image Failed Error Manually:
Note: I recently came across another way to fix this error. I will say Method 1 below has worked for YEARS. It wasn’t until today that I guess my site got big enough that Method 2 was required.
Method 1
Log into your cPanel – most often it’s just at yourdomainname.com/cpanel
(This will be the login information you received from your host to log into that account.)
Scroll down to “Software” and click on “Select PHP Version.”
You’ll see what PHP version you’re currently set at and a couple of tabs. Click on the “Options” tab.
From here all you need to do is set your memory_limit line to the max in the drop down – in my case, this was 512M. It saves when you select it, so don’t worry about having to hit a “Save” or “Commit” button anywhere.
Method 2 – Swap your PHP Extensions
This one is probably going to require your hosting company to jump on board with some tech support, but if Method 1 didn’t help resolve the issue, this worked right away when I ran into this error again years later and was already maxed out on my PHP Memory Limit size.
You need to ask your host to disable the gd php extension, and enable the imagic extension.
Method 3 – Installing the necessary module
Error logs
.htaccess: Invalid command ‘SetEnv’, perhaps misspelled or defined by a module not included in the server configuration, referer:
The control of internal environment variables that are used by various Apache HTTP Server modules are controlled by the module mod_env.
By default module ‘mod_env’ will not be enabled in apache2.4. This will cause below error while using ‘SetEnv’ in htacess file.
Invalid command ‘SetEnv’, perhaps misspelled or defined by a module not included in the server configuration
To resolve this problem, we need to install the module ‘mod_env’ manually.
For easyapache4 users,
#yum install ea-apache24-mod_env.x86_64