WotWP Blog

Your images after a website move: missing files, alt text and SVG logos

An open cardboard moving box packed with blank white photo prints, each with a small blank paper tag tied to its corner, labeled PHOTOS on a strip of kraft tape, on a blue background

The short answer

Images go missing after a website move for a few plain reasons: the files were never copied from the old site, a page still points at an address that no longer answers, or the new site turned a file type away, such as an SVG logo. Before the old WordPress site is switched off, check that every image file arrived, that old image addresses still answer, that the descriptions came along, and that the logo and image sizes survived.

  • Files go missing when the copy fails. The new site downloads each image from the old one, so the old site has to stay online, and every failed file lands on a list you can ask to see.
  • Addresses break when an image lives somewhere else. Images your pages borrow from other websites are not copied, and links from outside your site still point at the old image addresses.
  • Alt text comes with the images in your content. Images drawn by your theme, a page builder or a slider are rebuilt, and their descriptions have to be typed in again.
  • SVG logos and image sizes need a decision. EmDash leaves SVG files off its default upload list, and resized copies depend on a setting that fails without an error.
  • The proof is a check of every image, not a glance at the homepage. A short list of checks catches all four problems while the old site is still there to copy from.

None of this is a reason to keep a site you would rather leave. It is a list of things to check, and every one of them is easier to fix before launch than after.

Missing files: the copy failed or never ran

Most missing images were never copied. A WordPress export file holds your words and the addresses of your images, not the images themselves. EmDash, the open-source CMS from Cloudflare that calls itself "the spiritual successor to WordPress", says a WordPress export "points to media on the WordPress origin; it does not contain the attachment bytes" (EmDash docs). The importer then fetches each file from your old site, one by one.

That has one plain consequence: the old site must be up while the copy runs. The same guide says "The source site must remain reachable while EmDash downloads attachments." If the old hosting expired, or someone switched WordPress off early, every image download fails.

Failures do not disappear quietly. EmDash's docs say that "Media behind authentication, removed files, and redirects to private network addresses fail individually and remain in the media error list", and that "The final media result lists failed source URLs" (EmDash docs). Whoever runs your move can show you that list. Ask for it, and ask what happened to each line.

Why a file is missing

What you see

What fixes it

The old site was off or unreachable during the copy

Empty spaces where images were, on many pages

Bring the old site back and run the image copy again

The file was deleted from WordPress, but a page still uses it

A broken image on the old site too

Find the original on your computer or drop it from the page

The file sat behind a login

A line in the error list

Make it public for the copy, or upload it by hand

A security service on the old site blocked the downloads

Many failures at once

Let the copy through for the length of the move

The last row catches owners out. EmDash's docs warn that Cloudflare's bot protection "can answer EmDash's requests with a challenge page", and the fix they give covers the uploads folder where WordPress keeps your images. Running the copy again is safe: EmDash says "Rerunning the media step reuses already stored byte-identical files", so nothing doubles up.

The same docs add a caution worth repeating to anyone in a hurry: "Do not delete or redirect the WordPress origin after an interrupted import. First compare collection counts, inspect errors, finish media downloads, and verify rewritten links."

Broken addresses: borrowed images and old links

An image can arrive safely and still break, because an address points the wrong way. This happens in two directions.

Images your pages borrow from other websites. The importer copies attachments, the files in your WordPress media library, then "rewrites matching URLs" in your content to the new copies (EmDash docs). An image that was pasted into a page from another website was never in your library, so it is not on the copy list. The new page keeps pointing at the other site. It looks fine on launch day and breaks the day that site removes the file, and you never had a copy. If you have the right to use the image, download it and add it to the new site's media library before launch.

Old addresses other people link to. WordPress keeps every upload at an address that starts with /wp-content/uploads/. Google Images, other websites, old newsletters and PDFs you sent out all point at those addresses. A move gives each file a new home and fixes the links inside your pages, but it cannot change a link on someone else's site. Unless the old addresses still answer, those links break.

Images in a page builder's layout are a third case. Section backgrounds and slider images live in the builder's settings, not in your content, so they come across with the layout rebuild, as our guide to moving away from Elementor explains.

Alt text: what carries over and what you retype

Alt text is the short description attached to an image. Screen readers read it aloud to people who cannot see the picture, and search engines use it to understand what the image shows. It carries over when it was written on the image inside your page, and it has to be typed in again for images your theme or builder draws.

In WordPress, alt text can live in two places: on the image in the page, and on the file in the media library. The import converts your pages into EmDash's editor format, and an image written into a page arrives with the description that was on it. Images outside your content, such as the header photo, a slider, builder widgets or the logo, are rebuilt on the new site, so their alt text is part of that rebuild.

EmDash's editor makes the gaps easy to spot. When you select an image, "The Alt text button is highlighted once the image has a description", and "Alt text that is only a Media Library image's file name doesn't count" (EmDash docs). A description like "IMG_4021" is not one. Galleries keep "per-image alt text and caption", so a photo gallery's descriptions stay with each photo (EmDash docs).

A purely decorative image, such as a divider line, can have an empty description on purpose. Every image that carries meaning should have one.

SVG logos and image sizes: two things EmDash does differently

Two image details change when you leave WordPress, and neither shows up as an obvious error.

SVG logos. SVG is a file format often used for logos and icons because it stays sharp at any size. EmDash's media library leaves it out on purpose: "SVG is excluded from the default upload list because SVG files can contain active content" (EmDash docs). Active content means code inside the file, which is why an SVG needs more care than a photo. WordPress does not accept SVG uploads out of the box either, so if your logo is an SVG, a plugin or your theme put it there.

