Figma Mac app: when the desktop build is worth installing

Figma runs in a browser tab and always has. That is the reason it won, and it is also why the download link on figma.com raises a fair question: if the tab already works, what does installing anything actually change. For most web services the honest answer is very little. Figma is one of the exceptions, and the differences are specific enough to name.

What the desktop build actually adds

Figma's own documentation is unusually direct about this. The desktop app gives access to the same features and functionality as the browser, plus two things.

Develop plugins and widgets for your organization or the Figma Community. Access and use fonts installed on your device without needing the font installer. Source: help.figma.com

Beyond that headline pair, the documented list of desktop only behavior is longer than most people assume. Desktop notifications reach the macOS menu bar and are marked as available on the desktop app only. Split tab view puts two files side by side in one window, either two different files or two views of the same file, with edits in one appearing live in the other. Tabs can be pinned, muted when a prototype is playing audio, and collected into named and colored tab groups. Tabs can be dragged out into separate windows and dragged between them. Trackpad haptics can be turned on for actions like snapping.

None of that is a rendering advantage. Figma draws through WebGL in both places, so the canvas is the same canvas. What the desktop build changes is everything around the canvas: window management, notifications, and the file system boundary. For a designer with fifteen files open, window management is not a small feature.

The font question is the whole argument

The single most common reason a Figma file looks wrong on one machine and right on another is fonts, and this is where the browser and the app genuinely differ.

A browser cannot enumerate the fonts installed on the machine, so Figma ships a helper called FigmaAgent to bridge that gap. The documentation describes what it does and how it does it.

Behind the scenes, FigmaAgent runs an HTTP and HTTPS server on localhost. It only allows connections from figma.com and isn't exposed to the public internet. Source: help.figma.com

It has no interface, runs silently, and detects fonts already installed. It also shows up in console logs and activity monitors, which is why it periodically alarms someone in IT who has not seen it before. The loopback address it uses resolves to 127.0.0.1.

Two consequences follow. The first is that the desktop app is simpler on a machine with a large local font library, because the helper is built in and there is nothing separate to keep alive. The second is that the browser is not blocked from local fonts either. Installing FigmaAgent on its own puts the same capability behind a tab, which matters on machines where the full app cannot be installed but a small helper can.

Anyone working entirely in Google Fonts and shared team libraries can ignore this section completely. Anyone whose brand typeface is licensed and installed locally should treat it as the deciding factor.

Where the version numbers diverge

The requirement lines for the two routes are not the same, and the gap is exactly one macOS release.

	Desktop app	Browser
Minimum macOS	macOS 12 (Monterey) or later	macOS 11 or later
Processors	Optimized for Intel and Apple Silicon	Whatever the browser supports
Minimum browsers	Not applicable	Chrome 99+, Firefox 101+, Safari 16+, Edge 121+
Shader support	Follows the bundled engine	Chrome 113+, Firefox 141+, Safari 26+
Version lifetime	Support removed six months after release	Follows the browser's own updates

Three details in that table repay attention. Figma states that support for previous versions of the desktop app is removed six months after release, so an app left un-updated on a managed machine has a shelf life. The shaders row is a second, higher bar than the base requirement, because those features want WebGPU rather than WebGL 1.0 and cannot run in compatibility mode. And Edge carries a setting of its own: the Strict mode privacy setting has to be disabled for figma.com before Figma will run there.

An Intel Mac that Apple stopped at macOS 11 falls below the desktop app line and above the browser line. That machine is not out of the game. It is a browser machine.

Performance is a graphics question, not an app question

A common assumption is that the downloaded app is faster because it is native. Figma's own requirements page points somewhere else entirely.

Figma renders through WebGL, and the requirements it publishes are graphics requirements rather than application ones. On macOS, Figma notes that OS releases update Safari and carry WebGL fixes with them, which is a different maintenance path from Windows and Linux, where driver updates do the work. The company also states that it cannot support or troubleshoot dedicated graphics cards, and points at Apple's own documentation for choosing between an integrated and a discrete GPU on a MacBook Pro.

