A slow MacBook Air needs measurements taken while the delay is happening. Open Activity Monitor and compare the CPU list with the Memory Pressure graph; then check free storage. A busy application, pressure from several open workloads and a nearly full startup disk lead to different remedies. Installed RAM alone does not decide which is responsible, and a memory-cleaner app does not supply that diagnosis. First save work and restart. Reproduce the same delay with your usual apps, then quit one suspect app and repeat it. If that changes the result, investigate the app or its documents before reinstalling macOS.
If the whole Mac remains slow with ordinary workloads and adequate free space, record the macOS version and measurements for Apple. Keep a backup before removing large files, clearing an app’s stored data or attempting a repair.
Differential
Likely causes of “Apple MacBook Air runs slowly”, and how to tell them apart
- 1
One demanding or stuck process
What separates it The delay follows a particular app or document
How to confirm Repeat the action after saving and quitting that app.
- 2
Too much simultaneous memory demand
What separates it The pressure graph changes as workloads open and close
How to confirm Compare responsiveness after reducing the workload without installing a cleaner.
- 3
Too little room on the startup disk
What separates it Storage is nearly full before the slow task begins
How to confirm Move a verified copy of a large file off the disk, then check both free space and the task.
Before you touch a setting
Record this first — changing settings destroys the evidence
- Whether the slowness began after a macOS update and which build
- The top processes by CPU in Activity Monitor
- Free storage and memory pressure
- Whether Reduce Transparency helps
Try in this order
0 of 6 completedMeasure processor use during the delay
ReversibleIn Activity Monitor, select CPU and sort the process list. Watch whether the same app stays busy while your document or browser is slow, then save its work and quit it normally to compare.
Read pressure instead of unused memory
ReversibleSelect Memory. Apple describes green pressure as efficient memory use; yellow or red calls for reducing the workload. Close a large project or several tabs and see whether the graph and responsiveness improve together.
Review the startup disk
Signs you outUse Apple menu, System Settings, General, Storage. Move a backed-up project or remove known downloads if the disk is nearly full. Empty Trash only after confirming you no longer need those files.
Separate login activity from the app
ReversibleNote what opens when you sign in. Temporarily remove an unnecessary login item through the appropriate settings, restart and repeat the original task; restore it if the comparison makes no difference.
Compare the same task in a second account
ReversibleUse a small test document that the account can access. A faster result points toward account-specific apps or preferences, but a different file or empty workload is not a fair comparison.
Escalate with measurements
ReversibleTake a note or screenshot of the busy process, pressure color, available storage and the action that becomes slow. Redact document titles or account details before sharing it.
Model-specific
What is true of this model and not of its siblings
- A worked comparison
- Suppose editing is slow with a large video project open and memory pressure is red. Save the project, close it and repeat a simple browser action. If the graph returns to green and browsing recovers, the workload matters. That observation is stronger evidence than assuming that an M4 chip should make every combination of apps fast.
- When a green graph changes the next step
- Green pressure does not promise that an app is responsive. Check CPU activity and the file location next. A document on a slow external drive or a remote service can stall while the Mac itself has spare memory; compare a small local file before changing the laptop’s software.
- Do not confuse deletion with a repair
- Removing unfamiliar Library folders may lose app settings or work without identifying the cause. Prefer the app’s own storage controls and a verified backup. If the symptom started immediately after a particular update, include that version and timing in the support record rather than assuming every later slowdown has the same cause.
Stop boundary
When this stops being a self-service repair
- !If the Mac is slow with indexing finished, Reduce Transparency on and a clean macOS update, run Apple Diagnostics
- !If the SSD shows errors in Disk Utility, back up and book service
- !If the Mac freezes completely, note the macOS version for Apple
Evidence ledger
Sources behind this answer
Exact questions
Common questions
Does free RAM prove my MacBook Air is healthy?+
No. Apple explains that unused memory alone does not improve performance; pressure and the workload are more informative.
Should I replace the Mac before testing an app?+
First compare the same action with the suspect workload closed and record the result. That can identify a software or document problem.
Why use a small local test file?+
It helps distinguish the Mac’s responsiveness from an external drive or network delay.
What should I send Apple for persistent slowness?+
The repeatable action, macOS version, CPU observation, memory-pressure color and available storage.
slow performance: model differences
Also covered: Apple MacBook Air 13-inch (2018 to 2020); Apple MacBook Air (M2, M3 and M4).