WordPress “Uploaded File Could Not Be Moved” Fix

Updated 10 November 2026 · Standard formula, shown below

The WordPress error “The uploaded file could not be moved” usually means the server cannot move an uploaded image or other file into the Media Library’s uploads folder. Check the folder path and permissions first, then investigate disk space, security rules, or hosting configuration if the problem continues. Before changing files, make a backup and keep your hosting account’s file manager or SFTP access available.

What You’ll Need

Administrator access to your WordPress dashboard.
Access to your hosting control panel’s file manager or an SFTP client.
A recent site backup, especially before editing configuration files or changing permissions.
Your hosting provider’s support contact, if server settings need to be changed.

Step-by-Step

Confirm that the error is repeatable. Try uploading a small image with a simple filename, such as test-image.jpg. Note whether the issue affects every file or just one, and whether it happens in one browser or across browsers. Do not repeatedly upload large files while troubleshooting; failed attempts can use server space.
Check the uploads folder in WordPress. In the dashboard, open Settings > Media and look for the option that specifies where uploaded files are stored. On many sites, the field is blank and WordPress uses its standard uploads directory. If the field contains an old or incorrect path, record its current value before correcting it. Avoid guessing a server path; ask your host if you do not know the correct location.
Verify that the destination folder exists. Open your host’s file manager or connect with SFTP, then navigate to the WordPress installation’s wp-content/uploads folder. Check that the folder exists and that it contains the expected year or month subfolders. If the folder is missing, create it only in the correct WordPress installation and ensure it is owned and accessible by the account running the site. If you are unsure about ownership, ask your host to correct it.
Check folder permissions without making them too broad. In the file manager, inspect the permissions for wp-content, uploads, and any relevant subfolders. WordPress needs permission to write into the destination. A common starting point on shared hosting is 755 for directories and 644 for files, but server ownership and configuration can change what is appropriate. Apply a change only to the affected directories, not the whole site. Do not set permissions to 777; that grants excessive access and does not reliably solve ownership problems. If the folder is not writable by the correct account, have the host fix ownership or permissions.
Check available disk space and account limits. Your hosting account may be out of storage or have reached an inode limit, which restricts the number of files and folders. Look for disk-usage information in the hosting panel. If space is exhausted, remove only files you have identified as unnecessary, or ask the host about the limit. Do not delete unknown WordPress files or backups just to make room.
Review security and optimization tools. A security plugin, firewall, malware scanner, or host-level rule can block file moves. Check the relevant plugin’s logs and temporarily pause one suspected plugin at a time, then retry a small upload. Restore each plugin immediately after the test. If the error stops, review that plugin’s settings or ask its provider or your host for help; do not leave security protections disabled.
Check the PHP temporary upload directory with your host. WordPress first receives an upload in a temporary server location before moving it to the Media Library. If that temporary location is missing, full, or unwritable, the final move may fail even when the uploads folder looks correct. Ask your host to check the PHP upload temporary directory and server error logs. Avoid editing PHP configuration values unless your host confirms what needs to change.
Retry and confirm the file is usable. After each change, upload one small test file through Media > Add New Media File. If it succeeds, confirm that the file appears in the Media Library and opens correctly. Then retry the original upload. If the fix involved permissions or a plugin, keep the change narrowly scoped and restore any temporary test settings.

Common Mistakes

Setting permissions to 777: This is an unsafe shortcut and may still fail if the folder owner is wrong. Correct ownership and suitable permissions are safer.
Changing permissions recursively across the whole site: Directories and files need different access settings. A broad change can expose or break parts of WordPress.
Editing the uploads path without recording the old value: A wrong absolute path can create a new failure. Confirm the correct location with your host.
Assuming the image is too large: Size limits can stop an upload, but this specific message can also result from a destination or temporary-folder problem. Check the exact error and server logs.
Leaving a security plugin disabled: Use a brief, controlled test and restore protection as soon as it is complete.

Tips

Test with a small file and a plain filename to separate file-specific problems from site-wide upload failures.
Change one thing at a time and retry the same test upload. This makes the cause easier to identify.
Keep a note of the original path, permissions, and plugin settings before changing them.
Ask your host to check ownership, PHP temporary storage, disk space, and server logs together; these are server-level details that may not be visible in WordPress.

Troubleshooting

The uploads folder exists and permissions look correct, but uploads still fail: The account that runs PHP may not own the folder, or a host security rule may block the move. Ask your hosting provider to inspect directory ownership and the server error log at the time of a failed upload.

Only one file fails: Try a supported image format and a shorter filename without unusual symbols. The file may be damaged, too large for the configured limits, or affected by a filename or format restriction. Check the upload message in WordPress and ask your host about applicable PHP limits if needed.

Uploads fail after a migration or restore: The saved uploads path may point to the previous server, or files may have incorrect ownership. Confirm the current WordPress installation path and ask the host to repair ownership. Do not copy a path from another site unless it matches this installation.

The problem returns after a permission change: A hosting process may reset permissions, or the actual cause may be ownership rather than the permission number. Avoid repeating increasingly broad changes; ask the host to set the correct owner and writable access for the uploads directory.

You cannot access the file system or logs: Send your host the exact error, the time of a failed attempt, the affected file type, and whether all uploads fail. Request a check of the uploads destination, PHP temporary directory, account storage limits, ownership, and security logs.

Frequently Asked Questions

What does “The uploaded file could not be moved” mean?
WordPress received a file but could not move it from temporary storage into the configured uploads folder. The cause is often a path, access, storage, or server configuration issue.

Will changing permissions to 777 fix the error?
It is not recommended. It gives broad access and may not correct wrong ownership or a broken path. Ask your host to set the appropriate ownership and directory permissions.

Where is the WordPress uploads folder?
It is usually wp-content/uploads within the WordPress installation, often organized into year and month folders. A site can use a different configured location, so verify the actual path.

Could the file size cause this message?
Yes, upload limits or storage restrictions can interfere, but a failed move often points to the temporary folder or destination access. Check the specific upload limit and server logs rather than assuming size is the only cause.

Should I contact my hosting provider?
Yes, if the path and available space look correct, or if you cannot inspect ownership, PHP temporary storage, or server logs. Those settings are commonly controlled by the host.

Do I need to change the uploads path in Settings > Media?
Usually not. Change it only if it is demonstrably incorrect and you know the correct destination. Otherwise, ask your host to verify the path before editing it.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.