Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting · Troubleshooting

How to Fix the WordPress "Could Not Create Directory" Error

Short answer

WordPress shows “Installation failed: could not create directory” when it cannot create a folder for a plugin or theme under wp-content, usually because folder permissions or file ownership block the write. Fix it by setting folders to 755 and files to 644, then retry the install. If the error stays, check disk space and ask your host to correct file ownership.

Key takeaways

  • “Installation failed: could not create directory” means WordPress cannot write a new folder under wp-content.
  • Folders should be 755 and files 644, with wp-config.php tighter at 440 or 400.
  • Ownership matters as much as numbers: PHP must run as the account that owns the files.
  • Tools → Site Health → Info → Filesystem Permissions shows which folders are writable.
  • A full disk shows the same message, so check storage before changing permissions.
  • Never use 777: the WordPress handbook says no folder should ever get it.

What does “Installation failed: could not create directory” mean?

The error means WordPress tried to create a folder for a plugin or theme, and the server refused to write it.

When you install a plugin or theme from the dashboard, WordPress downloads the files and creates a new folder under wp-content. If the server blocks that write, the install stops at once.

The message is about the server, not the plugin. Kinsta's guide to this error explains that the plugin or theme lacks permission to write in the website's root folder, so WordPress cannot save its files.

When does this error appear?

It appears when you install a plugin or theme, when you update one, or when you upload files to wp-content.

During an update the wording often changes to “Update failed: could not create directory”. Kinsta notes the cause and the fix are the same for both wordings, because an update also has to write new folders on the server.

The same failure can also show up when you add media, since uploads also need a writable folder. A related guide to fixing the destination folder already exists error covers the opposite case, where the folder is already there.

What causes this error?

The most common cause is file permissions that stop the server from writing to wp-content.

  • Folder permissions on wp-content, wp-content/plugins, or wp-content/themes are too strict for the server to write.
  • File ownership is wrong: the folders belong to a different user than the one PHP runs as.
  • The disk is full, so there is no room for the new folder.
  • A wp-config.php setting forces the wrong filesystem method or blocks installs.
  • The host blocks writes to the site's folders.

Ownership deserves attention first. The WordPress handbook on changing file permissions says files should be owned by your user account, never by the web server account. When PHP runs as another user, such as www, apache, or nobody, a folder at 755 still gives PHP read access only.

A full disk can produce the exact same message. Kinsta points out that old backup files can fill a small plan, and the fix is to delete what you no longer need or move to a larger plan.

Wrong permissions can cause other errors too. The same settings that block an install can lock you out with a 403, which the guide to fixing the 403 error covers step by step.

CauseHow to spot itFirst fix
Permissions too strictSite Health shows “Not writable”Reset folders to 755
Wrong ownershipPermissions look right but installs still failAsk the host to fix the owner
Disk fullHost panel shows no free spaceDelete old backups and files
Wrong filesystem methodWordPress keeps asking for FTP detailsSet FS_METHOD to “direct”
Installs blocked in wp-config.phpNo install or update worksRemove DISALLOW_FILE_MODS

How do you check whether permissions are the problem?

Open Tools → Site Health → Info and scroll to Filesystem Permissions to see which folders are writable.

WordPress 5.2 introduced the Site Health tool, and its Filesystem Permissions section lists the main folders with “Writable” or “Not writable” next to each one. Kinsta's walkthrough of this error uses the same check as the first step before changing anything.

If wp-content or the plugins folder shows “Not writable”, permissions or ownership are the problem. If every folder shows “Writable”, look at disk space or your wp-config.php settings instead.

How do you fix folder permissions with FTP?

Connect with an FTP client such as FileZilla and set your WordPress folders to 755 and files to 644.

Back up your site before you change permissions. The WordPress handbook warns that setting incorrect permissions can take your site offline, so keep a copy you can restore.

  1. Open FileZilla and connect with the FTP details from your hosting account.
  2. Open public_html, the folder that holds your WordPress files.
  3. Select wp-admin, wp-content, and wp-includes, right-click, and choose File Permissions.
  4. Set the numeric value to 755, tick Recurse into subdirectories, and choose Apply to directories only.
  5. Click OK, then select the files in public_html and set them to 644 with Apply to files only.
  6. Go back to the dashboard and try the install again.

On servers where PHP runs as the file owner, the WordPress handbook lists 755 or 750 for folders and 644 or 640 for files, with wp-config.php at 440 or 400. These values are the safe baseline as of November 2026.

PathFoldersFiles
WordPress root, wp-admin, wp-content, wp-includes755644
wp-config.phpNot applicable440 or 400
wp-content/uploads755644

How do you fix permissions from your hosting panel?

Many hosts offer a one-click reset that restores the standard 755 and 644 values without FTP.

On SiteGround, go to Site Tools → WordPress → Install & Manage, open the Actions menu for the site, and choose Reset Permissions, then Confirm. SiteGround's knowledge base gives this as the fix when wrong permissions stop WordPress from creating folders.

