Installation and licensing

Load the extension, activate your license and connect the data pack.

Use Burp Suite Professional for the complete scanning and persistent-project workflow. Load the extension with the Java runtime used by Burp; you do not need to install a separate native JNA library for the current packaged JAR.

Install the extension

1. Download the Burp Bounty Pro release JAR and its data pack from your distribution channel.

2. In Burp, open Extensions → Installed → Add.

3. Select Java, choose the supplied JAR and finish loading it. Development builds are named BurpBountyPro-1.0-jar-with-dependencies.jar.

4. Confirm that the Burp Bounty Pro tab appears and inspect extension errors if loading fails.

5. Open the License tab, enter your key and activate it. Check the status and expiration date.

Adding a Java extension in Burp Suite

Configure the data pack

Extract the pack while preserving its layout:

BurpBountyData/
  profiles/
    example.bb
  rules/
    rule_example.bb

Choose the pack root

In Settings → General, use Directory to select the base BurpBountyData directory, then Reload. Pro locates its profiles and rules subdirectories. This differs from Server's --profiles-dir, which points directly to BurpBountyData/profiles.

Check the three profile tables and the Rules table. The catalogue is supplied as files; it is not a catalogue to extract from the extension JAR. Counts vary by pack and by enabled state; see the reviewed pack inventory.

If you previously used BurpBountyData_3.0, select the renamed directory explicitly. A saved path does not follow a filesystem rename automatically.

Updating and rollback

Keep the previous JAR, a copy of your data directory and any custom profiles/rules before replacing a release. Use the update controls in About to check available packages. Treat data-pack updates as file changes: compare your customizations before replacing them.

Unload the old extension and load the intended new JAR. Check the complete path in Burp's Installed extensions table; a similarly named JAR on the Desktop may be an older build. Avoid keeping duplicate versions loaded.

Apple Silicon and license errors

The packaged build includes the JNA native support used by licensing and initializes it for Burp's class-loading environment. If Unable to locate JNA native support library appears, first verify the JAR path and reload the current complete build. Preserve the full extension error for diagnosis; repeatedly activating a license will not repair a missing native library.

A license activation problem and a native-library loading problem are different failures. For server startup and header authentication, use the Server licensing guide.