Alfred on Mac: how to set it up

The app is installed, the preferences window is open, and there are eight tabs with no obvious starting point. The usual outcome is to leave everything at defaults, use it as a plain app launcher, and discover six months later that a feature was never working because a permission dialog got dismissed during a meeting.

Setup order matters here more than it does for most utilities, because several features fail silently when their prerequisites are missing. This is the order that avoids that, drawn from the vendor's own documentation.

Get it from the right place

The first decision is the download source, and it has a trap in it.

Searching the Mac App Store returns an app with the same name. That listing is version 1.2 and is no longer updated. Following a June 2012 change in Apple's requirements, current versions are distributed exclusively from the vendor's own site. Anyone who installs the App Store listing gets software more than a decade behind the current release.

The vendor also publishes a note about third party unzipping tools causing problems with fresh installations, and recommends sticking to the standard macOS handling of the downloaded file. This is a small thing that produces a confusing failure, so it is worth respecting.

The minimum supported system is macOS 10.14, with a warning dialog shown at startup below that. The current release is 5.7.3, dated 1 April 2026. Support for macOS 26 arrived in 5.7 in September 2025, which also rewrote how the app searches macOS System Settings. On older builds, that part of the behaviour will not match current documentation.

The four decisions in General preferences

Open the General tab first. Four things there need an actual decision.

Launch at login. A checkbox. The app has to be resident to be summoned, so unless this is a trial run, it goes on.

The hotkey. The default is Option and Space, chosen specifically so it does not collide with the system search shortcut on Command and Space. Moving it to Command and Space is possible and is what many people want, but it requires disabling or reassigning the macOS shortcut first. The vendor maintains a separate page for that one change, which is a fair indication of how often it goes wrong.

Location. Setting a country makes web searches use regionally appropriate sites, such as a local Amazon or Google. Choosing International instead returns non-localised results, which is the better choice for anyone who works primarily in English regardless of where they are.

Permissions. This one is large enough to deserve its own section.

Permissions decide which features actually work

Since macOS 10.14, Apple has split into separate grants what used to be a single level of access. Several features depend on these grants and fail quietly without them. The app requests them at first launch, and offers a way to request them again later:

Alfred will ask for permissions when you first launch Alfred, but you can also find a quick-access "Request Permissions..." button in Alfred's General Permissions. Source: alfredapp.com

Two grants carry most of the weight.

Accessibility is required for snippet expansion, for simulating key events from workflows, for clipboard integration, and for system commands. Without it, those features appear configured and do nothing.

Full Disk Access is required for reading user level files, which is what makes browser bookmark search possible.

The failure mode is worth naming because it is so common: a feature gets enabled in preferences, a system dialog appears at an inconvenient moment, it gets dismissed, and the feature is then permanently non-functional with no error message. The vendor's troubleshooting section has separate entries for granting permissions after saying no, and for re-granting permissions that were given but stopped working, which is the situation after a reinstall or a major system upgrade.

The rule that follows: when something that used to work stops working, check permissions before checking anything else.

It is also worth granting both up front rather than waiting for a feature to demand one. Granting Accessibility on day one costs nothing if snippets are never used, and it removes an entire category of confusing behaviour later. The alternative, granting each one at the moment a feature first misbehaves, means diagnosing the same problem repeatedly across months, each time from scratch, with no error message pointing at the cause.

Five things worth learning in week one

The feature list is long. The subset that pays off immediately is short, and all of it is in the free version.

• Launching apps and files. Summon the window, type part of a name, press Return. Result ordering adapts to what actually gets opened.
• Web search. Built in search sites plus custom ones. Assigning a keyword to a frequently used site turns a three step navigation into one line of typing.
• The calculator. Type an expression, get a result, press Return to put it on the clipboard.
• Spelling and definitions. Look up a word without opening a dictionary app.
• System commands. Sleep, empty Trash, start the screen saver, all by keyword.

Two more are worth adding once those are automatic: tapping Shift on a selected result gives a Quick Look preview without opening the file, and Large Type throws text such as a phone number across the screen at readable size.

