Thrum

What is MIDIServer, and why is it running on my Mac?

Last reviewed: 19 November 2026. Path, launchd job, launch triggers and man page checked on macOS 26.3.1.

MIDIServer is the central part of Apple's CoreMIDI framework: it loads MIDI driver plug-ins and passes MIDI messages between music apps and keyboards, controllers and other MIDI devices. It starts when an app uses MIDI or a Bluetooth MIDI device connects, and it is idle the rest of the time. Sustained CPU use usually comes from a device or driver sending a constant stream of data.

MIDIServer at a glance

MIDIServer
Made byApple (part of macOS, CoreMIDI)
TypePer-user agent
Location/System/Library/Frameworks/CoreMIDI.framework/MIDIServer
Runs asyour user
Started bylaunchd job com.apple.midiserver
Can you quit it?Yes, when no music app is open; launchd starts it again the next time an app uses MIDI. Quitting it while a music app is running cuts that app off from its MIDI devices.

What is MIDIServer?

The MIDIServer(8) man page describes it as the agent supporting the CoreMIDI framework: it provides a central implementation of the CoreMIDI APIs, loads driver plug-ins and handles MIDI input and output between client applications and drivers. Apps such as GarageBand, Logic Pro and Audio MIDI Setup do not talk to MIDI hardware directly; they go through MIDIServer.

It runs as your user through the launchd agent com.apple.midiserver. Besides starting when an app asks for it, the job lists a Bluetooth launch trigger for the standard Bluetooth LE MIDI service, so connecting a Bluetooth MIDI instrument can start it too. Apple's own MIDI drivers (USB, Bluetooth, network and inter-app) are plug-ins in /System/Library/Extensions; drivers from other companies go in /Library/Audio/MIDI Drivers.

Is MIDIServer safe?

Yes. MIDIServer is part of macOS inside the CoreMIDI framework on the read-only system volume, and it is signed by Apple. A copy outside /System/Library/Frameworks/CoreMIDI.framework would not be Apple's.

Why does MIDIServer use so much CPU and memory?

How much CPU is normal for MIDIServer?

Typical: MIDIServer is not running at all until an app uses MIDI, and then sits near 0% CPU apart from short spikes when devices connect.

Steady CPU use of several percent with no music app open is not normal and points to a device or driver.

How do you stop MIDIServer from using so much CPU?

  1. Quit music apps. Quit GarageBand, Logic Pro, DJ software and other MIDI apps. If MIDIServer settles, the load came from what those apps were sending or receiving.
  2. See your MIDI setup. Open Audio MIDI Setup (in Applications > Utilities) and choose Window > Show MIDI Studio. It shows every MIDI device and driver MIDIServer knows about.
  3. Unplug devices one at a time. Disconnect USB and Bluetooth MIDI devices one by one and watch MIDIServer in Activity Monitor. A device that sends clock or sensor data continuously is the usual cause.
  4. Remove old third-party drivers. In Finder, choose Go > Go to Folder and open /Library/Audio/MIDI Drivers. Update or remove drivers for hardware you no longer use, following the maker's uninstall instructions.

When should you worry about MIDIServer?

Look closer if MIDIServer uses CPU with nothing connected and no music app open; a third-party driver is the most likely cause.

Repeated crashes of MIDIServer in Console's Crash Reports also usually point to a driver plug-in.

How do you check MIDIServer in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type MIDIServer in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every MIDIServer process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'MIDIServer' | grep -v grep

How can Thrum help with MIDIServer?

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 MIDIServer 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. Click MIDIServer in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.

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 MIDIServer

Why does MIDIServer start when I have no MIDI devices?

Any app that uses CoreMIDI starts it, including some audio and music apps that only check for devices at launch. It exits again when it is no longer needed.

Is MIDIServer the same as coreaudiod?

No. coreaudiod handles audio streams such as speakers and microphones. MIDIServer handles MIDI, the note and control messages used by instruments and controllers.

Sources