A guide to customizing the Wingpanel indicator area in elementary OS

The small cluster of symbols at the right edge of the elementary OS panel looks minor, yet it is often the quickest route to sound, network, power, Bluetooth and background applications. The Wingpanel indicator area, sometimes described as a system tray or status area, can also become crowded when several utilities are installed. A useful layout exposes relevant status without competing with the applications you are using.

Wingpanel supplies elementary OS with its top bar and the region that hosts built-in status items and compatible third-party indicators. An indicator is a tiny graphical representative of an application or service; selecting it may open a menu, launch a program or reveal details. It is not the same thing as a normal application window, and an indicator can remain visible after its main window has been closed.

Customisation is easiest when changes are made in stages: use the built-in panel controls first, add only the indicators that solve a real need, then adjust their startup and behaviour. This guide covers current elementary OS releases and older Switchboard layouts, because the controls and Wayland support vary slightly. It also avoids treating forum commands as universal when an installation may use different settings keys.

Many Australian users move between an NBN connection, 5G hotspot and public Wi-Fi during a day, particularly across Sydney, Melbourne, Brisbane and university campuses. That makes network visibility useful, while crowded transit or café workspaces can favour a quieter panel. The aim is not to display every possible statistic; it is to leave the right information available at the moment it can change what you do.

Know which parts of the panel Wingpanel controls

In elementary OS, Wingpanel provides the top bar, while the indicator area is the right-hand region reserved for status and application-menu items. Elementary’s own components normally handle network, sound, power and the clock, alongside items such as Bluetooth when suitable hardware is present. Their exact arrangement can change with the release, screen width and connected devices.

Third-party indicators use a compatibility layer such as AppIndicator or a newer status-notifier interface. That distinction matters: a Flatpak app with excellent notifications may still lack a panel icon, while an older GTK indicator may show a menu but behave poorly under Wayland. An icon’s presence therefore reflects protocol support and startup configuration as much as the app’s features.

elementary OS 8 uses the newer Settings application and can offer an experimental Wayland session; elementary OS 6 and 7 generally expose related controls through Switchboard. The Xorg session remains relevant for legacy indicators in some installations. Before changing anything, record the elementary OS release, desktop session and whether an icon is built in, supplied by another network tool or added as an extension.

Keep a simple map of the panel before editing. Note which icons respond to a click, which open a separate settings window and which expose a right-click menu. This map helps when an application update changes behaviour, and it prevents mistaking a notification for a missing indicator. Elementary’s menu items can remain stable while third-party items around them are added or removed.

Configure the built-in panel settings

Open Settings and select Panel in elementary OS 8, or open Switchboard and select Panel on older releases. Depending on the version, switches are provided for the clock, date, user name and elements of the system menu. On some installations, the optional Tweaks application exposes the same controls. Toggle only what the interface provides; it is safer than deleting files from the panel.

Handle the clock separately through Settings, then Date & Time. Australian English commonly uses a 24-hour clock and a day-first date, and the panel follows the selected locale, time zone and clock format. Daylight saving is handled automatically in NSW, the ACT, Victoria, South Australia and Tasmania, while Queensland, Western Australia and the Northern Territory do not observe it.

For settings not exposed by the graphical panel, inspect the elementary Wingpanel schema from Terminal:

gsettings list-keys org.elementary.desktop.wingpanel
gsettings list-recursively org.elementary.desktop.wingpanel

Keys differ between elementary OS releases, so use only keys that appear in the results. If show-clock is listed, for example, it can be changed with:

gsettings set org.elementary.desktop.wingpanel show-clock false
gsettings reset org.elementary.desktop.wingpanel show-clock

These settings belong to your user account, so do not run gsettings with sudo. A text backup provides a useful reference before larger changes:

dconf dump /org/elementary/desktop/wingpanel/ > ~/wingpanel-settings.txt

Choose indicators that earn their place

Choose indicators by task, not novelty. A VPN client may need a visible icon when it changes routes; a disk-usage or CPU-frequency indicator is useful on a workstation but distracting on a small laptop. Synchronisation, clipboard and hardware sensors can help, provided they remain readable and do not expose sensitive activity to anyone watching the screen.

AppCenter is the friendliest place to start because it identifies the source and handles installation. The Ubuntu repositories inherited by elementary OS also contain many packages named “indicator” or “applet”. Search before installing:

apt search indicator
apt show indicator-multiload
sudo apt install indicator-multiload

