Skip to content
Tutorials Center
My learning

Topics

Lesson 6 of 38 ยท Setup and Proxy

Installing Burp and the First Launch

Install Burp Suite Community on Windows, macOS or Linux, choose a project and configuration at startup, and tour the first screen before you test anything.

Burp Suite is a Java application packaged with its own runtime, so installation is closer to installing any desktop program than to setting up a server. This lesson walks through downloading it, the startup choices (temporary project, configuration), and what you see on the first screen. The screens below are described from the real application; this website cannot run Burp itself.

Always download Burp from PortSwigger's official site. Cracked or repackaged copies are a well-known way to get malware onto a security tester's machine, which is a particularly bad place for it to land.

What you need

  • A 64-bit computer running Windows, macOS (Intel or Apple silicon) or Linux.
  • Around 4 GB of free memory for comfortable work (more for big projects).
  • A web browser. Burp includes its own preconfigured Chromium-based browser, and you can also use Firefox or Chrome.
  • Administrator rights are only needed if you install system-wide.

Installing

  1. Open PortSwigger's download page and pick Burp Suite Community Edition (or Professional if you have a licence).
  2. Choose your operating system and download the installer.
  3. Run it. On Windows it is a standard installer; on macOS a disk image you drag to Applications; on Linux a shell script (make it executable with chmod +x, then run it).
  4. Start Burp Suite Community from the Start menu, Applications folder or terminal.

Your first launch may show a licence agreement and, in newer releases, an offer to share anonymous usage data. Read both, and decline optional data sharing if you prefer.

The startup dialogs

Choosing a project

Burp asks what kind of project to open:

Choice Meaning
Temporary project Kept in memory only; gone when you close Burp. The only option in Community.
New project on disk Saved to a file so you can resume later (Professional).
Open existing project Reload an earlier session (Professional).

A project stores everything: history, site map, scope, issues, Repeater tabs. That is why it must be handled as sensitive data, as the legal lesson explained.

Choosing a configuration

Next Burp asks which configuration to use:

  • Use Burp defaults: the sensible choice for beginners.
  • Use options saved with project: restores the project's own settings.
  • Load from configuration file: apply a JSON file you previously exported, useful for sharing team-wide settings (such as scope rules and match-and-replace rules).

Configurations are plain JSON. Treat them like code: keep them in version control, but never include secrets in them.

The first screen

When Burp opens you see a row of tabs. A newly started Community session looks like this (text mock-up, not a screenshot):

TEXT
Dashboard | Target | Proxy | Intruder | Repeater | Collaborator | Sequencer | Decoder | Comparer | Logger | Organizer | Extensions | Learn
-----------------------------------------------------------------------------------------------------------------------------------
Tasks:  (none running)               Event log:  Burp Suite Community Edition ready.
                                                  Proxy listening on 127.0.0.1:8080

Your tab list may differ by version and edition. Two things matter right now:

  1. Event log (Dashboard): messages from Burp itself. If something fails to start, such as the proxy listener, the reason appears here.
  2. Proxy listening on 127.0.0.1:8080: Burp's default listener. It means Burp accepts connections only from your own computer, on port 8080.

Settings you will use

Burp's configuration lives in one Settings window (opened from the Burp menu or with the gear icon). Settings split into User settings that follow you across projects (fonts, display, keyboard shortcuts) and Project settings that belong to one engagement (scope, proxy listeners, session handling). Useful first visits:

  • Tools > Proxy: listeners, intercept rules, match-and-replace.
  • Network > TLS: certificates and protocol options.
  • Display: dark mode and font size.
  • Suite > Updates: update behaviour; keep Burp current, as it receives security fixes of its own.

Memory and performance

Large applications create large histories. If Burp feels slow, increase the Java heap size with the launcher's -Xmx setting (for example -Xmx4g) and clear history you no longer need. Do not run Burp on a tiny virtual machine and expect a smooth session.

Try it: validate a proxy listener setting

A stand-in that models one real habit: checking a listener setting before use. It rejects listeners that would expose the proxy to your network, because a proxy open to everyone lets anyone on that network route traffic through your tool.

Python Stand-in: check a proxy listener binding

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Try it: a project settings file

Configurations are JSON. This stand-in loads a made-up configuration (the real Burp format is larger and differs by version), checks required keys and flags dangerous values.

Python Stand-in: load and lint a config file

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

A good first-launch checklist

  • Use a dedicated browser profile or Burp's built-in browser so proxy settings do not affect your normal browsing.
  • Keep the proxy on loopback.
  • Decide where you will store project files and who can read them.
  • Update Burp, then test the listener with the steps in the next lesson.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does a temporary project mean in Burp Community?

    Community supports temporary projects only. Saving and restoring projects is a Professional feature.
  2. 2. The default proxy listener is 127.0.0.1:8080. What does 127.0.0.1 imply?

    127.0.0.1 is the loopback address. Binding there keeps the proxy private to your machine.
  3. 3. Why should Burp be downloaded only from the official site?

    A security tester's computer holds sensitive client data, so a trojanised copy is especially damaging.
  4. 4. Where would you look first if the proxy listener failed to start?

    The Dashboard's event log reports Burp's own messages, including listener startup problems such as a port already in use.

Summary

  • Install Burp from the official source; Community is free and enough for manual learning.
  • Startup asks for a project (temporary in Community) and a configuration (defaults are fine at first).
  • The first screen shows the tool tabs, a task area and an event log; the proxy listens on 127.0.0.1:8080 by default.
  • Settings split into user-level and project-level; configurations are shareable JSON.
  • Keep the listener on loopback and protect project files.

Next: Browser proxy and the CA certificate