Original WebP images open directly but WordPress thumbnail previews are missing. This is a narrower problem than a complete WordPress failure: the most useful evidence is the condition under which it begins.
Recognize the exact failure
Primary symptom. Original WebP images open directly but WordPress thumbnail previews are missing. Record the precise point of failure and whether the same input, account or connected device succeeds in another supported mode. That working comparison establishes the scope of the repair.
What can produce this behavior
The first hypothesis is a mismatch in the failing path. Compare original attachment URLs with generated intermediate sizes and image processor support. The second is a lower-level state that the interface may not show: inspect attachment metadata, MIME detection and CDN image transformation behavior. A third possibility is a feature or version limitation, which should be checked against supported documentation before a reset.
For this WordPress issue, capture WordPress version, relevant hook, plugin conflict and sanitized logs and compare the same operation on a staging copy without unrelated plugins. Preserve the last known working configuration so you can tell whether a successful retry came from an actual correction or a temporary recovery.
A decision table for this case
| What you observe | What it suggests | Focused response |
|---|---|---|
| Original WebP images open directly but WordPress thumbnail previews are missing | The failure affects the specific workflow described here; the entire system is not necessarily broken. | Compare original attachment URLs with generated intermediate sizes and image processor support. |
| The basic comparison exposes a difference between a working and failing configuration. | A local setting, version, account context or device route deserves attention. | Confirm GD/Imagick WebP support and regenerate only missing derived sizes after backing up originals. |
| The same failure persists after a reversible correction. | A deeper dependency or compatibility issue may remain. | Inspect attachment metadata, MIME detection and CDN image transformation behavior. |
Before changing anything: Never delete original uploads or regenerate every media size without storage planning. Save a screenshot or anonymized log line, record the previous setting, and back up relevant user data. Do not reset every related service just because one test fails.
Choose a recovery route. The Beginner path checks compare original attachment URLs with generated intermediate sizes and image processor support. The Advanced path investigates inspect attachment metadata, MIME detection and CDN image transformation behavior. They address different evidence; use the path that matches your result.
Step-by-Step Troubleshooting
Choose the Beginner route for reversible checks or Advanced for evidence-driven diagnosis.
Identify the exact failure boundary
Original WebP images open directly but WordPress thumbnail previews are missing. Before editing settings, note the exact time, affected account or device, and whether it started after an update, move, hardware change or network change. This is the baseline for the WordPress Media Library Shows Broken Thumbnails Only for WebP Uploads guide.
Check original attachment URLs with generated intermediate sizes
Compare original attachment URLs with generated intermediate sizes and image processor support. Observe whether the symptom changes. A clean comparison tells you which part of the process is healthy and avoids unnecessary resets.
Adjust gD/Imagick WebP support and regenerate only missing
Confirm GD/Imagick WebP support and regenerate only missing derived sizes after backing up originals. Change only this variable, record its former value, and try the failing action once. If there is no improvement, restore the prior configuration before exploring the Advanced route.
Verify a regenerated thumbnail resolves at its actual URL and
A regenerated thumbnail resolves at its actual URL and appears in the Media Library. Repeat using the same account, network, file, title or hardware condition that previously failed. Do not count a different test as confirmation.
Create an evidence baseline
Collect the error text or state relevant to WordPress Media Library Shows Broken Thumbnails Only for WebP Uploads. Record WordPress version, relevant hook, plugin conflict and sanitized logs; anonymize account IDs, public IPs and secret-bearing log fragments before sharing.
Inspect attachment metadata, MIME detection and CDN image
Inspect attachment metadata, MIME detection and CDN image transformation behavior. Record the difference between successful and failed cases and keep the first meaningful error rather than the last cascade message.
Retest the alternative path
Where practical, compare the same operation on a staging copy without unrelated plugins. If the alternate case works, return to the single configuration difference instead of changing multiple services. Use the vendor-supported method for your current version.
Preserve a reproducible outcome
A regenerated thumbnail resolves at its actual URL and appears in the Media Library. Leave the previous value documented for rollback, then monitor one normal operating cycle. If symptoms recur, attach the sanitized evidence to a vendor or administrator support request.
Interpret the results
After the first corrective action, interpret the result carefully. If the original task now works, leave the other settings unchanged. If it still fails, inspect attachment metadata, MIME detection and CDN image transformation behavior. Compare the same operation on a staging copy without unrelated plugins rather than adding random fixes on top of one another.
For escalation, retain WordPress version, relevant hook, plugin conflict and sanitized logs, the original output, and a single before/after comparison. Redact passwords, tokens and personal data. A support agent can then distinguish the same operation on a staging copy without unrelated plugins from a general outage without repeating risky actions.
How to prove it is fixed
Pass condition: A regenerated thumbnail resolves at its actual URL and appears in the Media Library. The validation must exercise the same path that failed originally. A successful settings screen, single ping, application homepage or idle system is not enough if the original failure appears during a different action.
Repeat the test under the original conditions once after a safe relaunch, reconnect or new session. For intermittent failures, record the time and the difference between a clean result and a failed one instead of claiming success from a single attempt.
If the symptom returns
If the problem persists, restore any test-only settings, preserve the evidence and stop before destructive reset, firmware flash or credential recreation. Give official support the exact symptom, the first failing timestamp and what the comparison established. Never delete original uploads or regenerate every media size without storage planning.
Prevent recurrence: Document the working correction: Confirm GD/Imagick WebP support and regenerate only missing derived sizes after backing up originals. Retain the accepted result (a regenerated thumbnail resolves at its actual URL and appears in the Media Library) as a future regression test after configuration, software or hardware changes.
Solution Checklist
Questions specific to this fault
How do I know the symptom is actually resolved?
A regenerated thumbnail resolves at its actual URL and appears in the Media Library. A generic diagnostic test outside the affected workflow is not a substitute.
Should I reset or reinstall everything first?
No. Compare original attachment URLs with generated intermediate sizes and image processor support. Then choose the smallest supported intervention: confirm GD/Imagick WebP support and regenerate only missing derived sizes after backing up originals. Preserve recoverable settings and user data.
What should I include in a support request?
Provide the exact failing action, product and version, time, non-sensitive log evidence, and this deeper observation: Inspect attachment metadata, MIME detection and CDN image transformation behavior. Do not include credentials or private customer data.