Merchlint
Available now
Next, in this order
  • DeutschDE
  • EspañolES
  • FrançaisFR
  • ItalianoIT
  • PortuguêsPT
  • NederlandsNL
  • SvenskaSV
  • TürkçeTR

A language shows up here once its pages are actually written. Nothing on this site is machine-translated, except a few German and Spanish pages that no native speaker has reviewed yet.

Install free Install
← All checks

The image is there and cannot be shown

The file is on disk and WordPress points to it, but it is empty or only a few pixels wide. Customers see a blank tile, just as if the photo were missing.

Group
Media
Confidence
F — fact read directly from your store
Name on the plugin screen
Image that cannot be shown
Included in
the Pro add-on, still being prepared
Updated
Code
D7

The symptom

The Media Library lists the image. The file exists at the path WordPress expects. Every check that only asks “is the file there?” passes. And the product page still shows a blank box, or a tiny dot where the photo should be.

Two things cause it, and both look the same from the admin. The file is zero bytes, usually because an upload or a migration was interrupted. Or the image is only a few pixels across: a broken import or a dead hotlink often leaves a 1 × 1 pixel image behind.

What it costs

Exactly what a missing photo costs, with one addition: it gets past the checks you would normally run.

  • The product page has a hole in it where the deciding piece of information should be. A customer who cannot see the item rarely buys it.
  • It usually arrives in batches. An interrupted bulk upload or a broken import affects dozens of products at once.
  • Nobody notices from the admin. The thumbnail in the Media Library is blank too, and it looks like a temporary glitch.

How to check it yourself

Empty image files, straight from the shell:

find wp-content/uploads -type f -empty \( -iname '*.jpg' -o -iname '*.jpeg' -o -iname '*.png' -o -iname '*.webp' \)

Main images 50 pixels or smaller on either side, with WP-CLI:

wp eval 'foreach ( wc_get_products( array( "status" => "publish", "limit" => -1, "return" => "ids" ) ) as $id ) { $f = get_attached_file( (int) get_post_thumbnail_id( $id ) ); if ( $f && is_readable( $f ) && filesize( $f ) > 0 ) { $s = @getimagesize( $f ); if ( $s && ( $s[0] <= 50 || $s[1] <= 50 ) ) { printf( "%d\t%dx%d\t%s\n", $id, $s[0], $s[1], basename( $f ) ); } } }'

It prints the product ID, the size and the file name.

A file that is damaged but not empty is a different problem, and Merchlint does not detect it. To look for those, identify from ImageMagick reports an error on each broken file:

find wp-content/uploads -name '*.jpg' -exec identify -quiet {} + 2>&1 | grep -i error

How to fix it

  1. Upload the original again for an empty file. There is nothing to repair; the data is not there.
  2. Replace a tiny image with a real photo, at least as large as your catalog thumbnails. Anything smaller gets stretched and looks worse than no photo.
  3. Fix the source of the batch. If several show up at once, check the last import or migration. One broken batch is a far more common cause than several separate accidents.

When it’s a false alarm

  • Images kept on a CDN or in cloud storage by an offload plugin, where the local file is deliberately an empty stub. Merchlint does not recognize offload plugins, so it reports every stub. Hide those findings.
  • Tiny graphics used on purpose, such as color swatches or icons. Check how such a product looks in a category listing next to the others before you hide the finding.

How Merchlint finds it

Merchlint takes the main image of every published product, and each variation’s own image, and checks the file on disk. It reports an image when the file is zero bytes, or when its width or height is 50 pixels or less. It reads the dimensions from the file itself, not from what WordPress recorded at upload.

A file this PHP build cannot read, such as SVG, or AVIF on older PHP versions, is left alone rather than guessed at. The price is stated plainly: a damaged file that is not empty passes unnoticed.

One photo can belong to many products, so the finding points to the image. It shows why the image was reported, its size and one product that uses it.

A tiny image also appears under Photo too small for Google, which is in the free version: one check says customers cannot see it, the other that Google will not take it. One new photo fixes both.

Confidence: F—fact from the file. The file is empty or tiny, or it is not.

This check is part of the Pro add-on, which is still being prepared. The free plugin does not run it.

Install free

Doesn't match what you see in your store? Email us—we read every message. contact@merchlint.com