Package availability and maintenance vary, so inspect the description and project homepage before adopting an obscure utility. An old tutorial may recommend software that works but receives no security or compatibility updates.

Flatpak packages may not display a legacy tray icon because sandboxing and desktop integration differ. A missing icon does not always mean a failed installation. Review permissions for network monitoring, clipboard access or hardware sensors, and install from a trusted repository or verified publisher. Do not add a second AppIndicator compatibility package merely to force an icon; elementary may already provide one, and duplicate libraries can cause conflicts.

Test one addition at a time and leave the desktop running for a full session before making another. A second icon may duplicate a built-in status, consume a noticeable amount of panel width on a 1366×768 display or require elevated privileges. Good indicators expose their purpose clearly, start quietly and provide a dependable way to leave or disable them.

Control startup and indicator behaviour

Most indicators start through a desktop entry when you log in. Open Settings, then Startup Applications to review commands, or inspect ~/.config/autostart/ for entries that apply to your account. Package-managed entries may live in /etc/xdg/autostart and should not be edited there because an upgrade can overwrite them.

To disable one temporarily without removing its software, copy its desktop entry into ~/.config/autostart/ and add Hidden=true while retaining the existing fields. Keep a backup until the next login confirms the change. Some indicators are systemd user services instead; systemctl --user list-units --type=service can reveal those. Right-clicking an indicator usually opens its own preferences when the author supplied them.

Treatment of ordering differs among Wingpanel builds. Where drag-and-drop is offered, status icons can be placed before menu-style applets; otherwise leave the order alone rather than editing package internals. More importantly, avoid two programs claiming the same function. A standalone network applet beside elementary’s network indicator creates duplication, so disable one provider and let the remaining icon handle connections.

Fix missing, duplicate or broken indicators

If an indicator disappears, first check the Panel controls, an overflow area if your build has one, and whether the application was started. Legacy XEmbed indicators can be absent in the experimental Wayland session; trying the Xorg session is a practical diagnostic. Starting the program from a terminal often reveals a missing library, display or protocol complaint that the graphical session hides.

Duplicate Wi-Fi, volume or battery symbols usually mean that two providers are active, not that Wingpanel has multiplied the icon. Identify possible processes with:

pgrep -af 'indicator|applet'
systemctl --user list-units --type=service | grep -i indicator

Disable the redundant provider, normally through Startup Applications or its preferences, and then log out and back in to verify the result.

For deeper diagnosis, run the indicator binary using its actual command name and read the error, then check the current user journal:

journalctl --user -b | grep -i indicator

If the package itself appears damaged, reinstall the exact package rather than the whole desktop. For example:

sudo apt install --reinstall indicator-multiload

If a configuration directory exists and appears corrupt, move it aside with a new backup name rather than deleting it permanently. Resetting the complete dconf database is rarely necessary and would discard unrelated preferences.

A practical order of diagnosis saves time: verify the session, check the built-in switch, confirm that the process starts, inspect duplicate providers and test the application under Xorg. Change one variable per attempt. Screenshots of the panel and exact terminal errors are useful when asking in the elementary OS forums, but reinstalling the desktop is rarely the first sensible response.

Build a practical daily layout

A minimal laptop layout normally keeps the clock, network, sound and power controls, adds Bluetooth only when a Bluetooth device is regularly used, and hides rarely needed applets. A development machine can retain CPU, disk, synchronisation and VPN indicators. For meetings in Melbourne or Brisbane cafés, a temporary uncluttered layout preserves screen space and avoids exposing account names or synchronisation status on a shared display.

Local conditions make some indicators more useful. NBN and 5G networks, public transport and hybrid work mean the network item should be easy to find, while hot weather and long commutes make power status worth keeping visible. Community Linux groups and small studios in Australian cities often rely on upstream projects and peer support rather than commercial indicator vendors, making project activity an important purchasing signal. A paid indicator sold to Australian consumers can be covered by the consumer guarantees that apply to software sold as goods under the Australian Consumer Law.

For organisation-managed devices, remember that many Australian organisations are bound by the Privacy Act 1988 and the Australian Privacy Principles. A network monitor, clipboard manager or hardware sensor can reveal more than its icon suggests, so follow workplace policy and avoid unapproved inspection tools. The detail to remember is simple: customise deliberately, keep one trusted provider for each status, and leave visible only the information that helps you act.