An earlier version of this article was in Infinite Ink’s TGIH: Themeless & Gitless Introduction to Hugo in a section called “Debugging tips.”
If there is a problem with a Hugo site that you are developing, here are some things you can try.
Use Ctrl-C to stop the Hugo server and then restart it.
In your web browser, do a “hard reload” or “hard refresh.” How to do this in many web browsers is in en.wikipedia.org/wiki/Wikipedia:Bypass_your_cache.
hugo server with flags such as:
-v (equivalent to
Check that the port number in your web browser
is correct. If you have multiple Hugo servers running, you may need to look at
This can happen when you are using multiple terminals.
View your site with a different web browser.
Explicitly specify a different port, e.g.
hugo server -D -p 8888.
Put debug code in layout files.
Delete the Hugo server cache. To find its location, run
and look for the value of
resources/ directory that Hugo generates. An example
resources/ directory is discussed in
5 of TGIH: Themeless & Gitless Introduction to Hugo.
In your config file(s) and front matter, make sure that any value
that you intend to be a string is not being interpreted as a number,
and vice versa. You can force a number to be interpreted as a string by using quotes,
🧐If you have a problem viewing emoji, smart quotation marks (such as “), mathematical symbols (such as ℵ), or any non-ASCII character, make sure your web server’s HTTP configuration and your Hugo source and destination files are all using UTF-8 encoding. UTF-8 is the standard file encoding for the web nowadays.