WordPress Cannot Create Directory Uploads? 11 Fixes That Work

A laptop on a clean desk showing simple folder shapes and a file manager layout — wordpress cannot create directory uploads fix guide
WordPress needs a working uploads folder before it can save any image — when the folder cannot be created, every upload stops.

You try to upload an image, and WordPress answers with a blunt message: unable to create directory. The upload fails, the Media Library stays empty, and no image can be added to any post. When wordpress cannot create directory uploads appears, the site is telling you that it cannot make the folder it needs to store your files.

The good news is that the message points at a small set of causes. The uploads folder may be missing, its permissions may be wrong, the upload path may point somewhere that does not exist, the disk may be full, or the server may not own the folder. This guide works through those causes in order, from the simplest check to the deeper server fixes. Before you change any file or folder on the server, take a full backup of the site, including the database, so you can restore it if anything goes wrong.

Table of Contents

  • Why This Error Happens
  • Quick Checks
  • Diagnosing the Problem
  • Fix 1: Create the Uploads Folder Manually
  • Fix 2: Fix the Folder and File Permissions
  • Fix 3: Check the Upload Path Setting
  • Fix 4: Free Up Disk Space and Check Your Quota
  • Fix 5: Ask Your Host to Fix File Ownership
  • Fix 6: Deactivate Plugins and Test for a Conflict
  • Fix 7: Check Security Rules That Block New Folders
  • Fix 8: Check the Month and Year Folder Setting
  • Fix 9: Fix the Path After Moving or Migrating the Site
  • Fix 10: Check Server Restrictions with Your Hosting Provider
  • Fix 11: Restore from a Backup and Rebuild the Uploads Folder
  • What to Avoid
  • Frequently Asked Questions
  • Conclusion
  • Helpful Official Resources

Why This Error Happens

WordPress stores every uploaded file in the wp-content/uploads folder, inside smaller folders named by year and month. When you upload a file, WordPress checks whether the folder for the current month exists, creates it if needed, and saves the file inside it. If any step in that chain fails, you see the directory error. These are the reasons it fails most often.

1. The Uploads Folder Is Missing

The uploads folder can go missing after a site move, a failed update, or an accidental deletion. WordPress tries to create it, but if the parent folder does not allow new folders, the attempt fails. A missing folder is the simplest cause of wordpress cannot create directory uploads, and it is also the easiest to fix, because creating the folder by hand takes a minute.

2. The Folder Permissions Are Wrong

Permissions are numbers that control who can read, write, and run files on the server. If the wp-content folder or the uploads folder has permissions that block writing, WordPress cannot create new folders inside it. Wrong permissions often appear after moving a site, restoring a backup, or changing hosts, when the move resets the numbers to values that do not suit WordPress.

3. The Server User Does Not Own the Folder

Even with correct permissions, WordPress can be blocked if the server user does not own the folder. The web server runs as a particular user account, and it can only write to folders that account owns or has write access to. After a migration, files sometimes end up owned by a different account, and the server is locked out of its own folders. Only the hosting provider can fix ownership safely.

4. The Upload Path Points to the Wrong Place

WordPress stores the upload path in its settings. If that path points to a folder that does not exist, or to a folder from an old server, WordPress tries to create directories in the wrong place and fails. This happens most often after moving a site, when the old path is carried over but the folder structure on the new server is different.

5. The Disk Is Full or the Quota Is Reached

A full disk cannot accept new files or new folders. Hosting accounts have disk quotas, and a site that has grown with years of images, backups, and logs can reach its limit quietly. When the quota is reached, WordPress cannot create the month folder, and the upload fails with the directory error — even though the folder settings are all correct.

6. A Plugin or Security Rule Blocks Folder Creation

Security plugins and server security rules can block WordPress from creating folders, as a protection against malicious uploads. A rule that is too strict blocks legitimate uploads as well. A plugin that changes the upload path, or that manages media storage, can also redirect uploads to a folder that does not exist. In both cases the folder settings look fine, but something stands between WordPress and the folder, so wordpress cannot create directory uploads persists until that block is removed.

