The ChatGPT desktop app for Mac, and when the web version wins

The ChatGPT desktop app for Mac is a small download and a short decision, and most people make it without thinking about it. The tab is already open. Installing a native app that shows the same conversation seems like a free upgrade. It usually is, but not always, and the cases where it is not tend to surface a week later, when a second account is needed, or a link opens in the wrong place, or the Dock has quietly filled with one icon per service.

What follows is what the app requires, what it does that a browser tab cannot, what the browser tab still does better, and how the choice changes once there are several web services in daily use rather than one.

What the app requires, and which app it is now

Two things are worth checking before downloading anything.

The first is the requirements. The published system requirements for the macOS app are macOS 14 and either Apple Silicon (M1 or better) or an Intel processor. OpenAI also states plainly that no version compatible with older operating systems will be released. On a Mac running macOS 13 or earlier, the decision is already made: the browser is the only route.

The second is that there are now two apps with similar names.

As of July 9th, the new ChatGPT desktop app combines Chat, Work, and Codex and is available for macOS and Windows. The previous macOS desktop app has been renamed ChatGPT Classic, and continues to be supported. Source: help.openai.com

The download page at chatgpt.com/download detects whether the Mac uses Apple Silicon or an Intel processor and offers the matching installer, so the architecture question answers itself. The naming question does not. Anyone following a tutorial written before July will be describing ChatGPT Classic, and screenshots will not match.

What the desktop app adds over a browser tab

The strongest argument for the native app has nothing to do with the model. It is the way the app sits in the operating system.

A global keyboard shortcut. The documented shortcut is Option and Space together, which opens a small input field over whatever is on screen. A question can be asked without leaving the current application, without finding a browser window, and without hunting through tabs. For anyone who asks short questions many times a day, this single behaviour is the reason to install it.

Working with other applications. The macOS app can read from other apps, starting with coding tools such as IDEs, terminals, and Notes. A browser tab has no route to the contents of a terminal window. This is the category of feature that only a native application can provide, and it is where the gap is genuinely structural rather than cosmetic.

A built-in browser. The app ships with its own browsing view, described by OpenAI as a way to browse, sign in, download files, and review pages without leaving ChatGPT.

Its own window and its own place in the Dock. The conversation stops competing with forty tabs for attention. Command and Tab reaches it directly.

None of these are available from a tab. If any of them describe the actual daily pattern, install the app and stop reading comparisons.

What the browser tab still does better

The reverse case is less discussed, and it is not nostalgia.

Extensions. Password managers, clipping tools, and translation extensions live in the browser. A native app has none of them. Work that involves pasting between a chat and an extension is smoother in a tab.

Multiple accounts. A personal account and a work account are common, and a single desktop application signed in to one account at a time makes switching a sign out and sign in operation. Browsers solved this years ago with profiles, and macOS added a second route in Sonoma.

Where links open. A link clicked inside a native app may open in the default browser, which may be signed in to the wrong profile. Inside a browser window, the link stays where the session already is.

Update management. A browser tab updates when the browser updates. A native app updates on its own schedule, and every additional native app adds another schedule.

Old hardware and old operating systems. macOS 13 and earlier cannot run the app at all. The browser continues to work.

The account problem is the one that decides most cases

If one account is in use, the decision is a preference. If two or more are in use, it becomes structural, and it is worth knowing what macOS itself offers.

Since macOS Sonoma 14, Safari can save any webpage as a standalone app through File and then Add to Dock. The result behaves like an application, and the important part is how it treats the session.

A web app functions independently of Safari. It shares no browsing history, cookies, website data, or settings with Safari. In this way, it keeps your browsing separate, similar to using a Safari profile. What you do in a web app stays in the web app. Source: support.apple.com

That single sentence is the reason this route exists. One account in the saved app, another in Safari, no signing out. Chrome offers a similar path through More, then Cast, save, and share, then Install page as app, and pairs it with profiles that each hold their own cookies.

The trade is real. A Safari web app has a reduced toolbar with a back button, a forward button, a share button, and buttons for any enabled Safari extensions. There are no tabs and no bookmarks. Apple's stated escape hatch is the share button and Open in Safari. For a chat interface, which is one page used repeatedly, losing tabs costs almost nothing. For research that fans out into twenty links, it costs a lot.

