hugo/content/templates/404.md

aliases	lastmod	date	linktitle	menu	next	notoc	next	prev	title	weight
/layout/404/	2015-12-30	2013-08-21	Custom 404 page	main parent layout	/taxonomies/overview	true	/templates/debugging	/templates/sitemap	404.html Templates	100

---

aliases:

• /layout/404/ lastmod: 2015-12-30 date: 2013-08-21 linktitle: "Custom 404 page" menu: main: parent: layout next: /taxonomies/overview notoc: true next: /templates/debugging prev: /templates/sitemap title: 404.html Templates weight: 100

---

When using Hugo with GitHub Pages, you can provide your own template for a custom 404 error page by creating a 404.html template file in your /layouts folder. When Hugo generates your site, the 404.html file will be placed in the root.

404 pages will have all the regular page variables available to use in the templates.

In addition to the standard page variables, the 404 page has access to all site content accessible from .Data.Pages.

▾ layouts/
    404.html

404.html

This is a basic example of a 404.html template:

{{ partial "header.html" . }}
{{ partial "subheader.html" . }}

<section id="main">
  <div>
   <h1 id="title">{{ .Title }}</h1>
  </div>
</section>

{{ partial "footer.html" . }}

Automatic Loading

Your 404.html file can be set to load automatically when a visitor enters a mistaken URL path, dependent upon the web serving environment you are using. For example:

• GitHub Pages - it's automatic.
• Apache - one way is to specify ErrorDocument 404 /404.html in an .htaccess file in the root of your site.
• Nginx - you might specify error_page 404 = /404.html; in your nginx.conf file.
• Amazon AWS S3 - when setting a bucket up for static web serving, you can specify the error file.
• Caddy Server - using errors { 404 /404.html }. Details here