#fs #err #error


A drop-in replacement for std::fs with more helpful error messages

13 releases (stable)

2.6.0 May 6, 2021
2.5.0 Sep 27, 2020
2.3.0 Mar 17, 2020
2.0.1 Feb 22, 2020
0.1.2 Feb 10, 2020

#19 in Filesystem

Download history 27506/week @ 2021-08-14 28860/week @ 2021-08-21 31617/week @ 2021-08-28 27679/week @ 2021-09-04 36259/week @ 2021-09-11 31954/week @ 2021-09-18 31186/week @ 2021-09-25 31787/week @ 2021-10-02 35381/week @ 2021-10-09 34204/week @ 2021-10-16 33934/week @ 2021-10-23 30412/week @ 2021-10-30 30321/week @ 2021-11-06 30857/week @ 2021-11-13 30070/week @ 2021-11-20 25846/week @ 2021-11-27

122,246 downloads per month
Used in 50 crates (32 directly)


795 lines


Crates.io GitHub Actions

fs-err is a drop-in replacement for std::fs that provides more helpful messages on errors. Extra information includes which operations was attempted and any involved paths.

Error Messages

Using std::fs, if this code fails:

let file = File::open("does not exist.txt")?;

The error message that Rust gives you isn't very useful:

The system cannot find the file specified. (os error 2)

...but if we use fs-err instead, our error contains more actionable information:

failed to open file `does not exist.txt`
    caused by: The system cannot find the file specified. (os error 2)


fs-err's API is the same as std::fs, so migrating code to use it is easy.

// use std::fs;
use fs_err as fs;

let contents = fs::read_to_string("foo.txt")?;

println!("Read foo.txt: {}", contents);

fs-err uses std::io::Error for all errors. This helps fs-err compose well with traits from the standard library like std::io::Read and crates that use them like serde_json:

use fs_err::File;

let file = File::open("my-config.json")?;

// If an I/O error occurs inside serde_json, the error will include a file path
// as well as what operation was being performed.
let decoded: Vec<String> = serde_json::from_reader(file)?;

println!("Program config: {:?}", decoded);


Licensed under either of

at your option.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

No runtime deps