M1 MacBook Air is sluggish after macOS Tahoe update with 8GB memory

M1 MacBook air very sluggish when running Tahoe or later, including, being slow, experiencing lag-spikes commonly, A lot of stuff is very slow, This problem is system-wide, I believe the liquid glass is the problem because it uses extra graphics that use the GPU power, and memory, I believe so because I have downgraded it to Sequoia, and it’s perfectly working, everything is smooth and fast and no performance drops at all.

Bottleneck is believed to be the 8GB Physical memory


Here’s what I’ve done or what I have and everything I’m aware of:


  • I’ve reset it multiple times
  • Updated to Tahoe after resetting the Mac, set up as new.
  • No cleaner apps, No anti-viruses, Already know how macOS security works
  • Also tried to set it up and restore from my sequoia backup on Tahoe, it worked but still sluggish
  • No outdated applications
  • No other web browsers are used except safari, with light usage
  • Already know that the first week, It will be slow due to indexing of the major update, but it is STILL sluggish, after waiting for weeks
  • Battery health is at 81%


It’s SYSTEM-WIDE LAG, not just browsing performance drops, Memory usage when Mac is first turned on is 6GB of 8GB on Tahoe, Approx. 4GB of 8GB on Sequoia


I was advised by a member of the community that their M2 Mac mini with 8GB of memory works perfectly on Tahoe and there are no performance drops, putting doubt into my mind that whether something is wrong with my Mac, and whether 8GB really is suitable for liquid glass and Tahoe.


If anyone wants to say “The MacBook Neo has 8GB memory and it came with Tahoe as its first OS”, You’re right, BUT the m1 was made for big sur, and the Neo was made for Tahoe, Performance can be compared

Correct me if I’m wrong, Thank you.


Earlier Mac models

Posted on Sep 24, 2026 12:55 AM

Reply
Question marked as Top-ranking reply

Posted on Sep 24, 2026 8:23 AM

Your testing points to a substantial difference between macOS Tahoe and Sequoia on your M1 MacBook Air, but it does not yet establish that 8 GB of memory is the bottleneck.


Apple officially supports the M1 MacBook Air (2020) on macOS Tahoe, so your configuration is within Apple's supported hardware range. (Apple Support)


The most significant part of your testing is that the same physical Mac is smooth and responsive on Sequoia but consistently sluggish on Tahoe. You have also tested Tahoe after resetting the Mac and setting it up as new, and you allowed substantial time for indexing to finish. 


This is important because restoring or migrating from a previous macOS installation can transfer applications, user accounts, settings, and other data. 


Consequently, a migrated environment can potentially reintroduce an application, setting, or other component that could contribute to a problem that would not occur on a genuinely clean installation.


Apple documents what Migration Assistant transfers here. (Apple Support)


Because you also tested Tahoe as a new installation without restoring your previous environment and still experienced the same sluggishness, the problem cannot reasonably be attributed simply to something inherited from your Sequoia installation. That strengthens the evidence for a Tahoe-specific issue on this particular Mac/configuration.


The approximately 6 GB of memory used after startup should not be treated as proof that the 8 GB is exhausted. Apple explains that macOS uses available memory efficiently, including for cached files. The relevant measurements are Memory Pressure, Swap Used, and compressed memory. Persistent yellow or red memory pressure, particularly while the lag is occurring, would provide much stronger evidence that the 8 GB configuration is contributing to the problem. (Apple Support)


Your Liquid Glass explanation is possible, but it should remain a hypothesis rather than a conclusion. Tahoe's redesigned interface changes the graphical workload, but your observations alone cannot establish that Liquid Glass itself is consuming enough GPU or memory resources to cause the system-wide slowdown.


A useful test is to enable Reduce Transparency and Reduce Motion in System Settings → Accessibility → Display. If responsiveness improves substantially, that would provide evidence that Tahoe's visual effects are contributing to the problem. It would not, by itself, prove that GPU usage or 8 GB of memory is the underlying bottleneck.


The 81% battery health figure also does not, by itself, explain the Tahoe-versus-Sequoia difference. It is worth checking whether macOS reports Normal or Service Recommended battery health rather than treating the percentage alone as evidence of a performance problem.


The most useful test now is to open Activity Monitor while a lag spike is actually occurring. Check Memory Pressure and Swap Used, but also CPU, GPU, and Disk activity and whether a particular process becomes unusually active at the same time. This can help distinguish memory pressure from CPU, graphics, storage, or another system-process issue.


Because the M1 MacBook Air's unified memory is not user-upgradable, sustained memory pressure would be significant evidence that the 8 GB configuration is a genuine limitation for that workload. Conversely, if Memory Pressure remains green and swap activity is low while the system is lagging, the evidence for 8 GB being the cause becomes considerably weaker.


