Help for owners
Pictures are missing or broken on my website since it was moved
Short answer
Images break after a move when the files were not copied, when pages still point at the old address, or when paths and file names changed. Do not delete the old site yet: your images are probably still there. Find one broken image's address, and ask whether it points to the old or the new place.
Does this sound like your situation?
- Some pictures show a broken icon or an empty box on the new site.
- Product or gallery images are missing but text is fine.
- Images appear for me but not for visitors, or only on some pages.
- Images in Google results have disappeared.
- Everything looked right on the test version before launch.
Why does this happen?
The files were not all copied
Uploads folders are large and are often skipped, partly copied or cut off by a size limit during the move.
Pages still point to the old address
Content often stores the full web address of each image. If that address was the old domain or a test address, images fail once the old one is switched off.
Paths or file names changed
A new platform may organise uploads differently, change letter case or rename files with spaces and accents. A path that worked on one server can fail on another.
Images were stored somewhere else
Some images lived in a separate image service or in the old builder's own library and need to be exported from there.
Image addresses changed for search
Google advises using standard img elements with a src, referencing the same image URL consistently, and submitting an image sitemap to help it find images. A changed address can drop images from results until recrawled.
Confirmed by developers.google.com
What can I do about it today?
- Keep the old site and hosting aliveDo not cancel or delete it. It may be the only complete copy of your images.
- Pick one broken imageRight-click it, open the image in a new tab and copy the address. Note whether the address belongs to the old or new site.
- Send that address to your developerOne concrete example finds the cause faster than 'images are broken'.
- List which areas are affectedBlog, products, banners, logos: patterns point to the cause.
- Check on a phone with mobile dataThis shows whether visitors see what you see.
When should I bring someone in?
- Hundreds of images are affected.
- Images were in a builder or image service you cannot access.
- Search traffic or product pages suffer.
How do I handle it?
- Compare counts and addressesI compare the image files and the addresses used in content between old and new.
- Copy what is missingMissing files are brought across in full, with names and folders kept stable.
- Correct the stored addressesAddresses saved in content are updated in one controlled pass, after a backup.
- Redirect where addresses changedOld image addresses that remain in use are sent to the new ones.
- Check every page typeI check the main templates, not just the home page.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Are my images gone for good?
Usually not. They typically still exist on the old site or backup, provided nothing has been deleted.
Why did it look fine on the test site?
The test copy may still have been reading images from the old site. That hides a missing file until the old one is turned off.
Will it affect Google?
Images can drop out of image results while addresses are broken or changed. Keeping addresses consistent and submitting an image sitemap helps Google find them again.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.
For your developer: the technical fixes
Unexpected response from the server. The file may have been uploaded successfully. Check in the Media Library or reload the page.WordPress media upload fails with "Unexpected response from the server"404 Not Found for /storage/avatars/photo.jpgUploaded images return 404 after deploying a Laravel app