The new web UI
Added: after 2026-10-R1
A new UI, still changing
After 2026-10-R1, Kismet has a new web UI, served at / (for instance http://localhost:2501/). The previous UI is still available at /legacy/ (http://localhost:2501/legacy/), and the Legacy UI item in the new UI’s top bar opens it.
The new UI is evolving rapidly in the nightly (git) packages and in Kismet git: windows, settings, and features are added and changed from one nightly to the next, and the documentation here may lag behind what a nightly build shows. If something is missing or behaves differently than described, check that you’re running a recent nightly, and report problems as Kismet GitHub issues.
Plugins which add pages to the previous UI keep working in it from /legacy/; the new UI lists plugins which don’t have a page for it yet. Both UIs use the same login, and settings in one don’t change the other.
What’s in it
- Overview, Devices, SSIDs, Alerts, Map, and Insights tabs.
- Windows for data sources, channel coverage and the channel heat map, device rules, packet rates, memory, thermal, CPU, and GPS, from the menu and the top bar.
- The Messages panel along the bottom. Drag the bar above it to resize it, or minimize it to its tab bar with the
_button at its right; it stays minimized in every tab and after a reload, until you click the button again, click one of its tabs, or drag the bar. - A top bar of stats, including the CPU load of the system and of Kismet (after 2026-10-R1), and the temperatures of the system Kismet runs on. Choose the stats it shows under Settings, Ribbon; stats Kismet can’t read show
---. - The device list’s Search or filter box, which takes device filters as well as plain searches.
- A Tags column and row highlights from the server’s device rules, set under Settings, Device Highlights.
- Display units for speeds, lengths and temperatures, under Settings, Units.
- Names too long for their column are shortened, in the middle (
too l...ame) or at the end (too long n...), set under Settings, Appearance, Shorten long names; point at a name to see it in full (after 2026-10-R1). Censor mode censors shortened names too. - Wi-Fi device details with a Multiple BSSID section: for a network an access point hosts in its multiple BSSID element (after 2026-10-R1), the access point that advertises it and its index; for that access point, the networks it hosts. The Insights views show the hosted networks as part of their access point.
- Bluetooth and BTLE device details with service names, battery, distance, beacon, and connection sections, the advertised data decoded, and the address type, linked addresses, class of device, and controller version and features.
- Censor mode, for screenshots and demos.
- The receiver range on the map.
- Installing the UI as an app on a phone or desktop.
A tour
The screenshots here show made-up devices, networks, and locations. Each is shown in the light or dark theme to match these pages; the button under it switches theme, and Zoom, or clicking the screenshot, shows it full size.
The Overview tab sums up what Kismet sees in cards; the pencil at the top right moves, resizes, hides, and adds them back. Every tab has the top bar of stats above it and the Messages panel below it.

After 2026-10-R1, the Overview tab can hold several dashboards, picked from the Dashboard list at its top. Each dashboard has its own cards, layout, and card settings, and can hide the top bar of stats and the Messages panel while it’s showing; the pencil also names a dashboard, sets those two, and adds or deletes dashboards. While arranging, a card with settings of its own has a gear button: the Devices, Active devices, and New devices cards can leave out their graphs, and the Map card picks which kinds of device and map overlays it draws, whether it shows paths and the receiver range, and whether it keeps Kismet’s GPS location in view. The Map card is the map tab without its list, and isn’t on the Overview until it’s added.
The Wardriving dashboard is made for a phone: the Active devices and New devices counts above a map that follows Kismet’s location, without the stats bar or the messages. Reset layout puts the Overview and Wardriving dashboards back as they started; dashboards you make can be deleted.

The Devices tab lists every device, with the Tags column and the row highlights from the device rules. The Search or filter box takes device filters. Searching in a smaller view also shows how many devices match in all devices; clicking that count shows them. It can be turned off under Settings, Device list.

The SSIDs tab lists the Wi-Fi networks, and the Alerts tab the alerts:


The Map tab places devices by where they report themselves or where Kismet heard them, with a checkbox for each kind of device. Without a map server, it draws them on a blank map:

The Insights tab shows how devices relate: here, Wi-Fi clients and the access points they use.

After 2026-10-R1, the flow graph stays readable in a busy area. Each column shows its busiest entries, and every entry with a finding: up to 15 access points, 20 networks and 20 groups of connected devices, or about half that on a phone. The rest are merged into one more entry. Clicking a more access point or network entry pages through that column, busiest first, with the page shown in the bar; clicking a more group of devices lists them. Back returns to the view before, and Show all switches between everything and the busiest. Clicking a network, or Show only what links through this on an access point or a group of devices, shows only that entry and what links through it, and the search box does the same for a network, access point, or device name or MAC address; these views are trimmed the same way. The flow table shows up to 80 columns and 120 access point addresses.
After 2026-10-R1, the Insights views also group 802.11s mesh networks and multiple BSSID sets. Each mesh ID is listed with the networks, outlined in the mesh color, and linked to every mesh point heard; mesh points are no longer shown as hidden networks. An access point which sends further networks in its multiple BSSID element is named for the address sending them and tagged MBSSID, with the number of networks in the set; its card in the Access points view lists the networks in the set.
Clicking a device opens its details, in sections for each kind of device; this is a Bluetooth LE tag reporting its battery:

Windows
Windows open as panels which stay open while you use the rest of the UI; drag a title bar to move one and its corner to resize it. After 2026-10-R1, the Data sources, Channel coverage, and Packet rates windows have a button in their title bar which makes them fill the browser window, and takes them back to their size when clicked again.
The data sources, opened from the menu or the Sources stat in the top bar:

Channel coverage, live, and as a heat map over time:


The server’s device rules, by rules file:

Packet rates, from the menu or the Packets stat:

The GPS, from the menu or the GPS stat: the fix, the satellites in view and their signal, and their history:

Settings
Settings, Units:

Settings, Device Highlights:

Settings, Ribbon:

Settings, Censor mode:

Memory window
After 2026-10-R1, the Memory window, opened from the menu or by clicking the memory figure in the top bar, shows how much memory Kismet uses and why, over the last minute, hour, or day:

- Kismet’s memory and its peak, the device count, the memory per device, the system memory free, and how long Kismet has run.
- A graph of Kismet’s memory (the left axis) against the device count (the right axis), a graph of the tracked fields (every value Kismet keeps, in devices and everything else), and a graph of the system memory in use.
- What the memory is: the heap and stacks, the program and libraries, shared memory, and swap.
- What the heap holds: what Kismet needed once it had loaded (before opening data sources), its data sources, recent packets kept to spot duplicates, freed packets kept for reuse, and devices.
- The memory settings in effect, from
kismet_memory.conf,kismet_site.confand the other config files.
The memory per device counts only the memory devices use: Kismet’s memory once it had loaded, an estimate for each data source, and the packets it keeps are taken out first. Dividing all of Kismet’s memory by the device count overstates it, often several times over with few devices.
Insights flag what the memory is doing:
- About how much memory each new device costs, once the device count has changed enough to tell.
- Memory growing, at what rate, and when the system’s free memory would run out at that rate, with a pointer to
tracker_device_timeoutandtracker_max_deviceswhen devices are never forgotten. - Memory growing while the device count holds: when tracked fields grew too, data kept in the devices (clients, probed SSIDs, history); when they didn’t, something outside device data, such as packet queues, web clients, or memory the allocator holds.
- Low system memory, Kismet’s share of it, memory swapped out, a peak far above the present, and freed memory the allocator holds for reuse.
- Settings which cost memory (
keep_location_cloud_historyandkeep_per_datasource_stats), and a phy type which holds most of the devices.
Close an insight with its ×; it stays closed until it becomes more serious (a note turning into a warning), and Show closed insights below the list brings them all back.
The memory per device, and the cost of a new device, are estimates and can be well off, most of all soon after Kismet starts: the packet buffers are still filling, and with few devices the one-time costs are spread over too few of them.
The window reads the /system/memory endpoint. Against an older Kismet server without it, only the memory and device graphs are shown. The process and system memory figures are only available on Linux, and the heap figures with glibc 2.33 or newer.
Thermal window
After 2026-10-R1, Kismet reads the temperature sensors of the system it runs on every second: the lm-sensors sensors, when Kismet is built with lm-sensors, and the Linux thermal zones. It keeps a history of each, for the last minute, hour, and day.
The Thermal window, opened from the menu or by clicking the temperature in the top bar, shows:
- The hottest sensor, the average of the sensors, and how many are read.
- A graph of the sensors over the last minute, hour, or day. Check sensors in the list to graph them; with none checked, the four hottest are graphed. The CPU load of the system and of Kismet is graphed with them, against the right axis.
- Every sensor’s temperature now, and its lowest, highest, and average over the time shown.

The Thermal stat in the top bar shows the hottest sensor, or the sensors checked under Settings, Ribbon, Thermal. Temperatures are shown in Celsius or Fahrenheit, set under Settings, Units.
The window reads the /system/thermal endpoint. Against an older Kismet server without it, or a system with no sensors Kismet can read, the window says so and the top bar shows ---.
system_thermal_history={ true } / { false }
true; set to false to keep only the current temperatures.system_thermal_max_sensors={ count }
32, and can be 1 to 1024.CPU window
After 2026-10-R1, the CPU window, opened from the menu or by clicking the CPU stat in the top bar, shows the CPU load of the system Kismet runs on, and of Kismet itself, as a percent of all the CPUs:
- The load now, the number of CPUs, and the highest load over the time shown (its tooltip has the average). The tooltip of Kismet’s load also gives it as a share of one CPU, which shows a single busy thread.
- A graph of both over the last minute, hour, or day.

The window reads the /system/cpu endpoint. The CPU load is only read on Linux; elsewhere, and against an older Kismet server without it, the window says so.
After 2026-10-R1, the Overview tab also has CPU, Memory, and Temperatures cards: each shows the reading now and a graph over the last minute, hour, or day, and opens its window when clicked. The Temperatures card graphs the same sensors as the Thermal window; without temperature history it lists the hottest sensors now instead. Against an older Kismet server without the CPU or thermal endpoints, the cards say so.

Radiation window
After 2026-10-R1, the Radiation window, opened from the menu or by clicking a radiation stat in the top bar, shows the radiation sensors, such as the Radiacode. With more than one sensor, pick which one to show.
- The count rate (counts per second) and dose rate, and for sensors which report them, the accumulated dose the sensor has counted, its temperature, and its battery.
- History: the count rate, and the dose rate against the right axis, over the last minute, hour, or day.
- Spectrum, for sensors which send one: the gamma energy spectrum since Kismet started (Session), over the past hour, or as the sensor has accumulated it (Device), on a log or linear scale. Gamma lines marks the energies of common isotopes, and Waterfall adds the past hour minute by minute, newest at the top and brighter for more counts. For a sensor without a spectrum, the section says so.
Both sections fold away, and the window fits its height to what it shows until you resize it.
Never rely on radiation readings shown by Kismet for safety: they depend on the detector, its calibration, and how it is held.
The top bar has Radiation counts and Radiation dose rate stats, shown once the server has a radiation sensor, and hidden or shown again under Settings, Ribbon. The Overview tab offers a Radiation card (the dose and count rates, with the last minute of counts) and a Radiation spectrum card, with its own window, scale, and gamma line settings; neither is on a dashboard until added with Edit layout.
The window reads the radiation endpoints.
API keys window
After 2026-10-R1, the API keys window, opened from the menu just above Settings, manages the API keys of the server in use. Programs and remote capture use a key in place of a login. Managing keys needs an admin login.
- Each key is listed with its name, role, and when it expires. Keys are hidden until Show is pressed, and hidden again when the window closes; Copy copies a key without showing it. Over plain HTTP the browser has no clipboard, so Copy shows and selects the key to copy by hand.
- Revoke removes a key, after asking. Anything using the key loses access. If the key is the one the app uses for another server, the app asks to log in again.
- Create a key takes a name, a role (readonly, admin, datasource, scanreport, ADSB, datalog for saving tagged data to the kismetdb log, or another role a plugin defines), and how long until it expires. The new key opens in a window with a Copy button.
When the server sets httpd_allow_auth_view=false, it never sends keys back, so a key can only be copied when it’s made. With httpd_allow_auth_creation=false, keys can’t be made or revoked from the UI.
Serving the UI, HTTPS, and proxies are covered in the webserver configuration.