How to turn off SelfControl on Mac

How to stop SelfControl on a Mac

You can't turn off SelfControl while a block is running. The app is built so the block lasts until its timer ends, even if you restart the Mac or delete the app. SelfControl's own FAQ answers "How do I disable SelfControl once it has started?" with: "You can't. That's the idea. Just wait." When the timer reaches zero, the block lifts and the sites load again.

That's the honest answer, and this guide won't offer tricks to get around it. What it covers instead:

1. What happens if you restart the Mac or delete SelfControl.
2. What SelfControl's documentation says to do if the timer ended and sites are still blocked.
3. Why SelfControl Killer isn't the answer on current versions.
4. How to uninstall SelfControl once the block is over.
5. How to set things up so you don't get stuck next time.

The SelfControl details below come from SelfControl's FAQ and its GitHub wiki, checked in October 2026. The current version on selfcontrolapp.com is 4.0.2.

Why SelfControl can't be turned off

SelfControl is a free, open-source Mac app that blocks the sites on your blocklist for a set time. Its homepage says that until the timer expires, "you will be unable to access those sites—even if you restart your computer or delete the application."

The app has no setting to pause or end a block early. That's the whole point of it. One r/macapps user called it "near impossible to shut off", and meant it as praise.

Restarting the Mac

Restarting doesn't end the block. The timer keeps running, and the block is still in place when the Mac comes back up.

Deleting the app

Deleting SelfControl doesn't end the block either. The FAQ warns that it may "cause problems with the block ending at the proper time" and says plainly: "Don't do it!" If you want SelfControl gone, wait for the block to finish and then uninstall it (steps below).

Updating mid-block

The FAQ also advises against installing a new version of SelfControl while a block is running. Wait until it ends.

If you need a blocked site right now

The block applies to this Mac. If something urgent is on a blocked site, such as a work login you blocked by accident, use another device for that one task and let the block run out on the Mac.

To avoid this, the FAQ's own advice is to test a short block before a long one, and to be careful with domains that serve many things. Blocking google.com, for example, may block several Google services at once.

If the timer ended but sites are still blocked

This is the case where SelfControl's documentation does give you steps. Its wiki page "Help! SelfControl is still blocking sites even after the block should have ended!" splits it into two situations.

The timer is stuck on "Finishing" or "00:00"

For SelfControl 2.0 and later:

1. Open SelfControl and leave it on the "Finishing" (or 00:00) screen.
2. Wait about ten seconds. A button labeled Stuck? Stop block manually replaces the Add to Blocklist button.
3. Click it to remove the block.
4. If sites are still blocked, restart the Mac.
5. If they're still blocked after the restart, click Stuck? Stop block manually again.

This button only appears once the timer has run out. It is a fix for a block that failed to end, not a way to end one early.

SelfControl shows no block, but sites are still blocked

1. Make sure nothing else is blocking the site, such as a work firewall, another blocker, or Screen Time, and that the site loads on another device.
2. Clear your browser's cache, then restart the Mac. The wiki calls this the most common fix.
3. If that doesn't work, start a new SelfControl block for 1 minute, let it expire, then restart the Mac and test again.

The FAQ adds simpler steps for a block that's over but a site that only partly loads: refresh the page, clear your cache, and restart your browser.

Still stuck after all that

The wiki asks you to email the developer at the address on that page, with your SelfControl and macOS versions, when the block started and should have ended, what SelfControl shows now, and whether you use a VPN or proxy. SelfControl is a volunteer project maintained almost entirely by one person, and the FAQ says replies can take months, so work through the steps above first.

What about SelfControl Killer?

SelfControl Killer was a separate app for very old versions. The wiki says to use it only on versions before SelfControl 2.0, and states that it "will not remove the block with SelfControl 2.0 and later, and may wreak havoc on your system." If you're on a current version (4.x), don't use it. Use the Stuck? Stop block manually button described above instead.

How to uninstall SelfControl

From the FAQ:

1. Wait for the current block to end. You can't uninstall SelfControl while a block is running.
2. Quit SelfControl.
3. Drag it from Applications to the Trash.

The FAQ says this leaves a few small settings files that don't do anything. If you want them gone too, it gives these Terminal commands:

sudo find -E /usr/local/etc -regex '.*\/\.[a-z0-9]{40}\.plist' -delete -print
defaults delete org.eyebeam.SelfControl
sudo rm /etc/SelfControl.lock

If SelfControl isn't blocking in Firefox

Some people search "how to stop SelfControl" when the real problem is the opposite: the block isn't holding. The FAQ says Firefox's DNS over HTTPS can make SelfControl blocks "unreliable or fail entirely", and the fix is to quit and restart Firefox after starting each block. It also says SelfControl won't block properly while a VPN is on. For the general version of this problem, see the hosts file guide, which covers secure DNS, Private Relay, and subdomains.

How to avoid getting stuck next time

Most "how do I turn off SelfControl" moments come from a block that was too long, too broad, or started on impulse. A few habits help:

• Test first. Run a short block with a new list before a long one, as the FAQ suggests.
• Keep blocks short. Several short blocks are easier to live with than one long one. SelfControl hides blocks longer than 24 hours for this reason.
• Block only what distracts you. Avoid shared domains like google.com unless you've tested what else breaks.
• Know when access returns. Pick an end time you'd be happy with before you click Start.

Consider a schedule with a known end time

SelfControl starts one block at a time, and you choose its length each time. It has no built-in schedule. The FAQ points to third-party command-line tools such as auto-selfcontrol for that.

A scheduled blocker works differently. You decide the hours once, when you're thinking clearly, and the block starts and ends at the same times every week. You always know when access comes back.

Cactus for Mac works this way. You set one recurring schedule (the weekdays, one time range, one site list), and the menu bar shows when access returns while the app is open. Like SelfControl, Cactus has no way to end an active block early, so you'd be in the same position during a block. The difference is that its end time is fixed in advance and the same every week. Changes you make during a block apply from the next one. A Mac administrator can still remove Cactus.

SelfControl does some things better. It's free and open source, and it can block mail servers, ports, and IP ranges, not only websites. Cactus blocks websites only and costs $19.99 once, with a 7-day free trial (see pricing). The SelfControl alternative comparison goes through the differences, and how to block websites on a schedule covers every scheduled option on Mac.