Quick Checks

Two minutes before the deep fixes.

  • Open your host’s File Manager and look inside wp-content — does an uploads folder exist?
  • Check the hosting control panel for disk usage — is the account near its quota?
  • Think about when it started — did wordpress cannot create directory uploads begin after moving hosts, restoring a backup, or installing a plugin?
  • Try uploading a very small image — does it fail with the same directory message?
  • Check whether the error names a specific folder path — write that path down, because it shows where WordPress is looking.
  • Check Tools, then Site Health, for warnings about file permissions or the uploads folder.

Diagnosing the Problem

SymptomCauseGo to Fix
Uploads folder is missingFolder deleted or never createdFix 1
Folder exists but uploads failWrong permissionsFix 2
Error names a strange or old pathUpload path setting is wrongFix 3
Error started when the site grew largeDisk full or quota reachedFix 4
Error started after moving hostsFile ownership is wrongFix 5
Error started after a plugin changePlugin conflictFix 6
Error only in certain monthsMonth folder setting or ruleFix 8
Error after migration, old paths shownPaths carried over from old serverFix 9

Fix 1: Create the Uploads Folder Manually

Start by checking whether the folder exists, and creating it by hand if it does not. This is the simplest fix, and it solves the error whenever the folder itself is the missing piece.

A person organising paper folders and files on a desk beside a laptop showing folder shapes
If the uploads folder is missing, creating it by hand in the File Manager takes a minute — and uploads can start again.
  1. Before you start, take a full backup of the site, including the database, so you can restore it if needed.
  2. Open your host’s File Manager and go to the wp-content folder.
  3. Look for a folder named uploads. If it is there, skip to Fix 2 — the folder exists and the cause is elsewhere.
  4. If it is missing, click New Folder and create a folder named exactly uploads, all lowercase.
  5. Open the new uploads folder and check that it is empty and ready.
  6. Try uploading a small image through Media, then Add New, and check whether it succeeds.
  7. If it succeeds, WordPress will create the year and month folders inside uploads on its own from now on.

The folder name must be exactly uploads, spelled with one word and all lowercase, inside wp-content. A folder named Uploads or upload will not be found. If the File Manager refuses to create the folder, the wp-content folder itself has a permissions or ownership problem, and Fix 2 and Fix 5 cover those. Do not create the folder on your computer and upload it as a file — use the New Folder button in the File Manager so the folder is created with the server’s own settings. After creating the folder, the first successful upload proves the fix. If the folder exists but uploads still fail, the permissions are the next suspect, and Fix 2 checks them.

Fix 2: Fix the Folder and File Permissions

Permissions control who can write to a folder. If the uploads folder or its parent has permissions that block writing, WordPress cannot create the month folders it needs, and every upload fails.

  1. Before you start, take a full backup of the site, including the database, so you can restore it if needed.
  2. Open your host’s File Manager and go to the wp-content folder.
  3. Right-click the uploads folder and choose Permissions or Change Permissions.
  4. Set folders to 755 and files to 644 — these are the standard WordPress permissions.
  5. Apply the change to the folder and all the folders and files inside it, if the File Manager offers that option.
  6. Check the wp-content folder itself and confirm it is also set to 755.
  7. Never set permissions to 777 — that gives everyone full access and leaves the site open to attack.

The numbers 755 and 644 are the standard values WordPress expects. In plain language, 755 on a folder means the owner can read, write, and enter it, while others can read and enter it. 644 on a file means the owner can read and write it, while others can only read it. Those values let WordPress work while keeping the site reasonably safe. Setting 777 removes all protection and is never the right fix, even if it seems to work — it invites abuse, and many hosts will flag or revert it. Some hosts offer a permissions repair tool in the control panel that sets the standard values safely; use that if your host provides it. If the permissions are already correct and uploads still fail, the upload path may be pointing elsewhere, and Fix 3 checks it. For a Media Library that will not load, our guide to WordPress media library not loading covers that problem.

