You click “Update” on a pluginSoftware that adds specific features or functionality to a W... More or themeTheme A collection of files that determine a site's design, ... More. WordPress thinks for a moment. Then you see it: “Update failed: Could not create directory.”

On managed WordPress hosting, this error is especially frustrating. Managed hosts are supposed to just work. But when they don’t, you can’t always fix things the usual way, you may not have SSH access, or permission controls might be locked down.

This guide covers what causes this error on managed hosting and how to fix it, with a focus on solutions that work within managed hosting constraints.

Table of Contents

1. What Causes “Could Not Create Directory”?
2. Quick Diagnosis: Check Site Health
3. Fix #1: Check Disk Space (Most Common on Managed Hosts)
4. Fix #2: Verify and Reset Permissions
5. Fix #3: Define a Temporary Folder
6. Fix #4: Force Direct Filesystem Method
7. Fix #5: Contact Your Host (When All Else Fails)

1. What Causes “Could Not Create Directory”?

Despite the scary wording, this error has a few simple causes :

Cause	Likelihood on Managed Hosting
Out of disk space	HIGH: many plans have strict limits
Incorrect file permissions	LOW: managed hosts usually handle this
PHP temporary folder missing	MEDIUM: can happen after server changes
Filesystem ownership mismatch	LOW: but possible after migrations
PluginSoftware that adds specific features or functionality to a W... More conflict	LOW: but possible

On managed hosting (Kinsta, WP Engine, Cloudways, etc.), disk space is the most common culprit. These hosts enforce strict storage limits, and it’s easy to hit them without realizing .

2. Quick Diagnosis: Check Site Health

Before making changes, confirm the issue:

1. Go to Tools → Site Health in your WordPress adminThe admin (administrator) is the highest user role with full... More
2. Click the Info tab
3. Scroll to Filesystem Permissions

Ideally, you should see “Writable” for all key directories . If you see “Not writable” for plugins or themes, you have a permissions issue. If everything says “Writable” but updates still fail, disk space is likely your problem .

Also check:

• Tools → Site Health → Status: look for warnings about disk space
• Updates pageStatic content (e.g., "About Us," "Contact") not part of chr... More: sometimes shows storage warnings

3. Fix #1: Check Disk Space (Most Common)

Managed hosting plans have strict storage limits. When you exceed them, WordPress can’t write new files .

How to check your disk usage:

Kinsta:

1. Log into MyKinsta
2. Go to Sites → [Your Site] → Info
3. Check Disk Usage

WP Engine:

1. Go to your WP Engine dashboardThe dashboard, or admin panel, is the backend interface wher... More
2. Look for Storage usage indicator

Cloudways:

1. Go to Servers → [Your Server]
2. Check Storage Used

General method: Most hosts show disk usage in cPanel or their custom dashboardThe dashboard, or admin panel, is the backend interface wher... More.

Free up space quickly:

• Delete old backups: Many managed hosts keep automatic backups. Remove older ones.
• Clear expired transients: Use a pluginSoftware that adds specific features or functionality to a W... More like “Advanced DatabaseWhere all WordPress content, settings, and user data are sto... More Cleaner”
• Remove unused plugins and themes: Delete them, don’t just deactivate
• Optimize your databaseWhere all WordPress content, settings, and user data are sto... More: Remove postDynamic, time-based content (e.g., blog entries) displayed i... More revisions, spam comments, trashed items
• Clean up uploads: Remove unused media files via Media LibraryA repository within WordPress where all uploaded images, vid... More

Pro tip: Some hosts (like Kinsta) include backupA copy of your WordPress site's files and database, saved to... More storage in your plan limit. If you have many backups, they count against your space.

4. Fix #2: Verify and Reset Permissions

On managed hosting, you usually can’t change permissions yourself. But you can check if they’re correct, then ask support to fix them.

Correct WordPress permissions :

Type	Permission
Folders	755
Files	644
wp-config.php	640 or 644
.htaccess	644 or 640

If you have FTP access (some managed hosts allow it):

Using FileZilla or similar :

1. Connect to your site via SFTP
2. Navigate to /wp-content/
3. Right-click the plugins folder → File Permissions
4. Set to 755, check “Recurse into subdirectories” → “Apply to directories only”
5. Repeat for themes and uploads folders

For files, set to 644 (applied to files only).

If you don’t have permission controls:

Contact support. Ask them to:

• Verify ownership of all WordPress files
• Reset permissions to WordPress standards (755 for folders, 644 for files)
• Check that the web server user owns the files

This is a 5-minute fix for most hosting support teams.

5. Fix #3: Define a Temporary Folder

Sometimes PHP’s temporary folder is missing or inaccessible. You can tell WordPress exactly where to put temporary files .

Step-by-step:

1. Access your files via SFTP or hosting File Manager
2. Edit wp-config.php in your WordPress root directory
3. Add this code right before the line that says /* That's all, stop editing! Happy publishing. */ :

php

define('WP_TEMP_DIR', dirname(__FILE__) . '/wp-content/temp/');

4. Save the file
5. Create the temp folder inside /wp-content/ (if it doesn’t exist)
6. Set permissions on the temp folder to 755

Alternative: Add to wp-config.php instead of editing php.ini

This method is often easier on managed hosting because you can’t always access php.ini .

If the error persists, your host may need to configure upload_tmp_dir in the server’s PHP settings . This is another quick request for support.

6. Fix #4: Force Direct Filesystem Method

WordPress usually handles filesystem access automatically. But you can force it to use the direct method, bypassing FTP/SFTP prompts .

Add this to your wp-config.php (before the “stop editing” line):

php

define('FS_METHOD', 'direct');

What this does: Tells WordPress to write files directly using the same user as the web server .

Note: This only works if permissions are already correct. If ownership is wrong, this won’t help, but on managed hosting, ownership is usually correct.

7. Fix #5: Contact Your Host (When All Else Fails)

Managed hosting support exists for exactly these situations. Don’t suffer in silence.

What to tell them:

“I’m getting ‘Update failed: Could not create directory’ when updating plugins/themes. I’ve checked disk space and it’s not full. Can you check:

1. Filesystem ownership (should be web server user)
2. PHP temporary directory (upload_tmp_dir) exists and is writable
3. No disk quotas or inode limits are blocking writes”

Which hosts are most responsive:

Host	Response Time	Known Issues
Kinsta	Excellent	Rarely see this error
WP Engine	Excellent	Usually disk space
Cloudways	Good	Sometimes permission-related
Pressable	Good	Usually disk space
Flywheel	Good	Sometimes temp folder

Final Thoughts

The “Could not create directory” error is frustrating, but on managed hosting, it’s rarely a complex problem. Check disk space first, it’s the most common culprit and the easiest to fix. If that’s not it, work through permissions and the temporary folder fix.

And remember: You pay for managed hosting support. Use it. A quick chat or ticket can resolve in minutes what might take you hours to diagnose.