On Hostinger, go to Websites → Advanced → Fix File Ownership, tick the confirmation box, and click Execute. Hostinger's tutorial says the tool resets files to 644 and folders to 755.

If your host has no reset tool, use its File Manager to set the same values by hand. Open the folder, choose Permissions or Change Permissions, and apply 755 to folders and 644 to files.

What if permissions are correct but the error stays?

Check file ownership next, because correct numbers do not help when the wrong user owns the folders.

The WordPress handbook explains that files should be owned by your user account, not by the web server account. When PHP runs as a different user, it cannot write even to a folder set to 755, so ask your host to correct the owner of wp-content.

A forced filesystem method can also block installs. The WordPress wp-config handbook says FS_METHOD accepts only “direct”, “ssh2”, “ftpext”, or “ftpsockets”, and you should change it only when you have update problems. Setting it to “direct” tells WordPress to write files itself instead of asking for FTP details.

define( 'FS_METHOD', 'direct' );

Add that line above the “That's all, stop editing!” line in wp-config.php.

Also check for a line that blocks installs outright. The wp-config handbook says define( 'DISALLOW_FILE_MODS', true ); stops plugin and theme installs and updates from the admin area. If that line is present, remove it or ask your host why it was added.

How do you fix it when disk space is full?

Free space first, because no permission change helps when the disk is full.

Kinsta notes that a server out of disk space shows this same message, often because old backup files were never deleted or the plan is too small for the site. Delete old backups and unused files, then check your host's disk usage screen before you retry the install.

If the disk fills up again soon after, the plan may be too small. Your host can confirm the usage and tell you the next plan size.

How do you know the fix worked?

Retry the same install and watch for the success message instead of the error.

Go back to Tools → Site Health → Info → Filesystem Permissions and confirm the folders now show “Writable”. Then install the plugin or theme again; a clean install with no error means the write problem is gone.

Also open the plugin or theme page in the dashboard and confirm the new item appears and activates. If it activates, the folders were created and WordPress can write to them.

When should you contact your host?

Contact your host when you cannot change ownership, when the disk is full on a managed plan, or when the error returns after a correct reset.

On shared and managed hosting, only the host can change file ownership or raise a disk quota. Tell support the exact error, the plugin or theme name, and what Site Health shows. A guide to WordPress hosting requirements explains the baseline a host should meet.

What mistakes should you avoid?

The biggest mistake is setting a folder to 777 to force the install through.

  • Do not use 777. The WordPress handbook is blunt: no folder should ever get 777, even uploads, because any account on the server could then write to it.
  • Do not set every file to 755 with one recursive command. Files and folders need different values, so set folders first and files second.
  • Do not edit wp-config.php without a backup. A typo in that file can take the whole site offline.
  • Do not blame the plugin or theme first. The error is about the server, not the code you tried to install.
  • Do not keep retrying the install while the disk is full. Each retry fails the same way until space is free.

Wrong permissions can also break other parts of the site. The same settings that block an install are a common cause of a 500 error, covered in the guide to fixing the 500 error.

Frequently asked questions

Can I fix this error without FTP access?

Yes. Use your host's reset tool or File Manager instead. SiteGround offers Reset Permissions under Site Tools, and Hostinger offers Fix File Ownership under Websites and Advanced. If your host has neither tool, open a support ticket and ask them to reset permissions and check ownership for wp-content. You should not need FTP at all.

Is it safe to set wp-content to 777?

No. A 777 folder lets any user or process on the server read, write, and run files inside it, which is a security risk on shared hosting. The WordPress handbook says no folder should ever get 777, even uploads. Use 755 for folders and 644 for files, and fix ownership instead if the error stays.

Why does this error happen on a brand-new site?

New sites hit this error often because the files were created by a different account than the one PHP runs as. A fresh install can also inherit strict permissions from the server setup. Check Site Health first: if folders show Not writable, reset permissions to 755 for folders and 644 for files, then retry the install.

Does this error mean the plugin or theme is broken?

No. The error says the server refused to create a folder, not that the plugin code is faulty. The same plugin usually installs fine once WordPress can write to wp-content. If the install still fails after permissions, ownership, and disk space are all correct, then try a fresh download of the plugin file.

What is the difference between this error and "destination folder already exists"?

This error means WordPress could not create the folder at all, usually because of permissions, ownership, or a full disk. The destination folder error means the folder is already there from an earlier install, so WordPress cannot move the new files in. The two errors need different fixes, so check the exact wording first.

Will changing permissions break my site?

It can, if you set the wrong values. Folders at 755 and files at 644 are the standard WordPress values, and a backup lets you undo a mistake. Avoid 777, avoid setting every file to 755, and change one folder at a time so you can see what each change does.

Sources

  1. Changing File Permissions WordPress Developer Resources
  2. Filesystem WordPress Developer Resources
  3. Editing wp-config.php WordPress Developer Resources
  4. How to Fix "Installation Failed: Could Not Create Directory" Kinsta
  5. How to Fix WordPress Image Upload Problems SiteGround
  6. What Is 413 Request Entity Too Large and How to Fix It? Hostinger

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test