Fix 3: Check the Upload Path Setting

WordPress stores the path where uploads should go. If that path is wrong — pointing to a folder that does not exist, or to a location from an old server — WordPress tries to create directories in the wrong place and fails.

  1. Before you start, take a full backup of the site, including the database, so you can restore it if needed.
  2. Go to Settings, then Media, in the WordPress dashboard, and look for an upload path field if your version shows one.
  3. If the field shows a path, check that it reads wp-content/uploads and nothing else unusual.
  4. If the path is blank, that is normal on most sites — WordPress uses the default path when the field is empty.
  5. If the path names an old server folder, clear it back to the default, or set it to wp-content/uploads, and save.
  6. Try uploading a small image and check whether the error is gone.
  7. If there is no path field in Settings, then Media, ask your host to check the upload path stored in the database.

The upload path can also be set in the wp-config.php file with a line defining the uploads folder. If such a line exists and points to the wrong place, it overrides the dashboard setting. Do not edit wp-config.php unless you are comfortable doing so, and always save a copy first. The safe route is to ask your host to check both the database setting and the wp-config.php file, and to correct whichever one is wrong. A wrong path often carries a tell-tale sign: the error message names a folder path that does not match your current server. Write down the path from the error message and show it to your host — it tells them exactly where WordPress is looking. If the path is correct and uploads still fail, disk space is the next check, and Fix 4 covers it.

Fix 4: Free Up Disk Space and Check Your Quota

A full disk cannot accept new folders or files. Hosting accounts have quotas, and a site can reach its limit through years of images, backups, logs, and old files that nobody cleared out.

  1. Open your hosting control panel and find the disk usage display for your account.
  2. Check how much space is used and how much is free — if usage is at or near 100 percent, the disk is the cause.
  3. Look for large backup files stored on the server, and download the ones you want to keep, then delete the rest from the server.
  4. In WordPress, go to Media, then Library, and delete images you no longer use, then empty the media trash.
  5. Check for old log files and cache files in the File Manager, and clear caches through your caching plugin if you use one.
  6. Ask your host whether the quota can be raised, or whether old backups held by the host can be cleared.
  7. After freeing space, try uploading a small image and check whether the error is gone.

Backups are the most common hidden space eater. A backup plugin that stores every backup on the same server can fill the disk within months. Keep one or two recent backups on the server, download older ones to your computer or cloud storage, and delete the rest from the server. The media trash deserves attention too: deleting an image in WordPress moves it to the trash, but the file stays on the disk until the trash is emptied. Empty the trash from the Media Library to recover the space. If the disk has plenty of free space and uploads still fail, the ownership of the folders may be wrong, and Fix 5 asks your host to check it. For images that fail for size reasons, our guide to WordPress image upload exceeds maximum file size covers that limit.

Fix 5: Ask Your Host to Fix File Ownership

Ownership decides which server account can write to a folder. If the files are owned by a different account than the one the web server runs as, WordPress cannot create folders even when the permissions look correct. Only the host can fix ownership safely.

Close-up of hands typing on a laptop keyboard with simple folder and file shapes on the screen
Ownership is invisible in the dashboard — when permissions look right but uploads still fail, ask the host to check who owns the folders.
  1. Note the exact error message, including any folder path it names, and when the problem started.
  2. Contact your hosting provider’s support and describe the error and the fixes you have already tried.
  3. Ask them to check the ownership of the wp-content and wp-content/uploads folders.
  4. Ask them to set ownership so the web server user can write to the uploads folder.
  5. Ask them to confirm the permissions at the same time, so ownership and permissions are fixed together.
  6. After they confirm the change, try uploading a small image and check whether it succeeds.
  7. Keep a note of what they changed, so the same problem is faster to solve if it returns after a future move.

