Find out what happened while you were away.

Activity Monitor only knows about right now. Vitals keeps CPU, memory, energy, disk and network from the last hour back to the last year, with the apps that used the most ranked hour by hour, so a Mac that was slow at three can still be asked why at five.

Memory by Type
82%
in use
App 22.15 GB
Wired 5.67 GB
Compressed 24.54 GB
Cached 10.32 GB
Free 1.32 GB
Memory by App
59.25 GB
all apps
Google Chrome 21.23 GB
VS Code 8.17 GB
Terminal 3.86 GB
Safari 2.69 GB
Other 23.30 GB
Power by App
1.7 W
all apps
GitHub Desktop 427 mW
Google Chrome 367 mW
Zoom 145 mW
Terminal 86 mW
Other 650 mW
Now
27 %
Average today36%
Load3.41
User
19%
Your apps
System
8%
macOS
Cores
12
8 P4 E
Top App
Google Chrome
18.2%
AppCPU
Google Chrome
96 processes
–
Terminal
49 processes
–
Safari
16 processes
–
Docker
9 processes
–
Visual Studio Code
63 processes
–
Slack
13 processes
–
Figma
14 processes
–
Zoom
8 processes
–
In use of 64 GB
52.63 GB
Normal
Free11.37 GB
Swap0 MB
App
23.43 GB
Wired
5.37 GB
Compressed
23.82 GB
Top App
Google Chrome
20.59 GB
AppMemory
Google Chrome
96 processes
–
Visual Studio Code
63 processes
–
Terminal
49 processes
–
Safari
16 processes
–
Docker
9 processes
–
Slack
13 processes
–
Figma
14 processes
–
Zoom
8 processes
–
Free of 994.66 GB
479.72 GB
Used514.94 GB
Written today38.9 GB
Reading
737 kB/s
Writing
195 kB/s
Volumes
2
Macintosh HDBackup
Top App
Photos
121 kB/s
AppWriting
Photos
6 processes
–
Google Chrome
96 processes
–
Docker
9 processes
–
Visual Studio Code
63 processes
–
Xcode
22 processes
–
Mail
4 processes
–
Slack
13 processes
–
Music
5 processes
–
Downloading
12 kB/s
Today4.4 GB
Last 30 days212 GB
Uploading
419 kB/s
Last 7 Days
48.3 GB
Interface
Wi-Fi
en0
Top App
Safari
8 kB/s
AppDownloading
Safari
16 processes
–
Google Chrome
96 processes
–
Slack
13 processes
–
Zoom
8 processes
–
Music
5 processes
–
Mail
4 processes
–
Docker
9 processes
–
Notion
6 processes
–
Apple M2 Max
60 %
Average32%
Peak95%
Memory
1.69 GB
Average
32%
Peak
95%
Top App
Figma
35%
AppGPU
Figma
14 processes
–
Google Chrome
96 processes
–
Safari
16 processes
–
Zoom
8 processes
–
Visual Studio Code
63 processes
–
Xcode
22 processes
–
Slack
13 processes
–
Notion
6 processes
–
16-core Neural Engine
2 %
Average3%
Peak16%
Memory Traffic
79.9 MB/s
Average
3%
Peak
16%
Top App
Photos
3 connections
AppNeural Engine
Photos
6 processes
–
Xcode
22 processes
–
Safari
16 processes
–
Zoom
8 processes
–
Mail
4 processes
–
Notion
6 processes
–
Google Chrome
96 processes
–
On battery
64 %
Remaining2h 46m
Cycles412
Power Draw
12.6 W
Health
76%
Temperature
31°
Top App
Google Chrome
4.3 W
AppPower
Google Chrome
96 processes
–
Zoom
8 processes
–
Figma
14 processes
–
Slack
13 processes
–
Safari
16 processes
–
Visual Studio Code
63 processes
–
Docker
9 processes
–
Music
5 processes
–
Output
MacBook Pro Speakers
64%
AppStatusVolumeLevel
Music Playing 100%
Zoom Playing 80%
Google Chrome Playing 35%
Slack Silent Muted
Safari Silent 100%
Figma Silent 100%
Notion Silent 100%
Mail Silent 100%
3 connected
Lowest battery: AirPods Pro, left, 42%. Beats Fit Pro is paired but away.
42% Bluetooth Settings
DeviceKindBatteryLevel
AirPods Pro Headphones
Left 42%
Right 58%
Case 80%
Magic Trackpad Trackpad 67%
Magic Keyboard Keyboard 91%
4 dev servers are running but idle
Stopping them frees 1.37 GB and ports 3000, 4321, 4322, 8000.
Stop All…
storefront
9 processes
working
1.18 GB
storefront-web
node
4322 up 3 days, barely used
458 MB
scraper-api
python
8000 up 4 days, barely used
412 MB
marketing-site
node
4321 idle 2 hours
296 MB
billing-api
node
30009229 idle 45 min
204 MB
docs
node
5173
188 MB
ml-notebooks
python
8888
164 MB
design-tokens
node
6006 idle 20 min
121 MB
infra
3 processes
96 MB
auth-service
go
8080
74 MB
email-templates
node
3030 idle 3 hours
58 MB
0%
Claude
This week
On pace · 10% to spare
0%
Codex
5-hour session
Resets in 3h 12m
0%
GitHub Copilot
Premium requests
Runs out in 4d at this rate
0%
Cursor
This billing cycle
Resets in 12d 5h
Checkout flow tests Working Waiting for you
Claude Code · storefront · running 48 min
410 MB
Started · 4 Quit Session…
vitest command · 61% CPU 520 MB
node server · port 3,001 240 MB
Google Chrome for Testing browser 310 MB
mcp-server-fetch tool server 64 MB
Codex idle 48 min
docs · in Terminal · Nothing started
290 MB
4 containers in Docker
674MB
Lowest592.3 MB
Peak674 MB
By Container
postgres312 MB46%
rabbitmq206 MB31%
minio142 MB21%
redis14 MB2%
CPU
3.0%
most in postgres
Closest to Its Limit
rabbitmq
86% of 240 MB
Network
9kB/s
↓ 6 kB/s · ↑ 3 kB/s
Published Ports
6
5433567263799000+2
storefront 2 containers
Started together by Docker Compose · 2 ports · 2 running
1.9% 326 MB
postgres postgres:16
Up 5 hours
5433
1.6% 312 MB
redis redis:7-alpine
Up 5 hours
6379
0.3% 14 MB
api 1 container
Started together by Docker Compose · 2 ports · 1 running
0.9% 206 MB
rabbitmq rabbitmq:3-management
Up 3 hours
567215672 86% of 240 MB
0.9% 206 MB
minio minio/minio
Up 26 hours
90009001
0.2% 142 MB

