Why Is My MacBook Air Running So Slow: Memory, Tabs and Heat

The machine starts the day quick. By the middle of the afternoon, switching between applications has a delay, the underside is warm, and a video call that was fine last week now drops frames. General advice for a slow Mac applies here, but the Air is a particular machine with two traits that change the diagnosis, and skipping over them leads to hours spent on cleanup that was never going to help. One is how it handles heat. The other is that the memory it shipped with is the memory it will always have.

Two traits of this machine set the boundaries

Apple describes the current MacBook Air design in one phrase that matters more than it sounds.

All with a silent, fanless design. Source: apple.com

No fan means there is no way to increase cooling when work gets heavy. On a machine with fans, sustained load produces noise first and a performance change later. On the Air, the only signals are the case getting warm and the work getting slower, and neither of those is loud.

The second trait is memory. The current configuration is stated on the same page.

512GB of storage and 16GB of unified memory. Source: apple.com

Unified memory on Apple silicon is fixed at the time of purchase. Whatever figure a particular Air was configured with is the figure it keeps for its whole life, which can be confirmed for any machine by opening Activity Monitor and reading Physical Memory in the Memory pane. That single fact changes what a diagnosis is for. On a machine where memory can be added, finding that the working set is too large produces a shopping decision. On an Air, it produces a decision about the working set.

Everything below follows from those two limits, and both of them are visible in tools that are already installed.

Sustained work and short bursts are different problems

An Air handles a demanding task for a short time very well. The pattern that produces complaints is different: work that continues for many minutes without a pause. A long video call, an export, a large build, a browser session with several applications all doing something at once.

The signature is timing. If the machine is quick for the first few minutes of a task and then eases off, and if it recovers after a break, that is thermal behaviour rather than a fault. Open Activity Monitor, choose Window then CPU History, and watch during a long task. A pattern that starts high and settles lower, with the case warm to the touch, is the picture.

Physical conditions matter more on this machine than on one with fans. A laptop on a bed, on a cushion, or in a case rests on a surface that insulates it. Direct sunlight on the lid adds to the same problem. Raising the machine so that air can reach the underside is not a trick, it is the only cooling adjustment available on a fanless design.

There is a useful distinction to draw before blaming heat. Heat makes work slower and then lets it recover. Memory pressure makes switching between applications slow and does not recover until something closes. If the machine is sluggish immediately on waking, before any heavy work has happened, heat is not the explanation.

External displays add to the same budget

An Air driving an external display is doing more work than the same Air on its own, and on a fanless machine the extra work has nowhere to go. It shows up as a warmer case and slightly slower everything, rather than as a specific fault.

The test is straightforward. Disconnect the display, work for ten minutes, and notice whether the sensation changes. If it does, the display is part of the picture, and the practical responses are fewer things animating on screen and fewer live applications open at once rather than any display setting in particular.

Reading memory on a machine that cannot be upgraded

Open the Memory pane and ignore the Memory Used figure, which on a healthy Mac is close to the total by design. The pressure graph is the reading that matters, and Apple's definitions of its colours are brief.

Green memory pressure: Your computer is using all of its RAM efficiently. Yellow memory pressure: Your computer might eventually need more RAM. Red memory pressure: Your computer needs more RAM. Source: support.apple.com

On an Air, yellow that appears during the busiest part of the day and clears afterwards is normal operation. Yellow that arrives at ten in the morning and stays until the machine is restarted is the case worth acting on, because it means the daily set of open applications does not fit and every switch between them involves compression or a read from the disk.

The second figure to read is swap, and its behaviour tells more than its size.

Swap Used: The amount of space being used on your startup disk to swap unused files to and from RAM. Source: support.apple.com

Swap that grew during a heavy morning and then stopped is history. Swap that climbs while the pane is being watched is current, and climbing swap is what produces the specific sensation of clicking an application in the Dock and waiting for it to come back.

The startup disk has a second job

Because swap is written to the startup disk, free space on an Air is not only about where files live. A disk with very little room left gives the system less space for swap, caches and temporary files at the moment it most needs them, which is why a machine can feel adequate at two thirds full and poor near capacity with no change in the work being done.

