A WordPress image upload error is a server or configuration failure that prevents WordPress from saving an image to your media library — and the fix depends entirely on which error message you see, because each one points to a different root cause. Understanding what your website needs to run reliably starts with knowing how to interpret these signals.
Most guides dump nine steps in sequence and tell you to work through them all. This post maps each error message to its single most likely cause and the single most effective fix, so you are not applying memory-limit changes to a permissions problem.
South African businesses running WordPress on shared hosting — whether through Xneelo, Afrihost, or similar providers — face a compounding factor: shared plans cap PHP memory and upload limits at values lower than a developer might expect, and those caps are enforced at the server level, not within WordPress itself. WordPress image upload issues on shared SA hosting often trace back to limits the host controls, not settings you can change inside WordPress.
That distinction matters for how you apply the fixes below. For a broader look at keeping your site running smoothly, the website uptime monitoring guide covers the monitoring layer once your upload issue is resolved.
Quick Answer
A wordpress image upload error in WordPress is caused by one of six root issues: a temporary server glitch, a PHP memory or file-size limit, incorrect file permissions on the uploads folder, a plugin or theme conflict, an unsupported file type, or an inode or disk-space limit on the hosting account. Match your exact error message to the table below to identify the right fix — increasing memory when the problem is actually permissions wastes time. On South African shared hosting, check your host's PHP resource panel first before editing any configuration files.
Jump to a section
Fixing PHP memory and upload limits
Imagick and image processing conflicts
Is your WordPress site showing errors you can't pin down?
Send us a description of the error and your hosting environment — we'll tell you exactly which fix applies to your setup.
Get a free diagnosisDiagnosing Your WordPress Image Upload Error by Message
The error message WordPress displays is the fastest diagnostic tool available — each message points to a specific layer of the system. Reading it precisely, rather than treating all upload failures as the same problem, cuts troubleshooting time significantly.
| Error message | Most likely cause | First fix to try |
|---|---|---|
| HTTP error (generic, no detail) | Temporary server glitch or Imagick memory conflict | Retry upload; if persistent, switch to GD Library |
| "The server cannot process the image. This can happen if the server is busy or does not have enough resources…" | PHP memory limit too low for the image file | Increase WP_MEMORY_LIMIT in wp-config.php |
| "The uploaded file exceeds the upload_max_filesize directive in php.ini" | File is larger than the server's upload size cap | Increase upload_max_filesize and post_max_size via .htaccess or php.ini |
| "Unable to create directory wp-content/uploads/YYYY/MM. Is its parent directory writable by the server?" | Incorrect folder permissions on /wp-content/uploads/ | Set uploads folder permissions to 755 via FTP or cPanel |
| "Sorry, this file type is not permitted for security reasons." | File format not on WordPress's allowed list | Convert to JPG, PNG, or WebP before uploading |
No visible error message? If the upload progress bar fills and then the image simply disappears without any message, the most common culprit is an inode limit on shared hosting (the server has hit its maximum number of stored files) or a full disk. Contact your host to check both before troubleshooting PHP settings.
How to Fix PHP Memory and Upload Size Limits
PHP memory and file-size limits are set at the server level, which means the fix depends on what your hosting provider allows — and on shared hosting in South Africa, those ceilings are lower than developers often assume.
Xneelo, one of South Africa's largest shared hosting providers, publishes its maximum PHP resource limits: 512 MB memory, 64 MB POST size, 90 seconds execution time. Critically, new hosting packages are not configured to these maximum values by default — you need to raise them in your hosting control panel before editing any WordPress files.
Step 1 — Check what your hosting plan allows
Log into your hosting control panel (cPanel, Plesk, or your provider's dashboard). Look for "PHP Configuration", "PHP Options", or "Select PHP Version". This shows your current limits and the maximum your plan permits. If the maximum is already lower than what you need, contact your host — not WordPress.
Step 2 — Increase the WordPress memory limit
For the "server cannot process the image" error, add this line to your wp-config.php file, just before the line that reads "That's all, stop editing!":
wp-config.php addition:
define( 'WP_MEMORY_LIMIT', '256M' );
This tells WordPress to request up to 256 MB of PHP memory. Your hosting plan must allow this amount — if it doesn't, the line has no effect.
Step 3 — Increase upload and post size limits
The upload_max_filesize and post_max_size directives cannot be changed via wp-config.php at runtime — they must be set in your .htaccess file (Apache servers), php.ini, or .user.ini. The recommended starting values for a business site handling product photography or high-resolution brand imagery:
.htaccess method (add to your root .htaccess file):
php_value upload_max_filesize 64M
php_value post_max_size 128M
php_value memory_limit 256M
php_value max_execution_time 300
Note: post_max_size must be larger than upload_max_filesize — WordPress needs headroom beyond the file size itself to process the upload. On Xneelo shared hosting the maximum execution time is 90 seconds — set that value to 90 rather than 300. On other SA providers, check your PHP configuration panel for the permitted maximum before setting a higher value; on a VPS where you control php.ini directly, 300 seconds is a reasonable general starting point.
If your server runs Nginx rather than Apache, the .htaccess method does not apply — ask your hosting provider to update the configuration directly, or use a .user.ini file with the same key-value pairs.
Key point on shared hosting limits
On South African shared hosting plans, the host controls the ceiling. If your plan's maximum POST size is 64 MB and you need to upload a 90 MB image file, no configuration change inside WordPress will solve it — you need to either compress the image before uploading, or upgrade your hosting plan. Compress product images to under 2 MB for web use; there is no legitimate reason a website image should exceed 5 MB.
How to Fix WordPress File Permission Errors
A wordpress image upload error that reads "Unable to create directory wp-content/uploads" is a file permissions failure — WordPress cannot write to the folder where it stores uploaded images.
The correct permissions for WordPress directories and files are: 755 for folders (the server can read and execute; only the owner can write), and 644 for files (the server can read; only the owner can write). Any more permissive setting (777) is a security risk; any more restrictive setting (700, 600) will cause upload failures.
Fixing permissions via FTP
- Connect to your server using an FTP client (FileZilla works on Windows and Mac and is free).
- Navigate to your WordPress installation, then into
wp-content/. - Right-click the
uploadsfolder and select "File Permissions" (or "Properties"). - Enter
755in the numeric value field. - Tick "Recurse into subdirectories" and select "Apply to directories only".
- Click OK, then repeat with
644for files if individual files are also locked.
Fixing permissions via cPanel
If your host provides cPanel, use the File Manager: navigate to public_html/wp-content/uploads, select the folder, click "Permissions" in the toolbar, and enter 755. Tick the recursive directory option before saving.
Common mistake: Setting /wp-content/uploads to 777 "to make the error go away." Permissions of 777 mean any script on the shared server can write to your uploads folder — on shared hosting, that includes other customers' sites. Fix the root cause (wrong ownership or restrictive permissions) rather than removing all access controls.
VPS or dedicated server? On a Linux VPS running Apache, the error can be caused by incorrect file ownership rather than wrong permission bits. The web server process (typically running as www-data) must own the uploads directory. A developer can fix this with chown -R www-data:www-data /path/to/wp-content/uploads. chmod alone may appear to work but break again — ownership is the permanent fix.
Not sure whether your issue is permissions or PHP limits?
Share your exact error message and we'll give you a clear answer on which fix applies — no jargon, no guesswork.
Ask us now — no obligationHow to Resolve Imagick Image Processing Conflicts
Imagick is a PHP extension WordPress uses to process and resize images during upload. On shared hosting, Imagick can hit memory limits while processing large files — producing what is commonly called the WordPress image upload HTTP error, a generic message with no further detail. This is among the more frustrating upload failures because the message gives no indication of the actual cause.
Option A — Limit Imagick threading
Add this line to your root .htaccess file:
SetEnv MAGICK_THREAD_LIMIT 1
This restricts Imagick to single-threaded processing, which uses less memory on shared server environments. On many shared plans this alone resolves the HTTP error.
Option B — Switch to GD Library
WordPress can use either Imagick or GD Library to process images. GD Library is lighter on memory and typically handles the image sizes used on business websites without issue. To switch, add this code to your active theme's functions.php file, or paste it into a site-specific plugin (recommended so it survives theme updates):
Switch to GD Library (functions.php or site plugin):
add_filter( 'wp_image_editors', function( $editors ) {
$gd_editor = 'WP_Image_Editor_GD';
$editors = array_diff( $editors, array( $gd_editor ) );
array_unshift( $editors, $gd_editor );
return $editors;
} );Imagick vs GD Library — which should you use?
Imagick produces slightly better image quality at high compression ratios and handles a wider range of colour profiles. GD Library is faster, uses less memory, and is sufficient for web-optimised JPEG and PNG files — which are the only formats that matter for a standard business website. If you are running a photography studio or print-on-demand shop with high-fidelity image requirements, keep Imagick and increase memory limits instead. For most SA businesses, GD Library is the lower-maintenance choice.
Diagnosing Plugin and Theme Conflicts
Plugin and theme conflicts are the catch-all category — they produce variable error messages (or none at all) and can mimic any of the other causes. Security plugins, caching plugins, and image optimisation plugins are the most frequent offenders because they intercept the upload process.
The isolation method
- Deactivate all plugins from the WordPress admin Plugins page (Plugins → Installed Plugins → select all → Deactivate).
- Switch your active theme to a default WordPress theme (Appearance → Themes → activate Twenty Twenty-Four or similar).
- Attempt the image upload again. If it succeeds, the problem is a plugin or theme conflict.
- Reactivate your theme and test again. If the error returns, it is the theme.
- If the theme is not the issue, reactivate plugins one at a time, testing after each, until the error reappears. The last plugin reactivated is the conflict.
Skipping the isolation step: Many site owners try upgrading PHP, adjusting memory limits, and resetting permissions without isolating the cause first. A plugin conflict will persist through all of those changes because the problem is in application logic, not server configuration. Run the isolation test before touching PHP settings.
Unsupported File Types and Filename Issues
WordPress accepts JPG, JPEG, PNG, GIF, ICO, and WebP for images. When WordPress cannot upload images and the error message says "this file type is not permitted", the file format is the cause — not your server settings. SVG files are blocked by default because they can contain executable code; use the Safe SVG plugin for secure SVG support. HEIC (iPhone camera default format), TIFF, and BMP files are also rejected without additional configuration.
Filename problems are simpler to solve. WordPress rejects filenames containing spaces, accented characters, or special symbols (?, &, #, !, @, $). Rename the file before uploading: use only letters, numbers, hyphens, and underscores. An image named my-product-photo-1.jpg will upload cleanly; one named my product photo #1!.jpg will not.
Pre-upload checklist for images
Before uploading an image to WordPress: (1) confirm the format is JPG, PNG, or WebP; (2) rename the file to use only letters, numbers, and hyphens; (3) compress the image to under 500 KB for most web uses — a 10 MB product photo adds no visual benefit over a well-compressed 300 KB version and creates upload and page-speed problems. Tools like Squoosh (free, browser-based) compress images without requiring software installation.
Why South African Businesses Choose Growth Pulse Media for WordPress Support
Growth Pulse Media was built by Dirk van Greuning, who scaled a South African ecommerce operation before founding the agency — which means WordPress configuration problems, hosting panel limitations, and the gap between what a global tutorial recommends and what a South African shared host actually allows are familiar territory, not theoretical concepts.
Our web design service treats your site as a business asset, not just a design project. That includes configuring PHP resource settings correctly for your hosting environment, setting up proper file permissions at launch (not after the first upload error), and building on a WordPress stack that stays maintainable. All work is executed in-house — no juniors, no outsourcing — and we keep a limited client load so every site gets senior attention.
When a WordPress error surfaces, we diagnose from the error message outward, not from a checklist inward. Applying the right WordPress image upload fix in one pass — rather than working through nine sequential steps — is the difference between a 10-minute resolution and a three-hour troubleshooting session. For related reading on keeping your WordPress site technically sound, see our guides on WordPress contact form email failures and WordPress scheduled posts not publishing — both follow the same root-cause diagnostic model.
Who This Guide Is NOT For
You have a managed WordPress host with white-glove support. If your hosting plan includes 24/7 WordPress-specific support (WP Engine, Kinsta, and similar), contact them directly — they have access to your server configuration and can resolve PHP-level issues in minutes without you touching a configuration file.
You need to upload files larger than your host's maximum POST size. If Xneelo's 64 MB POST limit, or your host's equivalent ceiling, is genuinely too low for your use case (video files, high-resolution print assets), WordPress configuration changes will not override the server limit. Evaluate a VPS plan or use cloud storage (Google Drive, Amazon S3) with a plugin to serve media, rather than the WordPress media library.
You are running a heavily customised WordPress build with a page builder. Page builders (Elementor, Divi, WPBakery) add their own image handling hooks and can produce upload errors that don't respond to standard PHP fixes. If the isolation test points to your page builder plugin, the fix is often a plugin update or a setting within the builder's own configuration panel — not server settings.
You are looking for a way to allow SVG uploads without security review. Adding define('ALLOW_UNFILTERED_UPLOADS', true); to wp-config.php disables WordPress's security filtering for all uploads and is not appropriate for a business site. Use the Safe SVG plugin, which sanitises SVG files before allowing them into the media library.
Spending too much time on technical fixes instead of running your business?
Book a free technical audit — we'll review your WordPress hosting setup and tell you what's causing errors and what needs to change.
Book your free WordPress auditFrequently Asked Questions
Why does WordPress show an HTTP error when uploading images?
A generic HTTP error during WordPress image upload most commonly points to an Imagick memory conflict on shared hosting, or a temporary server resource spike. The first step is to retry the upload — if the error is intermittent, it is likely a transient server load issue. If it is consistent, switch WordPress's image processing library from Imagick to GD Library by adding a filter in functions.php, or add SetEnv MAGICK_THREAD_LIMIT 1 to your .htaccess file to restrict Imagick to single-threaded processing. Increasing your PHP memory limit via wp-config.php can also resolve this if the root cause is memory exhaustion.
What file permissions should the WordPress uploads folder have?
The wp-content/uploads folder should be set to 755 permissions: the server can read and execute, but only the file owner can write. Individual image files inside should be 644. Never set the uploads folder to 777 — on shared hosting, that allows any script on the same server to write to your folder, which is a security risk. Apply the permissions recursively to all subdirectories via FTP or cPanel File Manager, selecting "apply to directories only" when setting 755.
How do I increase the maximum image upload size in WordPress?
The directives upload_max_filesize and post_max_size must be set in .htaccess, php.ini, or .user.ini — they cannot be changed in wp-config.php. The memory limit is the exception: adding define('WP_MEMORY_LIMIT', '256M'); to wp-config.php tells WordPress to request up to that amount of PHP memory, subject to your host's ceiling. On shared hosting, your host controls the ceiling for all values — check your PHP configuration panel before editing any files. On Xneelo shared hosting the maximum POST size is 64 MB, which cannot be exceeded without upgrading your plan.
Can I upload SVG files to WordPress?
WordPress does not support SVG uploads by default, because SVG files can contain executable code that poses a security risk. To enable safe SVG uploads, install the Safe SVG plugin, which sanitises the file before adding it to the media library. Do not use the ALLOW_UNFILTERED_UPLOADS constant in wp-config.php on a live business site — it disables security filtering for all file types, not just SVG.
How do I fix a WordPress image upload error caused by a plugin?
To diagnose a plugin conflict, deactivate all plugins from your WordPress admin panel, then try the upload again. If it succeeds, reactivate plugins one at a time, testing after each, until the error returns — the last reactivated plugin is the conflict. Security plugins, caching plugins, and image optimisation plugins are the most frequent sources of upload conflicts because they intercept the upload process. Once identified, check the plugin's settings for upload-related options, or contact the plugin developer with the specific error message.
Why does my WordPress image upload fail silently with no error message?
A silent upload failure — the progress bar completes but the image does not appear — usually points to either an inode limit or a full disk on your shared hosting account. Each file and folder stored on your server counts as one inode; shared hosts typically cap the total. Contact your hosting provider and ask them to check your current inode usage and available disk space. If either is at or near the limit, you will need to clean up old files, delete unused plugins or themes, or upgrade your plan.
Your WordPress Site Should Work Without You Debugging It
Growth Pulse Media builds and maintains WordPress sites for South African businesses — with correct PHP configurations, proper file permissions, and a setup that doesn't break when you add a product image. Senior attention, in-house execution, and a response within 24 hours. No obligation.
Talk to us about your WordPress site

