Thank you for considering helping to translate BleachBit into your native language! It's hard work, but the web-based interface makes it easier.


  • You must read English well.
  • You must write well in your native language.
  • You need to translate about 2200 English words (as of May 2021). If someone has started translating this language, there will be less work. There is no commitment: it is OK to translate some strings but not others.

As of January 2015, being a member of a translation team is not required, and translations no longer require review for those who are not members.

February 2022: Translation platform moved from Launchpad to Weblate.


Please do not submit translations to GitHub as a pull request. Instead, follow this procedure:

See the BleachBit page on Weblate. Create an account and follow the instructions there.

Verifying translations

There are several ways to verify your translation. (If you are confident in your work, you may skip these steps.)

  • Use the spell checker in your web browser as you type new translations.
  • Download your translation and use your office application. In Weblate, open the language, click files tab, click customize downloads, and choose CSV or XLSX. Proof read in the spreadsheet, or copy and paste into word processor. Make any edits in Weblate.
  • Download the translation and load it in to BleachBit to see the translations in context.
    1. Go to the list of languages.
    2. Click on the language.
    3. Click Files tab and Customize Download.
    4. Choose gettext mo.
    5. Rename the file to your your locale code (Spanish is, for example).
    6. Move this file to /usr/share/locale/(your locale code)/LC_MESSAGES/ (Linux) or c:\Program Files\BleachBit\share\locale\(your locale code)\LC_MESSAGES (Windows).
    7. Start (or restart) BleachBit.
  • If you already have an updated .po file on your computer, use a .po to .mo file converter, and then follow the procedure above.
  • Shortly after commiting translations to Weblate, the AppVeyor CI system will rebuild the whole application and provide a Windows build at the BleachBit CI site. Use the installer or portable version to test your translations.

Understanding context

If you are not clear on how to translate a string, you have several options:

  • Download and run BleachBit to understand the context. Use the latest stable or CI build.
  • Look for hints. Hints in the source code are copied to the .pot, and Launchpad automatically displayed them like what follows. Launchpad is no longer used. Does Weblate show the hints too? Launchpad showing translation tip for the word 'vacuum'
  • If you have any programming skills, cross reference the source code. To find the right file, open the string in Weblate, and look on the right sidebar for "source code location."
  • Ask in the forum or open a GitHub issue. Ask to add a hint to the source code (which displayed in Launchpad, maybe in Weblate too), modify the English string, provide a screenshot, or record a video of the application. Weblate can attach screenshots to strings.


Translations must be licensed under the GNU GPL v3+, the BSD license (without the advertising clause), or both.


BleachBit is under active development, so please check back occasionally for new strings to translate. Some options are:

  • Watch on Weblate
  • Subscribe to RSS feeds from Weblate
  • Follow BleachBit on Facebook or Twitter for release announcements.
  • Watch for update notifications in the BleachBit app. Enable notifications for beta releases.