WindowsLinux

Where Does BleachBit Store Settings and Cleaners?

Where BleachBit keeps its bleachbit.ini preference file and custom cleaner definitions on each OS.

Last updated

BleachBit keeps preferences in bleachbit.ini: %APPDATA%\BleachBit on Windows, ~/.config/bleachbit on Linux. Custom CleanerML definitions live in a cleaners folder beside it.

The ini is small and safe to copy, which makes migration trivial and explains most lost preference reports after reinstalls into new folders. Winapp2.ini rules (Windows) extend the same folder. When the cleaner list looks wrong, the cleaners folder is guilty before the ini. The preview run lists hits before deleting, which belongs in every new cleaner test.

Where BleachBit stores this, by platform

Windows
%APPDATA%\BleachBit\bleachbit.ini

bleachbit.ini plus cleaners/ for custom XML and winapp2.ini for extended rules. The portable build relocates everything beside the exe. Close the app before copying; it writes on exit.

Linux
~/.config/bleachbit/bleachbit.ini

Same ini name under the XDG config home, with cleaners/ beside it. Honors $XDG_CONFIG_HOME when set. Root runs (bleachbit as admin) use root's config home, not yours.

Frequently asked questions

where is the bleachbit settings file

In bleachbit.ini (Windows: %APPDATA%\BleachBit\bleachbit.ini; Linux: ~/.config/bleachbit/bleachbit.ini). It holds language, window state, and enabled cleaners. Copy it with the app closed to migrate preferences. Deleting it resets to defaults.

where do custom bleachbit cleaners go

As CleanerML XML files in the cleaners/ folder beside the ini (plus system files you must not edit). Drop a custom XML there and it appears in the list. Share them between machines by copying the folder, not the whole profile.

can bleachbit run portable with its settings

Yes for preferences. The portable build keeps bleachbit.ini in a BleachBit folder beside the exe (or --portable mode). Installed and portable builds read different spots by default, so point them at one file deliberately.

Notice an outdated path? Let us know.