The numbers are simulated: a web page cannot read your Mac, and should not.

01Over Time

Any range from the last hour to the last year.

CPU, memory, energy, disk and network, for the Mac and for every app, in one chart where the range is a tap. For recent days you also get the apps that used the most, ranked hour by hour, so you can find out what was running during the call.

  • CPU, memory, energy, disk and network
  • The Mac as a whole, and every app
  • The last hour, 24 hours, 7 days, 30 days, 90 days, 6 months or a year
  • The apps that used the most, by the hour
Over Time1 h24 h7 d30 d90 d6 mo1 y
CPUMemoryEnergyDiskNetwork
Sep 16Oct 1Oct 16
Used the most, by the hour
Google Chrome41 h
Xcode18 h
Zoom9 h
The range, as a tap The Mac, and every app
02Peaks

The worst moment, and when it was.

A Peaks card under Over Time shows the highest CPU, memory pressure, temperature and power in the range you chose, the moment each happened, and how long your Mac spent at a limit, so you know whether Tuesday was a blip or a pattern.

  • The highest CPU, memory pressure, temperature and power
  • When each one happened
  • The stretches at a limit, and how long they lasted
  • From a reading every five minutes
PeaksLast 30 days
CPU94%Tue 14:20
Memory pressure88%Oct 9, 11:05
Temperature92°Tue 14:24
Power41 WOct 3, 16:40
At a limit1 h 12 m, in 4 stretches
The highest, and when The stretches at a limit
03Memory

See when the Mac started running short.

The Memory tab charts memory pressure under its memory chart, and swap used beside it once your Mac needs swap, so a week of running short is one picture instead of a hunch.

  • Memory pressure, charted over time
  • Swap used beside it, once the Mac needs swap
  • Red in the menu bar while memory is under pressure
  • An assistant can ask how much memory and swap is in use
Memory pressure7 days
Oct 9Thu, 11:05 · 88%Oct 16
Swap usedup to 3.2 GB
When it started running short Red in the menu bar, meanwhile
04Your file

One file on your Mac, and it is yours.

