How to use X on a Mac: the shortcuts and the limits

Anyone looking for instructions on using the X app on a Mac hits an odd wall early: the instructions describe buttons that are not on the screen. That is because X's own download page covers two platforms, iOS and Android, and the desktop experience is the website. So the useful version of this question is not how to operate an application, but how to operate x.com well enough that it stops feeling like a website. That turns out to be mostly a matter of keyboard shortcuts, a handful of compose rules, and one setup decision that quietly determines whether the site keeps working at all.

The desktop client is the site, and X says so

X's help page for downloading the application is titled for iOS and Android, and its two download buttons are for iPhone and iPad, and for Android phones and tablets. Its own FAQ answers the device question the same way: the application for iOS installs on iPhones and iPads, and the Android application installs on most Android phones and tablets. No Mac entry exists on that page.

The supported browsers page carries the other half of the picture. X officially supports versions from the past year of Edge, Safari, Chrome, Firefox, and any browser based on Webkit or Chromium engines, naming Opera, Samsung Internet and UCBrowser as examples. So the browser is not a degraded fallback here. It is the client X builds for and tests against on a desktop.

Posts made this way are labelled, and the label is visible to everyone. X documents post source labels as appearing at the bottom of a post's detail page, giving X for iPhone, X for Android and X for Web as examples. Anyone using a Mac will carry the X for Web label, which is worth knowing before assuming a wrapper is hiding something.

The keyboard shortcuts, which are the actual skill

The single largest difference between using X on a phone and using it on a Mac is that the desktop has a full keyboard shortcut set, published by X. Learning six of them changes the experience more than any tool ever will.

Key	Action
n	new post
l	like
r	reply
t	repost
m	Direct Message
u	mute account
b	block account
enter	open post details
o	expand photo
/	search
cmd-enter	send post

Navigation runs on a second set: j moves to the next post, k to the previous one, space pages down, a full stop loads new posts, and a question mark opens the full keyboard menu.

The third set is the one that most people never discover, because it uses two keys pressed in sequence rather than together. Pressing g and then a letter jumps to a timeline: g then h for the Home timeline, g then n for the Notifications tab, g then r for Mentions, g then p for a profile, g then l for the likes tab, g then i for the lists tab, g then m for Direct Messages, g then s for Settings and privacy, g then u to go to someone's profile, and g then o for Moments.

Two of these are worth committing to memory immediately. The forward slash puts the cursor in search from anywhere, and g followed by m opens Direct Messages without touching the sidebar. Those two remove most of the pointing and clicking from a normal session.

The shortcuts only exist on the web. That is the strongest practical argument for treating a Mac window as the primary way to use X rather than a compromise while waiting for an application that is not coming.

What the compose box allows

The rules X publishes are specific enough to plan around.

A post holds up to 280 characters. Attachments are capped at four photos, or one GIF, or one video, and those options do not combine. The Post button sends, and so does Command and Enter from the keyboard.

Drafts and scheduling live in the same place and are easy to miss. Selecting the X icon in the top left of the compose box offers Save, which stores a draft. The calendar icon at the bottom of the compose box sets a date and time, then Confirm schedules it. Both drafts and scheduled posts are reached through Unsent posts from inside the compose box. There is no separate menu item for them, which is why so many people believe the web version cannot schedule.

Longer posts are a paid feature rather than a hidden setting. X documents them as an X Premium feature, written in the ordinary compose box, holding up to 25,000 characters. The behaviour of the character counter changes at the 280 mark: below it the circle tracks progress around its perimeter, and above it the circle fills.

What the mobile application is built around

Reading X's own description of the mobile application makes the split between the two clients clearer, and it is not the split most people assume.

The feature list on the download page covers posting and public conversations, following breaking news, extra context from Community Notes, going live with Spaces for audio, streaming live video including sports, Direct Messages, subscribing to X Premium, earning from exclusive content and ad revenue in replies, creating and joining Communities, uploading and watching videos up to three hours long, and writing long form posts.

