BleachBit 2.3 beta

Please test BleachBit 2.3 beta. This has major changes for the next final release, which will be 3.0.


For a list of changes see the commit log and GitHub bug tracker.


These tests are for both Windows and Linux.

  • Test the user GUI in general because of the major upgrade from GTK+ 2 to GTK 3.
  • Make chaff.
  • Click the stop button while BleachBit is working.
  • Restart BleachBit to verify it saves its window size, position, and whether it was full screen.
  • Use command line option --wipe-free-space to wipe the free space in a path.
  • In the preferences, toggle the "hide irrelevant cleaners." It should retrigger a re-scan only when closing the dialog, not when toggling.
  • In the preferences, try the new dark mode.
  • In the preferences, try the new option for debug logging.
  • Application startup should be much faster.
  • Scanning for files should be much faster. This might be most noticable in application startup, preview, deep scan, and when deleting many small files.
  • Mangle the bleachbit.ini configuration file and start BleachBit. It should notify you that the file was reset.
  • Test these cleaners with significant changes: aMule, FileZilla, Firefox, Flash, Internet Explorer, Midnight Commander, Opera, Silverlight, VIM, VLC, Vuze, Windows Defender, WinRAR.


  • Overwrite files on a network drive (issue 338).
  • Select many files to shred (issue 348).
  • Watch for encoding errors (issues 328, 451, 567, and others).
  • Clean symlinks in the recycle bin (issue 385).
  • Mark a file read-only, and then shred it.


  • Verify it does not delete the Bluetooth daemon directory (issue 572).
  • Test new distributions: Debian 10 and Ubuntu 19.04.


See the downloads folder for BleachBit 2.3 beta. For Linux, there are .deb and .rpm packages. For Windows, there is a digitally signed installer and portable package.

There have already been a few fixes since BleachBit 2.3 beta. Windows users can try CI builds.

After testing

If something is broken, please file a bug report. If it works well, please post a comment with what you tested in the testing forum or at the bottom of this page.

Blog tags: