Skip to main content
Bearsampp stores its global settings in a file called bearsampp.conf, located in the root of your Bearsampp folder. You can edit this file directly in any text editor, or change the most common settings through the tray menu — Bearsampp updates the file automatically when you make a change from the UI.

​
Configuration file location

The configuration file is at:
Settings are stored in INI format as key = "value" pairs. When you change a setting from the tray menu (such as switching language or toggling online mode), Bearsampp writes the new value back to this file immediately.

​
Configuration options

The table below lists every key in bearsampp.conf, its type, and what it controls.

​
Logging verbosity levels

The logsVerbose key controls how much detail Bearsampp writes to its log files.
Use 2 (Debug) or 3 (Trace) temporarily when diagnosing a problem, then set it back to 0 or 1 to keep log files small.

​
Changing settings from the tray menu

Many settings are available directly from the tray menu without opening bearsampp.conf:

Language

Right-click the tray icon → Settings → Language to choose from the supported interface languages.

Launch on startup

Right-click the tray icon → Settings → Launch on Windows startup to toggle the launchStartup setting.

Online / Offline mode

Right-click the tray icon → Put Online or Put Offline to toggle the online setting.

Logs verbosity

Right-click the tray icon → Settings → Logs verbose to cycle through verbosity levels.
Every change you make through the tray menu is saved to bearsampp.conf automatically. You do not need to restart Bearsampp for most setting changes to take effect, but restarting ensures all components pick up the new values.

​
Editing the file directly

If you prefer to edit bearsampp.conf by hand, open it with any plain-text editor. Each line follows this format:
Save the file and restart Bearsampp to apply changes made outside the tray menu.
Do not change defaultLang unless you know what you are doing — it is the fallback language and removing a valid value can cause the UI to fail to load strings correctly.