Figma Mac app: when the desktop build is worth installing

Yes, there is an official Figma Mac app, it is free on every plan, and it needs macOS 12 Monterey or later. It is downloaded from figma.com, not from the Mac App Store. The app listed under the name Figma in the App Store is the mobile viewer for iPhone and iPad, which is a different product. If the browser tab already works, the desktop build is worth installing for two documented reasons: fonts installed on the Mac show up without a separate helper, and plugins and widgets can be developed locally. Everything else it adds is about managing windows and tabs.

The rest of this guide covers the requirements as stated on Figma's own pages (checked on October 18, 2026), the install steps, what the app adds over the browser, the cases where the browser is the better choice, and what changes when IT installs it for a team.

What the desktop build needs before installing

Figma lists two different sets of requirements, one for the desktop app and one for the browser, and they do not match. That gap matters for anyone on an older Mac.

Requirement	Figma desktop app	Figma in a browser
Minimum macOS	macOS 12 Monterey	macOS 11 Big Sur
Processor	Intel and Apple Silicon	Any Mac that runs a supported browser
Browser minimum	Not applicable	Chrome 120, Firefox 128 ESR, Safari 17.4, Edge 121
Plan needed	Any plan	Any plan
Where to get it	figma.com downloads page	Nothing to install

The desktop figures come from the Guide to the Figma desktop app, which says the app is optimized for Macs with Intel and Apple Silicon processors and requires macOS 12 or later. The browser figures come from the Figma system requirements page, which sets macOS 11 as the floor and lists the minimum versions for each browser.

So a Mac stuck on Big Sur can still run Figma, but only in a browser. To check the installed version, open the Apple menu, choose About This Mac, and read the number under the version name.

The browser page also notes that Figma renders through WebGL, and that shader features need WebGPU, with higher browser minimums (Chrome 113, Firefox 141, Safari 26). It also says the desktop app's requirements are generally the same as the browser's with regard to WebGL and graphics cards. In other words, the canvas does not get faster or more capable because it runs in the desktop build. The graphics path is the same.

How to install it on a Mac

The install is a short drag and drop. These are the steps as Figma documents them.

1. Open the Figma downloads page and choose the desktop app for macOS.
2. Open the downloaded file to run the installer.
3. Move the Figma icon from the Downloads folder to the Applications folder.
4. Delete the installer from the Desktop or Downloads folder.
5. Open Figma and log in with email and password, Google single sign on, or a SAML identity provider.

The downloads page carries a note worth reading: the desktop app includes the font installer. Someone who only uses Figma in a browser needs to install that font helper separately. It is offered on the same page as its own macOS download.

There is also a beta build. Figma's guide says it can be installed alongside the regular app, appears as Figma Beta in the Dock, does not need the same account, and does not unlock unreleased features. It exists to test bug fixes and performance changes before general release. For most people the regular build is the right one.

Updates are handled inside the app. When the app is behind, it shows a message asking to update. The guide states that support for previous versions is removed six months after release, so leaving the app unpatched for a long time eventually stops being an option. At the time of checking, the version file Figma publishes for Mac deployments listed 126.9.13 as the current release.

What the desktop app adds over a browser tab

Figma's guide opens with a clear statement: the desktop app gives access to the same features and functionality as using Figma in a browser. Then it lists what it adds on top.

Local fonts without a helper

This is the main reason to install. In a browser, Figma cannot read the fonts installed on the Mac by itself. It relies on a background helper called FigmaAgent. Figma describes it as having no interface. It runs a small HTTP and HTTPS server on localhost that only accepts connections from figma.com and is not exposed to the internet. That is why entries for it can show up in Console or in network monitoring tools. The desktop app bundles this, so fonts just appear.

For a team where each designer has licensed fonts installed locally, this removes the most common cause of a file that looks right on one Mac and wrong on another.

Plugin and widget development

Developing plugins and widgets for an organization or for the Figma Community is listed as a desktop app capability. Running published plugins works in both places. Building them locally is the part that needs the app.

Window and tab management

The rest of the list is about handling many files at once.

• Pinned tabs, which collapse to a favicon on the left of the tab bar
• Tab groups with a name and a color, which can be collapsed
• Split tab view, with two files side by side, or two views of the same file where edits in one appear in the other
• Dragging a tab out into a new window, and dragging tabs between windows
• A tab menu in the top right that lists open and recently closed tabs across all Figma windows
• Muting a single tab when a prototype plays audio
• On Mac only, an option under View to always show tabs when presenting a prototype

