The Media Library grid stays blank, spins indefinitely, or fails to load existing images.
You do not have to become a server administrator because one part of your website stopped cooperating. Start with the checks that stay inside WordPress. If the problem moves into hosting or server configuration, I will show you where the risk begins—and where it may make more sense to hand the headache to me.
Start with the checks inside WordPress
- Switch the Media Library between Grid view and List view.
- Open the dashboard in a private browser window and test again.
- Open one known attachment directly from Media → Library to see whether the file itself still exists.
After each change, test the same action again. Change one thing at a time so you know what helped and what did not.
A good place to pause
When this leaves normal WordPress editing
If the files exist but the library keeps spinning or appears blank, the failure is commonly in JavaScript, an AJAX or REST request, attachment metadata, or a database query. That is no longer a simple media-screen problem.
If you inherited the website, took over after parting ways with a developer, or normally use WordPress only to add photographs and text, you may have never opened cPanel before. That is normal, but if you are new to backend server configuration, you need to proceed with caution. This is where you can break your site.
You also do not need to end up with more damage than you bargained for just to solve one aggravating problem. The standard repair is $149.00 if you would rather hand it off.
If you are comfortable with backend server configurations, continue with the technical steps below.
Technical checks
- Check the browser console and network panel for the first failed admin request.
- Review security and caching rules that may be blocking admin-ajax.php or REST requests.
- Test plugin conflicts in a controlled way, with a backup and a record of every change.
- Inspect attachment queries and metadata only after confirming that the files are still present.
Proceed with caution
Do not delete attachment records or rebuild the media database as a first step. That can separate real files from the pages that use them.
Test the repair without making a second problem
- Keep a note of the original setting or filename before you change it.
- Make one change, clear only the relevant cache, and repeat the exact test.
- Check both the public page and the WordPress dashboard.
- If the error changes, stop and record the new message before continuing.
You can hand this off
If these checks have taken you beyond the part of WordPress you normally use, you can stop. I can trace the cause, make the repair, test the site, and tell you what was changed without turning one problem into your new full-time job.