Two specifics are worth knowing before blaming the container for a slow file. Intel HD Graphics 3000 is listed by name as a GPU with known bugs that may cause rendering glitches, and behavior on it varies from browser to browser. Virtual desktop infrastructure such as Citrix or VMware is called out as likely to perform poorly, because those environments are often provisioned without graphics acceleration at all, and this applies to both the web version and the desktop app.

The practical reading is that a stuttering canvas is usually a GPU, driver, or virtualization problem, and moving the same file from a tab into an installed app will not fix it. Checking which graphics processor is in use is a faster diagnosis than reinstalling anything.

Updates, betas, and the six month clock

The desktop app has a maintenance story that the browser does not, and it catches teams by surprise.

Figma removes support for previous versions six months after release, and prompts inside the app when a newer build exists. On a company managed Mac, that prompt may not be actionable by the person seeing it, since the documentation notes that an administrator may need to perform the update. A design team on managed hardware should treat the six month figure as a calendar item rather than a footnote.

There is also a separate beta build. It installs alongside the regular app, both versions carry the same core features, and the beta does not unlock unreleased functionality. Usefully for anyone juggling accounts, the documentation states that being logged into the same account on both versions is not required, so the regular app and the beta can hold two different logins. That is a legitimate two account setup with no third party tool involved, with the caveat that a beta channel is a test environment and behaves like one.

The browser side has none of this. It updates when the browser updates, which happens whether anyone is paying attention or not.

When the browser is the right container

Setting aside version numbers, three situations point at the browser even on a current Mac.

The first is a managed laptop. On a device where installers require an administrator, a browser tab is the only route that does not involve a ticket, and Figma runs there with no feature loss on the canvas itself.

The second is two accounts. A freelancer with a personal account and a client organization, or a designer who belongs to two companies, needs two Figma sessions that do not sign each other out. Browser profiles solve this cleanly, since each profile carries its own cookies and its own login.

The third is a review only workflow. Someone who opens Figma to leave comments, check a spec, and copy a hex value does not need tab groups, haptics, or local font access. For that person the desktop app is an extra icon and an extra updater for no return.

There is one hard limit worth stating in the same breath. Figma documents that on a mobile device only a view only version of files is available, so a phone browser is not a workaround for anything. Tablets running a full desktop operating system are treated differently.

Giving the browser version a window of its own

A tab has one problem that has nothing to do with Figma's feature list: it is not addressable. Cmd+Tab does not reach it, quitting the browser closes it, and on a busy afternoon it sits somewhere in a row of forty favicons.

A site to app tool closes that gap without installing a second application from Figma. Instead of bundling its own copy of Chromium, this kind of tool points at a Chromium browser already installed and wraps a single URL in a real app bundle. The window gets a Dock position, a Cmd+Tab entry, its own space in Mission Control, and it stays open when the browser is quit.

For Figma the useful part is what comes with that window. Each app gets its own browser profile, so a personal Figma and a client organization Figma can sit side by side as two icons with two logins, neither one signing the other out. Extensions are enabled per app, which keeps a screenshot or accessibility extension in the design app without following the rest of the browser around. Seven engines are supported, including Chrome, Brave, Microsoft Edge, Vivaldi, and Opera, and the supported services list covers 318 services with the URL, official icon, and app name already paired.

What it does not do is manufacture the desktop app's features. Plugin and widget development still requires the desktop build. Split tab view and tab groups belong to the desktop build. Local fonts still route through FigmaAgent, exactly as they do in the browser. A tool of this kind changes the container, not the client, and any page that claims otherwise is selling something.

Running both without confusion

Nothing forces a single choice, and a split setup is common among people who do this daily.

The desktop app takes the main account and the deep work: files being edited, plugins being written, local typefaces in use. A separate app window built on the browser takes the second organization, the client handoffs, and the review links that arrive by email. The two do not share a session, so a link opened from a client's message lands in the right account instead of triggering the wrong one.

The cost of testing that arrangement is close to zero, since the tool is free for up to three apps and the paid tier is a one time purchase rather than a subscription. Two weeks is long enough to know whether the second window earns its Dock slot.

What to change first

Check the macOS version and the font library, in that order. On macOS 12 or later with locally installed typefaces, install the official desktop app and stop there. On macOS 11, or with a second Figma account that keeps signing out the first, put figma.com in its own window with its own profile, which is what Kagemusha is for.