You have two choices. Export the logo as a PNG at about twice the size it appears on screen, so it stays sharp. Or have your developer allow SVG on one specific field, since the docs say "An image or file field can define its own list of accepted file types".

Check the logo and the favicon, the small icon in the browser tab, by name. EmDash keeps one of each under Settings. The importer can bring them over through the EmDash Exporter plugin from version 1.2.0, and the docs are blunt about older versions: "the import completes without them and does not report them as missing" (EmDash docs).

Image sizes. WordPress saves several copies of every upload, from a small thumbnail to a large version, and each page uses the size it needs. EmDash keeps the original and makes sized copies on Cloudflare as pages ask for them, through a connection to Cloudflare's image service that the docs call the IMAGES binding. When that connection is missing, nothing looks broken. On the default setup, the docs say "pages still render and nothing is logged, but every image is the full-size original rather than a variant scaled to the space it occupies" (EmDash docs). A phone then downloads a full-size photo for a small card, and the page gets slower for every visitor.

The old thumbnail addresses are a related detail. A file named photo-150x150.jpg was a cropped copy that WordPress made. If the new site keeps that address answering with the original photo, a hard-cropped square shows the whole uncropped picture instead.

How to check your images before the old site goes off

The proof is a check of every image on every page, done while WordPress is still running. This is the order we would follow:

  1. Ask for the image error list. Every failed download is on it. It should be empty, or each line should have a reason and a fix.
  2. Compare the counts. The number of files in the old media library and in the new one should match, allowing for duplicates. EmDash stores identical files once, so two copies of the same photo become one.
  3. Open the pages that matter side by side. Look at the old and new versions on a phone and on a desktop. Empty boxes, broken-image icons and missing backgrounds show up fast.
  4. Look for borrowed images. Open an image in a new browser tab and read its address. Any image whose address points at another website was not copied. Download it, if you may, and add it to the new library.
  5. Try a few old image addresses. Take image links from Google Images or from an old newsletter and open them on the new site. Each should show the picture, not an error page.
  6. Read the alt text. Select images in the editor and check that the Alt text button is highlighted on every image that carries meaning.
  7. Check the logo and favicon by name. If either was an SVG, decide on a PNG or an allowed field before launch.
  8. Check image sizes. Open a small image in a new browser tab. If a card-sized picture opens as a huge photo, resized copies are not being made.

Back up the uploads folder before any of this. A WordPress export is not a backup of your images, and our website hosting checklist covers backups and restore tests. The website migration SEO checklist covers the rest of the move: the address list, redirects, launch and the 90 days after.

Who should stay on WordPress

If your site's images are run by a plugin that is the heart of the site, stay on WordPress for now. A photography portfolio built on a gallery plugin with proofing for customers, or a stock-photo shop, depends on that plugin's features, and moving it means rebuilding a product, not copying pictures.

Stay put as well if:

  • It is a store, a member area or an online course. Those are rebuilds of a different kind.
  • Your images sit behind logins that visitors use, such as private galleries for paying members.
  • The site works, costs you little and nobody touches it. A careful move keeps your images, but a site that already just works may not need one.

If you are unsure which side you are on, the fit guide explains what moves well and what does not.

How we handle images on a move

On a move from WordPress to EmDash, your images keep their old addresses, so links from Google Images, other websites and old newsletters keep working. Before launch, we check your images against your live site, and anything that does not show the right image fails the check.

We also compare the titles, copy, images and descriptions on every page against your live site, and we tell you before launch about any detail that changes. You see everything on a private preview while your WordPress site stays live and untouched, approve it, and keep a written way back.

It is how we bring a WordPress site into the AI era on EmDash and Astro without losing a picture. The conversion starts at $790 for up to 25 pages, as our pricing shows.

To see where your own site stands, check your site for free.

Frequently asked questions

Why are my images missing after a website migration?

Usually because the files were never copied. A WordPress export holds the addresses of your images, not the images, so the new site downloads each one from the old site. If the old site was offline, the file was deleted, or a security service blocked the downloads, the image is missing. Ask for the list of failed downloads.

Do I need to keep my old WordPress site running during the move?

Yes. EmDash downloads every image from the old site while it imports, so the old site has to stay reachable until every file has arrived and every page has been checked. Switching it off early is the most common reason images go missing. Keep it running until the new site has passed its checks.

Will my alt text transfer when I move off WordPress?

Alt text written on images inside your pages comes across with those images. Images drawn by your theme, a page builder or a slider are rebuilt, so their descriptions need to be typed in again. In EmDash's editor, the Alt text button is highlighted once an image has a real description, which makes gaps easy to find.

Why won't EmDash accept my SVG logo?

EmDash leaves SVG off its default upload list because SVG files can contain code. You can export the logo as a PNG at twice its display size, or a developer can allow SVG on one specific image field. WordPress does not accept SVG uploads out of the box either, so a plugin or theme probably added yours.

Will old image links from Google still work after the move?

Only if the old addresses keep answering. WordPress keeps images at addresses starting with wp-content/uploads, and Google Images and other sites link to those. A move fixes links inside your pages, not links elsewhere. Ask whoever runs the move whether old image addresses will still show the picture.

Why did my website get slower after the move even though the images look fine?

The new site may be sending full-size originals instead of resized copies. On EmDash, resizing relies on a connection to Cloudflare's image service. When it is missing, pages still look right, but every image is the full-size file. Open a small image in a new tab: if it opens huge, resizing is off.