The first stable release. Checking media on other websites is now off until you turn it on in Settings, and the menu item moves to the bottom of the admin menu. Your scans, issues and repair history are kept.<\/p>","1.0.0-rc.12":"
Replacement suggestions: the issue page now offers files from your Media Library that are plainly the right replacement, and says why. Nothing is repaired until you choose one.<\/p>","1.0.0-rc.11":"
Internal only: no behaviour changes. Safe to skip unless you also run Media File Fixer Pro.<\/p>","1.0.0-rc.10":"
Groundwork for the Pro add-on. No change to how the free plugin behaves; take it whenever convenient.<\/p>","1.0.0-rc.9":"
Elementor Image widgets are now found and repaired where Elementor actually keeps them. Worth taking if you use Elementor, or used to: broken images in Image widgets are fixable from the plugin, are no longer double-counted, and are correctly dropped if Elementor is removed.<\/p>","1.0.0-rc.8":"
Elementor Image widgets are now found and repaired where Elementor actually keeps them, instead of being refused. Worth taking if you use Elementor: broken images in Image widgets are now fixable from the plugin, and are no longer double-counted.<\/p>","1.0.0-rc.7":"
Important if you use a page builder: repairs inside Elementor pages could report success while the image stayed blank. Those repairs are now refused with an explanation instead, and repair counts match what you see on the issue.<\/p>","1.0.0-rc.6":"
Important if you have replaced a deleted image: repairs could report success while the page still showed a broken image, because only one of the addresses in the image was replaced. Repairs now fix the whole image and are only closed once the page really no longer refers to the old file.<\/p>","1.0.0-rc.5":"
Recommended for every site on MySQL or MariaDB: fixes repeat actions on an issue being wrongly refused, and stops database errors from writing table names or saved values into your debug log.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3796370,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3796370,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3796370,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3796370,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3796370,"resolution":"1","location":"assets","locale":"","width":2880,"height":1994},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3796370,"resolution":"2","location":"assets","locale":"","width":2880,"height":2756},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3796370,"resolution":"3","location":"assets","locale":"","width":2880,"height":3094},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3796370,"resolution":"4","location":"assets","locale":"","width":2880,"height":4154},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3796370,"resolution":"5","location":"assets","locale":"","width":2880,"height":3438},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3796370,"resolution":"6","location":"assets","locale":"","width":2880,"height":1800},"screenshot-7.png":{"filename":"screenshot-7.png","revision":3796370,"resolution":"7","location":"assets","locale":"","width":2880,"height":1800}},"screenshots":{"1":"A scan in progress. Scans are batched and resumable, show real progress, and only ever read your site.","2":"The Dashboard: a media health score calculated from the files that were checked, with the counts behind it, the most urgent issues and your recent repairs.","3":"Every issue found, with the file, what is wrong, how many places use it and when it was detected \u2014 filterable by type, severity and status.","4":"An issue in detail: the root cause in plain language, and every page, post and featured image that uses the file.","5":"A repair preview. Nothing has been changed yet \u2014 this is what would change, and what would be left alone.","6":"Repair History: everything the plugin has changed, what the check afterwards found, who did it, and a way to undo it.","7":"Settings. External media checks stay off until you turn them on, and scheduled scans and email notifications are clearly marked as features the free plugin does not include."}},"plugin_section":[],"plugin_tags":[128337,84,233,292034,2956],"plugin_category":[50],"plugin_contributors":[292035],"plugin_business_model":[],"class_list":["post-400859","plugin","type-plugin","status-publish","hentry","plugin_tags-broken-images","plugin_tags-media","plugin_tags-media-library","plugin_tags-missing-files","plugin_tags-thumbnails","plugin_category-media","plugin_contributors-potensdigital","plugin_committers-potensdigital"],"banners":{"banner":"https:\/\/ps.w.org\/media-file-fixer\/assets\/banner-772x250.png?rev=3796370","banner_2x":"https:\/\/ps.w.org\/media-file-fixer\/assets\/banner-1544x500.png?rev=3796370","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/media-file-fixer\/assets\/icon-128x128.png?rev=3796370","icon_2x":"https:\/\/ps.w.org\/media-file-fixer\/assets\/icon-256x256.png?rev=3796370","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/media-file-fixer\/assets\/screenshot-1.png?rev=3796370","caption":"A scan in progress. Scans are batched and resumable, show real progress, and only ever read your site."},{"src":"https:\/\/ps.w.org\/media-file-fixer\/assets\/screenshot-2.png?rev=3796370","caption":"The Dashboard: a media health score calculated from the files that were checked, with the counts behind it, the most urgent issues and your recent repairs."},{"src":"https:\/\/ps.w.org\/media-file-fixer\/assets\/screenshot-3.png?rev=3796370","caption":"Every issue found, with the file, what is wrong, how many places use it and when it was detected \u2014 filterable by type, severity and status."},{"src":"https:\/\/ps.w.org\/media-file-fixer\/assets\/screenshot-4.png?rev=3796370","caption":"An issue in detail: the root cause in plain language, and every page, post and featured image that uses the file."},{"src":"https:\/\/ps.w.org\/media-file-fixer\/assets\/screenshot-5.png?rev=3796370","caption":"A repair preview. Nothing has been changed yet \u2014 this is what would change, and what would be left alone."},{"src":"https:\/\/ps.w.org\/media-file-fixer\/assets\/screenshot-6.png?rev=3796370","caption":"Repair History: everything the plugin has changed, what the check afterwards found, who did it, and a way to undo it."},{"src":"https:\/\/ps.w.org\/media-file-fixer\/assets\/screenshot-7.png?rev=3796370","caption":"Settings. External media checks stay off until you turn them on, and scheduled scans and email notifications are clearly marked as features the free plugin does not include."}],"raw_content":"\n
Broken media is hard to find and risky to fix. An image disappears from a page, a thumbnail stops loading, a PDF link goes dead \u2014 and the usual advice is to run a search-and-replace across your database and hope for the best.<\/p>\n\n
Media File Fixer takes the opposite approach. It scans what your site actually stores, tells you which media files are missing or at risk, explains why<\/strong> each one is broken in plain language, shows you every place<\/strong> it is used, and then repairs it in a way you can preview beforehand and undo afterwards.<\/p>\n\n Published, private, scheduled, draft and pending content is scanned. Trashed content, auto-drafts and revisions are not.<\/p>\n\n The last three need Check external media URLs<\/strong>, which is off by default. While it is off, external files are reported as Not Checked and are never counted as healthy or broken.<\/p>\n\n Every repair runs the same way: analyse, preview, snapshot, repair, verify, log.<\/p>\n\n So you know what you are getting:<\/p>\n\n Scanning covers posts, pages, featured images, the Media Library and Elementor Image widgets. Custom post types can be added with the It is not an image optimiser, a CDN, a backup plugin, a security scanner, an SEO suite, a compression or WebP plugin, or a media cleaner. It never deletes your media, and a file that nothing uses is reported as \"0 locations\" \u2014 information, never a problem.<\/p>\n\n Media File Fixer does not send your website URL, media URLs, content, scan results, or any analytics to Media File Fixer or Potens Digital. There is no telemetry, no tracking, no account, and no external service to sign up for.<\/p>\n\n Suggested privacy policy text is available under Settings \u2192 Privacy.<\/p>\n\n Out of the box, Media File Fixer contacts no other website. External media checks are off by default<\/strong>: nothing is sent until an administrator turns on Check external media URLs<\/strong> under Media File Fixer \u2192 Settings.<\/p>\n\n While it is on, scans and re-checks send a HEAD request (or a GET request limited to 1 KB) directly to each external media URL found in your content, to find out whether that file still loads. These requests go to whichever third-party servers host those files, never to Media File Fixer or Potens Digital, and those servers' own terms and privacy policies apply. Each server receives your server's IP address, the address of the file, and a user agent naming the plugin and its version. The requests carry no cookies, no login details and no information about your visitors. Private and internal network addresses are never contacted.<\/p>\n\n While it is off, no lookup or request is made for external files. They are reported as Not Checked and left out of the health score. Turning the setting off also stops a scan that is already running from contacting anyone, from its next batch on.<\/p>\n\n The plugin creates its own database tables. It loads nothing on the front end of your site.<\/p>\n\n Every scan is started by an administrator from this screen; the free plugin never starts one by itself. Large sites are scanned in small batches, so a scan can be paused, resumed and continued later. Once you have started a scan, you can leave the scan page open to keep it moving quickly, or close it and let WordPress's scheduled tasks (WP-Cron) continue that scan's remaining batches in the background.<\/p>\n\n Media hosted on other websites is not contacted unless you turn on Check external media URLs<\/strong> in Settings. See \"External requests\" in the description for exactly what that sends.<\/p>\n\n Uninstalling the plugin leaves your data in place unless you switch on Delete Data on Uninstall<\/strong> in Settings \u2192 Advanced. Your media files are never deleted either way.<\/p>\n\n\n No. Media File Fixer never deletes a media file. The only repair that writes a new file is \"Regenerate missing image sizes\", which creates sizes that are missing and never overwrites an existing file. Your original images are only ever read.<\/p><\/dd>\n Only when you ask it to, and only the exact occurrence you chose. Every content repair is previewed first, the original value is stored before the change, and the content is read back afterwards: if anything beyond that one reference moved, the previous content is written back and the repair is recorded as failed.<\/p><\/dd>\n Yes, for repairs that replaced something \u2014 a file or an address. Open Repair History<\/strong>, choose the repair, and you will see what it changed before you confirm. If the content has been edited since the repair, undoing is refused rather than overwriting that newer work. Regenerating image sizes cannot be undone, because it only ever added files that were missing.<\/p><\/dd>\n From your own Media Library, by rules you can read: the same file name in another folder, the original of a missing generated size, a re-upload with a copy number added, the same image dimensions, a matching title. Each suggestion says which of those it matched and is marked a Strong match<\/strong> or a Possible match<\/strong> \u2014 never a percentage. Only files of the same kind that really exist on your server are offered, and nothing is suggested when nothing is a confident match. Nothing is sent anywhere, no AI is involved, and a suggestion is never used until you choose it and confirm the preview.<\/p><\/dd>\n No. See the Privacy section above. The only outbound requests the plugin can make are the optional checks of external media, which are off until an administrator turns them on and go to the host serving that file, not to us.<\/p><\/dd>\n Not unless you ask it to. Check external media URLs<\/strong> is off by default, and while it is off, scans, background batches and re-checks send nothing to anyone. When you turn it on, it sends small requests to the servers hosting the external media your content uses. \"External requests\" in the description says exactly what they receive.<\/p><\/dd>\n A scan only ever starts when an administrator starts one from the Media File Fixer screen in wp-admin. The free plugin never starts a scan by itself; recurring scheduled scans are part of Media File Fixer Pro. Once you have started a scan it runs in small batches: the scan page drives them while it is open, and if you close the page, WordPress's scheduled tasks (WP-Cron) can continue that scan's remaining batches in the background until it finishes. You do not have to keep the page open, but it is quicker if you do.<\/p><\/dd>\n Never. Content is re-parsed with the same parser the scan uses, and only the single occurrence you selected is rewritten.<\/p><\/dd>\n The check was inconclusive. A server may block automated requests, rate-limit them, time out, or return an error. That is not proof the file is broken, and it is certainly not proof it is fine, so the file is reported honestly as unverified and is never counted as healthy or broken.<\/p><\/dd>\n Because someone else controls it. It works today, but it can disappear without warning. If you serve your own media through a CDN, you can tell the plugin that host belongs to you with the No, and the plugin will never tell you it is. Unused files are still checked so you know whether they are intact, but \"used in 0 locations\" is information, not an issue. Media File Fixer is not a media cleaner.<\/p><\/dd>\n Partly, and only where it has been verified. Elementor Image widgets<\/strong> are fully supported: they are read from Elementor's own data, repaired there, and checked afterwards \u2014 so an image is found and fixed even on a page whose stored content is empty. Everything else in Elementor is not: background images, galleries, carousels, sliders and images set in custom CSS are reported if they happen to appear in the copy of the page Elementor keeps, but they are not repaired.<\/p>\n\n Other builders, including Divi, are not supported in version 1.0. Plain HTML stored in your content is always found normally. Shortcode attributes, widgets and menus are not parsed.<\/p>\n\n Where a page is built by a builder this plugin cannot repair, it says so and refuses rather than changing a copy of the page and reporting a success you could not see.<\/p><\/dd>\n Not by default. Posts, pages, featured images, Elementor Image widgets and the Media Library are scanned. Developers can add more post types with the No. Nothing is loaded on the front end \u2014 no scripts and no styles, and none of the scanner, admin or repair code is built when a visitor's page is served. The admin screens only run in wp-admin. A scan runs in small batches with time and memory budgets, so it stays well within what shared hosting allows, and any batches it leaves for the background run through WordPress's scheduled tasks in their own requests, not inside a visitor's page.<\/p><\/dd>\n Yes. Each site in a network gets its own tables and its own scans and issues. There is no network-wide dashboard.<\/p><\/dd>\n It depends on how much content and media you have. Scans are batched and resumable, and the Scan screen shows real progress throughout. A site with a few thousand posts is scanned in minutes with the page open.<\/p><\/dd>\n Yes. The admin screens are checked against WCAG 2.1 A and AA with automated tooling, every string is translatable, and a translation template ships with the plugin.<\/p><\/dd>\n\n<\/dl>\n\n\nHow it works<\/h4>\n\n
\n
What it scans<\/h4>\n\n
\n
srcset<\/code>, links to documents, <source><\/code>, <video><\/code>, <audio><\/code>, inline url()<\/code> in style attributes)<\/li>\nProblems it identifies<\/h4>\n\n
\n
Repairs included<\/h4>\n\n
\n
Built to be safe<\/h4>\n\n
\n
Not in the free plugin<\/h4>\n\n
\n
media_file_fixer_scan_post_types<\/code> filter but are not scanned by default. Other page builders' storage, shortcode attributes, widgets, menus and theme or plugin CSS files are not parsed.<\/p>\n\nWhat Media File Fixer is not<\/h4>\n\n
Privacy<\/h4>\n\n
External requests<\/h4>\n\n
Requirements<\/h4>\n\n
\n
Credits<\/h3>\n\n
\n
\n
media-file-fixer<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n\n
Will it delete or change my media files?<\/h3><\/dt>\n
Will it change my posts and pages?<\/h3><\/dt>\n
Can I undo a repair?<\/h3><\/dt>\n
How are replacement files suggested?<\/h3><\/dt>\n
Does it send anything to your servers?<\/h3><\/dt>\n
Does it contact other websites?<\/h3><\/dt>\n
Does it scan on its own, or in the background?<\/h3><\/dt>\n
Does it run a search and replace on my database?<\/h3><\/dt>\n
What does \"Could not verify\" mean?<\/h3><\/dt>\n
Why is a working file on another website shown as \"at risk\"?<\/h3><\/dt>\n
media_file_fixer_local_hosts<\/code> filter, and it will be treated as local.<\/p><\/dd>\nI have media that nothing uses. Is that a problem?<\/h3><\/dt>\n
Does it work with page builders like Elementor or Divi?<\/h3><\/dt>\n
Does it scan custom post types?<\/h3><\/dt>\n
media_file_fixer_scan_post_types<\/code> filter.<\/p><\/dd>\nWill it slow down my website?<\/h3><\/dt>\n
Does it work on multisite?<\/h3><\/dt>\n
How long does a scan take?<\/h3><\/dt>\n
Is it accessible and translation-ready?<\/h3><\/dt>\n
1.0.0<\/h4>\n\n
\n
1.0.0-rc.12<\/h4>\n\n
\n
1.0.0-rc.11<\/h4>\n\n
\n
bulk_repair<\/code> history label used by Media File Fixer Pro. No change to how\nthe free plugin scans, diagnoses or repairs anything, and nothing new runs on a site without Pro.<\/li>\n<\/ul>\n\n1.0.0-rc.10<\/h4>\n\n
\n
1.0.0-rc.9<\/h4>\n\n
\n
1.0.0-rc.8<\/h4>\n\n
\n
1.0.0-rc.7<\/h4>\n\n
\n
1.0.0-rc.6<\/h4>\n\n
\n
<img><\/code> tag, and only the one address was being replaced \u2014 so a browser picking any of the others still asked for a file that was gone.<\/li>\n1.0.0-rc.5<\/h4>\n\n
\n
1.0.0-rc.4<\/h4>\n\n
\n
1.0.0-rc.3<\/h4>\n\n
\n
1.0.0-rc.2<\/h4>\n\n
\n
1.0.0-rc.1<\/h4>\n\n
\n
0.7.0-alpha<\/h4>\n\n
\n
0.6.4-alpha<\/h4>\n\n
\n
0.6.3-alpha<\/h4>\n\n
\n
0.6.2-alpha<\/h4>\n\n
\n
0.6.1-alpha<\/h4>\n\n
\n
0.6.0-alpha<\/h4>\n\n
\n
0.5.0-alpha<\/h4>\n\n
\n
0.4.1-alpha<\/h4>\n\n
\n
0.4.0-alpha<\/h4>\n\n
\n
0.3.1-alpha<\/h4>\n\n
\n
0.3.0-alpha<\/h4>\n\n
\n
0.2.0-alpha<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n