Almost none of that is exclusive to a phone. It is a description of the service rather than of the application, which is the point. The mobile application exists because phones need one, not because the desktop is missing pieces. What the phone genuinely does better is capture: a camera in hand, a microphone for Spaces, and a device that is already unlocked when something happens.

What the desktop does better is everything that involves typing and reading volume. A long form post of up to 25,000 characters is a different writing task from a 280 character reply, and it is not a task anyone enjoys on a phone keyboard. Sorting through Mentions and Notifications with j and k, then acting with l or r without moving a hand, is faster on a Mac by a wide margin.

The practical division is capture on the phone, composition and triage on the Mac. Framing it that way removes the sense that a Mac user is missing an application. There is no application to miss. There is a keyboard, a larger screen and a shortcut set that the phone does not have.

The one thing to check before relying on this division is which features a given account has. X Premium gates the longer posts and several other capabilities, so a free account planning long form writing on a Mac will find the character counter stopping at 280 regardless of which client it is typed into.

The one setup mistake that breaks the site

X's supported browsers page contains a warning that matters enormously when building a dedicated window for the site.

The page states that using X on an older version of the listed browsers, on browsers not listed, or with a browser extension which modifies the user agent, may make X unusable.

That last clause rules out an entire category of approach. Tools that fake a browser identity, or that ship an old embedded engine and present themselves as something else, are exactly the configuration X warns about. The failure is not graceful either. It presents as a blank timeline, a login loop, or an unsupported browser notice, and it is easy to misread as an account problem.

The safe construction is the opposite one: a window that runs a current, real browser and identifies itself as that browser. A tool that turns a website into a standalone Mac application by building on a Chromium browser already installed on the machine satisfies this, because the engine, the version and the user agent are all the genuine browser's. Nothing is being spoofed. The Features page describes how that construction differs from an embedded engine approach.

Two accounts, and where the sidebar switcher stops helping

X supports switching between accounts inside one session, and for two accounts checked occasionally that is enough. It stops being enough in two situations that come up constantly on a work machine.

The first is when both accounts need to be visible at once. Switching is not viewing. Anyone monitoring a brand account while posting from a personal one is switching back and forth all day, and every switch is a chance to post from the wrong one.

The second is when the accounts should not share anything. Separate browser profiles keep cookies, sessions and history apart, so a personal account and a company account genuinely cannot leak into each other. Building one application per account, each with its own isolated profile, produces two icons in the Dock and removes the switching step entirely.

This is also where a dedicated window earns its place for a single account. A tab labelled with a bird icon among thirty other tabs is not findable. A window with its own icon and its own entry in the application switcher is reachable with Command and Tab, exactly like any installed program, which is the whole point of the exercise.

Setting up the window so the shortcuts still work

Three settings matter once the window exists, and getting them wrong wastes most of the benefit.

Turn the tab bar off for this one. With a tab bar present, the window drifts back into being a browser and the single letter shortcuts compete with browser behaviour. A single page window keeps n, r, l and the g sequences unambiguous.

Allow notifications deliberately, once. Notification permission is granted per site, and granting it inside a dedicated window keeps the alerts attached to that window rather than to the main browser. Denying it and relying on badge counts is a reasonable choice too. The decision just needs to be made rather than dismissed.

Keep the browser current. X supports versions from the past year, so a window built on a browser that stopped updating will eventually stop working. A window that references an installed browser rather than bundling its own copy inherits every update automatically, which removes this as an ongoing task. The Guide covers the creation steps for that arrangement.

What to do next

Learn the g sequences and the forward slash first, because they change the daily experience more than any configuration does. Then decide whether the friction that remains is about finding the tab or about juggling accounts. If it is either of those, give x.com its own window built on a current Chromium browser, so the keyboard shortcuts, the extensions and the real user agent all survive. A tool such as Kagemusha produces that window from a browser the Mac already has.