Notifications and haptics

Notifications about files, comments and Community activity appear in the Mac menu bar, and Figma marks this as available on the desktop app only. Trackpad haptic feedback can be turned on under Figma menu, Preferences, Trackpad Haptic Feedback. It needs Force Click and haptic feedback enabled in the Mac's trackpad settings.

When the browser tab is the better choice

The desktop build is not automatically the right answer. Several situations favor the browser.

An older Mac. As the table above shows, macOS 11 can run Figma in a browser but cannot run the desktop app. Until the OS is upgraded, the browser is the only route.

Several Figma accounts. The desktop app is one app with one login at a time. Freelancers who work in a client's organization and their own team often keep one account in the desktop app and a second in a browser profile. The beta build can also be logged in to a different account, since Figma says the two builds do not need the same login, but the beta is a test environment and is not meant as a second production seat.

Locked down machines. On a managed Mac where installing software needs approval, the browser works without waiting for IT.

Occasional use. A product manager who opens two files a week to leave comments gains little from split tabs or tab groups. A browser bookmark, or a dedicated window for Figma, covers that need.

Viewing only on a phone. Figma's mobile app, which is the one in the App Store, is for viewing files, commenting, playing prototypes and mirroring frames from the desktop. It is not an editor for Figma Design files.

A reasonable rule: install the desktop app when locally installed fonts matter, when building plugins, or when more than a handful of files are open at once. Stay in the browser when the Mac is older, when switching accounts often, or when Figma is opened only now and then.

Installing Figma across a team

Figma has a separate page for IT administrators, Deploy Figma on macOS, and it adds details that the regular guide leaves out.

Choice	What Figma documents
Install in /Applications	Available to all users. Users need write access to Figma.app for auto updates.
Install in ~/Applications	Single user install. Auto updates work without special permissions.
Universal stub installer	Supports Intel and Apple Silicon, downloads the latest build on first launch. Needs write access to the app bundle.
Architecture specific builds	For setups where the app bundle is not writable. The app does not try to auto update.

The last row has a consequence that is easy to miss. When the app directory is not writable by the user, Figma says desktop app versions are supported for only up to two months, so updates have to be pushed manually and on time. That is a tighter window than the six months mentioned in the general guide, and it applies specifically to installs that cannot update themselves.

Organizations on the Enterprise plan can also use a macOS Enterprise installer to deploy the Figma package to many Macs at once, and there is a separate page on configuring desktop app settings with property lists. For a small team without device management, the simplest path is a per user install in ~/Applications, which keeps auto updates working.

A third option: Figma in its own window, without the full app

Some people want Figma out of the browser tab bar but do not need font access or plugin development. They want a Dock icon, Command Tab switching, and a window that does not get lost among forty other tabs. There are two ways to get that without the official app.

The first is built into macOS. Since macOS Sonoma 14, Safari can save any webpage as a web app through File, Add to Dock. Apple's page on Safari web apps on Mac explains that such a web app shares no history, cookies or website data with Safari, is saved to the Applications folder inside the home folder, and can show a badge for unread notifications in the Dock. For Figma, the Safari engine has to meet the Safari 17.4 minimum from Figma's browser requirements.

The second is a site to app tool built on a Chromium based browser. Tools of this kind wrap one website in its own app with a separate browser profile, so a second Figma account can sit in its own window with its own Dock icon. Chrome extensions keep working in that window. Figma is among the presets listed on the supported services page, and the features page describes how profiles and extensions are kept separate per app.

Neither route adds the two things that only the official desktop app documents: bundled local font access and local plugin development. Fonts in either wrapper still depend on the font installer, just as they do in a normal browser tab.

Need	Official desktop app	Browser tab	Wrapped window
Local fonts without a helper	Yes	No, needs font installer	No, needs font installer
Plugin development	Yes	No	No
Runs on macOS 11	No	Yes	Depends on the tool
Second account side by side	Only via the beta build	Yes, in another profile	Yes, separate profile per app
Own Dock icon	Yes	No	Yes

What to change first

Check the macOS version first. On macOS 12 or later, install the official Figma app from figma.com if local fonts or plugin work matter. If the real problem is a second account or a Figma tab lost in the browser, a wrapped window from Kagemusha covers that without changing anything else in the setup.