Detailed answer
Check the resolved URL, response status, filename case, and document directory.
A case mismatch can work locally but fail on a different hosting filesystem. The network panel shows the actual request rather than the intended disk path. Keep useful alternative text while fixing the unavailable resource.
Example
<img src="/images/html-example.png" alt="An HTML example page" width="640" height="360">
Understanding the behavior
An image path is resolved as a URL, not as the file manager's current folder. Deployment can expose case mismatches that a local system tolerated. The response can also fail because of permissions, a wrong base URL or an HTML fallback response.
Practical implementation notes
Open the resolved image URL and inspect its status and content type. A successful 200 response containing an error page is still not a valid image, so check the returned body as well as the code.
How to check it
Compare case, separators, resolved URL, and actual response on the target host.
Expected result
The browser requests the correctly cased URL rather than a filesystem path.
Watch out: Windows backslashes are not portable web URL separators.
Read the reference ↗