Hugo takes the parameters listed below into consideration when choosing a layout for a given page. They are listed in a priority order. This should feel natural, but look at the table below for concrete examples of the different parameter variations.
The page Kind (the home page is one). See the example tables below per kind. This also determines if it is a single page (i.e. a regular content page. We then look for a template in _default/single.html for HTML) or a list page (section listings, home page, taxonomy lists, taxonomy terms. We then look for a template in _default/list.html for HTML).
See Custom Output Formats. An output format has both a name (e.g. rss, amp, html) and a suffix (e.g. xml, html). We prefer matches with both (e.g. index.amp.html, but look for less specific templates.
We will consider a language code in the template name. If the site language is fr, index.fr.amp.html will win over index.amp.html, but we will index.amp.html will be chosen before index.fr.html.
Can be set in page front matter.
Is value of type if set in front matter, else it is the name of the root section (e.g. “blog”). It will always have a value, so if not set, the value is “page”.
Is relevant for section, taxonomy and taxonomyTerm types.
Hugo Layouts Lookup Rules With Theme
In Hugo, layouts can live in either the project’s or theme’s layout folder, and the most specific layout will be chosen. Hugo will interleave the lookups:
This way it is possible to override specific templates from the theme.