Pictures not loading on a website can make a page look incomplete, confuse visitors, and prevent them from accessing important information. If you notice images not loading on a website, broken picture icons, blank image spaces, or photos that disappear after a page refresh, the cause could be your browser, internet connection, website settings, or image files. The good news is that most image-loading problems can be diagnosed with a few simple checks. This guide explains how to identify the cause and fix images that will not load, whether you are browsing a website or managing one yourself.
Images may fail to appear for several reasons, and the correct solution depends on where the problem occurs. Sometimes, the issue is temporary and affects only your browser. In other cases, the website may have broken image links, server errors, incorrect file permissions, or a configuration problem.
Here are some common causes of website images not displaying:
Before changing advanced settings, determine whether the problem affects one image, one website, or every website you visit. This simple distinction can save time and help you choose the right fix.
If pictures are not loading, start with the easiest troubleshooting steps. Test each solution before moving to the next one so you can identify what actually resolves the issue.
An unstable internet connection can interrupt image downloads even when the text on a website loads successfully. Images may appear as blank boxes, remain stuck while loading, or display only after you refresh the page.
Try opening another website that contains several images. If those images also fail to appear, restart your router or switch to another network. You can also compare Wi-Fi with mobile data to determine whether the problem is related to your connection.
If only one website has missing images, your internet connection may not be the main cause.
A temporary loading error may prevent a browser from displaying images correctly. Refreshing the page forces the browser to request the page resources again.
On Windows, press Ctrl + R or F5. On a Mac, press Command + R.
If the images still do not appear, try a hard refresh to reload resources rather than relying on cached copies. The exact shortcut may vary by browser and operating system.
Repeated refreshing is unlikely to help if the image file has been deleted or the website server is returning an error.
Browsers store temporary files to make websites load faster. However, an outdated cached image or other stored resource can sometimes cause display problems.
To troubleshoot this issue, open your browser settings and find the option for clearing browsing data. Select cached images and files, then clear the cache.
Close and reopen the affected website afterward.
You usually do not need to delete saved passwords or all browsing history to test this solution. Start with cached files to avoid removing data you want to keep.
Extensions can interfere with website images. Ad blockers, tracking protection tools, script blockers, and some security extensions may prevent certain image requests from completing.
To check whether an extension is responsible, open the affected website in a private or incognito window, where extensions may be disabled by default. Keep in mind that some browsers allow extensions to run in private browsing, so verify their settings.
If images load correctly in that window, disable your extensions one at a time and test the website again. Re-enable extensions that are not responsible for the issue.
Avoid permanently disabling security protections just to display images.
An outdated browser can sometimes have compatibility problems with modern image formats, website scripts, or security requirements.
Check for available updates in your browser’s settings. Install any appropriate update, restart the browser, and revisit the website.
If images are not loading in Chrome but appear correctly in Firefox, Safari, or Microsoft Edge, the problem may be related to Chrome’s settings, extensions, cached data, or version.
Testing another browser helps narrow down the cause, although it does not automatically identify the exact problem.
Sometimes, the website itself is responsible. Its image server may be temporarily unavailable, or a content delivery network (CDN) may be experiencing a disruption.
Try accessing the same page from another device or network. If the images are missing everywhere, the website owner may need to investigate the problem.
If only some images are missing, the website may contain broken links or files that were removed during an update.
When the issue is on the server side, changing your browser settings will not repair the missing files.
If you manage a website and an image does not appear in HTML, start by checking the image element and the file location. A small mistake in the image path, filename, or server configuration can cause the browser to display a broken image icon.
An HTML image is commonly displayed using the <img> element and its src attribute. The src value must point to an accessible image file.
For example:
<img src="/images/product-photo.jpg" alt="Product photo">Check that the filename, directory, and file extension match the actual image. Some web servers distinguish between uppercase and lowercase filenames, so Product-Photo.jpg may not resolve to product-photo.jpg.
Also confirm that the image path is correct relative to the page or that the absolute URL points to the intended resource.
Copy the image URL and open it in a new browser tab. If the file cannot be accessed directly, investigate the URL, server response, and file location.
Common HTTP status codes include:
Browser developer tools can help you inspect the Network tab, identify failed image requests, and review their status codes.
Images that work on a local computer but disappear after deployment often have incorrect paths or missing files.
Verify that the image was uploaded to the production server and that the website references the correct directory. Check file and directory permissions according to your hosting environment, ensuring that the web server can read the image.
If the website was recently migrated, updated, or redeployed, confirm that the migration included the required image files and preserved their URLs.
Sometimes, the image file loads successfully but remains invisible because of a styling or scripting problem.
Check whether CSS properties such as display: none, visibility: hidden, zero dimensions, or an unexpected overlay are hiding the image. Also inspect the browser console for JavaScript errors that might interrupt image rendering.
If the website uses lazy loading, verify that images become visible when they enter the intended loading area. Incorrect lazy-loading logic can leave placeholders on the page indefinitely.
WordPress images not showing on a website may be caused by incorrect media URLs, caching problems, plugin conflicts, migration errors, or server permissions.
Try these checks before making major changes to your website.
Open the WordPress Media Library and locate an affected image. Confirm that the file exists and that its URL points to the correct location.
If the image URL contains an old domain or an incorrect directory after a migration, update the relevant references using an appropriate WordPress migration or URL-replacement method. Back up your website before making bulk changes.
If your website uses a caching plugin, hosting cache, or CDN, clear the relevant caches after changing image files or URLs.
A stale cached page may continue referencing an outdated image even after the underlying file has been corrected.
Image optimization, lazy-loading, security, and performance plugins can sometimes conflict with each other or with a theme.
Test for conflicts carefully, preferably on a staging website. Disable one suspected plugin at a time, then check whether the images return. Avoid making disruptive changes to a live website without a backup.
If the issue started after a theme update or migration, review the changes and check the website’s error logs.
When images are visible on a desktop but missing on a phone, the problem may involve mobile browser settings, responsive image markup, network conditions, or mobile-specific CSS.
Start by refreshing the page and switching between Wi-Fi and mobile data. You can also clear the mobile browser’s cache or test the page in another browser.
If you manage the website, inspect the responsive image configuration. The HTML srcset and sizes attributes allow browsers to select images based on screen size and resolution. Incorrect file references can cause the browser to request an image that does not exist.
Check whether CSS hides images at certain screen widths and confirm that the mobile version of the website does not use broken background-image URLs.
If images work on desktop but fail on mobile across multiple browsers, investigate the website’s responsive layout, server responses, and image delivery configuration.
Images may fail to display if the file is corrupted, incorrectly labeled, or encoded in a format that the browser or delivery system cannot handle.
Common web image formats include JPEG, PNG, WebP, and SVG. Modern browsers support many of these formats, but the actual file content must match its declared format and be valid.
For example, renaming a file from .png to .jpg does not convert the image. Use a proper image conversion tool if you need to change formats.
Large image files can also take longer to load, particularly on slow connections. Although a large file does not necessarily cause a broken image, it can make the page appear incomplete while the browser downloads it.
Compressing images and serving appropriately sized versions can improve loading performance. However, compression will not fix a missing file, incorrect URL, or server permission error.
If the basic fixes do not resolve the problem, investigate the technical configuration of the website.
A website served over HTTPS may encounter security restrictions when it attempts to load certain resources over insecure HTTP connections.
Check the browser console for mixed-content warnings and update affected image URLs to valid HTTPS addresses where supported. Ensure that the image server has a correctly configured certificate.
A content delivery network can improve image delivery, but incorrect CDN settings, expired access rules, or origin-server problems can prevent images from loading.
Hotlink protection may also block images when requests come from an unapproved domain. Review the relevant rules and confirm that legitimate website requests are allowed.
DNS resolution errors, network firewalls, security rules, and unavailable image servers can prevent the browser from reaching an image URL.
Check server logs and network requests to determine whether the failure occurs before the image reaches the browser. If a third-party image host is involved, verify that its service is available and that the image URL remains valid.
Use the following checklist to narrow down the problem.
| What you notice | Possible cause | What to check |
|---|---|---|
| Images are missing on every website | Browser settings, extensions, or network problems | Test another browser and network |
| Only one website has missing images | Website configuration or server issue | Test the site on another device |
| One image is broken but others work | Incorrect URL or missing file | Open the image URL directly |
| Images work after clearing the cache | Outdated cached resources | Review browser and website caching |
| Images work locally but not after deployment | Incorrect paths or missing uploads | Check production files and URLs |
| Images fail only on mobile | Responsive markup or mobile-specific settings | Inspect srcset, CSS, and mobile requests |
| Images remain blank while scrolling | Lazy-loading or JavaScript issue | Inspect browser console and loading behavior |
| Images return a 403 or 404 error | Access restriction or missing resource | Check permissions, paths, and server rules |
These clues are useful starting points rather than definitive diagnoses. A single symptom can have several possible causes, so confirm the issue by testing the relevant URL or browser request.
Text and images are often requested as separate resources. The browser may successfully load the page’s HTML while image requests fail because of broken URLs, blocked requests, server errors, or network interruptions.
Chrome may have outdated cached files, an extension conflict, restrictive settings, or a temporary browser problem. Clear the cached images, test the website in a private window, update Chrome, and compare the result with another browser.
A broken image icon usually indicates that the browser could not retrieve or decode the requested image. Check the src attribute, filename, file path, HTTP response, and image format.
A migration may change the domain, directory structure, or image URLs. Some files may also have been omitted during the transfer. Verify that the images exist on the new server and that the website references their current locations.
Image compression can reduce file sizes and improve loading speed, but it cannot repair broken URLs, missing files, incorrect permissions, or server outages. First confirm that the image is accessible and valid. Then optimize its size if performance is the concern.
Different images may be stored on separate servers, use different URLs, or have different permissions and formats. Inspect the failed image requests individually to identify whether the problem affects particular files, directories, or image sources.
When pictures are not loading on a website, the best solution is to identify where the failure occurs rather than changing settings at random. Start with your internet connection, browser cache, extensions, and page refresh. If the problem affects a website you manage, check image URLs, HTML paths, server responses, permissions, caching, and responsive image settings.