You can store and manage Bambdas in the Extensions > Bambda library tab. This enables you to organize your Bambdas for easy reuse across your Burp projects. To add Bambdas to the library either create and save your own or import them from the 2025.2-early-adopter branch of our GitHub repository.
Bambdas are listed in a table containing the following information:
Name - The name of the Bambda.
Function - The task that the Bambda is designed to perform. For example, View filter or Custom column.
Location - The tool in Burp that the Bambda is intended to be used in. For example, HTTP history or Logger.
Last modified - The time and date that the Bambda was most recently saved to the library.
You can filter the table contents as follows:
Search the table - Click Search and enter an expression.
Filter the table - Click the Filter settings bar to open the Bambda library filter window. You can filter by Function and Location.
You can import Bambda files that have been shared with you or downloaded from the 2025.2-early-adopter branch of our Bambdas GitHub repository. For information on how to do this and how to keep your imported Bambdas up-to-date, see Importing Bambdas into your Bambda library.
If you're importing Bambdas from our Bambdas GitHub repo, use the 2025.2-early-adopter branch. All Bambdas on this branch have unique IDs, allowing Burp to recognize and update them when re-imported in the future. If you import Bambdas from the main library instead, they won't have these IDs, meaning Burp won't recognize them as the same Bambdas when the GitHub main branch is updated with the next release.
For more information about the role of the unique ID when re-importing Bambdas, see Updating your Bambdas.
Bambdas can run arbitrary code. For security reasons, please be cautious when using Bambdas from unverified sources.
You can create Bambdas directly from the Bambda library. For more information, see Creating Bambdas.
To share Bambdas with others, select Bambdas, then click . They're exported as .bambda files.
Each file includes a unique ID, name, function, and location as metadata. Burp uses the unique ID to recognize and match Bambdas. It is important to preserve the unique ID when sharing your Bambda, as this ensures consistency and prevents conflicts if the Bambda is reimported.
You can perform the following actions on the Bambdas in your library:
Edit - Select the Bambda that you want to edit, then click .
Copy - Select the Bambdas that you want to copy, then click .
Delete - Select the Bambdas that you want to delete, then click .