Of these, custom web searches tend to deliver the largest return for the smallest effort, and they are the most often skipped. Any site with a predictable search URL can be turned into a keyword, which collapses the usual sequence of switching to a browser, opening a tab, loading the site and clicking into its search box down to a few characters. Issue trackers, internal wikis, documentation sites and package registries are all good candidates. Adding three or four of the sites visited most often, on the first day, changes the app from a faster app launcher into something that materially shortens a working day.

There is also a preferences feature that saves a lot of searching for answers. Every section of the preferences window carries a question mark icon, and clicking it opens the documentation page for that specific feature. When an unfamiliar option appears, that is faster than looking it up externally, and it is the reason the settings screens can afford to be terse.

Resist configuring workflows and snippets in the first week. Those are the features people set up enthusiastically and then forget how to trigger, because the invocation habit was never built. The base habit comes first.

When search misses

The most common complaint after a week is result quality: the wrong app ranks first, or a known file does not appear. There are three places to look, in order.

First, use the file search keywords rather than expecting everything in the default results. The vendor's own framing is that keyword based file search is what keeps the default results fast and focused. Dumping every file type into default results makes the whole thing slower and less accurate.

Second, check the result count and ordering settings. Release 5.7.2 changed the default result limit options to 40, 50, 75 and 100, and changed file search so that results arrive from macOS pre-sorted, a consequence of changes in the underlying metadata index. If that ordering feels wrong, the previous behaviour is still available under Features, File Search, Search, Default Order. Search behaviour changing without any settings being touched is usually explained by an update, not by anything on the machine.

Third, suspect the system index itself. The Advanced tab has an option to rebuild macOS metadata, which opens Terminal and runs mdutil. The documentation warns this may take over an hour, so it is not something to start five minutes before a meeting.

One related note from the same release cycle: contacts search using metadata is documented as available on macOS 15 and earlier. Contacts disappearing from results after a system upgrade may be explained by that rather than by a broken configuration.

Settings that are easier to decide now than later

A few options change behaviour in ways that are awkward to retrofit.

Query history is off by default. Enabling it in Advanced makes the app remember the last 20 typed queries, with an additional option to automatically show the most recent one if the window is summoned within 5 minutes of the last query. Useful for repetitive lookups, and a reasonable thing to leave off on a machine that gets screen shared often.

Forced keyboard matters for anyone using more than one input source. Advanced can pin the app to a single input language so the search field does not inherit whatever the last app was using.

Action modifiers let Control, Option and Command each trigger an alternative action when held before pressing Return. Easy to miss entirely, and the kind of thing that is much harder to adopt after a year of muscle memory built without it.

Preferences syncing should be decided before the second Mac enters the picture. Settings can be kept in a shared folder so multiple machines read the same configuration. Turning it on later means choosing which machine's settings win, and losing the other set.

Also worth knowing before it is needed: the documented removal procedure is to quit from the menu bar item and drag the app from Applications to the Trash. The vendor specifically advises against app cleaner utilities, on the grounds that they can be overzealous and remove files the current version still depends on.

What to do about the menu bar item

Installation adds one more icon to a row that was probably already full. Since the app is summoned by hotkey, that icon will rarely be clicked, which makes it look like an obvious thing to remove.

It is, eventually. It is not on day one. Until the hotkey is automatic, that icon is the only guaranteed route back into the app, and the vendor has a standalone troubleshooting page for people who hid it and then could not find the app again. The setting lives in Appearance, behind Options in the bottom left, and can be flipped at any time.

A more useful sequence is to leave it alone for a few weeks, then review the whole menu bar at once rather than app by app. With a dozen resident utilities, handling the row in one place is what makes the decision revisable later. The Features page covers what that kind of tool does, and How it compares sets it against hiding icons through each app's own preferences.

What to change first

Do the General tab and the permissions today, before anything else, because everything else silently depends on them. Leave the menu bar question for a month, and when it comes up, look at all the icons together rather than this one. Koffret is one way to handle that part.