Therefore, the most accurate conclusion is: 8 GB may limit the performance headroom of the M1 MacBook Air under Tahoe, but your current evidence does not prove that it is the bottleneck. What your testing demonstrates much more clearly is a substantial Tahoe-versus-Sequoia performance difference on the same Mac. Because the problem also occurs on a clean Tahoe installation, migration from Sequoia is unlikely to be the explanation. Activity Monitor measurements during an actual lag spike are needed to determine whether memory pressure, graphics, CPU, disk activity, or another Tahoe process accounts for the difference.


Apple's relevant documentation includes Transfer to a new Mac with Migration Assistant, which explains what Migration Assistant transfers, and Restore your Mac from a backup, which explains restoring information from a Time Machine backup. (Apple Support)

12 replies
Question marked as Top-ranking reply

Sep 24, 2026 8:23 AM in response to Mu-iOS

Your testing points to a substantial difference between macOS Tahoe and Sequoia on your M1 MacBook Air, but it does not yet establish that 8 GB of memory is the bottleneck.


Apple officially supports the M1 MacBook Air (2020) on macOS Tahoe, so your configuration is within Apple's supported hardware range. (Apple Support)


The most significant part of your testing is that the same physical Mac is smooth and responsive on Sequoia but consistently sluggish on Tahoe. You have also tested Tahoe after resetting the Mac and setting it up as new, and you allowed substantial time for indexing to finish. 


This is important because restoring or migrating from a previous macOS installation can transfer applications, user accounts, settings, and other data. 


Consequently, a migrated environment can potentially reintroduce an application, setting, or other component that could contribute to a problem that would not occur on a genuinely clean installation.


Apple documents what Migration Assistant transfers here. (Apple Support)


Because you also tested Tahoe as a new installation without restoring your previous environment and still experienced the same sluggishness, the problem cannot reasonably be attributed simply to something inherited from your Sequoia installation. That strengthens the evidence for a Tahoe-specific issue on this particular Mac/configuration.


The approximately 6 GB of memory used after startup should not be treated as proof that the 8 GB is exhausted. Apple explains that macOS uses available memory efficiently, including for cached files. The relevant measurements are Memory Pressure, Swap Used, and compressed memory. Persistent yellow or red memory pressure, particularly while the lag is occurring, would provide much stronger evidence that the 8 GB configuration is contributing to the problem. (Apple Support)


Your Liquid Glass explanation is possible, but it should remain a hypothesis rather than a conclusion. Tahoe's redesigned interface changes the graphical workload, but your observations alone cannot establish that Liquid Glass itself is consuming enough GPU or memory resources to cause the system-wide slowdown.


A useful test is to enable Reduce Transparency and Reduce Motion in System Settings → Accessibility → Display. If responsiveness improves substantially, that would provide evidence that Tahoe's visual effects are contributing to the problem. It would not, by itself, prove that GPU usage or 8 GB of memory is the underlying bottleneck.


The 81% battery health figure also does not, by itself, explain the Tahoe-versus-Sequoia difference. It is worth checking whether macOS reports Normal or Service Recommended battery health rather than treating the percentage alone as evidence of a performance problem.


The most useful test now is to open Activity Monitor while a lag spike is actually occurring. Check Memory Pressure and Swap Used, but also CPU, GPU, and Disk activity and whether a particular process becomes unusually active at the same time. This can help distinguish memory pressure from CPU, graphics, storage, or another system-process issue.


Because the M1 MacBook Air's unified memory is not user-upgradable, sustained memory pressure would be significant evidence that the 8 GB configuration is a genuine limitation for that workload. Conversely, if Memory Pressure remains green and swap activity is low while the system is lagging, the evidence for 8 GB being the cause becomes considerably weaker.


Therefore, the most accurate conclusion is: 8 GB may limit the performance headroom of the M1 MacBook Air under Tahoe, but your current evidence does not prove that it is the bottleneck. What your testing demonstrates much more clearly is a substantial Tahoe-versus-Sequoia performance difference on the same Mac. Because the problem also occurs on a clean Tahoe installation, migration from Sequoia is unlikely to be the explanation. Activity Monitor measurements during an actual lag spike are needed to determine whether memory pressure, graphics, CPU, disk activity, or another Tahoe process accounts for the difference.


Apple's relevant documentation includes Transfer to a new Mac with Migration Assistant, which explains what Migration Assistant transfers, and Restore your Mac from a backup, which explains restoring information from a Time Machine backup. (Apple Support)

