One Switch: how to uninstall it cleanly

The decision to remove One Switch has been made, and dragging it to the Trash looks like the whole job. It mostly is. But three things sit outside the application bundle, and one of them is easier to handle before the app is gone than after.

There is no bundled uninstaller. The shipping package contains no removal tool and no removal instructions, so this is a manual job across three places: the licence, a helper installed into the system, and the macOS settings the app rewrote while it was running. Everything below was checked against the shipping bundle on 10 September 2026.

Release the licence seat before anything else

Licences here are sold by device count, in one, two, and five device tiers. Which Macs hold the seats can be changed afterwards, but the control for releasing a seat exists only inside the app.

The License tab has a Deactivate License item. Choosing it confirms that deactivating allows reactivation later, on this Mac or a different one.

Once the app is deleted, that screen is gone and the seat stays occupied. This is recoverable rather than fatal. Entering the same key on the next Mac produces a message saying the code has already been used, alongside a Deactivate All Devices option that releases every seat at once. The cost is having to reactivate every other machine afterwards.

Keep the purchase email as well. The vendor's own description of delivery is that an activation code arrives by email after purchase, and activation needs both that code and the email address it was sent to. Deleting the app removes the only place the key is visible, so make sure the message is findable first.

One exception: if the app arrived through a subscription bundle rather than a direct purchase, licensing is handled by that service. Remove it through the bundle's own app rather than by hand.

Quit properly, then delete

This app runs as a menu bar agent with no Dock icon, so closing its window does not quit it. Use Quit from the menu bar panel, or the Quit item in the General tab of settings.

Deleting while it is still running either fails as in use, or succeeds and leaves a running process with no application behind it until the next restart.

With the app quit, move it from the Applications folder to the Trash. That handles everything visible. What follows is the part that is not.

The privileged helper lives outside the bundle

Two switches, Low Power Mode and Energy Mode, change macOS power management. That is not something an ordinary user process can do, so the app installs a small privileged program into the system and routes those operations through it. The administrator password prompt on first use is that installation.

The helper goes where macOS requires privileged helpers to go: an executable in the system's privileged helper tools directory, and a matching launch configuration in the system's launch daemons directory. Both are named after the app's bundle identifier with PrivilegedHelper appended, which makes them straightforward to identify.

Neither is inside the application bundle, so neither goes to the Trash with it. What remains is a launch entry pointing at a helper for an app that no longer exists. It is not harmful, but it is untidy, and it is the single most commonly missed piece of this particular removal.

The test for whether it applies is simple. Was an administrator password ever entered for Low Power Mode or Energy Mode? If those two switches were never used, the helper was never installed and there is nothing to clean up.

Verifying it by hand is a matter of looking rather than running anything. Both files are named after the bundle identifier, which is studio.fireball.OneSwitch, with PrivilegedHelper on the end. Anything else in those directories belongs to a different app and should be left alone. This is a system location, so removal needs administrator rights, which is a good reason to be certain about the filename before touching anything.

None of this applies to a bundle install

Two distribution routes exist, and only one of them leaves a privileged helper for you to find.

A direct download from the vendor arrives as a disk image containing the application, signed and notarised for distribution outside the App Store. That is the case this article describes, and it is the one where manual cleanup applies.

A copy that arrived through a subscription bundle is managed by that service instead. The bundle's own app installs and removes titles, tracks entitlement, and does not use the licence key mechanism at all. Removing such a copy by dragging it to the Trash leaves the service believing it is still installed. Use the bundle's remove command instead, and skip the licence deactivation step entirely, since there is no seat to release.

The quick way to tell them apart, if the install is old enough that nobody remembers: a direct copy shows the licence fields under its License tab, while a bundle copy does not need them.

Permission records and the login item

System Settings keeps its own records.

The app requests different permissions depending on which switches are in use. Dark Mode and Hide Dock drive System Events, Empty Trash drives Finder, and Play Music drives Spotify or Music, all through Automation. Headphones Connect uses Bluetooth. The sunrise to sunset variant of the Dark Mode schedule uses Location Services.

Each grant is recorded under Privacy and Security. After the app is deleted, its name can linger in those lists. Nothing runs, since the executable is gone, but the entries can be removed by opening Automation, Bluetooth, and Location Services and clearing the relevant rows.

