First of all: I’m not allowed to put links in here. So I have to change them… I updated to latest hugo (I was many versions behind) today. Then realized that my pictures are not displayed. I used to have them in the /static directory. Then went on to read: hugo docu: introduction/#from-file-to…

Displaying images is fairly straightforward. Use Markdown. ![](path-to-img.jpg). Then, it won’t matter if you have your images in static or assets. If you don’t want to process images using Hugo, you can let them exist in static. So, if your image exists at: /static/images/img1.jpg, you can add it…

Why do I need the last part only one time, and shouldn’t there be the filename of the image somwhere in there?

[image] jubalh: Why do I need the last part only one time It’s because of Render Hooks. Basically, you’re telling Hugo how to render the HTML content of the Markdown Image syntax. So once it’s created, all the images in Markdown written in the Markdown syntax will render with the code in that…

I put my images in /static/images/… (which get published into /images/… ) and just use plain markdown to add them to posts. I think the /assets/images directory is for images that need to be processed by Hugo? I pre-process all images outside of Hugo, and just put the web-ready files in /static/imag…

Thanks! I found this very difficult because the docs show {{...}} embedded somewhere, and I inferred I could simply use it as shown in the .md content.

Displaying images

support

Topic		Replies	Views
How to show images on post pages if they're located in the assets folder? support	15	8026	September 9, 2021
Migrating image links from classic markdown support	5	138	March 30, 2025
Restoring ![]() functionality for images in /assets, with render-image.html support	2	458	September 22, 2023
Placement of images where and why? support	3	649	May 28, 2023
Image processing outside of the page resource scope	5	1317	April 17, 2020

Displaying images

Related topics