Keep 30 days, 90 days, 6 months or a year. Export it as three CSV files, open the file yourself, or let an assistant ask about it over MCP. Nothing leaves your Mac.

  • 30 days, 90 days, 6 months or a year
  • CSV: your apps by day, your Mac by hour, the readings every five minutes
  • The file itself, with its tables documented
  • An assistant can ask about a day, a week or a year
General
Customize
Layout
Insights
Integrations
License
History
Keep History For1 year ▾
Export History as CSV…
Show History File in Finder
Delete History…
apps-by-day.csvyour apps, by day
mac-by-hour.csvyour Mac, by hour
readings.csvevery five minutes
One file, on your Mac Nothing leaves it
Why it matters

History, before and after

Activity Monitor is a window onto this second. Its graphs scroll off the right edge in a minute or two, and the one long view it keeps, twelve hours of energy, is a single column. If the Mac was slow at three and you opened Activity Monitor at five, there is nothing to look at.

The questions worth answering are about the past: what was running when the fans came on during the call, which app used the battery between nine and one, whether the Mac has been short of memory all week or only today.

Vitals keeps CPU, memory, energy, disk and network, for the Mac and for every app, from the last hour to the last year. Over Time shows any range with the apps that used the most, ranked by the hour for recent days, and a Peaks card with the highest CPU, memory pressure, temperature and power in the range and when each was. It is one file on your Mac. Export it as CSV, open it yourself, or ask an assistant about it.

How to use it

Where it is in Vitals

The tab, the menu bar item and the setting, in the order you would reach for them.

  1. 01

    Open Over Time

    From the window, choose the range: the last hour, 12 or 24 hours, 7 or 30 days, 90 days, 6 months or a year, with a tab for each metric. Memory pressure and swap are charted on the Memory tab, under the memory chart.

  2. 02

    Choose how much to keep

    Settings → General → Keep History For: 30 days, 90 days, 6 months or a year. Delete History… is beside it. The history is one small file on your Mac and nothing leaves it.

  3. 03

    Read the peaks

    The Peaks card under Over Time shows the highest CPU, memory pressure, temperature and power in the range you chose, when each was, and the stretches your Mac spent at a limit. Vitals keeps a reading every five minutes for it.

  4. 04

    Take it with you

    Export CSV from Over Time, from File → Export History as CSV, or from Settings → General: your apps by day, your Mac by hour, and the readings every five minutes. The file's own tables, and some queries to start from, are on the history data page. Over MCP, an assistant can ask the same questions.

Compared

History: Activity Monitor and Vitals

The whole comparison is row by row. These are the rows about history.

Activity Monitor Vitals
How far back
Activity MonitorA minute or two of graphs, 12 hours of energy
VitalsThe last hour to the last year
Per app
Activity MonitorRight now
VitalsThe apps that used the most, by the hour
Peaks
Activity MonitorNone
VitalsHighest CPU, memory pressure, temperature and power, and when
Memory pressure and swap
Activity MonitorRight now
VitalsCharted over time
Export
Activity MonitorNone
VitalsCSV, three files, and the file itself

The words behind it

What the numbers mean, from the Activity Monitor glossary.

Questions

The ones people ask about history before they buy.

How much history does Vitals keep?

Up to a year. You choose 30 days, 90 days, 6 months or a year in Settings, and it lives in one small file on your Mac.

Does the history leave my Mac?

No. It stays in a file on your Mac. Vitals goes online only to check for updates and to check your license.

Can I see which app was busy at a given time?

For the last two days, yes, hour by hour: the apps that used the most in each hour. Further back, the Mac's own readings are kept for each metric.

What does Activity Monitor keep?

Live graphs, and twelve hours of energy. Everything else is this second only.

How often does Vitals save a reading?

Every five minutes, for the peaks and the stretches at a limit, plus your apps by the hour and by the day for the rankings.

Can I export the history?

Yes, as CSV: three files, your apps by day, your Mac by hour, and the readings every five minutes. From Over Time, from the File menu, or from Settings → General.

Can I open the history file myself?

Yes. It is one file on your Mac, and the history data page describes its tables and gives some queries to start from.

Does it chart memory pressure and swap over time?

Yes. The Memory tab charts memory pressure under its memory chart, and swap used beside it once your Mac needs swap.

Read on

Guides that use this, and how Vitals compares with the apps people buy for it.

More of Vitals

All features

Get Vitals for $15 while the launch price lasts

50 left at this price. The regular price is $39. One payment, lifetime updates, 14-day refund.

Get Vitals for $15