How to stream TFT on Mac: recording and going live

Recording your Teamfight Tactics games and streaming them live are two separate projects, and treating them as one is the fastest way to load a laptop for nothing. Recording wants a file on disk and nothing more. Streaming wants continuous encoding, an overlay, usually a camera, all of it while the match is already running. On a Mac there is one extra layer worth knowing about: since patch 18.1, the one that opened Set 18 and moved TFT onto Unreal Engine, macOS is no longer supported by the game, with neither support nor fixes. Riot calls that removal temporary and says it is working to support the system in a future update, with no date announced. What runs on your machine is the Android build, still supported, served by OSFT Launcher inside an ordinary macOS window. For capture that is good news, because the window records and streams like any other. If the launcher is not installed yet, our install guide covers it in a few minutes.

Reviewing your games and broadcasting them are not the same job

A recording exists so you can read yourself back: why a comp melted the moment the lobby started levelling, where a prep phase went slow, which fight was worth showing to a friend. The file lands on disk, nobody watches it being written, and a dropped frame somewhere costs no one anything. A live stream has to produce a steady picture without pause: the encoder never stops, the upload runs the whole time, and every stutter is seen by everyone at once. The first job runs on a modest machine. The second needs headroom the game has already eaten into, which is exactly why the two are not configured the same way.

• To review yourself: the built-in macOS tool is enough, there is nothing to install and setup takes a minute.
• To broadcast: you need a scene-based tool such as OBS as soon as you want an overlay, a camera, several sources, or an upload to a streaming platform.
• To show a match to two or three friends, a voice-channel screen share is still simpler than a real broadcast.
• Either way the source is the same: the launcher window, and only the launcher window.

Record a TFT game on a Mac with nothing installed

macOS ships its own capture bar, opened with Shift + Command + 5. It offers the whole screen or a selected portion, and depending on your version of the system, one specific window. That is plenty for reviewing yourself: the file goes to whatever folder you pick in the Options menu, and the machine handles the encoding without bringing the match to its knees. One limit to know before you build a channel on it: depending on the version of macOS, this tool does not necessarily record system audio, so it may not record the game. That is one of the reasons people move to OBS, though not the only one.

1. 1Take the launcher out of full screen and give its window the size the video will have. What you frame now is what you get later.
2. 2Press Shift + Command + 5, then pick window recording if your system offers it, otherwise frame the selection on the launcher window.
3. 3Open the Options menu and set the destination folder before you start, rather than hunting for the file afterwards.
4. 4Start, play, then stop from the menu bar icon. A recording left running through a whole evening fills a disk faster than you would think.

Where OBS starts to earn its place

OBS becomes necessary the moment something other than the game is on screen: an overlay with your name and rank, a camera, a break screen between matches, an upload to a streaming platform. The idea fits in two words, sources stacked into scenes. A game scene with the launcher window and the camera, a break scene with a still image, and you switch between them without ever touching the match. The Mac-specific point: every source you add is extra work for the processor, and an animated overlay costs more than a static one. Start with two scenes and nothing else, then add only what you actually miss.

Capture the launcher window, never the entire screen

This is the setting that changes everything, and the one most beginners get wrong, because capturing the whole screen requires no thought at all. Except the whole screen also means your notifications, your tabs, your file names and the chat window you open without thinking at the end of a match. A window capture shows the window and nothing else, so everything else can happen on top without ever appearing. It has a second, less obvious benefit: it follows the window. Switch desktops, move the launcher, open something over it, and the broadcast picture does not flinch. And with fewer pixels to encode than a full screen, the machine gets some room back. If you play on two displays the question disappears entirely, because the second screen becomes the place for everything that must not be seen.

The macOS full screen trap

An app sent to full screen with the green button does not fill your desktop: macOS builds it a Space of its own, and you switch into it the way you switch desktops. For capture that is the fastest route to a frozen picture, an empty wallpaper or a black rectangle the moment you go back to your usual desktop to read a message. The rule is simple: to record or stream, play in a window, enlarged to the edges of the display if you like. You lose the height of a menu bar and you gain a capture that never cuts out.

The Screen Recording permission, and the relaunch it demands

1. 1Open System Settings, then Privacy and Security, then Screen Recording.
2. 2Switch on the app doing the capturing, OBS or another broadcast tool. The built-in macOS capture bar does not need to appear in that list.
3. 3Quit the app completely, then relaunch it. A permission granted while it is running only takes effect at the next launch, which is exactly why half of all users decide the checkbox does nothing.
4. 4Then check that the list of capturable windows actually contains the launcher. An empty or short list almost always means the previous step was skipped.

What encoding costs a fanless MacBook

Encoding video while a game runs is never free. The game is already using the GPU, encoding takes its share, and on a fanless chassis the heat eventually pulls the clock down. The symptom is easy to recognise: the game is smooth early in the evening and gets sluggish later on, with nothing else changed. The test that settles it takes two games. Play one with no capture at all, play a second one while streaming, and compare. If only the second one struggles, the culprit is neither the game nor your connection. The full method for telling a frame rate drop apart from a real network problem is in our article on lag, and it applies here with the encoder as first suspect. On battery, remember that capture is added on top of rendering and shortens the session, as our battery article lays out.

Encoding bigger than you display: the most common waste

Here is the trade-off almost nobody makes, and it weighs more than all the others put together. On one side, the size of the launcher window, which is what the game has to draw. On the other, the output resolution of the stream, which is what the encoder has to produce. When the second is larger than the first, the software is enlarging a picture that holds no extra detail: you pay for the computation and the viewer sees nothing better. The reverse, a window much larger than the output, makes the game draw pixels that get shrunk a moment later. So line the two up: pick the output resolution your machine holds without straining, then size the game window to match. On a laptop that runs warm, stepping that output down one notch buys more headroom than any exotic setting.

What must never make it on screen

• Notifications: turn on a Focus mode before you start, it is the one setting that silences messages, reminders and app banners in a single move.
• The chat window and the browser: a window capture keeps them out, but park them on another desktop anyway, because a misconfigured share happens fast.
• The second display: check what is on it before you begin, since it becomes visible the moment you capture a screen instead of a window.
• The desktop itself: file names, screenshots, work in progress, it is the most talkative backdrop a Mac has.
• Launcher windows that are not the match: settings, account, licence, all of that happens before the capture starts.

Framing a turn-based game: the board and the shop carry everything

An auto battler is not filmed like a shooter. There is no aim to follow and no reflex to admire: the information sits in the board, the shop and the opponent list, and that is where the viewer looks from start to finish. The practical consequence is blunt, the camera does not need to be big. A thumbnail in a corner is enough, placed where the game writes nothing, never over the shop or the bench. Same logic for the overlay: a discreet bar beats a frame that crops the board. And since the planning phase is a nearly static picture, text legibility matters more than smoothness, so a sharp board at a modest frame rate reads better than a fluid blurry one. The rest is commentary, and that is what TFT vods lack most, showing the final comp without ever explaining why it was picked.

The checklist before you hit record

• Launcher in a window, never full screen.
• Capture source: the launcher window, not the display.
• Screen Recording permission granted, app relaunched afterwards.
• Output resolution chosen first, window size lined up with it.
• Focus mode on, chat app and browser out of frame.
• One control game with no capture, so you know what your machine looks like at rest.