Windows Guide
Profiles (Windows)
Save, switch, export, import, rename and delete ProxyBridge profiles on Windows. What a profile contains, where the files live, and the .pbprofile format you can share between Windows, macOS and Linux.
Profiles on Windows
A profile is a saved setup: your proxy servers, your rules, your log filters and your settings. Profiles let you keep different configurations side by side, for example one for web application testing, one for a client project and one for everyday use, and switch between them in a click.
The window title always shows the active profile: ProxyBridge - Default.
What a profile contains
| Saved in the profile | |
|---|---|
| Proxy servers | Including their authentication details |
| Rules | Applications, hosts, ports, protocol, action, localhost option, on/off state, name |
| Log filters | The Include and Exclude filters for the Connections log |
| Settings | Enable Traffic Logging, Close to Tray, Auto Clear Logs, Log Every Connection, language, text size |
Some things belong to the app, not the profile: which profile is active, whether to check for updates, and Run at Startup (see Settings, tray and pausing). The Enable ProxyBridge switch is never saved; ProxyBridge always starts enabled.
The Profile menu
| Menu item | What it does |
|---|---|
| New Profile... | Asks for a name and creates an empty profile, then switches to it |
| Rename Profile | Renames the active profile. The Default profile cannot be renamed |
| Delete Current Profile | Deletes the active profile and switches to Default. The Default profile cannot be deleted |
| Import Profile... | Loads a .pbprofile file as a new profile and switches to it |
| Export Profile... | Saves the active profile to a .pbprofile file |
| Switch Profile | Lists your profiles. The active one is ticked. Choose another to switch |
Profile names cannot contain < > : " / \ | ? *. Those characters are replaced with _.
Switching
Switching applies the new profile at once: the previous profile's proxies and rules are removed from the engine and the new profile's are loaded. Connections that were already open keep their route until they close.
Everything is saved automatically
Changes to proxies, rules, filters and settings are written to the active profile as soon as you make them. There is no Save button.
Export and import
Use Export Profile... to back up a setup, move it to another PC, or hand it to a colleague. Use Import Profile... on the other side.
- Importing creates a new profile named after the file (
work.pbprofilebecomeswork). It never overwrites an existing one: if the name is taken,(2),(3)and so on is added. ProxyBridge then switches to it. - The
.pbprofilefile is plain JSON. You can edit it in a text editor, keep it in version control and use it with the command line. - The format is shared with ProxyBridge on macOS and Linux. A profile exported on one system can be imported on another.
Passwords are stored in the file in clear text. Before you share an exported profile, remove the
UsernameandPasswordvalues of the proxy servers, or make sure the proxy account is one you can discard.
Where the files are
| What | Where |
|---|---|
| Profiles | %APPDATA%\ProxyBridge\profiles\<name>.pbprofile |
| App settings (active profile, update check) | %APPDATA%\ProxyBridge\settings.json |
%APPDATA% is the Roaming folder of your Windows account, usually C:\Users\<you>\AppData\Roaming. Each Windows account has its own set. To back up everything, copy the ProxyBridge folder.
The .pbprofile format
{
"Version": "1.0",
"Name": "work",
"IsTrafficLoggingEnabled": true,
"AutoClearConnectionLogs": true,
"LogEveryConnection": false,
"Language": "en",
"CloseToTray": false,
"FontZoom": 100,
"NextProxyConfigId": 3,
"ProxyConfigs": [
{
"Id": 1,
"Name": "Burp",
"Type": "HTTP",
"Host": "127.0.0.1",
"Port": "8080",
"Username": "",
"Password": "",
"SendDomainToProxy": true
},
{
"Id": 2,
"Name": "Office SOCKS",
"Type": "SOCKS5",
"Host": "proxy.example.com",
"Port": "1080",
"Username": "alice",
"Password": "secret",
"SendDomainToProxy": true
}
],
"ProxyRules": [
{
"Name": "Browser to Burp",
"ProcessName": "chrome.exe; msedge.exe",
"TargetHosts": "*",
"TargetPorts": "*",
"TargetDomains": "*",
"Protocol": "TCP",
"Action": "PROXY",
"IsEnabled": true,
"LocalhostViaProxy": false,
"ProxyConfigId": 1
},
{
"Name": "Company network",
"ProcessName": "*",
"TargetHosts": "10.*.*.*",
"TargetPorts": "*",
"TargetDomains": "*.corp.example.com",
"Protocol": "BOTH",
"Action": "PROXY",
"IsEnabled": true,
"LocalhostViaProxy": false,
"ProxyConfigId": 2
}
],
"LogFilters": [
{
"Mode": "Exclude",
"ProcessName": "svchost.exe",
"Ip": "",
"Port": "",
"Protocol": "All",
"Action": "All"
}
]
}
| Field | Meaning |
|---|---|
ProxyConfigs[].Id |
A number that stays with the proxy. Rules refer to it |
ProxyConfigs[].Type |
SOCKS5 or HTTP |
ProxyConfigs[].SendDomainToProxy |
The Let proxy resolve DNS option |
ProxyRules[].ProcessName |
The Applications field |
ProxyRules[].TargetHosts and TargetDomains |
The single Target Hosts box is saved as two lists: IP entries in TargetHosts and domain names in TargetDomains. The other platforms read them the same way. Windows merges them back into one box |
ProxyRules[].Action |
PROXY, DIRECT or BLOCK |
ProxyRules[].ProxyConfigId |
Which proxy a PROXY rule uses |
ProxyRules[].LocalhostViaProxy |
The Also proxy localhost traffic checkbox of that rule |
LogFilters[].Mode |
Include or Exclude |
Older profiles that have a single, global LocalhostViaProxy at the top level are still read: that value becomes the default for rules that do not have their own setting.
Ideas for using profiles
- One profile per proxy tool:
burp,mitmproxy,interceptsuite. Switch tools without re-entering rules. - A clean "no proxy" profile: switch to an empty profile to stop all routing, while keeping your real setup untouched.
- Per-project profiles for pentest engagements, stored with the project's notes.
- Shared team profile: export it, review it, commit it, and have everyone import the same rules.