There is also a login item. The Start at Login option registers a small launcher that ships inside the application bundle, and that registration is what appears in the Login Items list in General settings. If an unfamiliar entry remains there after deletion, that is what it is, and it can be removed from the same screen.

Revert the switches before deleting, not after

This is the part that produces confused support questions weeks later.

Most of these switches do not add behaviour of their own. They flip settings macOS already has. The shipping binary references several standard macOS preference domains directly, covering Finder, window management, the menu bar clock and focus mode, and Control Center. Whatever state a switch left behind stays behind.

Three cases cause actual trouble:

• Deleting with Hide Desktop Icons on leaves a desktop with no icons on it
• Deleting with Show Hidden Files on leaves Finder full of dot files
• Deleting with Low Power Mode on leaves the Mac in low power mode

The fix is an ordering rule rather than a repair procedure: turn every active switch off before quitting the app. It takes about fifteen seconds and removes the whole class of problem.

If the app is already gone, macOS can undo all of it natively. Desktop icon visibility lives in Finder's view settings, hidden files toggle with Shift plus Command plus period in Finder, and Low Power Mode sits under Battery in System Settings.

A checklist to run before quitting the app

Everything above collapses into one useful observation: almost all of the difficulty in removing this app comes from doing things in the wrong order. Five minutes spent inside the app before deleting it removes nearly every later complication.

• Open the License tab and choose Deactivate License, so the seat is released while the screen is still reachable
• Find the purchase email and confirm the activation code is still readable, in case reinstalling later becomes necessary
• Open the Customize tab and look at which switches are currently on, then turn each of them off
• Confirm whether Low Power Mode or Energy Mode was ever used, since that determines whether a privileged helper exists to clean up afterwards
• Check whether Start at Login is enabled, so the corresponding entry in Login Items is expected rather than mysterious
• Quit from the menu bar panel rather than closing a window

Only then move the app to the Trash. The order matters because three of those six steps become impossible or harder once the application binary is gone.

Leftover files in the user Library

Per user files remain. The app keeps a usage screen that counts how often each switch was pressed, so there is stored state as well as preferences.

Three locations inside the user Library folder are worth checking: the preferences folder, the caches folder, and the application support folder. Entries there carry either the product name or the bundle identifier, which takes the form studio.fireball.OneSwitch and appears as part of the file or folder name.

The app also uses a standard update framework, so a last check timestamp and possibly a downloaded update package can sit in caches.

None of this takes meaningful space and none of it does anything once the app is gone. It matters in exactly one situation: reinstalling later restores the old configuration from these files, so anyone who wants a genuinely fresh start should clear them first.

The Library folder is hidden by default. In Finder, open the Go menu and hold Option, and the Library entry appears.

One caution about cleaning here. Search by the bundle identifier rather than by the word switch, which is common enough to match unrelated files belonging to other software. The identifier is specific and will only match what belongs to this app.

If the app is being replaced rather than simply removed

Removals of this kind usually fall into two categories, and they call for different next steps.

The first is a straight removal, where the switches turned out not to be worth a permanent slot in the menu bar. In that case the checklist above is the whole job, and the freed slot goes back to whatever was already competing for it.

The second is a replacement, where the same jobs are being moved somewhere else. Here it is worth listing what was actually being used before installing anything new, because the answer is usually shorter than expected. Two or three switches out of twenty six is typical. Some of those have native equivalents: Dark Mode, Do Not Disturb, and Night Shift all sit in Control Center already, and hidden files toggle from Finder with a keyboard shortcut. What remains after that subtraction is the real requirement, and it is a much smaller thing to shop for.

There is also a third possibility, which is that the app was never the problem. If it was installed to reduce menu bar clutter by consolidating several controls into one icon, and clutter is still the complaint, then removing it makes the bar worse rather than better. The problem in that case is the total number of resident apps rather than any one of them.

What to change first

Work in this order: deactivate the licence, switch off everything still on, quit, then delete, then check for the privileged helper if either power switch was ever used. If the reason for removing this app was menu bar crowding rather than the app itself, one freed slot will not hold for long, since resident apps only ever accumulate. A tool that collapses the whole bar addresses that directly, and Koffret shows how icons get hidden behind a divider and brought back without expanding the row. The pricing and trial terms are worth reading before installing anything else, and a comparison of tools in this category sets out what each one requires in return.