Sep 24, 2026 8:58 AM in response to Mu-iOS

As suggested by myself and Owl, check the colour of the memory pressure when you are experiencing a performance lag.


If the pressure is actually green your memory is unlikely to be the culprit.


One possibility could be thermal throttling although that should not be occurring when the machine is under a light load unless you are working in an incredibly hot place or have your MBA sinking into a carpet or blanket which can cut off the ventilation.


Because it is fanless you should always have it seated on a hard surface and out of direct sunlight etc.

Sep 24, 2026 9:17 AM in response to Mu-iOS

If Liquid Glass really is the cause of the problem you can't disable it but you can reduce its impact on processing power.


System Settings>Accessibility>Display . . . . toggle ON "Reduce Transparency".


System Settings>Appearance . . . change Liquid Glass from Clear to Tinted. Also if you go lower down you can turn off "Tint window background with wallpaper colour"


System Settings>Accessibility>Motion . . . switch ON "Reduce Motion".


These adjustments do not disable LG completely but make the OS look more like Sequoia and should reduce the LG's need for extra processing power.

Oct 1, 2026 11:59 AM in response to Mu-iOS

Bottleneck is believed to be the 8GB Physical memory


Don't assume. Confirm for yourself. Read Check if your Mac needs more RAM in Activity Monitor - Apple Support. If its unitless "Memory Pressure" graph is consistently "green" then it is not the performance-limiting factor you suspect. Conversely, if it is frequently "yellow" or "red" the next step is to identify the resource-demnading process(es) responsible, and proceed on the basis of that knowledge.


Of course you cannot add any more memory than that Mac already has, but at least you can rule out that suspicion, or take corrective action.


Here’s what I’ve done or what I have and everything I’m aware of:
...
• No cleaner apps, No anti-viruses, Already know how macOS security works


Respectfully, EtreCheck will also confirm that. Post its report in a reply as suggested by others. It's not you, it's the multitude of reports from users who thought the same thing, until the EtreCheck report proved otherwise.


Apps are only one possibility, since other non-Apple products and services can affect a system in ways that are less apparent. Even if something notorious for causing trouble was installed and subsequently uninstalled, perhaps long ago, their effects can still remain. macOS updates or upgrades tend to reveal those effects.

Sep 24, 2026 7:16 AM in response to Mu-iOS

Hello,


I understand your frustration, and it’s totally valid. 8GB of RAM is definitely a hard limit, and it makes sense your MacBook Air is very laggy. Your point that MacBook Neo was made for Tahoe is also 100% valid. Honestly, as a power user of macOS, I will tell you right now:

  1. Open activity monitor
  2. Go to the Memory section
  3. on the bar under window management (the quit, minimize and maximize) there is a word which says memory, and shows "mem" of you have the activity monitor maximized.
  4. on that tab, make sure the arrow head is pointing DOWN to ensure most RAM consuming is on the top
  5. Check things that use most RAM, and quit them if not needed
  6. Also, check memory used and swap memory, this plays a big role as the SSD is slower than the RAM.

In my case:

Hope this helps,


Thanks, 

Sep 24, 2026 6:56 AM in response to Mu-iOS

Memory usage is confusing to many people and they get the wrong impression that they haven't got enough.


Macs are designed to use most of their memory even when idling . . . think of a car engine which has all its cylinders firing whether it's idling or going at full speed.


Using most of the memory all the time means that your Mac can accelerate rapidly the moment a stressful task is thrown at it.


If you had 32 GB RAM you would probably see most of it being used whilst idling.


For the first 20 years of owning a Mac I kept looking at the memory usage and feeling there wasn't enough.


Take a look at my M4 with 16 GB RAM. At the moment I am just sitting watching the screen and 75% of my memory is being used.


The important thing is the Memory Pressure which is shown by the green area. As you increase the workload that will turn yellow and when you are really stressing your machine it will go red.


Anyway you may have noticed that I am the only one replying after several hours which is why I advised you to copy your question onto the Tahoe forum which has many more users.


P.S. I noticed that I had several apps open so I closed them and the memory used dropped slightly to just under 75% . . . a negligible decrease.

Sep 30, 2026 5:45 AM in response to Owl-53

I have a 2020 M1 MacBook Air, 8GB RAM, 512GB SSD that worked very smooth on all versions of Tahoe and now on Golden Gate.


Every user system is different with different items installed on them and previously installed on them (improperly removed apps can leave hidden demons that can raise their heads at any time). Add to that the complexity occurrent operating systems and you will end up with some systems that have issues and others that don't.

M1 MacBook Air is sluggish after macOS Tahoe update with 8GB memory

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.