Mac menu bar icons duplicated: why two copies appear

Two identical icons, side by side, for an app that should only ever have one. It looks like a bug in the app, and occasionally it is. Far more often it is an accurate report of something true on the machine: there really are two of that app, or there was, and the menu bar is showing exactly what exists.

That distinction decides everything that follows. When Mac menu bar icons duplicated on your machine, the first job is not to remove one of them. It is to work out whether both are live, because deleting the wrong copy of an app is a much worse afternoon than a doubled icon.

Click both icons before doing anything else

The fastest test costs ten seconds. Click the first icon, note what the menu says, close it, then click the second one.

Three outcomes, and they lead to different places.

What the two menus do	What it means
Both open, and look identical	Two copies of the app are running
Both open, but show different version numbers or settings	Two different builds are installed
One opens, the other does nothing	The dead one is a stale item, not an app

If one of them does not respond at all, or opens and immediately closes, it is likely a leftover that the system never cleared. That case is covered further down and does not require uninstalling anything.

If both respond, look for an About entry or a version number in each menu. Two different version numbers is conclusive: there are two separate builds on disk, and they are both starting. Identical version numbers usually means the same build launched twice from two locations.

The common cause: two copies of the app on disk

Applications on macOS are folders that can be copied anywhere, and nothing stops two of them existing. The usual way this happens is ordinary and harmless at the time. An app is downloaded, opened from the Downloads folder to try it, and later dragged into Applications. The first copy stays where it was. Both register themselves to open at login, and both do.

Disk images produce the same result. An app launched while the disk image is still mounted runs from that image, and if it registered a login item from there, the system may keep trying to start something at a path that comes and goes.

Finding the copies is straightforward. Open Finder, press Command Space or use the Finder search field, and search the app's name with the scope set to This Mac rather than the current folder. Widen the search to include system files if the first pass finds only one. Check the obvious places by hand as well: the Applications folder, a personal Applications folder inside your home folder, Downloads, the Desktop, and any external volume that is usually connected.

When you find two, keep the one in Applications and move the other to the Trash. Quit the app first, from both icons, so nothing is running from the copy you are removing. Then log out and back in, which is the reliable way to confirm that only one starts.

There is a way to confirm which copy is actually running before anything goes into the Trash. In Activity Monitor, double-click the row for the app and open the Open Files and Ports tab, where the path of the running executable is listed near the top of the output. Selecting the row and choosing Show in Finder from the View menu does the same job in one step and lands you in the folder that holds the live copy. Doing this while both icons are still present tells you which of the two paths is the one starting at login, so the copy that gets removed is the copy you meant to remove rather than the one you happened to find first.

One caution before deleting. Settings for a Mac app usually live in your home folder rather than inside the app itself, so removing a duplicate copy of the application does not normally take your configuration with it. That is the general case, not a guarantee, and apps that store data inside their own folder do exist. If the app in question holds anything you would not want to recreate, check its own preferences for an export option first.

The same copy running twice

There is only one app on disk, both icons respond, and the version numbers match. In that case the same build is running as two processes.

Open Activity Monitor and search for the app by name. Two rows with the same name confirms it. Note that many apps legitimately run more than one process, a main app plus a helper or an updater, so look at whether the names are identical rather than merely similar.

This state usually comes from a launch race. An app that updates itself may start the new version while the old one is still quitting. A login item and the app's own relaunch logic can both fire during login. Some apps also register both an application and a background agent, and if the two are configured to show a status item independently, both appear.

Quitting both instances and launching once by hand is enough to clear it for the current session. Whether it comes back at the next login is the useful signal. If it does, the duplicate is being started by configuration rather than by chance, and the next section is where to look.

Duplicate entries in Login Items

Since macOS Ventura, everything that starts automatically appears in System Settings, then General, then Login Items. In macOS Sequoia the pane is named Login Items and Extensions. Two lists sit there: applications that open at login, and background items that apps have registered for themselves.

Duplicates in this pane are common after an app has been moved, renamed, or updated across a major version. The old entry can point at a path that no longer exists while a new one points at the current location. Sometimes the same app is listed twice with the same name, which is a strong hint that two copies exist somewhere on disk even if you have only found one.

Remove the entries you do not want with the minus button, then add back only the one you do, or let the app register itself by turning its own launch at login setting off and on again. Doing it in that order avoids leaving a half configured state where the app's preference and the system list disagree.

The background list deserves separate attention. A helper switched on there can start the app even when nothing appears in the Open at Login list, which is why the icon can return after you thought you had removed every trace.

Entries that name a developer rather than an app are the confusing part of that list. macOS groups background items by the team that signed them, so one row can cover several pieces of a single install, and turning it off can stop more than you intended. Expand the row where the interface allows it, read what is inside, and change one thing at a time. If an app stops behaving as expected after a change here, switching the same row back on restores it without a reinstall.

The same app installed from two places

Some developers publish both a Mac App Store version and a direct download from their own site. The two are separate installs with separate identifiers, and having both is a normal way to end up with a duplicated icon that survives every restart.

The same thing happens after moving to a new Mac. Migration Assistant copies applications from the old machine, and a fresh download of a newer version afterwards leaves both present. Restoring selectively from a Time Machine backup can do it too.

Telling them apart is easier than it sounds. Select each app in Finder and press Command I to open the info window. The version is listed there, and an App Store install often sits in Applications with different file permissions from a copy you installed yourself. Compare the two, decide which one holds your settings and your licence, and remove the other.

Before deleting anything, check where the licence lives. A paid app bought from the App Store is tied to that account, while a direct purchase uses a licence key or an account login. Removing the wrong one means going through recovery for no reason.

A stale item that nothing cleared

If one of the icons does not respond, no app is behind it. The menu bar is drawn by system processes, and those processes can retain an item after the app that owned it has quit, crashed, or been replaced during an update.

Logging out and back in clears this, and it is the safe method. In Terminal, killall SystemUIServer restarts one of the processes involved. On current macOS versions many system items are drawn by Control Center rather than SystemUIServer, so the command does not always affect what you expect. It changes no settings either way.

If the dead icon comes back after a redraw, it is not stale. Something is creating it, and you are back in one of the earlier cases. If it stays gone, the matter is finished and no cleanup of the app is needed.

When a manager is involved

A menu bar manager for macOS introduces its own possibility. Most of these tools work by keeping a second, hidden section of the bar, and depending on how the sections are arranged, an icon that is mid transition or that the tool has not finished classifying can briefly appear in both.

The check is the same as before: click both. A tool that is showing the same item twice will open the same menu from either one, and collapsing and expanding the bar usually settles it. If a specific app duplicates every time you toggle, its status item is being recreated rather than moved, which is worth reporting to whoever makes the tool.

This is also a reason to be deliberate about how many icons are hidden versus visible. The fewer items competing for space, the less often anything has to be shuffled. Sorting icons into the ones you read at a glance, the ones you click occasionally, and the ones that only prove an app is alive makes the hidden group the largest and the visible group stable. Features explains how hidden items stay usable rather than simply going out of view, and How it compares sets out what each tool in this category does and does not do, including which are free.

What to change first

Click both icons before touching anything, because a live duplicate and a dead one need opposite treatment. If both respond, find the second copy on disk or the second login entry and remove one. If only one responds, log out and back in, and treat the matter as closed. Once the bar is settled, decide which icons need permanent space and hide the rest with a tool such as Koffret, so a doubled icon is easy to spot the next time it happens.