To block Twitter (X) on your computer, block both x.com and twitter.com in your browser with a website blocker, turn the blocker on in Incognito, and run it as a timed session so it holds while you work. We build Kyte, a free Chrome extension that does this, and it lets you allow a single post on x.com while the timeline, Explore, and notifications stay blocked.
That last part is the reason most people's X block falls apart by Wednesday. Your work still sends you X links. A product launch thread, a status update from a service that is down, a reply someone wants you to see. If your blocker can only say yes or no to the whole site, the first one of those links turns it off, and it rarely goes back on.
How to block Twitter on your computer with Kyte
Kyte for Chrome is free, its core features need no account, and this takes about five minutes on a Mac or any computer that runs Chrome: - Install Kyte from the Chrome Web Store and pin it to the toolbar. - Block x.com and twitter.com. The old domain still redirects to the new one, and a rule on only one of them leaves a gap. - When you need a specific post, allow that exact page, for example x.com/yourcolleague/status/ followed by the post ID. - Start a timed session for your working block so the rules stay on until it ends.
The allowed post loads. Click the X logo, the For You tab, or a trending topic, and you are back at the block page. That is the whole point: you read the thing you were sent and there is no timeline underneath it.
Your blocklist stays on your device, and Kyte does not track what you browse. We think that should be the minimum for a tool that sees every link you open.
Why blocking all of x.com usually fails
Domain blocking works for a site you never need. X is rarely that site. Developers get bug reports and outage notices there. Marketers check campaign replies. Researchers follow people who post papers there before anywhere else.
So the block gets lifted for one legitimate reason, and the feed is right there when you finish reading. You came for one post and stayed for forty minutes of quote tweets. We wrote about this pattern in more depth in our post on URL-level versus domain-level blocking, and X is the clearest example of it we know.
Our opinion, plainly: if you need X for even one thing a week, a whole-domain block is the wrong tool. Block the site and allow the page.
The side doors on X
X has more ways in than its main address. Chrome Incognito is the first one. Extensions are off in private windows by default, so open chrome://extensions, click Details on Kyte, and switch on Allow in Incognito.
Then there is twitter.com, which still works as a way in because it forwards to x.com. Block both. Images and video come from twimg.com, and links inside posts go through the t.co shortener. You don't need to block either of those for focus, since neither one shows you a feed. Blocking t.co will break the links in the one post you allowed, which defeats the purpose.
If you catch yourself reaching X through some other route mid-session, a mobile site or a bookmarked search, add that address right then. It is the only rule change worth making in the moment. Every other edit should wait until the session is over.
How to block X on a Mac without an extension
macOS Screen Time can block a site. Open System Settings, go to Screen Time, then Content and Privacy, and under content restrictions set web content to limit adult websites, which lets you add x.com and twitter.com to a restricted list. It is built in and free. It is also all or nothing, and it is easy to switch off from the same settings page you used to set it up.
Editing the hosts file is the other route people suggest. You point x.com at 127.0.0.1 and the browser can't reach it. It needs admin access and a terminal, it blocks the whole domain with no exceptions, and browsers can keep a cached copy of the site for a while after you save the change. We don't recommend it for focus. It is a parental control dressed up as a productivity tip.
Both are fine if you never need a single X link for work. If you do, you are back to switching the block off, and that is the habit you were trying to break.
Can you block the X feed but keep posting?
Some people want to post on X without reading it, usually for work accounts. The cleanest version of that with Kyte is to allow the exact pages you need, such as the compose page or your own profile, and keep everything else blocked during focus hours. Write your posts in a session window you set for that, then let the block come back.
Be honest with yourself about this one. If posting turns into checking replies, which turns into reading the timeline, the allowlist is too generous. Cut it back to the single page and schedule the rest for outside your focus time.
When you know you'll turn it off
A timed session is enough most days. Some afternoons you will open the extension and end it early, and every blocker you can switch off has that weakness.
For those afternoons, Kyte's Locked In Mode runs blocking you cannot turn off before the time is up. It is a separate one-time purchase inside the Chrome extension and uses Google sign-in so it works across your devices. We'd keep it for deadline weeks, not every day.
If your distractions also live in desktop apps, Kyte for Mac blocks whole apps system-wide and runs recurring daily schedules, so your morning focus block starts on its own. It is a one-time purchase of $19, no subscription, on Apple Silicon and Intel. The Mac app doesn't block websites system-wide yet, so X in the browser is still the extension's job. Kyte doesn't run on iPhone or Android today, so for your phone, the built-in Screen Time or Digital Wellbeing limits are the fallback.
Block x.com and twitter.com before you open your first work tab tomorrow, and the next time someone sends you a post, allow that one page instead of lifting the block. A week of that and checking X stops being a reflex.
Block X, keep the one post you need. Add Kyte to Chrome, free.
Get started