This interacts with the fixed memory in a way that is specific to these machines. On a Mac with plenty of RAM, a full disk is mostly an inconvenience. On an Air whose memory cannot be extended, swap is doing real work every day, and the disk it writes to needs room to do it. Storage settings, in the General section of System Settings, shows what is taking the space, and the categories that usually matter are backups of phone devices, large media libraries, and downloads that were never removed.

Photo and video libraries deserve a separate mention because they cost twice. They take space, and they also get analysed in the background after imports and after system updates, which is processor work on a machine that has no fan to help with processor work.

Why tab and window counts matter more here

A browser session that a Mac with a lot of memory absorbs without complaint is the same session that puts an Air into a yellow plateau. The reason is not that the Air is a weak machine. It is that the same load has less room to spread into.

The important distinction is between pages and applications. Twenty documentation pages left open cost very little, because nothing in them is running. Six web applications, each holding a connection, each running a timer, each keeping a local database in memory, are six programs running at once. On a fanless machine they also produce continuous low-level processor work, which is the kind of work that makes the case warm without anything looking busy.

This is where the count that nobody keeps becomes the problem. In a single window, a live chat application and a static reference page look identical, so pruning is done by number rather than by kind. The result is that the cheap things get closed and the expensive ones stay.

Video calls sit at the intersection of all of this. The camera pipeline runs continuously, the encoder runs continuously, the window repaints constantly, and the call usually happens alongside every other application that was already open. A call that stutters on an otherwise healthy Air is frequently where the limits first become obvious, which makes it a useful measurement rather than a reason to doubt the machine.

Background work that nobody started

Before concluding that the Air is simply too small for the job, spend two minutes on the CPU pane. Sort the process list by percentage and read the top five rows. The distinction to look for is whether the names belong to applications that were opened deliberately or to macOS itself.

System-owned processes near the top mean the machine is doing its own work. Search indexes and media libraries get rebuilt after a system update, and after a large import of photos or video. That work is finite and it ends, usually within hours, and it runs best on a machine that is plugged in and left awake rather than interrupted.

File sync clients are the other common finding, and they do not end. A shared folder that grew, or a media library pointed at a synced directory, gives a client permanent work reading, hashing and uploading. Pausing it for twenty minutes is the cleanest test there is, because a machine that becomes responsive within a minute has answered the question.

Login Items, in the General section of System Settings, lists both the applications that open at login and the background items installed alongside them. On a machine with fans, three small helpers running permanently are unremarkable. On a fanless one they are three permanent contributions to heat, which is why this list deserves more attention on an Air than it usually gets.

Put together, the patterns above separate cleanly.

Pattern	Likely cause	What helps
Quick for minutes, then slower, recovers after a break	Sustained load on a fanless design	Airflow under the machine, shorter heavy sessions
Slow switching all day, memory pressure yellow	Working set larger than the installed memory	Reduce the number of live applications
Slow launches and saves, disk nearly full	No room for swap, caches and temporary files	Free space on the startup disk
Slow immediately after waking	Not heat, check pressure and swap	Read the Memory pane before anything else
Warm with nothing obviously open	Background analysis or a sync catching up	Check the process list for macOS-owned work
Slow only with an external display attached	Extra display work on top of everything else	Test without the display before changing settings

One arrangement that gives the Air more room

The change that helps most on a machine with fixed memory is to stop treating always-open applications and disposable pages as the same thing. Applications that must be live all day are a permanent cost. Pages opened to read once are not, and they are the ones that get closed when a session is pruned by number.

Running each application in its own isolated space makes the permanent cost visible and countable, which is the point. Five windows can be reviewed and reduced to three. A strip of forty tabs cannot. The separation also means that when one application misbehaves, reloading it does not disturb everything else, which matters more on a machine where restarting a browser means every application inside it reloads at once. The workspaces page covers how that separation is arranged, and the list of supported apps shows the kinds of services people usually keep permanently open.

What to change first

Read the Memory pane for a working morning and note whether pressure returns to green between tasks, because that single observation separates a heat problem from a memory problem. If pressure plateaus in yellow, reduce the number of live web applications rather than the number of tabs, and make sure the startup disk has room for swap to work in. If the same applications have to stay open every day, give each one its own window and its own login, which is the arrangement SpaceDeck is built around on macOS.