Source: https://fnflow.app/fn-key-dictation-mac

# Why holding fn doesn't work for dictation on Mac (and how to fix it)
Dictation apps like the fn key because nobody presses it while typing. macOS likes it too and gives it a job of its own. If holding fn opens the emoji picker, switches your keyboard layout or starts Apple's dictation, the cause is one menu in Keyboard settings.

## What macOS does with 🌐/fn

System Settings → Keyboard has a menu called "Press 🌐 key to" ("Press fn key to" on Macs whose key is labeled fn). Apple lists four options:

- Change Input Source switches between keyboard layouts.
- Show Emoji & Symbols opens the Character Viewer.
- Start Dictation starts Apple's dictation when you press the key twice.
- Do Nothing leaves the key alone.

The setting can also change without you opening that menu. Apple's dictation help says that choosing "Press Fn Key Twice" as the Dictation shortcut switches the Keyboard option to Start Dictation automatically.

A dictation app that listens for fn has two choices. It can try to swallow the key, and Wispr Flow's documentation says holding fn alone blocks the system action. Or it can pass the event on unchanged, as FnFlow does. Then macOS still sees the press and does whatever the menu says, so the Character Viewer pops up or the layout changes on top of your recording.

## Check the setting from Terminal

defaults read com.apple.HIToolbox AppleFnUsageType
A value of 0 means Do Nothing. On our Macs, 3 meant Start Dictation. This preference isn't a documented API, so treat the numbers as our observation and trust System Settings if they disagree.

## How an app catches a modifier key

Pressing fn on its own doesn't produce a keyDown event. A dictation app creates a Core Graphics event tap with CGEvent.tapCreate, listens for flagsChanged events and checks the secondary fn flag. fn arrives as keycode 63 and right ⌘ as keycode 54. Since left and right ⌘ share the same command flag, the app also checks the device-specific bit NX_DEVICERCMDKEYMASK (0x10) to make sure it's the right one.

let mask = (1 << CGEventType.flagsChanged.rawValue) | (1 << CGEventType.keyDown.rawValue)
let tap = CGEvent.tapCreate(tap: .cgSessionEventTap, place: .headInsertEventTap,
options: .defaultTap, eventsOfInterest: CGEventMask(mask),
callback: callback, userInfo: nil)

// inside the callback, for keycode 63
let fnDown = event.flags.contains(.maskSecondaryFn)
// for keycode 54 (right ⌘)
let rightCmdDown = event.flags.rawValue & 0x10 != 0
Apple's docs describe two kinds of tap. A listen-only tap (.listenOnly) is a passive listener, and an active tap (.defaultTap) is a filter that could change events. The docs don't spell out which privacy permission each one needs, so here is what we've seen. The listen-only tap needed Input Monitoring. With Accessibility granted, macOS let FnFlow create an active tap without Input Monitoring, and VoiceInk's open-source code takes the same route. That's one prompt fewer, and it matters because Input Monitoring often needs an app restart before it works, while Accessibility applies right away.

## Ways to fix it

The simplest is to set "Press 🌐 key to" to Do Nothing. fn is then free for any app, and you give up the one-press system shortcut.

The other option is a different key. Right ⌘ sits under your thumb and rarely matters on its own. Spokenly uses it by default, and Superwhisper defaults to ⌥Space. The app has to handle one catch: if you hold right ⌘ and press C, that's a copy, and dictation shouldn't start.

If Apple's own dictation is accurate enough for you, you can also leave fn on Start Dictation and use that. It starts on a double press, which is different from holding a key while you talk.

## What FnFlow does

On first launch FnFlow reads AppleFnUsageType. If it's 0, the dictation key is fn. If 🌐 does anything else, FnFlow picks right ⌘, so you don't have to visit Keyboard settings, and every hint in the app names the key it chose. FnFlow never changes the system setting itself, and you can switch keys in Settings whenever you like.

Any other key pressed while you hold the dictation key turns the press into a shortcut, so ⌘C with right ⌘ never records. Very short taps are ignored as well. When we went through the first 1,295 recordings, 70 had failed, and nearly all of them were shorter than 1.3 seconds because fn had been brushed on the way to another key. Recordings under 0.6 s now skip recognition.

## Questions

**Is it safe to set the 🌐 key to Do Nothing?**
Yes. It only changes what a press of that one key does, and you can switch it back in the same menu at any time.

**My keyboard has no 🌐 key. Where is the setting?**
In the same place. Apple's help calls it "Press fn key to" on Macs whose key is labeled fn and "Press 🌐 key to" on newer keyboards.

**Why does my dictation app ask for Input Monitoring?**
Probably because it uses a listen-only event tap. In our experience an active tap works with Accessibility alone, which dictation apps need anyway to paste text. FnFlow asks for Input Monitoring only if the active tap can't be created.

**Will right ⌘ break my ⌘ shortcuts?**
Not in FnFlow. If you press any other key while holding right ⌘, FnFlow treats it as a shortcut and doesn't start a recording.
