#trash #bin #recycle #remove #freedesktop #filesystem

app trashy

trashy is a simple, fast, and featureful alternative to rm and trash-cli

6 releases (stable)

2.0.0 Sep 30, 2022
1.0.3 Aug 23, 2022
1.0.2 Aug 18, 2022
1.0.1 Aug 8, 2022
0.1.0 Oct 14, 2020

#1650 in Command line utilities

42 downloads per month


996 lines


Build Status

trashy is a simple, fast, and featureful alternative to rm and trash-cli written in rust.

Quick links:




  • easy to use, just run trash PATH
  • recursive by default, without having the issues
  • beautiful output
    • colorized paths (similar to fd)
    • cool tables
  • very fast, and faster than trash-cli (see benchmarks)
  • much safer than rm -rf
  • intuitive syntax and fine grained control
  • uses the system trash on both linux and windows


Trash a path

$ trash first second third

This is just sugar for

$ trash put first second third

List items in the trash

$ trash list

Restore or empty some files

$ trash restore first second
$ trash empty first second third

The restore and empty subcommands both take very similar arguments and flags.

By default the arguments for restore and empty are interpreted as regular expressions. Use the -m option to interpret them differently.

Restore or empty all files

$ trash restore --all
$ trash empty --all



Restore with fzf

trash list | fzf --multi | awk '{$1=$1;print}' | rev | cut -d ' ' -f1 | rev | xargs trash restore --match=exact --force

Empty with fzf

trash list | fzf --multi | awk '{$1=$1;print}' | rev | cut -d ' ' -f1 | rev | xargs trash empty --match=exact --force


Using cargo

cargo install trashy

From Github Releases

Download the binary from Github Releases and put it in your $PATH.

From the AUR

Use your favorite AUR helper.

paru -S trashy

Using Nix

niv-env -i trashy

Or if you have flakes enabled:

nix profile install nixpkgs#trashy


These benchmarks are run on the rust compiler source in the compiler/ directory. The directory has about 2000 files. The benchmarks are run using hyperfine.

Running put on each file in the compiler/ directory recursively.

hyperfine -M 1 'fd -t f --threads 1 -x trash-put'
Time (abs ≡):        65.849 s               [User: 54.383 s, System: 11.370 s]

Now with trashy

hyperfine -M 1 'fd -t f --threads 1 -x trash put'
Time (abs ≡):         4.822 s               [User: 2.014 s, System: 2.918 s]

trashy has practically zero startup time, while trash-cli has a large startup time because it is written in python. This difference in startup time causes massive speed differences when used in scripts. The benchmark shows that trashy is about 13 times faster!

Listing the previously trashed items

hyperfine 'trash-list'
Time (mean ± σ):     383.7 ms ±  10.5 ms    [User: 321.8 ms, System: 59.4 ms]
Range (min … max):   375.9 ms … 412.0 ms    10 runs
hyperfine 'trash list'
Time (mean ± σ):     178.3 ms ±   1.9 ms    [User: 135.7 ms, System: 40.4 ms]
Range (min … max):   175.6 ms … 181.0 ms    16 runs

trashy is faster by more than 2 times.


Is this supported on MacOS?

No, see this issue

Should I alias rm='trash put'?

You should not. The alias will not be present on other systems and habits are really hard to break. An alternative is to alias trash put to rt or tp.


Copyright (c) 2020 Brian Shu

trashy is distributed under the terms of both the MIT license and the Apache License 2.0.



~732K SLoC