Thrum

What is the jamf process on my Mac, and why is it using CPU?

Last reviewed: 19 November 2026. Paths and launch daemons taken from Jamf Pro documentation; Jamf is not installed on the Mac used for checking.

jamf is the binary that carries out most tasks for Jamf Pro, the device management system many organizations use for their Macs. It runs at regular check-ins and at startup to apply policies, which can install software, run scripts or update settings, and it is busy while those tasks run. It is safe on a Mac your organization manages; its activity is logged in /var/log/jamf.log.

jamf at a glance

jamf
Made byJamf (Jamf Pro device management)
TypeDevice management agent
Location/usr/local/jamf/bin/jamf
Runs assystem (started by Jamf's launch daemons), not your user
Started bylaunchd job com.jamfsoftware.task.1
Can you quit it?No. It is installed and controlled by your organization's Jamf Pro server, and launchd starts it again at the next check-in.

What is jamf?

Jamf describes the jamf binary, at /usr/local/jamf/bin/jamf with a link at /usr/local/bin/jamf, as the binary used to execute most tasks for Jamf Pro. It is installed when a Mac is enrolled in an organization's Jamf Pro server.

launchd runs it through Jamf's launch daemons: com.jamfsoftware.task.1 manages the recurring check-in to the Jamf Pro server, and com.jamfsoftware.startupItem checks for policies with a startup trigger. Other parts of the Jamf management framework live in /Library/Application Support/JAMF/, including JamfDaemon.app, which handles Self Service tasks, restricted software and application usage monitoring.

Is jamf safe?

Yes, on a Mac enrolled in your organization's device management. It is how your IT team installs apps, applies settings and keeps the Mac compliant. If a personal Mac you never enrolled has /usr/local/jamf/bin/jamf, ask whoever set up the Mac, and check System Settings > General > Device Management.

Why does jamf use so much CPU, disk and network?

How much CPU is normal for jamf?

Typically jamf appears briefly at each check-in and then exits. Longer bursts during software installs or after a restart are normal.

A jamf process that stays at high CPU for a long time usually means a policy or script is still running or stuck.

How do you see what jamf is doing on your Mac?

  1. Read the jamf log. Jamf writes its messages to /var/log/jamf.log. In Terminal, tail -f /var/log/jamf.log shows each check-in and policy as it runs.
  2. Wait for the policy to finish. If the log shows a policy installing software or running a script, let it complete. Interrupting an install can leave an app half-updated.
  3. Use Self Service. If your organization provides the Self Service app, installs and updates it offers run there, so you can choose when they happen.
  4. Tell your IT team. If jamf stays busy at every check-in or a policy keeps failing in the log, send the relevant lines from /var/log/jamf.log to your IT team. Only they can change the policies.

When should you worry about jamf?

Repeated high CPU at every check-in, or the same policy failing again and again in the log, points to a problem with a policy or script that IT needs to fix.

Do not delete Jamf files or launch daemons on a work Mac. Removing them breaks management, and your IT team is the one to unenroll the Mac.

How do you check jamf in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type jamf in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. The Network tab shows its Sent Bytes and Rcvd Bytes. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every jamf process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password. nettop shows its live network traffic.

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'jamf' | grep -v grep
sudo fs_usage -w -f filesys jamf
nettop -p jamf

How can Thrum help with jamf?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when jamf is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.

Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.

Questions about jamf

Can I remove jamf from my Mac?

Not on a Mac your organization manages. Removal is done by IT through Jamf Pro. On a Mac you own outright, ask whoever enrolled it how to unenroll.

What does jamf check-in do?

Jamf's com.jamfsoftware.task.1 launch daemon runs the recurring check-in with the Jamf Pro server, which runs any policies that apply to the Mac at that time.

Where are Jamf's settings stored?

In /Library/Preferences/com.jamfsoftware.jamf.plist, which holds settings such as the Jamf Pro server address.

Sources