Crate rfd

source ·
Expand description

Rusty File Dialogs is a cross platform library for using native file open/save dialogs. It provides both asynchronous and synchronous APIs. Supported platforms:

  • Windows
  • macOS
  • Linux & BSDs (GTK3 or XDG Desktop Portal)
  • WASM32 (async only)



use rfd::FileDialog;

let files = FileDialog::new()
    .add_filter("text", &["txt", "rs"])
    .add_filter("rust", &["rs", "toml"])


use rfd::AsyncFileDialog;

let future = async {
    let file = AsyncFileDialog::new()
        .add_filter("text", &["txt", "rs"])
        .add_filter("rust", &["rs", "toml"])

    let data = file.unwrap().read().await;

§Linux & BSD backends

On Linux & BSDs, two backends are available, one using the GTK3 Rust bindings and the other using the XDG Desktop Portal D-Bus API through ashpd & zbus.

§GTK backend

The GTK backend is used with the gtk3 Cargo feature which is enabled by default. The GTK3 backend requires the C library and development headers to be installed to build RFD. The package names on various distributions are:

DistributionInstallation Command
Fedoradnf install gtk3-devel
Archpacman -S gtk3
Debian & Ubuntuapt install libgtk-3-dev

§XDG Desktop Portal backend

The XDG Desktop Portal backend is used when the gtk3 feature is disabled with default-features = false, and xdg-portal is enabled instead. Either the tokio or async-std feature must be enabled. This backend will use either the GTK or KDE file dialog depending on the desktop environment in use at runtime. It does not have any non-Rust build dependencies, however it requires the user to have either the GTK, GNOME, or KDE XDG Desktop Portal backend installed at runtime. These are typically installed by the distribution together with the desktop environment. If you are packaging an application that uses RFD, ensure either one of these is installed with the package. The wlroots portal backend does not implement the D-Bus API that RFD requires (it does not interfere with the other portal implementations; they can all be installed simultaneously).

The XDG Desktop Portal has no API for message dialogs, so the MessageDialog and AsyncMessageDialog structs will not build with this backend.

§macOS non-windowed applications, async, and threading

macOS async dialogs require an NSApplication instance, so the dialog is only truly async when opened in windowed environment like winit or SDL2. Otherwise, it will fallback to sync dialog. It is also recommended to spawn dialogs on your main thread. RFD can run dialogs from any thread but it is only possible in a windowed app and it adds a little bit of overhead. So it is recommended to spawn on main and await in other thread. Non-windowed apps will never be able to spawn async dialogs or from threads other than the main thread.

§Customize button texts of message dialog in Windows

TaskDialogIndirect API is used for showing message dialog which can have customized button texts. It is only provided by ComCtl32.dll v6 but Windows use v5 by default. If you want to customize button texts or just need a modern dialog style (aka visual styles), you will need to:

  1. Enable cargo feature common-controls-v6.
  2. Add an application manifest to use ComCtl32.dll v5. See Windows Controls / Enabling Visual Styles

Here is an example using embed-resource.

§Cargo features

  • gtk3: Uses GTK for dialogs on Linux & BSDs; has no effect on Windows and macOS
  • xdg-portal: Uses XDG Desktop Portal instead of GTK on Linux & BSDs
  • common-controls-v6: Use TaskDialogIndirect API from ComCtl32.dll v6 for showing message dialog. This is necessary if you need to customize dialog button texts.


API Stability
Filters✔ (GTK only)


AKA features that are not file related

MessageDialog✔ (GTK only)