Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Start with the image’s requested URL and HTTP response, not with random plugin changes. Open the image in a new tab, then use your browser’s Network and Console panels to see whether WordPress is serving a missing file (404), denying access (403), mixing HTTP and HTTPS, or failing while processing an upload. That classification usually points to the correct fix—database, filesystem, web server, WordPress settings, or cache.
1. Identify exactly what is failing
First determine whether the problem affects one image, a thumbnail, every image, the Media Library, or only the live page. Test while logged out or in a private window so an administrator session does not hide the failure.
Open the image URL directly
- On the broken page, right-click the missing image and choose Copy image address (the wording varies by browser).
- Paste that URL into a new tab. If it does not open, the delivery path is broken independently of the theme or page builder.
- Open Developer Tools (usually F12), select Network, reload the page, and click the image request. Record the request URL, status code, response headers, and any redirect.
- In Console, note mixed-content, CORS, JavaScript, or certificate errors. A console message is useful context, but the Network response is the primary clue.
Do not replace a theme or deactivate all plugins before this check. Those changes can remove evidence and do not repair a missing file or a server permission rule.
2. Match the response to the right fix
| Symptom or response | Likely location of the fault | First correction | Access normally required |
|---|---|---|---|
| 404 Not Found | Missing file, wrong path, renamed domain, or deleted upload | Verify the attachment and the file under wp-content/uploads; correct stale URLs or restore the file |
WordPress admin plus filesystem, database, or migration access |
| 403 Forbidden | Permissions, ownership, host firewall, hotlink protection, or security rule | Check server and host rules for wp-content/uploads; ask the host to correct ownership or blocking rules |
Host panel, FTP/SSH, or host support |
| HTTPS page requests HTTP image | Mixed content after an SSL or domain change | Update WordPress URLs and stored image references to HTTPS, then clear caches | WordPress admin and migration-safe search/replace access |
| Original opens but thumbnail fails | Missing or stale derivative size | Regenerate the required image sizes | Admin regeneration plugin or SSH/WP-CLI |
| Upload processing message | Unsupported type, server image library/resource limit, or transient failure | Follow the exact message; retry only when it indicates a temporary or possibly successful upload | WordPress admin; host help for server errors |
3. Fix 404 errors and missing Media Library files
Confirm the attachment in Media
Go to Media > Library, open the attachment, and use View attachment page or the file URL. If the original cannot be opened, check whether the site was migrated, the domain or uploads directory was renamed, or files were deleted from storage. Compare the attachment URL with the actual year/month path beneath wp-content/uploads. Restore the original from a backup or copy it back to the path WordPress expects before editing content.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match#1 Best Overall
Correct stale domains and paths safely
After a move, WordPress Address and Site Address are under Settings > General. Confirm both use the current scheme and domain. Also inspect any custom upload-path setting and the URL saved in the attachment or page content. Replace old domains or http:// references with a migration-aware search-and-replace tool that understands serialized WordPress data; a plain text replacement can corrupt serialized values. Back up the database first, run a dry run when available, then clear page, object, and CDN caches.
Do not change only the visible page HTML if the old URL is stored in blocks, widget settings, custom fields, or a page-builder database table. Search for the old host and scheme across those locations.
4. Resolve 403 Forbidden responses
A 403 is not a broken thumbnail. The web server received the request and refused it. Check the permissions and ownership of wp-content and its uploads subdirectory, plus any .htaccess, Nginx location rule, host security setting, hotlink protection, or firewall rule that can block image requests. WordPress documentation notes that correct permissions may be required for the wp-content directory when uploading media.
When to involve the host
Ask hosting support to inspect the server error log, file owner, security-module events, and upload-directory rules when you do not control those settings. Do not make permissions broadly writable as a shortcut. The host should apply the least-permissive values compatible with the web server and PHP user, and confirm that an ordinary GET request to an image is allowed.
5. Repair mixed-content and SSL problems
If the page is HTTPS but the image URL begins with HTTP, browsers may block or downgrade the request as mixed or insecure content. Confirm the certificate and canonical domain first, then update WordPress Address and Site Address in Settings > General. Use a migration-safe search-and-replace for stored http://old-domain and http://current-domain image references. Check theme options, widgets, CSS backgrounds, custom fields, and page-builder data as well as post content. Purge WordPress, reverse-proxy, browser, and CDN caches after the replacement.
6. Handle upload and image-processing errors
“This file cannot be processed by the web server”
This exact message generally indicates an unsupported file type or a server-side image-processing problem. Confirm the extension and MIME type, try a standard JPEG or PNG, and check the host’s PHP image-library and resource limits. Do not simply rename a file extension; convert it to a genuinely supported format.
“Unexpected response from the server”
The upload may have succeeded even though the editor received an unexpected response. Reload Media > Library and search for the filename before retrying. Repeated retries can create duplicates.
“The server cannot process the image”
WordPress.com’s troubleshooting guide uses this exact message for a server image-processing failure. Retry once if the failure may be temporary. If it persists, reduce unusually large dimensions, verify available memory and disk space, and ask the host to check PHP limits and the image library.
7. Regenerate missing thumbnails and responsive sizes
When the full-size original opens but a URL containing a size suffix such as -300x200 returns 404, the derivative is missing. Theme changes, imports, interrupted migrations, and changed image-size settings commonly cause this state.
WP-CLI method
Back up files and the database before any operation that can delete or replace derivatives. From the WordPress directory, regenerate all attachment sizes with:
wp media regenerateFor a specific size, use the documented selective option:
wp media regenerate --image_size=thumbnailTo create only sizes that are absent, use:
wp media regenerate --only-missingRun wp media regenerate --help on your installed WP-CLI version to review available options. A maintained thumbnail-regeneration plugin can perform the same job from the dashboard when SSH is unavailable. Regeneration cannot recreate an original file that no longer exists.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #4
8. Distinguish blurry images from missing images
A blurry image is present, so treat it as a sizing problem rather than a delivery failure. Use a source image large enough for its intended display, select the appropriate inserted size in the block or page builder, and regenerate derivatives after changing theme image sizes. A CDN can improve delivery speed and edge caching, but it cannot restore an absent file or correct a wrong URL.
9. Check caches, CDNs, and optimization layers last
Once the origin URL works directly, purge page and object caches and invalidate the CDN path. Temporarily bypass image optimization or WebP conversion only to isolate a transformation problem; restore the service after testing. Compare the origin response with the CDN response, including content type and status. A cache hit can preserve an old 404, while a security layer can return a 403 that never reaches WordPress.
10. A practical repair sequence
- Copy the failing URL and test it directly.
- Inspect Network and Console, recording the status and redirect chain.
- Check the attachment under Media > Library.
- For 404, verify the file, uploads path, domain, and migration references.
- For 403, have the host check permissions, ownership, and security rules.
- For mixed content, correct HTTPS settings and stored URLs, then purge caches.
- For upload messages, follow the specific diagnosis and reload Media before retrying.
- If the original works but a derivative does not, regenerate only the required sizes.
- Retest while logged out and on another network or browser.
Or skip the browser setup
If you need a reliable way to capture a diagnostic view after the page is fixed, ScreenshotNeo returns a screenshot or PDF from one request. It accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
See the ScreenshotNeo documentation for all options. A basic cURL request is:
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorscurl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots, and every feature is available on every plan. Create a free ScreenshotNeo account.
Best Value
Frequently Asked Questions
Why do images work in the editor but not on the live page?
The editor may use an administrator session or a different URL. Test the public image URL while logged out and inspect its Network response for a 404, 403, redirect, or mixed-content block.
Can clearing the cache restore a deleted image?
No. Clearing caches can remove a stale response, but it cannot recreate an absent original or derivative. Restore the file or regenerate the derivative after the origin is correct.
Should I disable every plugin to fix broken images?
Only use controlled plugin isolation after recording the failing URL and response. A 404 or 403 usually requires a path, filesystem, host, or security correction rather than a blanket deactivation.
Recommended Free Tools
The Bottom Line
Find the failing URL and HTTP response first. Then apply the fix that matches it: restore or correct a 404, involve the host for a 403, replace stale HTTP or domain references after migrations, follow the exact upload error, and regenerate derivatives when only thumbnails are missing.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
