When images fail in Chrome, first determine whether the problem affects one website or many. A single-site failure usually points to that site’s permissions, code, server, or content policy; images missing everywhere more often indicate an extension, damaged profile data, network/security software, or low system memory. Open the same page in an Incognito window: if images appear there, focus on extensions and stored profile data before changing system-wide settings.
1. Establish the scope before changing anything
- Reload the page. Use Ctrl+R (Windows/Linux) or Command+R (macOS). A transient connection or server response can leave broken-image icons.
- Verify the image and page URLs. A typo, expired link, case-sensitive filename, or redirect to a removed asset cannot be repaired by Chrome settings.
- Test a second website. If other sites display images, keep your troubleshooting site-specific. If several unrelated sites fail, investigate the browser profile, network, security software, and available memory.
This scope test prevents a global reset for what may be one broken image URL.
2. Use Incognito as an isolation test
Open the affected address in an Incognito window with Ctrl+Shift+N (Windows/Linux) or Command+Shift+N (macOS). Incognito starts without most saved site data and normally disables extensions unless you have explicitly allowed them.
- Images work in Incognito: an extension, cookie, cache entry, or profile permission is the leading suspect.
- Images fail in both modes: check the image URL, site code, network, firewall/antivirus filtering, VPN, and server response.
Incognito is a diagnostic comparison, not a permanent fix. It does not prove that Chrome itself is defective.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
3. If Incognito works, repair the normal profile
Disable extensions systematically
- Open Chrome menu ⋮ → Extensions → Manage extensions.
- Turn off every extension, reload the page, and check the images.
- If the images return, enable extensions one at a time and reload after each. Google’s guidance is: “If this solves your connection error or loading issue, re-enable your extensions one at a time to identify which extension is causing the problem.”
- Remove or reconfigure the extension that blocks the images. Ad blockers, privacy filters, script blockers, download helpers, and security plug-ins can block image hosts or CDN requests.
Clear data for the affected site
Targeted deletion is less disruptive than wiping every site’s login state. Open the page, select the site-controls icon to the left of the address, choose Cookies and site data (or Site settings), then delete the stored data for that site. Reload and sign in again if required.
For a broader cleanup, go to Chrome menu ⋮ → Settings → Privacy and security → Delete browsing data. Select Cookies and other site data and Cached images and files, choose an appropriate time range, and confirm. Clearing cookies signs you out and may remove preferences, so record anything you need first.
Check JavaScript and site permissions
- Open the affected page.
- Select the site-controls icon → Site settings.
- Set JavaScript to Allow (default) unless you intentionally manage it another way.
- Review relevant content permissions and reset an unusual block. Embedded images can also depend on third-party cookies; Chrome documents that cookie restrictions may affect embedded content.
- Reload in a new tab.
Do not permanently allow every site or disable all privacy protections. Change only the permission needed, then test again.
4. When images fail on many websites
Check the connection and filtering layers
- Open another browser or device on the same network. If it also fails, restart the router or switch networks briefly.
- Temporarily test without a VPN, DNS filter, parental-control service, or corporate proxy, following your organization’s policy.
- Review firewall and antivirus web-shield logs. Security software can block an image CDN, domain, or file type; update its rules rather than leaving protection disabled.
- Check whether a managed device policy is enforcing blocked content. Contact the administrator instead of attempting to bypass it.
Check memory and browser health
Close unused tabs and applications, then reload. Chrome may discard or fail to render resources when the device is under memory pressure. In Chrome menu ⋮ → More tools → Task manager, sort by memory and close a tab or extension that is consuming excessive resources. Restart Chrome and install pending browser and operating-system updates.
5. Diagnose the exact failed request
Developer Tools distinguishes a browser-side block from a server-side failure.
- Open the page and press F12 (or Command+Option+I on macOS).
- Choose Console and reload. Note messages mentioning mixed content, Content Security Policy (CSP), blocked requests, certificates, or CORS.
- Choose Network, filter by Img, reload, and select the failed request.
- Record the complete image URL, status code, redirect chain, response headers, and the console message. A 404 indicates a missing asset; 401/403 suggests authentication or access control; a certificate or CSP message identifies a policy problem; a request that never completes points toward connectivity, blocking, or timeout.
Save this information before contacting the site owner. It is more useful than a screenshot of the broken icon alone.
6. What site owners need to fix
Mixed content
An HTTPS page requesting an HTTP image creates mixed content. Browsers may auto-upgrade some image requests, but behavior can still fail because of redirects, certificates, or policy. MDN’s recommendation is direct: “The best strategy to avoid issues with mixed content is to serve all the content as HTTPS:” Replace http:// image URLs with https:// or same-origin relative URLs, verify the certificate and every redirect, then retest the console.
Content Security Policy
CSP can restrict image origins. Inspect img-src and the inherited default-src directive in the response header or meta policy. Compare the blocked host with the policy shown in DevTools and allow only the intended image origin. upgrade-insecure-requests can upgrade insecure resource requests, but it does not replace an img-src rule that permits the destination.
Recommended Free Tools
Server, CDN, and asset checks
- Request the exact URL directly and confirm a successful response.
- Ensure the final response has an image content type such as
image/png,image/jpeg, orimage/webp, not an HTML login or error page. - Check authentication, hotlink protection, CDN permissions, expiring or signed URLs, and rate limits.
- Correct filename capitalization and URL encoding; Linux servers commonly treat case differences as different files.
- Confirm lazy-loading code eventually assigns a valid
srcorsrcsetand that JavaScript errors do not stop that code.
Chrome cannot repair an origin that never returns the asset.
7. Fixes by symptom and reversibility
| Symptom | Most useful next test | Likely layer | Change type |
|---|---|---|---|
| One site only | Site settings, direct image URL, DevTools Network | Permission, server, CSP, URL | Targeted and reversible |
| Several sites, Incognito works | Disable extensions; clear site data | Profile or extension | Reversible |
| Several sites in every browser | Other network/device; firewall and VPN test | Network or security software | Temporary diagnostic |
| Console reports mixed content | Inspect image scheme and redirects | Website code or certificate | Permanent site fix |
| Console reports CSP violation | Compare URL with img-src/default-src |
Website policy | Permanent site fix |
8. Prevention for developers
- Use HTTPS for the document, images, redirects, and CDN endpoints.
- Test with a clean profile and Incognito, but also test with normal extensions and stored cookies.
- Monitor image URLs for 4xx/5xx responses and certificate expiry.
- Keep CSP narrow but include every legitimate image origin.
- Test lazy-loaded, responsive, authenticated, and signed assets at realistic viewport sizes.
Or skip the browser setup
If you need a clean reference capture while debugging a page, ScreenshotNeo provides a website screenshot API and MCP server. It accepts 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 result.
One request returns PNG, JPEG, WebP, or PDF:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the complete options and authentication details in the ScreenshotNeo documentation. Equivalent calls:
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)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);It also supports full-page and selector captures, dark mode, device presets, retina scale, PDF controls, custom CSS/JavaScript, clicks, waits, request blocking, headers, cookies, user agents, timezone and geolocation, transparent backgrounds, resizing, chosen cache TTLs, signed links, asynchronous webhooks, bulk capture of up to 100 URLs per call, usage reporting, and an OpenAPI specification. An MCP server exposes take_screenshot, get_page_info, and capture_pdf to Claude, Cursor, and other MCP clients.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →The Free plan includes 1,000 screenshots each month with no card. Paid plans start at $5 for 3,000 shots; every feature is included on every plan. Create a free ScreenshotNeo account.
Best Value
9. When to contact the site owner or administrator
Escalate after you have recorded the failing URL, status, console message, browser version, and whether Incognito or another network changes the result. Tell the site owner if only their domain fails; tell your administrator if a managed network, proxy, or security product blocks multiple domains. Avoid sending passwords, private cookies, authorization headers, or personally identifying query parameters in diagnostic logs.
Frequently Asked Questions
Why do images load in Incognito but not normal Chrome?
Incognito isolates much of the normal profile. An extension, cached response, cookie, or site permission in the regular profile is therefore the most likely difference; disable extensions one at a time and clear data for the affected site.
Can clearing Chrome data delete my passwords?
The Delete browsing data screen has separate categories. Select only the cached files and site data you intend to remove, and check the selected time range before confirming; saved passwords are a separate category.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsWhat should I send a website owner about a broken image?
Send the exact image URL, HTTP status and redirect result from DevTools’ Network panel, the Console error, your Chrome version, and whether the failure occurs in Incognito or on another network.
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.
