Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WordPress Theme Images Not Showing: Causes and How to Fix It

WordPress Theme Images Not Showing: Causes and How to Fix It

Short answer

WordPress theme images usually stop showing because of a wrong file path in the theme or child theme, a relative CSS background path that broke, Customizer settings lost after switching themes, demo images that never imported, mixed content, or stale cache. Check the failing image URL in your browser first.

Key takeaways

  • Find the failing image URL in the browser Network tab first.
  • Child themes need get_stylesheet_directory_uri() for their own images.
  • Relative CSS paths resolve from the stylesheet, not the page.
  • Logos and header images are saved per theme, so reset them after switching.
  • Regenerate thumbnails when a new theme uses different image sizes.

Why are my WordPress theme images not showing?

Theme images usually go missing because of a wrong file path in the theme or child theme, demo images that were never imported, settings lost after switching themes, mixed content, or cache and CDN problems.

Theme images are different from the pictures inside your posts. They include logos, header images, background images, icons and placeholder art that the theme loads from its own folder or settings.

If images inside your posts and pages are missing too, the problem is wider. Start with our general guide to fixing images not showing in WordPress.

If only theme parts are blank, work through the sections below in order.

How do you find which image is failing?

Open the page, right-click and choose Inspect, then check the Network tab or Console for images that return 404 or blocked errors and note the exact URL that failed.

The failing URL tells you most of the story. Look at three things:

  • Does the path point to the right theme folder?
  • Does it use http on an https site?
  • Does it use an old domain or a staging address?

Chrome's guide to inspecting network activity shows how to filter the list to images only.

Paste the failing URL into a new tab. A 404 means the file is not there. A 403 means the server is blocking it.

Is the theme using the wrong file path?

A very common cause is a hard-coded or relative path in a template that points to the parent theme when the image lives in the child theme, or the other way around.

WordPress has two functions for this. get_template_directory_uri() returns the parent theme's URL. get_stylesheet_directory_uri() returns the active child theme's URL.

If you copied a template into a child theme and added an image there, the path must use the stylesheet version:

<img src="<?php echo esc_url( get_stylesheet_directory_uri() . '/images/logo.png' ); ?>" alt="Site logo">

Hard-coded paths like /wp-content/themes/old-theme/images/logo.png break the moment the theme folder name changes. Use the functions instead.

Our explainer on what a child theme is covers how parent and child files relate.

Are CSS background images pointing to the right place?

Relative URLs inside CSS are resolved from the location of the stylesheet, not the page, so moving CSS into a child theme or a combined file often breaks background images.

A rule like background-image: url(images/hero.jpg) looks for the image next to the stylesheet. If you moved that rule into your child theme's style.css, the image must also be in the child theme folder.

MDN's page on the CSS url() function explains how relative paths are resolved.

Caching plugins that combine CSS files can also break relative paths. Turn off CSS combine or minify briefly and reload to test.

If your CSS edits are not loading at all, see WordPress child theme style.css not working.

Did the demo images never import?

Many themes show demo images in previews but the demo import skips them or uses grey placeholders, often because of licensing, timeouts or server limits.

Theme developers often cannot share stock photos, so the import replaces them with blank boxes. That is expected, and you need to add your own images.

If the import timed out, rerun it with a higher PHP time limit or import in smaller parts. Check the theme's documentation for its demo import plugin.

Did switching themes remove your logo or header image?

Yes, this happens often; logos, header images and background images set in the Customizer are saved per theme, so a new or reactivated theme starts without them.

These settings are stored as theme mods tied to the theme's folder name. A child theme counts as a different theme, so activating it also clears these images.

The fix is simple. Open Appearance, then Customize, or the Site Editor for block themes, and set the logo and header image again.

For block themes, the logo lives in the Site Logo block inside the header template part. See how to edit the header in a block theme.

Are thumbnails missing after a theme change?

New themes often register different image sizes, and WordPress only creates sizes when an image is uploaded, so older images may lack the size the theme asks for.

The theme then falls back to the full image, stretches a small one, or shows nothing in some layouts.

Regenerating sizes fixes this. The Regenerate Thumbnails plugin rebuilds every size for existing images.

If featured images do not show at all, the theme may not support them. Themes enable that with add_theme_support( 'post-thumbnails' ). Our guide on thumbnails not generating covers server-side causes too.

Is mixed content blocking theme images?

If your site runs on https but the theme loads images over http, browsers may block or upgrade them, which leaves blank spaces or a broken padlock.

This often comes from hard-coded http links in theme options, CSS files or old Customizer settings.

Search your theme options and custom CSS for http:// and change them to https://. A search and replace in the database fixes old settings.

Our guide to fixing mixed content warnings explains the full process.

Did a migration leave old URLs behind?

After moving domains or from staging to live, theme settings and CSS can still reference the old address, so images load from a site that no longer exists.

Serialized theme options make this tricky. A plain text search and replace can corrupt them.

Use a migration tool or WP-CLI search-replace, which handles serialized data. See fixing broken links after migration for safe steps.

Yes, wrong file permissions or hotlink protection rules can stop the server from serving theme images, usually with a 403 Forbidden error.

Theme image files should normally be 644 and folders 755. Our guide on setting correct file permissions in WordPress explains how to check them.

Hotlink protection in cPanel or a CDN can block images when the referring domain is not on the allowed list. Add your domain and any www version.

Also check file names. Linux servers treat Logo.png and logo.png as different files.

Could cache, CDN or lazy loading be the cause?

Yes, an outdated cache, a CDN that has not pulled new theme files, or a lazy load script that fails can all hide theme images.

Try these quick tests:

  • Clear your cache plugin, server cache and CDN.
  • Load the page in a private window.
  • Turn off lazy loading in your optimization plugin.
  • Deactivate optimization plugins one at a time.

Our guide on how to clear cache in WordPress covers the main plugins and hosts.

Quick reference: symptoms and fixes

Match the symptom you see to the most likely cause before changing anything.

SymptomLikely causeFix
Logo gone after theme switchTheme mods are per themeSet the logo again
Background image blankWrong relative CSS pathMove image or fix the url() path
Grey boxes on demo pagesDemo images not includedAdd your own images
404 on theme imageWrong theme folder in pathUse the right directory function
403 on imagePermissions or hotlink ruleFix permissions or allow domain
Works logged in onlyCache or CDNClear all caches

Frequently asked questions

Why did my logo disappear when I activated a child theme?

Logos and header images set in the Customizer are saved per theme. A child theme counts as a separate theme, so it starts empty. Set the logo again in the Customizer or Site Editor.

Why do theme demo images show as grey boxes?

Theme makers often cannot include licensed stock photos in demo imports, so they replace them with placeholders. Replace them with your own images, or rerun the import if it timed out.

Why are background images missing from my child theme?

Relative paths in CSS are resolved from the stylesheet's folder. If you moved CSS into the child theme, copy the image files there too or change the url() path.

Should I regenerate thumbnails after changing themes?

Yes, if the new theme uses different image sizes. WordPress only creates sizes on upload, so regenerating builds the missing sizes for images already in your library.

Why do theme images show for me but not visitors?

You are probably seeing a version that skips the cache. Clear your cache plugin, server cache and CDN, then check in a private browser window.

Sources

  1. get_template_directory_uri() WordPress Developer Resources
  2. get_stylesheet_directory_uri() WordPress Developer Resources
  3. url() CSS function MDN Web Docs
  4. Inspect network activity Chrome for Developers
  5. Regenerate Thumbnails WordPress.org Plugin Directory

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.