Installing Extended Hugo
Updated  2022-May-4

Page contents


Ongoing  According to Repology, the latest packaged Hugo is version newest packaged version of Hugo. To keep up with Hugo releases, see,, or

2022-February-13  Published this evolving⁠[1] article.



This article assumes…

Infinite Ink’s Hugo Tutorial and many Hugo themes require extended Hugo.


1. Find out your path

The hugo executable is one⁠[2] file and can be put anywhere on your path. To find out your path, run one of the following commands at a command-line prompt.

  • In a Unix-like shell, including Git Bash, run:

    • echo $PATH

  • In PowerShell, run either of the following:

    • $env:path

    • $env:path -split ";"

  • In cmd.exe,⁠[3] run:

    • set path


If you use a package manager to install hugo or hugo.exe, you will not need to deal with your path because the package manager will take care of that.


2. Install extended hugo

You can install extended Hugo with a package manager or manually.

If you are not a superuser, using a package manager is the way to go IMHO.


Install manually

Go to and download the newest:

  1. hugo_version_checksums.txt, for example:

    • hugo_0.99.0_checksums.txt

  2. hugo_extended_version_platform.extension, for example one of these:

    • hugo_extended_0.99.0_Linux-64bit.deb[4]

    • hugo_extended_0.99.0_Linux-64bit.tar.gz

    • hugo_extended_0.99.0_macOS-64bit.tar.gz

    • hugo_extended_0.99.0_macOS-ARM64.tar.gz


Then, check the checksum of the hugo package you downloaded, unpackage it,⁠[4][5] and put the hugo or hugo.exe executable somewhere on your path (discussed above).

  • On a Unix-like system, a reasonable place to put hugo is /usr/local/bin (because often this directory exists and is on your path).

  • On Windows, a reasonable place to put hugo.exe is C:\Windows (because usually this directory exists and is on your path).

Note that putting a file in either /usr/local/bin or C:\Windows usually requires admin privileges.


Install with a package manager

The guide at describes how to use a lot of Linux, Mac, and Windows package managers.


My Windows choice: Scoop

On Windows I use this sequence of commands to install extended Hugo:

scoop update
scoop install hugo-extended

And this sequence of commands to update extended Hugo:

scoop update
scoop update hugo-extended

To find out what version of Hugo is currently installed by Scoop, see​blob/master/bucket/hugo-extended.json or this Repology badge: Scoop Hugo package



My Linux choices

To learn about Linux package management in general, see Infinite Ink’s Linux Package Management.


Snap Store Desktop App

On Linux with a desktop environment, I use the Snap Store Desktop App because…

  1. it has a graphical user interface,

  2. it usually installs a recent version of Hugo, and

  3. it’s easy to specify an extended channel because there is a drop-⁠down menu in the upper right of the app window labeled Source that lets you choose extended/stable or, if available, extended/edge.

Details about what Hugo version the Snap Store is currently installing are at and in the following embedded card.


Starting 2021-October-25, the Hugo team has the option to have the Snap Store install Hugo with classic (rather than strict) confinement. Details about this are in the discussion about Request for classic confinement for hugo snap on To find out the current confinement level, see​blob/master/snap/snapcraft.yaml.


Homebrew on Linux

If you have Homebrew on Linux installed, the following command installs a recent version of extended Hugo.

brew install hugo

As of 2022-May-4, this installs the newest extended Hugo (v0.98.0).



The brew install hugo command in the previous section also works on macOS.


Installation tips


3. Check your hugo with the hugo version command

After you install hugo, check that it’s on your path and is an extended version, by running this at a command-line prompt:

hugo version

You should see something like this:

hugo v0.99.0-1de333e7a3fc863672ec6d6cd53ba66dbcdd2305+extended windows/amd64 BuildDate=2022-05-16T08:10:56Z VendorInfo=gohugoio


4. Locate hugo

To find out which directory the hugo executable is in, run one of the following shell commands.

  • In a Unix-like shell, run:

    • which hugo

  • In PowerShell, run:

  • In cmd.exe or Git Bash, run:

    • where hugo


5. Possible next steps

After you’ve installed extended Hugo, you might want to follow the steps in one or both of these Infinite Ink articles:



Packaging status


As you can see in the above badge, most package managers do not install the newest version of Hugo. This is the main reason I wrote this article.



1. Many Infinite Ink articles, including this one, are evergreen and regularly updated.
2. If you use Hugo modules, you need to install go. If you use a non-⁠built-⁠in renderer, such as asciidoctor or pandoc, you need to install that renderer and edit Hugo’s security configuration.
3. cmd.exe is also known as CMD and is pronounced “cee em dee.” It is sometimes referred to as the “Command Prompt” (which is a completely ambiguous name IMHO). Details are at Wikipedia’s cmd.exe.
4. On a Debian-based system, the command sudo dpkg -⁠-⁠install ./hugo_extended_0.99.0_Linux-64bit.deb will work if you invoke it from the directory that the .deb is in. Since hugo has no dependencies, there should be no issues installing it with dpkg -⁠-⁠install. (This is how I install hugo on WSL, which is also known as “Windows’ Subsystem for Linux” and “Bash on Ubuntu on Windows.”)
5. On most GUI systems, double clicking the downloaded .zip or .tar.gz will launch an unzip app. For example, some Linux distributions launch the ark archiving tool.
6. “Binary” is another word for executable.

Comments and questions 📝 🤔 👎 👍

Your public comment or question might immediately improve this page or help me to (eventually) improve this page.