The uploaded file could not be moved to ….
“The uploaded file could not be moved to …” in WordPress: causes and what to check
PHP first stores an upload in a temporary folder, and WordPress then moves it into wp-content/uploads. This message means that move failed: the target folder does not exist, cannot be written to, or is not the folder WordPress should be using.
Which of these do you see?
The message shows a folder from the old host, because the upload path saved in Settings › Media or in the upload_path option still points there.
The folder exists, but the web server user can no longer write to it.
WordPress cannot create the folder for the new year and month inside wp-content/uploads.
Common causes
References
- Media Library screen (WordPress.org Documentation)
- Changing File Permissions (Advanced Administration Handbook)
Rather not fix it yourself? Let WP119 handle it automatically.
A wrong upload path is handled automatically: the system resets it. The image files themselves stay on your host and are not copied, modified or moved. 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.
- Initial assessment: Site URL entry
- Copy to the recovery station: Work on a copy
- Diagnosis: Item-by-item checks
- Recovery and verification: Home and inner pages
- Write-back or delivery: Only after verification passes
Use WP119 when media uploads fail with this message after a migration or a permission change.
Check my site →