Three routes, compared on what actually differs

Route	Multiple accounts	Global shortcut	Extensions	Updates
Official desktop app	one signed-in account at a time	yes, Option and Space	none	its own schedule
Safari, Add to Dock	yes, separate from Safari's session	no	per app, from the Extensions tab	follows the system
Chrome, Install page as app	yes, one per Chrome profile	no	follows the profile	follows Chrome
A browser that keeps each web app in its own window	yes, by design	depends on the product	depends on the product	one product to update

The table is only useful alongside a count. Two numbers decide it: how many services are opened every day, and how many accounts exist per service. With one service and one account, the official app wins on the shortcut alone. With six services and two accounts each, installing six native apps produces twelve sign-in states and six update schedules, and the fourth row starts to matter.

Where one app per service stops scaling

The failure is gradual, which is why it is easy to miss.

Each native app takes a Dock slot and a position in the Command and Tab list. At three apps this is invisible. At ten, finding the right window becomes a small tax paid dozens of times a day. Notifications arrive from ten separate sources with ten separate settings panes. Sign-in states expire independently, so one morning a week begins with an authentication round.

The alternative is not to abandon native apps. It is to be selective about which services earn one. A reasonable rule: a service earns a native app when it offers something the web version genuinely cannot do, such as the app reading other applications, or a system-wide shortcut. Everything else can live in a window that a browser manages. Which services fall on each side of that line is worth checking against a Supported apps list before installing anything, and the way a single window can hold separate sessions per service is set out in Workspaces.

For anyone comparing products in that last category, the free tiers are capped in different places, so a direct pairing such as Compared with Wavebox is more useful than a ranked list.

Where the ChatGPT window should live once it is installed

Installing the app is the easy part. What decides whether it gets used is where the window ends up, and macOS offers several places to put it.

The global shortcut covers the quick question. Option and Space opens a small input field over the current application, which means the main window does not need to be visible at all for short lookups. Anyone who installs the app and then keeps hunting for its window in the Command and Tab list has not yet made that shortcut a habit, and the app is doing less than it could.

Longer sessions are a different shape. A conversation that runs for twenty minutes alongside a document or a terminal wants a fixed position, not a floating panel. Two arrangements work. The first is a dedicated Space, reached with Control and a number key, holding the chat window and nothing else. The second is a split view against the document being written. Both avoid the state the native app was supposed to remove, where the conversation ends up buried under a browser holding forty tabs.

Notifications deserve one pass through System Settings. The app arrives with its own entry under Notifications, separate from the browser, and a chat assistant that interrupts is worse than a tab that waits. Turning banners off and leaving the badge on keeps replies visible without pulling attention away from whatever is in front.

A four question check before installing anything

Four answers decide the route, and all of them can be found in about a minute.

Which macOS version is running. The Apple menu and About This Mac shows it. macOS 14 or later is required, and no build is planned for anything older, so a Mac on macOS 13 stops here and stays in the browser.

Which app the instructions describe. A guide written before July 9th describes the app now called ChatGPT Classic. The current download combines Chat, Work, and Codex. Menu names and screenshots differ between the two, and following the wrong guide costs more time than the install saves.

How many accounts are in play. With one account, the native app is the simpler route. With two or more, the question stops being about ChatGPT and becomes a question about how sessions are kept apart on this Mac, which is a question every other service in daily use is asking at the same time.

Which browser opens links by default. A link clicked inside a native app hands off to the default browser set in System Settings. If that browser is signed in to a different account than the work belongs to, every handoff becomes a correction. Checking the default before installing avoids a class of small interruptions that are hard to attribute afterwards.

Answering those four for one service is a preference. Answering them for every service opened daily is a policy, and that is the point where the cost of a dedicated tool becomes a number worth comparing against the time it returns. Anything in that category publishes its Pricing, and the comparison only means something with the count in hand.

What to change first

Count the services opened daily and the accounts held in each. If both numbers are small, install the ChatGPT desktop app, learn Option and Space, and stop there. If the second number is above one for several services, solve the account problem before adding any more native apps, either with browser profiles, Safari web apps, or a single window that holds them all, such as SpaceDeck.