Frequently Asked Questions
Q: Why do I see permissions denied errors on Linux?
A: If you are trying to clean the system (for example, localizations, APT, or DNF), run BleachBit with root permissions. To elevate permissions, choose the menu option “BleachBit as Administrator” or run sudo on the command line.
Alternatively, when running as a normal user, uncheck options that require root permissions.
Q: Why do I see permission denied errors on Windows?
This happens when cleaning certain files, such as Windows system logs under
A: When you first launch BleachBit it should prompt you with the User Access Control dialog, which asks, “Do you want to allow the following program to make changes to this computer.” Answer Yes to grant BleachBit the privileges to modify all files.
Q: On Linux do I need to run BleachBit both as a normal user and as an administrator?
A: It depends how your system elevates privileges. Linux has various tools (for example, kdesudo, gksudo sudo, su-to-root, and PolicyKit) with various options to elevate to root (administrator) privileges, and they create two different situations.
In the first case, they switch the user to the root account, so BleachBit cleans the root account and not the non-privileged account. For example, BleachBit will clean root’s web browsers, which are probably never used, so it may seem BleachBit is not finding the files you expect. In this case, use the Bleachbit as Administrator option to clean any system files that require special privileges, and then use regular BleachBit to clean files in your personal profile.
In the second case, BleachBit runs with elevated privileges in the context of the non-privileged account, so all options can cleaned from one session.
To check which case applies to you, start BleachBit as Administrator, click on Help - System Information, and look at the value for
os.path.expanduser('~'). If it equals
/root, then the first case is happening, so run BleachBit both as administrator and as a regular user to clean all files.
Another way to check is first to run BleachBit as administrator. Then run BleachBit as a regular user, and if the preview shows any files, then you may need to run BleachBit as a regular user.
Q: How do I recover a file deleted by BleachBit?
The success of recovery depends on whether the file was overwritten, and the ease of recovery depends on whether the metadata was overwritten. If in the preferences the option “Overwrite files to prevent recovery” was enabled, the file probably cannot be deleted. There is an exception if the file system is ext3 or ext4 in
data=journal mode. The default file system on Ubuntu is ext4 with
data=ordered mode, which makes recovery unlikely.
If the wipe free space command was used on the same file system, the file probably cannot be deleted regardless of the type of file system. See also Shred files and wipe disks for more information.
The chances of recovery decline as data is written to the drive and as time passes.
Immediately the file is deleted in a normal way (in other words, if it is not overwritten), the full contents still exist and full recovery is stil possible. To maximize the chance of recovery, avoid writing any data to the file system. This step is most important when there is little free space. Often the file system for which recovery is desired is also the primary file system, so the computer should be turned off and rebooted into a bootable operating system from a bootable CD or USB drive.
Finally, run a file recovery tool. Do a search on the web for “undelete” or “file recovery.”
Q: Why does BleachBit take a long time (more than five minutes) while filling up by hard drive?
A: You enabled the option to System - Free disk space to wipe free disk space for privacy. This works basically by creating a large, empty file (see Shred files and wipe disks for more information). When the hard drive is full, the file will be deleted immediately, and there will be no net change in disk space (you will be back where you started). It is generally recommended you disable this option.
If this option is disabled, and BleachBit is slow, look at the option Edit - Preferences - General - Overwrite Contents. Enabling this option makes BleachBit slower because more work is required to make files unrecoverable.
Q: I closed BleachBit while it was working for a long time, and now my hard drive is full. How do I fix it?
A: Run BleachBit, and clean the option System - Temporary Files. On Linux, also clean System - Cache. This will delete one or more files that are gigantic and have random filenames.
If you changed the default options under Preferences - Drives, look there for the large files.
These instructions are valid since BleachBit version 1.2 released in 2014.
Q: How many passes does BleachBit make for the overwrite file option (shredding file)?
A: See Shred files and wipe disks.
Q: How do I see BleachBit in my own language on Microsoft Windows?
A: There are a few ways to affect the language of the BleachBit user interface.
In the Windows search bar, type “Language settings” and open it. Under the Windows display language, choose the preferred language, and then restart BleachBit.
To force BleachBit to always show in English, download and install the English installer instead of the regular installer. If using the regular (non-English-only) installer, uncheck the option to install translations.
The language chosen in the BleachBit installer does not affect the BleachBit application: it affects only the language of the installer.
Things to know
While these may not be asked, they are not common knowledge:
Q: What is format for the versioning number system?
A: Since BleachBit version 1.0 the numbering system is like that of GNOME, Linux between 1.0 and 2.6, and other projects: the format is basically a.b. When b is odd like 1.1, it is an unstable release (alpha or beta), and when b is even like 1.2, it is a stable release. Also, b can be greater than 9, so version 1.10 is newer than version 1.8.
Q: Should I delete cache?
A: Cache generally improves the performance of your computer. For example, browser cache prevents many files (such as pieces of web pages) from being downloaded again. Getting the file from the cache is much faster than downloading it—even with fast bandwidth. Applications (such as web browsers) normally delete the useless parts of cache to prevent it from growing too large and to make room for new, potentially-useful data.
Yet, cache contains content you have viewed and can be used to reconstruct some of your browsing history. Especially for applications that you deleted, some cache is never used, so the space is wasted. Finally, deleting a large cache saves time and storage space before making a backup.
Q: Should I delete cookies?
A: Cookies are not inherently evil or dangerous. The following statements are false:
- Cookies have no uses besides advertising
- Cookies can infect a computer like a virus
- Cookies cause popup ads
- Cookies can read arbitrary information from your computer (such as your name, your credit card, or private documents)
On the other hand, some web sites use tricks (e.g., “evercookie” technology) to resurrect deleted cookies and try to track users between browsers on the same computer. Using another trick, cookies can track visitors between web sites for behavioural ad targeting: for example, once you visited an online camping store, and suddenly every other web site shows you ads for that camping store.
Q: Is BleachBit “safe”?
A: BleachBit identifies and organizes the files you are most likely want to delete. For a few options which are most likely to cause you regret, it shows a popup warning. In that sense, BleachBit is much safer for a novice computer user than poking through the random directories hunting for files to delete. On the other hand, if the saying “One man’s trash is another man’s treasure” were not true or the saying “one size fits all” applied here, BleachBit would have no options. Carefully read the descriptions and warnings, and do not choose any options you do not understand or which make you uncomfortable.
Q: Will BleachBit make my computer faster?
A: BleachBit probably will not make your computer faster in general, but there are two specific ways you may see your computer become faster. First, by removing excess files, you may see an improvement in the speed of virus scanning and for disk backups. Second, vacuuming SQLite databases speed up applications that use them. Firefox, Safari, and Google Chrome are some applications that stores various data, such as URL history, in an SQLite database. With heavy browsing, the databases become fragmented and bloated, and this happens at a level higher than the disk storage, so standard disk defragmentation tools are completely useless. BleachBit shrinks the SQLite database (saving disk space and disk I/O effort) and defragments them. You are most likely to see a dramatic benefit by not vacuuming for a while, using the application heavily, and then vacuuming it once, but to keep the application running quickly, vacuum often. Vacuuming is not a single solution to all performance problems, but it does complement other solutions. People buy faster computers with better CPUs and more RAM, but hard drive technology (other than the rare SSDs) has not become much faster than they were years ago. The hard disk is often the bottleneck, and vacuuming is one way to overcome this limitation.
Yet, deleting cache may make your computer slower because data will have to be re-downloaded or re-generated.