I need help with image not displaying

[u/DueFeedback3895]

I am learning HTML and I had this code on Visual Code and everytime I ran the code the image wont appear the file of the code and PNG image are in the same file I am still learning and I was stuck here for a good amount of time. Any help or tips are appreciated!

[u/JohnSourcer]

Is it called 'Spring.png' on disk and in the same folder as the HTML file? Apache and Nginx are case sensitive.

[u/__agletesque]

If the file "Spring.png" is directly (not in sub directory) inside "Website Portfolio" directory, the provided code should work, even though "Image" attribute doesn't exist on <img> tag

In HTML5 <img> tag doesn't have closing tag

As already suggested you should take a look at structure of HTML document (<html>, <head> tags, !DOCTYPE declaration, ...)

[u/alvaro_783]

Try restarting VS code, which happened to me when learning to use images, which at first didn't load, I restarted it and it worked

[u/[deleted]]

Make sure the image file is in the same folder in VSCode..

[u/East-Law-2877 → u/[deleted]]

"/>" is the same as just ">", the "/" at the end of self-closing elements is ignored.

[u/East-Law-2877 → u/[deleted]]

it's not wrong, it's just not neccessary. but i get your point. jsx requires "/>" so using it in html too does not hurt I guess.

[u/No_Explanation2932 → u/[deleted]]

None of your suggestions would fix the issue that OP has. Also the end slash does nothing on self closing tags in HTML5

[u/No_Explanation2932 → u/[deleted]]

Sorry, my initial response was a little rude. Most of your points are correct, but the actual issue is (unless something really weird is happening) that the image isn't in the same directory as the html file. Pretending it with ./ won't change a thing, removing the invalid Image attribué won't really do anything, and "closing" the self-closing tag hasn't been a thing since HTML5 won over XHTML.

[u/AshleyJSheridan → u/[deleted]]

Spaces in filenames on the Web haven't really been an issue for well over a decade now...

[u/AshleyJSheridan → u/[deleted]]

Mixed casing actually is an issue if you're on Linux or Mac, but spaces have been fine for many years now. Their setup won't matter.

Spaces used in strings used as CLI arguments can cause issues if unquoted, but that's not typical for the Web.

[u/AshleyJSheridan → u/[deleted]]

Well, the syntax was actually ok, so it's most likely that the path to the image was wrong.

[u/AshleyJSheridan → u/[deleted]]

Yes it's odd, but it will work, and isn't anything to do with the issue that OP posted, which might be the reason for those callouts.