Ownership problems almost always follow a site move. When files are copied from one server to another, they can arrive owned by the account that copied them, rather than by the account the web server uses. The result is a site that reads fine but cannot write anything — uploads fail, updates fail, and new folders cannot be created. Do not try to change ownership yourself with server commands unless you know the server well; a wrong ownership change can lock you out of your own files. Your host changes ownership routinely and can do it in minutes. When you contact them, mention that the problem started after a move, if it did — that single detail points them straight at ownership. If ownership is correct and uploads still fail, a plugin may be redirecting uploads, and Fix 6 tests for that.

Fix 6: Deactivate Plugins and Test for a Conflict

Plugins that manage media, change the upload path, or move uploads to external storage can redirect WordPress to a folder that does not exist. Deactivating plugins one group at a time finds the culprit without deleting anything.

  1. Before you start, take a full backup of the site, including the database, so you can restore it if needed.
  2. Go to Plugins, then Installed Plugins, in the WordPress dashboard.
  3. Deactivate all plugins at once using the bulk actions menu, then test an upload.
  4. If the upload works, reactivate the plugins one at a time, testing an upload after each one.
  5. When uploads fail again, the last plugin you reactivated is the culprit — leave it deactivated.
  6. Check whether that plugin has an update available, and check its settings for an upload path or storage option.
  7. If the plugin is essential, ask the plugin author for help through the official support forum, and describe the directory error.

Media management plugins and offload plugins are the most common culprits, because they change where WordPress stores files. A plugin set to store uploads on an external service can fail if the service settings are wrong, and WordPress reports the failure as a directory error. Security plugins can also block folder creation. Deactivating all plugins at once is safe: it does not delete settings, and reactivating restores everything. If you cannot reach the dashboard, rename the plugin folders through your host’s File Manager — renaming a folder deactivates that plugin. Ask your host for help if you have not used the File Manager before. If uploads fail even with all plugins off, a security rule may be the block, and Fix 7 checks that. For a broader guide to plugin problems, our guide to WordPress plugin conflict fix covers the full process.

Fix 7: Check Security Rules That Block New Folders

Security plugins and server security rules protect the site by limiting what WordPress can write. A rule that is too strict can block folder creation entirely, so uploads fail even though the folder settings are correct.

  1. Before you start, take a full backup of the site, including the database, so you can restore it if needed.
  2. Check your security plugin’s settings for options about file writing, folder creation, or hardening.
  3. Look for a setting that disables file editing or blocks new folders, and note its current value before changing it.
  4. Temporarily turn off the strictest hardening option, then test an upload.
  5. If the upload works, the rule was too strict — turn the option back on and add an exception for the uploads folder if the plugin allows it.
  6. Check the .htaccess file in the site’s main folder for rules that block access to wp-content — do not edit it without saving a copy first.
  7. If you find a blocking rule and are unsure what it does, ask your host to review it before changing it.

Security hardening is valuable, and the goal is not to remove it, but to shape it so legitimate uploads pass. Many security plugins offer a way to allow the uploads folder while keeping other protections on. The .htaccess file deserves care: it controls how the server handles requests, and a wrong edit can take the site down. Save a copy before opening it, change one thing at a time, and test after each change. If you did not write the rules in .htaccess yourself, ask your host to review them — they can tell in seconds whether a rule blocks uploads. If no security rule is blocking uploads, the month and year folder setting is the next check, and Fix 8 covers it.

Fix 8: Check the Month and Year Folder Setting

WordPress normally organises uploads into folders by year and month, creating a new folder each month. If that setting, or the month folder itself, is the problem, uploads fail at the start of a new month and work fine before it.

A desk with a laptop, a notebook with a checklist, and neat filing folders stacked beside it
Work through the checks in order and tick each one off — the cause is usually found before the list runs out.
  1. Go to Settings, then Media, in the WordPress dashboard.
  2. Find the option Organize my uploads into month- and year-based folders and note whether it is ticked.
  3. Open the File Manager and look inside uploads for a folder named with the current year, such as 2026.
  4. Open the year folder and look for a folder named with the current month number, such as 11.
  5. If the month folder is missing and WordPress cannot create it, create it by hand with the New Folder button.
  6. Set the new folder’s permissions to 755, then test an upload.
  7. If uploads work with the setting unticked but fail with it ticked, leave it unticked until your host fixes the underlying folder problem.

