You publish a blog post, send a newsletter, or list a product, and a few days later someone tells you the pictures are gone. In their place is a small broken-image icon, an empty box, or just the alt text. It is frustrating, but a broken image is rarely a mystery. The image either can’t be found, isn’t allowed to load, or can’t be displayed, and each of those has a short list of causes you can check in a few minutes.
This guide walks you through how to diagnose the problem, fix the most common causes, and set things up so your hosted images keep loading for the long haul.
What a Broken Image Actually Tells You
When a browser displays a web page, it reads each image tag and requests the file at the address in its src attribute. If the server at that address sends back a valid image, you see it. If anything goes wrong along the way, the browser shows a placeholder instead.
That means a broken image is almost always one of three things:
- The address is wrong. The URL points somewhere that has no image, or never did.
- The server refuses the request. The file exists, but the host won’t send it to that page or that visitor.
- The browser can’t use what it got. The file arrived, but it isn’t in a format the browser can display, or it was blocked for security reasons.
Figuring out which of the three you are dealing with is the fastest way to a fix.
Step 1: Test the Image URL on Its Own
Right-click the broken image (or the empty space where it should be) and choose the option to copy the image address. If you can’t do that, open the page source or your editor and copy the URL from the image tag. Then paste that URL into a new browser tab.
- If the image shows up on its own, the file is fine, and the problem is in how the page is loading it (permissions, hotlinking, mixed content or the page’s code).
- If you get an error page, a login screen, or an HTML page instead of a bare image, the URL itself is the problem.
- If the browser offers to download a file instead of displaying it, the format or the server’s file settings may be the issue.
Read the status code
For a more precise answer, open your browser’s developer tools (usually F12 or right-click and choose Inspect), go to the Network tab, reload the page, and filter by images. Each failed request shows a status code:
- 404 Not Found means nothing exists at that address. Think typo, moved file or deleted file.
- 410 Gone means the file was intentionally removed, often because a link expired.
- 403 Forbidden means the file may exist, but the server won’t serve it to you. Think private settings or hotlink protection.
- Blocked or (failed) with no code often points to mixed content, an ad blocker, or a browser privacy feature.
The Most Common Causes and Their Fixes
You copied a page link instead of a direct image link
This is the single most common mistake. Many hosting and file-sharing services give you a link to a viewing page, a page that contains your image along with buttons, menus and other content. That link works perfectly when you click it, but it can’t go inside an image tag because it returns a web page, not an image file.
Fix: Use the host’s direct link, which typically ends in a file extension such as .jpg, .png, .webp or .gif. Image hosts like ImageCoast provide direct links and embed codes for exactly this purpose. General file-sync and document services often don’t, so they are a poor choice for embedding.
The file was moved, renamed or deleted
If you reorganized folders, renamed a file to something more descriptive, or cleaned out an old account, every page that pointed at the old address now gets a 404.
Fix: Re-upload or locate the file and update the URL everywhere it appears. If you control the server, a permanent redirect from the old address to the new one can rescue links you can’t edit by hand.
Typos, capital letters and spaces
Many web servers treat Photo.JPG and photo.jpg as two different files. A single wrong letter, a missing slash or a stray space breaks the link.
Fix: Copy URLs instead of typing them. Going forward, name files in lowercase with hyphens instead of spaces, such as red-barn-sunset.jpg. Spaces get encoded as %20, and that encoding is easy to mangle when links are copied between tools.
Expired or temporary links
Temporary image hosting and time-limited sharing links are designed to stop working after a set period. Some cloud storage services also generate signed links that expire after hours or days. These are great for a quick one-off share and bad for anything permanent.
Fix: For blog posts, product listings and anything you expect people to see months from now, upload to a host with permanent links and replace the expired URL.
Hotlink protection and private settings
Hotlinking is displaying an image hosted on someone else’s server on your own page. Many sites block it to save bandwidth, so the image loads fine on their site and returns a 403 or a placeholder graphic everywhere else. The same thing happens if an album or file is set to private.
Fix: Only embed images from a host that explicitly allows embedding, ideally your own account. Check that the image or album is set to public or link-accessible. And if the image isn’t yours, ask permission or use a properly licensed copy rather than hotlinking.
Mixed content: HTTP images on HTTPS pages
If your site uses HTTPS but an image URL starts with http://, browsers treat it as mixed content. Depending on the browser, it may try to upgrade the request to HTTPS and block the image if that fails.
Fix: Change image URLs to https:// and confirm the image loads at the secure address.
Local file paths
A URL like file:///C:/Users/you/Pictures/logo.png only works on the computer where that file lives. It looks fine while you are drafting and breaks for every other visitor.
Fix: Upload the image to a host and use its public URL instead.
Unsupported formats
Phones often save photos as HEIC, which many browsers and email clients won’t display. Very large or unusual files, such as TIFF or RAW, can cause similar problems.
Fix: Convert to JPEG, PNG or WebP before uploading. Most phones can also be set to save or share in a more compatible format.
Special Cases: Email, Forums and Marketplaces
Some platforms add their own rules on top of the basics:
- Email: Many email clients hide images until the reader chooses to load them, so a missing picture may be a client setting, not a broken link. Make sure your images use absolute HTTPS URLs and include alt text, so the message still makes sense before images load.
- Forums: Forums that use BBCode or Markdown need the direct image URL inside the image tag. A viewing-page link will show up as a plain link or nothing at all.
- Marketplaces and social platforms: Many of these copy your image to their own servers when you upload, and some reject external image URLs entirely. Check each platform’s rules before assuming your host is at fault.
How to Keep Images From Breaking Again
Fixing a broken link takes a few minutes. Preventing the next one is mostly about habits:
- Use one dependable host for anything permanent. Keeping your published images in a single account, such as ImageCoast, means you always know where the originals live and which links are in use.
- Don’t rename or move files that are already published. If you must reorganize, upload a fresh copy and update links first.
- Reserve temporary links for temporary needs. Quick shares are fine; blog posts and product pages are not quick shares.
- Use clean, lowercase file names with hyphens instead of spaces.
- Always use HTTPS URLs for embedded images.
- Keep a local backup of every published image so you can re-upload quickly if something disappears.
- Check your important pages periodically. Many website platforms and free link-checking tools can scan for broken images so you catch problems before readers do.
Frequently Asked Questions
Why does my image work when I click the link but not on my website?
You are probably using a link to a viewing page instead of a direct image URL, or the host blocks hotlinking. Open the link in a new tab: if you see a full web page rather than just the image, switch to the direct link.
Why do my images show up for me but not for other people?
Your browser may be loading a cached copy, or the URL points to a file on your own computer or to a private album you are logged into. Test the page in a private browsing window to see what visitors see.
Will broken images hurt my website’s SEO?
Broken images won’t appear in image search and make pages look neglected, which can hurt the experience for visitors. Fixing them and adding descriptive alt text is good practice for both readers and search engines.
How can I find all the broken images on my site?
Use your browser’s developer tools on individual pages, or run a link-checking tool that crawls your site and reports images returning 404 or 403 errors. Many website platforms also offer plugins that do this automatically.
Should I host images on my own server or with an image host?
Either can work. An image host saves you from managing storage and bandwidth and gives you ready-made direct links, while self-hosting gives you full control. What matters most is choosing a permanent home and not moving files after you publish them.