What Hugo does with a Markdown file, and where an image fits

Hugo takes Markdown through a file under the content directory, carrying a front matter block at the top, and that is the door this page is about. The question worth asking is what an image looks like by the time it arrives, because Hugo never sees the image itself. It sees whatever the conversion handed over, and nothing else.

Hugo reads the front matter as data and everything after it as the page body. What comes out of an image here is the text of the image as Markdown, with a table rebuilt when the image held one, so the structure Hugo is looking for is actually present instead of merely implied. That is the entire trick, and there is nothing clever underneath it.

What survives from an image into Hugo

The conversion drops the background, the stamps, the shadows and the skew of the scan before Hugo ever sees them, because none of it carries meaning into Hugo and all of it costs something. What it keeps is the part you would otherwise have retyped by hand.

• The text comes out in reading order rather than in scan order, and Hugo receives it as structure rather than as something to infer.
• A visible table is rebuilt as a Markdown table instead of collapsing into a line of words, which is the part Hugo would otherwise have to reconstruct on its own.
• References and figures are read character by character, which is the part people retype by hand, so nothing downstream of Hugo has to guess at it.

What Hugo never gets back from an image

Every conversion costs something, and a page listing only the gains is a sales page. Here is what an image gives up on the way to Hugo, stated plainly enough that you can decide against it.

• Layout and colour are gone, and a colour that meant something meant it only to a human, and Hugo will not get it back from anywhere.
• Anything too small or too blurred to read is not returned, and not flagged either, so nothing you build in Hugo should depend on it.
• Certainty is gone: a model is reading, and a model can be wrong while sounding sure, which is a real cost inside Hugo and not a rounding error.

The Image to Markdown step behind this Hugo page was measured

Gemini 2.5 Flash Lite does the conversion, and it was proven end to end on 30 August 2026: a purchase order image built for the occasion, carrying a unique reference, came back with the reference, the quantity and the unit price all read correctly. That is one run on one day and not an average, which is exactly why the date travels with the claim instead of being left out of it. The same output is what Hugo would have received.

This capability returned nothing at all until 30 August 2026, and two probes failed that same day before the quota was restored. Hugo has no way of telling you any of that from the inside, so it gets said here instead, on the page that sent you there.

Once the image is Markdown, what to do inside Hugo

With the Markdown in hand, set title, date and draft in the front matter before the first build rather than after it. That is a Hugo habit rather than a conversion setting, and it is where most of the value of converting an image in the first place actually lands.

The constraint worth knowing before you start: a missing or malformed front matter block either fails the build or makes the page vanish, depending on where it broke. It bites the same way whether the Markdown came out of an image or out of something else entirely, but it bites hardest on long documents, which is what an image usually is.

What we will not pretend about Image in Hugo

• Hugo will not invent a title out of your first heading, and converting an image first does not change that in the slightest.
• a stray line of three dashes inside the body is read as the end of the front matter, which is a Hugo behaviour rather than anything the image conversion did.
• The conversion costs half a credit and the price is shown before the image is sent, whether the Markdown ends up in Hugo or nowhere at all.