The month-folder pattern has a tell-tale sign: uploads work for weeks, then fail on the first day of a new month, when WordPress needs a new month folder. If that pattern matches your site, the month folder is the focus. Creating the folder by hand is a safe workaround, but it only fixes one month — the underlying permissions or ownership problem will return next month, so still work through Fixes 2 and 5. Unticking the setting is also a workaround, not a cure: it stores all uploads in one folder, which works fine for small sites but becomes messy on large ones. Use the workaround to keep publishing, and fix the root cause with your host. If the setting is fine and uploads still fail, a site move may have left old paths behind, and Fix 9 repairs those.

Fix 9: Fix the Path After Moving or Migrating the Site

Moving a site carries settings from the old server to the new one. If the upload path, or the stored folder locations, still name the old server, WordPress tries to create directories where they cannot exist, and uploads fail.

  1. Before you start, take a full backup of the site, including the database, so you can restore it if needed.
  2. Read the error message carefully and write down the full folder path it names.
  3. Compare that path with the real path shown in your host’s File Manager — if they differ, the stored path is stale.
  4. Check the wp-config.php file for any line that sets an upload path, and note what it says. Do not edit it without saving a copy first.
  5. Ask your host to check the upload path stored in the database and correct it to the new server’s path.
  6. Ask them to check for other stale paths in the database, such as old domain names or folder locations.
  7. After the paths are corrected, test an upload and confirm the new file lands in the correct uploads folder.

Migration plugins usually update paths automatically, but a manual move — copying files and importing the database by hand — can leave stale paths behind. The database holds the upload path, the site address, and the locations of media files, and all of them must match the new server. Searching and replacing paths in the database is delicate work, because the data is stored in a format that breaks if edited carelessly. That is why the safe route is to ask your host, or to use a reputable migration plugin’s search-and-replace tool, rather than editing the database by hand. If the paths are correct and uploads still fail, a server-level restriction may be the cause, and Fix 10 asks your host to check it. For uploads that fail with a different message, our guide to WordPress image upload failed covers that problem.

Fix 10: Check Server Restrictions with Your Hosting Provider

Servers enforce restrictions that WordPress cannot override: limits on which folders PHP can write to, security modules that block folder creation, and disk quotas that stop writes. These restrictions are invisible from the dashboard, and only your host can see and change them.

  1. Note the exact error message, the folder path it names, and the fixes you have already tried.
  2. Contact your hosting provider’s support and describe the error and the steps you have taken.
  3. Ask them to check whether a PHP restriction, such as open_basedir, limits where WordPress can write.
  4. Ask them to check whether a security module, such as ModSecurity, is blocking folder creation.
  5. Ask them to confirm the disk quota and the ownership and permissions of the uploads folder in one check.
  6. Apply whatever fix they recommend, and test an upload while they are still helping you if you can.
  7. Ask them to confirm the fix in writing, so you have a record if the problem returns.

open_basedir is a PHP setting that limits file access to certain folders. If the uploads folder falls outside the allowed folders, WordPress cannot create directories there, whatever the permissions say. ModSecurity is a firewall that inspects requests and can block ones that look suspicious. Both are server settings, and both are routine for a host to check and adjust. When you contact support, include the details from step 1: the error message, the path, and the fixes you tried. Those details save a round of questions. Do not try to change server settings yourself unless you manage the server — a wrong change can affect every site on the account. If the host finds no restriction and uploads still fail, the last resort is a clean restore, which Fix 11 covers.

Fix 11: Restore from a Backup and Rebuild the Uploads Folder

When every fix has failed, restoring from a backup taken before the problem started removes whatever change broke uploads. Rebuilding the uploads folder cleanly, with the host’s help, gives WordPress a fresh start.

