Playing TFT on Mac with Discord: audio, mic and screen share

Teamfight Tactics is a solo game that is rarely played in silence. A partner in Double Up, a voice channel running through a ranked climb on EUW or NA, a board you show someone so they can tell you where the frontline belongs: on a Mac, all of that goes through Discord. And Discord on macOS does not behave the way it does on Windows. The system withholds explicit permission for the microphone, for screen recording, and for global keyboard shortcuts, and hands none of them over until you ask. Add the fact that macOS is no longer supported by TFT since patch 18.1 (the game now runs on a Mac from its Android build, inside the launcher) and there are four settings worth knowing before your first voice night. Here they are, in the order they will bite you.

Why Discord and TFT do not get along on a Mac out of the box

On a Windows PC, TFT and Discord are two desktop apps that have shared the same audio stack forever. On a Mac, patch 18.1 changed the picture: Riot removed macOS support when it moved the game onto Unreal Engine, and calls that removal temporary, saying it is working to support the system in a future update, with no date given. There is no native TFT client for macOS any more. What runs on your Mac is the Android build of the game, still developed and patched normally, served by OSFT Launcher inside an ordinary macOS window. Good news for Discord: that window can be captured and shared like any other. Bad news: macOS locks down almost everything Discord needs in order to reach it.

Audio: two streams, one pair of ears

Start with the pleasant surprise, which is that there is nothing to install. macOS mixes game audio and voice chat into the active output on its own, with no driver and no third-party tool. The real problem is never the mixing. It is relative volume and echo.

• Wear headphones. On speakers your mic feeds your own match back into the channel, so everyone hears their voice on a delay with a combat round layered on top.
• Turn the game down rather than turning Discord up. Carousel and combat phases are loud, and a voice cuts through better underneath them than over them.
• Discord sets per-person volume with a right click on a name, which beats a master slider when exactly one friend is too loud.
• Discord noise suppression erases a MacBook Pro fan in a late-game fight, but it also eats the first syllable of a sentence. Turn it off if your room is quiet.

The mic: two permissions macOS never grants on its own

This is the most common failure by a wide margin, and it has nothing to do with Discord. macOS refuses microphone access until you grant it explicitly. A mic that "does not work" on a Mac is nearly always a mic that was never authorised.

1. 1Open System Settings, then Privacy and Security, then Microphone, and switch Discord on.
2. 2On the same screen, open Accessibility and switch Discord on too. Without it, push-to-talk only fires while the Discord window is in front, which means never during a match.
3. 3Quit Discord entirely and relaunch it. A permission granted while the app is running takes effect at the next launch, not immediately.
4. 4In Discord voice settings, confirm the selected input is the one you actually use, and not the built-in Mac mic while you are wearing a USB headset.

Then pick the key carefully. The launcher runs TFT full screen with a keyboard mapping, so if push-to-talk lands on a key already bound to buying experience or rerolling the shop, you will broadcast on every reroll. Choose something the game leaves alone, such as a function key or a Control combination, and cross-check the defaults in our Mac keyboard guide.

Screen sharing: show the board without tanking your own game

Same logic on the video side: macOS blocks screen capture by default. In System Settings, Privacy and Security, Screen Recording, switch Discord on and relaunch the app. Without that box ticked, the share still starts, but viewers get a black rectangle or a frozen still. Once the permission is in place, four habits do the rest.

• Share the launcher window, not the whole screen. Your notifications, tabs and messages stay yours, and the machine has far fewer pixels to encode.
• Leave full screen before you start sharing. A full-screen app owns its own Space on macOS, and one Space switch turns your share into an empty desktop for everyone watching.
• 720p at 30 frames per second is plenty. A TFT board is a near-still image during planning, so sharpness matters far more than smoothness here.
• Stop the share between games. It saves more battery than any other single change, and nobody is studying the post-game screen.

One honest caveat about sharing application audio: it is the flakiest part of Discord on macOS. Depending on your system version and your Discord version, the option is there, missing, or present but silent for viewers. Do not build the evening on it. The approach that never breaks is one sentence long: everyone keeps their own game audio locally and you call the plays with your voice. On a TFT board the decisive information is visual anyway.

What Discord actually costs your Mac mid-match

Screen sharing is not free. Encoding video in real time takes processor time while the game is already using the GPU. On a fanless MacBook Air, a long sharing session eventually pulls clock speed down, and frame rate with it. If your match only stutters while you are sharing, that is your culprit, not your connection. The method for telling a frame-rate drop apart from a genuine network problem is laid out in our piece on lag on Mac, and it applies here unchanged, with the share as suspect number one.

Double Up and tournaments: where voice stops being optional

In solo ranked, voice chat is a comfort. In Double Up it is a game mechanic: you call your items, you warn before sending a unit over, you settle who takes the gold before the timer runs out. The same goes for custom lobbies, where the room code travels through a text channel and the whole event lives on a Discord server. That is also the moment a Mac keyboard pulls ahead of a phone: pasting a code, answering in a channel, switching windows, none of it taking your eyes off the board for more than a couple of seconds. Our rundown of the game modes covers which queues gain the most from being played in voice.