Look back at what happened earlier
Rewind the last two minutes, the last half hour, or the last year, and see which app was busy.
- Time
- 5 minutes
- Steps
- 9
What you need
- l/Activity has been open, with Monitor on, during the time you want to look at.
Steps
Step 1. The last two minutes: point at the timeline
On Overview (⌘1), the card Live timeline draws CPU, GPU, Neural Engine, memory, disk and network on one clock. Move the pointer over any lane. A line follows it through every lane, and the whole stage above rewinds to that moment.
Click to pin the moment. Click the × on the chip beside the title to go back to live.
OverviewUnderstand what your Mac is doing, and what is using its resources.SummaryDashboardSearch or jump to…⌘KPauseRecordInspecting10:41:32This Mac had capacity to spare.Whole-Mac readings from this sample. Workloads below follow the displayed sample.Pressure NormalThermal Nominal486 processes · 3,912 threadsUp 4d 3h · swap 0 bytesExport Visual Snapshot…Apple M4 Prosystem on chip · 14 CPU cores · 48 GB unified memoryCPUwhole Mac · every 2s24%User17.6%System6.4%Idle76.0%GPUevery 5s18%Renderer16%Tiler9%Neural Engine0.42Wpower, not utilizationpeak 2.31 W · 120 sUnified memoryshared by CPU, GPU and Neural Engine21.4GBestimated used of 48 GB · 44.6%App14.2 GBWired4.1 GBCompressed3.1 GBCache12.8 GBFree13.8 GBComponent power14.2Wpeak 31.6 WCPU 9.6 · GPU 4.2 · ANE 0.42 WDiskevery 2sRead2.1 MB/sWrite1.1 MB/sNetworkevery 2sReceived1.6 MB/sSent210 KB/sLive timelineLatest 120 seconds on one clock · hover to rewind the stage, click to pin · gaps stay visibleInspecting 10:41:32CPUevery 2s24%User 17.6% · System 6.4%100%0GPUevery 5s18%Renderer 16% · Tiler 9%100%0Neural Engineevery 5s0.42 Wpower, not utilization2.5 W0Memoryevery 2s21.4 GBPressure Normal48 GB0Diskevery 2s3.2 MB/sRead 2.1 · Write 1.1 MB/s↑ 20 MB/s↓ 20 MB/sNetworkevery 2s1.8 MB/sReceived 1.6 MB/s · Sent 210 KB/s↑ 5 MB/s↓ 5 MB/sApps using CPUApp helpers are included · 100% means one busy coreLLumen Edit6 processes212.4%KKite Browser23 processes38.6%FForge IDE14 processes24.9%HHarbor9 processes18.2%RRoundtable5 processes9.8%Sample 10:42:18Explore all processesWhat the numbers meanObservations from the displayed sampleInfoLumen Edit leads measured CPU usageIt uses 212.4% CPU across 6 processes, where 100% is one core.InfoMemory pressure is normalmacOS is meeting demand without heavy compression or swap.Step 01 Step 2. The last half hour: open History
Press ⌘7. The view Recent details keeps every sample of the last 5, 10 or 30 minutes, with the apps and processes that were running in each one. The strip across the top is CPU for the whole Mac, with the highest moments flagged.
HistoryRecent detailsSummariesWeekly reportSaved app historySearch or jump to…⌘KPauseRecordLive · latest in view10:42:1824.0%Mac CPU100% = whole MacLumen Edit is the largest workload.In the latest sample it used 212.4% CPU across 6 processes, where 100% is one core.Pressure NormalThermal NominalRecent detailsEvery sample keeps its apps and process lifetimesMac CPU12345100%50%0%10:12:2010:27:1910:42:18Previous sampleNext sampleSample 900 of 900 · 486 processesClick or drag to inspect the workloads at that time. Choose a workload below to see its resource history.Largest peaksHighest Mac CPU samples in this window, at least 1m 29s apart · select one to move the playhead196.8%10:31:06257.1%10:32:40330.5%10:38:06427.8%10:17:06526.2%10:35:46Recent activitySaved sessions10:12:20 – 10:42:18 · 900 samples · 29m 58s retainedRecent history updates on screen about every 5 seconds. The actual retained window is limited by time, samples, and process count.Average Mac CPU25.0%1,798 measured secondsObserved workloads2129 no longer presentAverage used memory21.2GBTime-weighted observed memoryWorkloads across this historyFind an app or executableSorted by measured CPU-seconds. Exited apps remain available for inspection. A partial label means some process measurements are unavailable.
WorkloadCPU-secondsAverage CPUPeak memoryLLumen Edit9 lifetimes3,014.1167.6%9.4 GBPPixelroom4 lifetimes · exited806.4170.1%2.8 GBKKite Browser26 lifetimes · partial740.841.2%4.6 GBKkernel_task1 lifetime406.322.6%2.4 GBFForge IDE14 lifetimes361.420.1%3.2 GBWWindowServer1 lifetime321.817.9%1.3 GBHHarbor9 lifetimes312.917.4%5.6 GBRRoundtable5 lifetimes172.69.6%940 MB212 of 212 workloads · 9 exitedLLumen Edit/Applications/Lumen Edit.appShow history forAll processes in this workloadResourceCPUGPU timeMemoryDisk readDisk writeReceivedSentCPU100% = one core1,000%500%0%10:12:2010:27:1910:42:18The axis is one core. A workload can pass 100%.Workload read: 3.4 GB in 1,798.0 measured secondsWorkload written: 11.2 GB in 1,798.0 measured secondsProcesses at 10:42:18ProcessCPUMemoryLumen Edit · PID 4812128.4%3.9 GBLumen Render Service · PID 487162.3%1.8 GBLumen Helper (GPU) · PID 481814.2%520 MBLumen Helper (Renderer) · PID 48215.8%340 MBLumen Cache Agent · PID 48361.4%180 MBLumen Audio Bridge · PID 48400.3%60 MBStep 02 Step 3. Jump to a peak
Under the strip, Largest peaks lists up to five. Click one. The playhead moves there, the sentence on the left changes to say which app was the largest at that moment, and a banner reminds you that you are looking at the past.
You can also drag along the strip, or step one sample at a time with the arrows beside the slider.
HistoryRecent detailsSummariesWeekly reportSaved app historySearch or jump to…⌘KPauseRecordReviewing10:31:0696.8%Mac CPU100% = whole MacLumen Edit was the largest workload.At this moment it used 986.2% CPU across 9 processes, where 100% is one core.Pressure NormalThermal FairRecent detailsEvery sample keeps its apps and process lifetimesMac CPU10:31:0612345100%50%0%10:12:2010:27:1910:42:18Previous sampleNext sampleSample 564 of 900 · 479 processesClick or drag to inspect the workloads at that time. Choose a workload below to see its resource history.Return to LiveLargest peaksHighest Mac CPU samples in this window, at least 1m 29s apart · select one to move the playhead196.8%10:31:06257.1%10:32:40330.5%10:38:06427.8%10:17:06526.2%10:35:46Recent activitySaved sessions10:12:20 – 10:42:18 · 900 samples · 29m 58s retainedRecent history updates on screen about every 5 seconds. The actual retained window is limited by time, samples, and process count.Average Mac CPU25.0%1,798 measured secondsObserved workloads2129 no longer presentAverage used memory21.2GBTime-weighted observed memoryWorkloads across this historyFind an app or executableSorted by measured CPU-seconds. Exited apps remain available for inspection. A partial label means some process measurements are unavailable.
WorkloadCPU-secondsAverage CPUPeak memoryLLumen Edit9 lifetimes3,014.1167.6%9.4 GBPPixelroom4 lifetimes · exited806.4170.1%2.8 GBKKite Browser26 lifetimes · partial740.841.2%4.6 GBKkernel_task1 lifetime406.322.6%2.4 GBFForge IDE14 lifetimes361.420.1%3.2 GBWWindowServer1 lifetime321.817.9%1.3 GBHHarbor9 lifetimes312.917.4%5.6 GBRRoundtable5 lifetimes172.69.6%940 MB212 of 212 workloads · 9 exitedLLumen Edit/Applications/Lumen Edit.appShow history forAll processes in this workloadResourceCPUGPU timeMemoryDisk readDisk writeReceivedSentCPU100% = one core1,000%500%0%10:12:2010:27:1910:42:1810:31:06 · CPU: 986.2%The axis is one core. A workload can pass 100%.Workload read: 3.4 GB in 1,798.0 measured secondsWorkload written: 11.2 GB in 1,798.0 measured secondsProcesses at 10:31:06ProcessCPUMemoryLumen Render Service · PID 4871512.6%2.9 GBLumen Encoder · PID 4874318.4%1.4 GBLumen Edit · PID 481284.2%3.6 GBLumen Media Reader · PID 483041.3%412 MBLumen Helper (GPU) · PID 481818.9%486 MBLumen Helper (Renderer) · PID 48217.6%298 MBLumen Cache Agent · PID 48362.4%164 MBLumen Audio Bridge · PID 48400.8%58 MBLumen Update Agent · PID 48520.0%22 MBStep 03 Step 4. See who was busy then
Below, Workloads across this history ranks apps by the processor time they used over the whole window. Apps that have since quit stay in the list, marked as exited. Select one to chart its CPU, GPU time, memory, disk or network over time on the right.
HistoryRecent detailsSummariesWeekly reportSaved app historySearch or jump to…⌘KPauseRecordRecent activitySaved sessions10:12:20 – 10:42:18 · 900 samples · 29m 58s retainedRecent history updates on screen about every 5 seconds. The actual retained window is limited by time, samples, and process count.Average Mac CPU25.0%1,798 measured secondsObserved workloads2129 no longer presentAverage used memory21.2GBTime-weighted observed memoryWorkloads across this historyFind an app or executableSorted by measured CPU-seconds. Exited apps remain available for inspection. A partial label means some process measurements are unavailable.
WorkloadCPU-secondsAverage CPUPeak memoryLLumen Edit9 lifetimes3,014.1167.6%9.4 GBPPixelroom4 lifetimes · exited806.4170.1%2.8 GBKKite Browser26 lifetimes · partial740.841.2%4.6 GBKkernel_task1 lifetime406.322.6%2.4 GBFForge IDE14 lifetimes361.420.1%3.2 GBWWindowServer1 lifetime321.817.9%1.3 GBHHarbor9 lifetimes312.917.4%5.6 GBRRoundtable5 lifetimes172.69.6%940 MB212 of 212 workloads · 9 exitedLLumen Edit/Applications/Lumen Edit.appShow history forAll processes in this workloadResourceCPUGPU timeMemoryDisk readDisk writeReceivedSentCPU100% = one core1,000%500%0%10:12:2010:27:1910:42:1810:31:06 · CPU: 986.2%The axis is one core. A workload can pass 100%.Workload read: 3.4 GB in 1,798.0 measured secondsWorkload written: 11.2 GB in 1,798.0 measured secondsProcesses at 10:31:06ProcessCPUMemoryLumen Render Service · PID 4871512.6%2.9 GBLumen Encoder · PID 4874318.4%1.4 GBLumen Edit · PID 481284.2%3.6 GBLumen Media Reader · PID 483041.3%412 MBLumen Helper (GPU) · PID 481818.9%486 MBLumen Helper (Renderer) · PID 48217.6%298 MBLumen Cache Agent · PID 48362.4%164 MBLumen Audio Bridge · PID 48400.8%58 MBLumen Update Agent · PID 48520.0%22 MBMeasured usage over timeCPU-seconds integrate measured CPU rates over their valid intervals. 100% for one second is one CPU-second. Averages cover measured intervals; missing values and gaps are excluded. Memory is sampled footprint, with resident fallback, and shared pages can overlap. Selected times also apply to the CPU, Memory, Disk, Network, and Processes pages.Step 04 Step 5. Days and months: switch to Summaries
Click Summaries in the title bar. l/Activity saves a summary of the whole Mac every minute. Choose a range from Last 24 hours to 1 year, and a metric: CPU, GPU, Memory, Disk or Network. Time when the Mac was asleep or the app was closed stays a gap.
HistoryRecent detailsSummariesWeekly reportSaved app historySearch or jump to…⌘KPauseRecordLatest summary13 Oct 2026 at 10:4123.6%Mac CPU · summary average100% = whole MacSummarized from 30 system samples.1-minute summary. System counters only; detailed app and process samples require a recording.Summary rangeLast 7 daysSummary metricCPUGPUMemoryDiskNetwork12345100%50%0%6 Oct, 10:429 Oct, 22:4213 Oct, 10:42Click or drag to inspect a summary. Missing measurements remain gaps.Largest peaksHighest CPU minutes in this range, at least 8h 24m apart · select one to move the playhead194.2%13 Oct, 10:31278.4%12 Oct, 16:07371.3%7 Oct, 15:12466.0%9 Oct, 11:48558.7%10 Oct, 16:24System historyMeasured summaries saved in /Users/sam/Library/Application Support/app.activity.desktop/Profile/History
Average16.8%Weighted by measured timePeak summary94.2%13 Oct 2026 at 10:31Summaries with readings9,240of 9,240 summarizedSystem samples277,200Captures summarizedSummary averages cover measured intervals only. Full minutes cover thirty days, hourly summaries ninety days and daily summaries one year. Missing time remains a gap. Long-term summaries contain system counters; detailed app and process samples require a recording.Refresh summariesStep 05 Step 6. Per app, over days: turn on saved app history
Summaries describe the Mac as a whole. To keep a record per app, open Settings (⌘,) → History & Recording, and in Saved app history set Retention to 7 days or more. It is off until you choose.
SettingsMake l/Activity work the way you do.Search or jump to…⌘KSearch settingsGeneralDark · Dock and menu barPermissionsFinder not checkedMonitoringEvery 2 secondsHistory & Recording30 min live · 24 h maxStorage & CacheEvery hour · 1.8 GBAlertsNotifications offAbout & PrivacyVersion 2.39Changes save automaticallyHistory & RecordingChoose how much activity to retain.Live historyRecent samples stay in memory until l/Activity quitsKeep history for30 minutesSystem graphs · 29m 58s span · 900 samplesProcess details · 29m 58s span · 900 samplesShown in History · Recent detailsClear HistorySystem summariesLonger trends without saving every process sampleSave system summariesRetention30 daysShown in History · System summaries and weekly reportsClear summaries…Saved app historyOptional, local resource aggregatesRetention7 daysShown in History → Saved app historyClear saved app history…Session recordingsRecord a session to retain detailed readings after quitting3 saved sessionsMaximum durationA recording stops after 24 hours24 hoursRecording budget: 2 GiB1 to 8 GiB for each recordingWhen a recording stopsRecordings stop when their duration or storage budget is reached. Saved sessions remain in ~/Library/Application Support/app.activity.desktop/Profile/Sessions.What l/Activity keepsConfigured maximum spans, on a log scale · actual live coverage appears aboveSystem graph historyIn memory · up to 30 minutesLightweight system samples. Process details may cover a shorter span because of the memory cap. Both clear when l/Activity quits.Minute summariesOn disk · 30 daysSystem averages and peaks for each minute, with gaps preserved.One session recordingOn disk · up to 24 hoursDetailed readings while you record, up to 2 GiB. Saved sessions stay in Profile.1 min10 min1 h1 day30 daysStep 06 Step 7. Read the per-app record
From then on, History → Saved app history lists your apps with the heaviest first for the range you choose. Select one for its average, its peak and a chart.
HistoryRecent detailsSummariesWeekly reportSaved app historySearch or jump to…⌘KPauseRecordSaved app historyLocal resource summaries of apps and their helpers
ResourceCPURange7 daysFind an app or executableRefreshLumen Edit31.8%Kite Browser4.1%Forge IDE2.0%Harbor2.3%Roundtable1.2%PixelroomPartial coverage6.4%Northwind Sync0.5%Tessel Design0.9%Tempo Player0.3%Brightline Mail0.2%Atlas Maps0.4%Quill Notes0.1%Finder0.1%Previous1–13NextLumen Edit/Applications/Lumen Edit.app6 Oct 2026 at 10:45 – 13 Oct 2026 at 10:41 · 554,400 measured seconds · 277,200 readingsAverage31.8%Measured intervalsPeak986.2%Observed readingTotal176,299.2CPU-sRetained measurementsFull minutes cover the last 24 hours, 15-minute summaries the previous six days, hourly summaries through 90 days, and daily summaries through one year. Averages exclude gaps; lines break at missing intervals and interruptions. Activity within a summary is not reconstructed.100% = one core1,000%500%0%6 Oct, 10:459 Oct, 22:4313 Oct, 10:41CPU uses a per-core scale. GPU time can overlap across clients and is not device utilization or watts. Memory is sampled footprint with resident fallback; shared pages can overlap. Disk and network totals integrate valid observed intervals only. Partial GPU/network readings are lower bounds.Step 07 Step 8. A week on one page
Weekly report → Prepare report sets last week beside the week before for CPU, GPU, memory, disk and network. App names are left out until you tick Include app names in this report. Export report… saves it as text.
HistoryRecent detailsSummariesWeekly reportSaved app historySearch or jump to…⌘KPauseRecordWeekly reportA local review of the last complete Monday–Sunday week
Earlier weekLater weekRefresh report5 Oct 2026 – 11 Oct 2026ResourceAveragePrevious weekMeasured coverageMac CPU14.2%12.9%154.0 h · 91.7% of weekDevice GPU9.8%8.1%153.6 h · 91.4% of weekUsed memory20.6 GB19.8 GB277,200 memory samplesDisk read1.9 MB/s2.3 MB/s154.0 h · 91.7% of weekDisk write3.1 MB/s2.6 MB/s154.0 h · 91.7% of weekNetwork received412 KB/s388 KB/s154.0 h · 91.7% of weekNetwork sent96 KB/s104 KB/s154.0 h · 91.7% of week9,240 retained summaries; largest bucket 1 minutes. Averages exclude missing time. App buckets crossing a week boundary are excluded. Comparisons reflect different measured coverage and do not establish a trend or cause.Include app names in this reportLeading retained apps by measured CPU time (100% = one core):App 1: 162,439.2 CPU-s · 29.3% averageApp 2: 21,067.2 CPU-s · 3.8% averageApp 3: 9,979.2 CPU-s · 1.8% averageApp 4: 6,098.4 CPU-s · 2.2% averageApp 5: 3,880.8 CPU-s · 0.7% averageReports use retained readings only. Collection can be enabled in Settings → History.Export report…Step 08 Step 9. Come back to now
Whenever you are looking at the past, Return to Live is in the banner under the title bar and beside the slider.
Jump to a step9 steps
- Step 1. The last two minutes: point at the timeline
- Step 2. The last half hour: open History
- Step 3. Jump to a peak
- Step 4. See who was busy then
- Step 5. Days and months: switch to Summaries
- Step 6. Per app, over days: turn on saved app history
- Step 7. Read the per-app record
- Step 8. A week on one page
- Step 9. Come back to now
02Good to know
The small print, in plain words
Note1 / 2
How far back each view goes
- Overview's timeline: 120 seconds.
- Recent details: 5, 10 or 30 minutes, kept in memory and cleared when you quit.
- Summaries: 30 days by default, up to one year. Saved on disk.
- Saved app history: off by default, up to one year.
- A recording keeps full detail for as long as you let it run. See Record a slowdown and compare.
Note2 / 2
Gaps stay gaps
If l/Activity was paused, closed or the Mac was asleep, nothing was measured and nothing is drawn. Missing time is never filled in or shown as zero.
03Keep going