A laptop on a desk beside labelled storage boxes and a filing tray in a bright tidy room
A backup taken before the problem started is the fastest way back when every other fix has failed.
  1. Before you start, take a fresh backup of the site as it is now, so nothing is lost by restoring.
  2. Find the most recent backup from before the uploads problem started.
  3. Ask your host to restore that backup, or restore it through your backup plugin, following its instructions.
  4. After the restore, check that the uploads folder exists and has permissions 755.
  5. Test an upload with a small image and confirm it appears in the Media Library.
  6. If the restore fixes uploads, reapply any changes made since the backup — new posts, new settings — one at a time, testing uploads after each.
  7. If the restore does not fix uploads, ask your host to rebuild the uploads folder structure with correct ownership and permissions.

Restoring is a bigger step than the earlier fixes, which is why it comes last. It can undo recent work, so the fresh backup in step 1 matters: it lets you recover anything the restore removes. The step-by-step reapplication in step 6 is how you find the change that broke uploads — if uploads fail again after one particular change, that change is the cause. If wordpress cannot create directory uploads survives a restore and a rebuilt folder structure, the fault is on the server itself, and your host must fix it or move the site to a healthy server. Keep the record of everything you tried, because it shows the host that the site side has been fully checked. Do not keep changing settings at random after a restore — each untested change adds a new possible cause.

What to Avoid

  • Do not set permissions to 777 — it leaves the site open to attack and most hosts will flag it.
  • Do not delete the uploads folder to fix the error — deleting it removes every image on the site.
  • Do not edit wp-config.php or the database without saving a copy first — one wrong change can take the site down.
  • Do not edit the database by hand to fix paths — use your host or a reputable migration tool instead.
  • Do not ignore the backup step before server changes — a backup turns a risky edit into a safe one.
  • Do not change server settings yourself unless you manage the server — ask your host instead.
  • Do not keep uploading the same file and hoping — find the cause with the checks above, then fix it once.

Frequently Asked Questions

Why can I upload files through the File Manager but not through WordPress?

Because the File Manager runs as your hosting account, while WordPress runs as the web server user. If the web server user cannot write to the folder, WordPress uploads fail even though your account can write there. Ownership is the difference, and only your host can fix it. Fix 5 explains this.

Why did the error appear at the start of a new month?

Because WordPress creates a new month folder for each month’s uploads. If it cannot create that folder, uploads fail on the first day of the month and worked fine before. Check the month folder and the permissions, and create the folder by hand as a workaround. Fix 8 covers this pattern.

Is it safe to create the uploads folder myself?

Yes, if you create it with the File Manager and name it exactly uploads inside wp-content. Creating the folder does not delete anything. Set its permissions to 755 afterwards, and test an upload. Fix 1 walks through the steps.

Can a plugin really cause this error?

Yes. Plugins that change the upload path, move media to external storage, or enforce security rules can all block folder creation. Deactivating plugins and testing uploads finds the culprit quickly. Fixes 6 and 7 cover plugins and security rules.

Why does the error name a folder path I do not recognise?

Because the stored upload path points to a folder from an old server, or to a location that does not exist on the current server. That stale path usually survives from a site move. Show the path to your host and ask them to correct the stored path. Fix 9 explains this.

Should I just turn off the month and year folders?

It works as a temporary workaround, but it stores every upload in one folder, which becomes hard to manage on a large site. Use it to keep publishing, and fix the underlying permissions or ownership problem with your host. Fix 8 explains the trade-off.

Conclusion

When wordpress cannot create directory uploads blocks your media, the fix is almost always the missing folder, the permissions, the path, or the ownership — not a broken WordPress. Create the folder by hand first, then check the permissions and the path, then free up disk space, and finally ask your host to check ownership and server restrictions. Finish with a simple test: upload one small image and watch it appear in the Media Library inside the correct month folder. That one successful upload is the proof that counts. Create it, check it, test it, and publish with pictures again.

Helpful Official Resources

Leave a Reply

Your email address will not be published. Required fields are marked *