| 开发者 | haritpanchal |
|---|---|
| 更新时间 | 2026年9月28日 20:01 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
<img> tags stay behind in your
post content, pointing at files that are no longer there. Visitors see a broken-image
icon, your server answers a 404, and the damage is spread across thousands of old
posts that nobody is going to open by hand.
Ghostpix Broken Image Cleaner finds those references and removes them from the content itself.
It edits your content, so it is built to be careful about it:
<img> usually strands the markup
that wrapped it. The plugin also removes the container when nothing else is left in
it — the Classic Editor's [caption] shortcode, a link that only wrapped the image,
and empty <figure>, <figcaption> and <picture> elements. No empty boxes or
orphaned captions left behind.
Built for Classic Editor content
This plugin targets content where images live as raw HTML in the post body, which is
how the Classic Editor stores them. That is exactly the older content most likely to
have accumulated broken images.
No external services
This plugin makes no outbound connections of any kind. It does not phone home, does
not send your content anywhere, and does not require an account. Everything happens
on your own server.
/wp-content/plugins/ghostpix-broken-image-cleaner, or install it
through the Plugins screen.No. It never deletes, moves or modifies any file, and it never deletes anything from your Media Library. It only edits the HTML in your post content, and only where the file is already missing.
An image is reported when its file cannot be found in your uploads folder, or when the file exists but is empty. Images hosted on other websites are not checked in this version.
The most common cause is a missing generated size — for example, photo-150x150.jpg
is gone but photo.jpg is still there. Those are reported separately and are not
included in the default selection, because the right fix is usually to regenerate
your thumbnails, not to delete the image.
Responsive images offer the browser several sizes through a srcset attribute.
If one of those sizes has gone missing the image still displays, because the
browser falls back to the one that works. Cleaning it edits only the srcset
list — the image itself is left exactly where it is.
Yes. The post's original content is stored before every edit, and the Undo button in the results table restores it. Undo data is kept for 30 days by default, and you can change that in the settings.
Detection works on any content stored as HTML, but this version is designed and tested for Classic Editor content. Block editor support is planned.
No. Scanning runs in the background in small batches and only in the admin. Nothing runs on the front end at all.
[caption] shortcodes and empty link, figure and picture wrappers.srcset, leaving the image itself in place.