# Web radar (/docs/guides/web-radar)

Start the browser radar, connect another device, and diagnose server failures.

## Start a local radar [#start-a-local-radar]

1. Open **Radar** and turn on **Enable Radar**.
2. Keep **Bind Host** at `127.0.0.1`, **HTTP Port** at `36364`, and **WebSocket Port** at `36365`.
3. Click **Start Server**.
4. Confirm **Status: running**, then click **Open In Browser**.

The browser opens `http://127.0.0.1:36364/` with the default HTTP port. The HTTP server serves the page, and the WebSocket server sends live updates. Both ports must be available and distinct.

**Enable Radar** makes the feature available. It does not start the server by itself. Turn on **Start On Launch** for automatic startup and **Open Browser On Start** to open a browser when the server starts.

Click **Stop Server** to stop serving the radar. Turning off **Enable Radar** also stops it.

## Connect another device [#connect-another-device]

1. Set **Bind Host** to `0.0.0.0` to listen on the machine's network interfaces.
2. Start the server if it is stopped.
3. On the other device, open `http://<computer-lan-address>:36364/`, replacing the address and port as needed.
4. Allow connections to both configured ports through the host firewall if required.

Use the computer's LAN address in the browser, rather than `0.0.0.0`. **Open In Browser** always opens a loopback URL on the computer running the application. If you bind only to a specific LAN address, open that address manually.

Changing **Bind Host**, **HTTP Port**, or **WebSocket Port** while the server runs restarts it with those values. Reconnect using the new address if needed.

## Adjust the display and save [#adjust-the-display-and-save]

Use **Radar Appearance** to change dot sizes, player names, buy zones, projectiles, smokes, zoom, and height indicators. **Transparent Background** is in the **Web Radar** section.

Save the profile in **Config** to keep server settings, appearance, and startup preferences. See [Configuration](/docs/concepts/configuration).

## Diagnose a failed connection [#diagnose-a-failed-connection]

The **Web Radar** section shows the running URL, WebSocket port, viewers, frame count, and the last server error.

- If **Status: stopped** follows a start attempt, read the error below it. Choose unused ports if the server cannot bind or listen.
- If the error reports missing radar assets, restore `assets/radar/` beside the executable from the build assets.
- If the page opens but live data does not arrive, check the WebSocket port and the application's connection to CS2.
- If another device cannot open the page, check **Bind Host**, the computer's LAN address, and access to both ports.

After correcting a startup failure, click **Start Server** again. The radar continues receiving snapshots while CS2 is unfocused.