Adventurer, choose your path! No, really it’s quite easy. Often. Do you want to..

a. download a binary/system package

hledger binaries or system packages are quickest to install, but they can be out of date or incomplete. (Please help your local packagers with this!).

Windows: 1.9.1 or latest nightly dev build (no hledger-ui, don’t work on old windows ?)
Mac: brew install hledger (only hledger CLI)
Arch Linux: pacman -S hledger
Debian, Ubuntu: sudo apt install hledger hledger-ui hledger-web
Fedora, RHEL: sudo dnf install hledger
Gentoo: sudo layman -a haskell && sudo emerge hledger hledger-ui hledger-web
Void Linux: xbps-install -S hledger hledger-ui hledger-web hledger-api
NixOS: nix-env -iA nixpkgs.haskellPackages.hledger nixpkgs.haskellPackages.hledger-ui nixpkgs.haskellPackages.hledger-web (problems with hledger-ui on MacOS ?)
Sandstorm: hledger-web Sandstorm app -> demo - a hledger-web server in 3 clicks (features needed)

b. build the latest release

Good choice! You’ll get the latest features mentioned in the release notes. Below are three ways to build the latest release, in order of preference.

Note, building all hledger tools for the first time could take as much as an hour, 1G of free memory, and 1G of disk space. (We’re not bloated; we just sit atop a lot of fine Haskell engineering!) You can kill and restart it without losing progress, and subsequent builds will be much faster. Also, here are some known build issues and workarounds:
arch: advice from Arch wiki
arch: No information found for ghc-8.4.2
freebsd 12: no cabal file found
openbsd 6: exec permission denied
openbsd: how to get stack

b1. with hledger-install

Our hledger-install script is recommended as the easiest and most-likely-to-just-work build method, on GNU/linux, mac and freeBSD (and possibly other BSDs if you install cabal-install first, or on unixlike environments on windows):

Here’s the quick, non-secure way to run it:

curl | bash

And here’s the more responsible way:

curl -O
less # do security review

If you see link errors (like “/bin/ error: cannot find -ltinfo”), you might need to install some extra system packages, such as the below, and try again (please send any updates for this list):

Centos: sudo yum install -y libstdc++-devel ncurses-devel zlib-devel # ?
Debian, Ubuntu: sudo apt install -y libncurses5 # ?
Fedora, RHEL: sudo dnf install -y ncurses-devel # ?

Set up $PATH

You should extend your $PATH with ~/.local/bin (for stack) and/or ~/.cabal/bin (for cabal). Eg, if you use bash:

echo "export PATH=~/.local/bin:~/.cabal/bin:$PATH" >> ~/.bashrc && source ~/.bashrc


Now you should be able to run the hledger tools and see the expected versions. Eg:

$ hledger --version
        hledger 1.9
        $ hledger-ui --version
        hledger-ui 1.9
        $ hledger web --version
        hledger-web 1.9
        $ hledger iadd --version
        This is hledger-iadd version 1.3.2

Need help ?

If you are having trouble, please capture a debug log and send it to me via paste & IRC, the issue tracker, or email:

bash -x 2>&1 | tee hledger-install.log

b2. with stack

stack is the newer and easier of the Haskell build tools. If you prefer more control or if hledger-install failed, here’s how to use stack yourself:

  1. Install or upgrade to the latest stack
    The latest version of stack (1.7) is recommended, for best avoidance of ecosystem breakages. If you can get at least stack 1.3 installed, eg from your system packages, you can usually run stack upgrade to quickly upgrade it to the latest.

    On Windows, the 64-bit version of stack is preferred.

  2. stack install --resolver=lts hledger-lib-1.9 hledger-1.9 [hledger-ui-1.9] [hledger-web-1.9.1] [hledger-api-1.9]
    This installs the specified hledger packages (and dependencies) from Stackage and/or Hackage. The bracketed packages are optional; if you include them, don’t type the brackets, and do always include the preceding hledger-lib and hledger packages.
    (windows: hledger-ui is not available)

    The command above uses stackage’s nightly snapshot. You might be able to reduce build time by specifying an older snapshot that you’ve used before (eg: --resolver=lts-10.8), or by omitting the –resolver option. To estimate the build time, add --dry-run. You can kill and restart this without losing progress.

    If you see “was generated with a newer version of hpack, please upgrade and try again” errors, you can ignore them. (Upgrade to the latest stack release to stop them.)

  1. If you see link errors..

  2. Set up $PATH

  3. Install addons ?
    Additional add-on commands, such as hledger-diff, hledger-iadd, hledger-interest, and hledger-irr can be installed similarly to the above. Eg:

    stack install --resolver=lts hledger-lib-1.9 hledger-1.9 hledger-iadd-1.3.2

  4. Test

b3. with cabal

cabal is the other Haskell build tool. If you’re a cabal expert, feel free to use this in the usual way.

c. build the development version

Also a good choice. Our master branch is stable enough for daily use, and includes the latest improvements.

  1. Install git and stack
  2. git clone
  3. cd hledger
  4. stack install [hledger] # build all (or, just the command line UI)
  5. If you see link errors..
  6. Set up $PATH
  7. Test (Development versions will have a .99 suffix, 1.9.99 means 2.0-dev)

cabal users may find the or cabal.project files useful.