Initial assessment

Could not create directory.

“Could not create directory.” when updating WordPress, plugins or themes: causes and what to check

Updated 2026-11-01

WordPress shows this message when an install or update needs a new folder, for example in wp-content/upgrade or wp-content/plugins, and the web server user is not allowed to create it. The update stops before any files are replaced.

Which of these do you see?

wp-content or its upgrade folder is not writable by the web server user.

The copied files keep permissions from the old server that do not work on the new one.

Common causes

Folder not writable: wp-content, wp-content/upgrade or wp-content/plugins is read-only for the web server user.
Permissions from another server: A migration or restore copied permission settings that do not fit this host.
Leftover upgrade folder: An interrupted update left a folder in wp-content/upgrade that cannot be replaced.
Disk space or quota: The account has no space left for new folders.

References

  1. Changing File Permissions (Advanced Administration Handbook)
  2. Upgrading WordPress (Advanced Administration Handbook)

Rather not fix it yourself? Let WP119 handle it automatically.

Wrong file permissions are handled automatically: the system resets them to safe, working values. Fixes are made on a copy of your site in the recovery station and written back only after re-verification passes. In your site’s database, the protected tables (members, comments, orders and form submissions) are copied as structure only. In SSH and FTP mode, the system creates a pre-recovery backup on your host before writing back and restores from it if verification after write-back fails. If the recovery cannot be completed, the recovery fee is refunded in full.

  1. Initial assessment: Site URL entry
  2. Copy to the recovery station: Work on a copy
  3. Diagnosis: Item-by-item checks
  4. Recovery and verification: Home and inner pages
  5. Write-back or delivery: Only after verification passes

Use WP119 when updates keep failing with this message because of file permissions.

Check my site →
Initial assessment →