#cross-platform #cli #hash #checksum

app dircs

A small cross-platform utility to get a hash of a file or directory

9 releases

0.1.7 Jun 22, 2023
0.1.6 Jun 7, 2023
0.1.4 May 31, 2023

#268 in Command line utilities

Download history 190/week @ 2023-05-28 70/week @ 2023-06-04 13/week @ 2023-06-11 31/week @ 2023-06-18 14/week @ 2023-06-25 15/week @ 2023-07-02 3/week @ 2023-07-16 16/week @ 2023-07-23 1/week @ 2023-07-30 19/week @ 2023-08-06 10/week @ 2023-08-13 1/week @ 2023-08-20 10/week @ 2023-08-27 30/week @ 2023-09-03

52 downloads per month


365 lines


crates.io link

A small cross-platform utility to get a hash of a file or directory. Comes with a variety of hash functions to choose from.

Note: I mostly wrote this for personal use, and there might be a lot of rough edges! Feel free to submit pull requests or bug reports.


dircs is on crates.io and is installable using cargo:

cargo install dircs --locked

As of writing, dircs is built using Rust 1.69.0.


$ dircs /your/path/here
/your/path/here -> 72ce3b5f2df28051cf7204712fe93de6b7b6d1f8e8fe5972b117a248423c290c

By default, dircs will use BLAKE3 with memmapping disabled, and an automatically chosen level of parallelism.

See more options by running dircs -h.

Supported hash functions

Currently, the following hash functions are supported:

  • BLAKE3
  • MD5
  • SHA1
  • SHA2 (digest sizes of 256, 384, 512)
  • SHA3 (digest sizes of 256, 384, 512)

How does this create hashes?

For a single file or a directory with just one file, dircs will simply hash the file using the given hashing function of choice, and output the bytes as a hex string.

For a directory with multiple files, it's a bit more involved, but also pretty simple/naive:

  1. For every single file, generate a hash using the chosen hashing function. This occurs in parallel if possible.
  2. With this generated list of hashes, sort them based on file name.
  3. Feed each hash in this order into the chosen hash function to generate one final hash, which is then output as a hex string.


Thanks to:

  • All library authors whose libraries I used.
  • The authors of b3sum, which I referenced a lot.


~118K SLoC