A new unstable resource-draining Adobe process that has recently appeared on my Mac is proving more difficult to hunt down and kill than the numerous other processes that Adobe creates. Generally following instructions here and elsewhere to disable the launching of these processes has worked, but I can't seem to figure out how to disable the latest: AdobeIPCBroker.

I've found instructions for Windows, but none for OS X.

How do I get rid of and permanently disable AdobeIPCBroker on OS X?

  • Isn't this part of Adobe's licensing model? Wouldn't you get support from the vendor for this?
    – bmike
    Commented Nov 3, 2016 at 18:00
  • 1
    @bmike: Can you explain? Adobe provides no support for removing its daemons and background processes (I've tried).
    – orome
    Commented Nov 3, 2016 at 18:06
  • It also could be an inter process comms broker - helps to sandbox reader (or other programs) - blogs.adobe.com/security/2010/11/… - if their software is misbehaving - it probably would be something you'd patch. You're not wrong to ask here, but we might not be the best place. Some speculate it reports back as part of licensing too - I couldn't say for sure.
    – bmike
    Commented Nov 3, 2016 at 22:05
  • 1
    @bmike: Ah. I don't really care what it does. I just what to hear from any Mac users who've succeeded in getting rid of it. If that kills Adobe's apps, then so be it.
    – orome
    Commented Nov 3, 2016 at 22:17
  • I'm going to link to apple.stackexchange.com/questions/218681/… since it has a nice CC cleaner app that might help in this case
    – bmike
    Commented Sep 23, 2019 at 0:43

6 Answers 6


This is what I had to do:

  1. Kill Core Sync.
  2. Kill CCLibrary.
  3. Kill CCXProcess.
  4. Kill AdobeIPCBroker.

I don't know if they'll come back the next time I reboot, but in an attempt to prevent that I also disabled the "Launch Agents" in com.adobe.AAM.Updater-1.0.plist and com.adobe.AdobeCreativeCloud.plist.

(Who in Adobe thought it was a good idea to spend CPU and battery life constantly just to check for updates or things to 'sync'? That's like kids going around trick or treating all year just to be sure they don't miss Halloween. There are smarter ways to schedule things.)

  • 7
    Why Adobe, why?
    – frozenjim
    Commented Apr 26, 2019 at 22:57
  • 1
    these files are in /Users/$YOUR_USERNAME/Library/LaunchAgents Commented May 16, 2020 at 21:26
  • In My Case it was caused by adobe Creative Cloud - i had to kick out all of it
    – Andreas
    Commented Jan 8, 2021 at 11:24
  • The plist files can also be in /Library/LaunchAgents/ and in /Library/LaunchDaemons/ and can also have different names, all starting with com.adobe
    – lapin
    Commented Sep 19, 2022 at 4:58

this is a terminal alias/command I use that prevents any Adobe stuff running in the background:

alias nothankyouadobe="sudo -H killall ACCFinderSync \"Core Sync\" AdobeCRDaemon \"Adobe Creative\" AdobeIPCBroker node \"Adobe Desktop Service\" \"Adobe Crash Reporter\";sudo -H rm -rf \"/Library/LaunchAgents/com.adobe.AAM.Updater-1.0.plist\" \"/Library/LaunchAgents/com.adobe.AdobeCreativeCloud.plist\" \"/Library/LaunchDaemons/com.adobe.*.plist\""

If you put that in your ~/.bash_profile you can then simply type nothankyouadobe or call that from Alfred or any other sort of script.

  • Neat idea making an alias for this (and putting it in your .profile so it runs on restart is nice), but these programs start themselves again.
    – Ulf Aslak
    Commented Nov 28, 2018 at 9:16
  • @UlfAslak what version of CC? I update my list for each version, I'll update this one when I can. Commented Nov 28, 2018 at 9:45
  • thanks so much for this! ... and also what are Adobe playing at these days, I wish they'd get some real competitors on the scene so that it forced them to fix their buggy, overpriced software
    – user206728
    Commented Jun 4, 2020 at 11:17
  • @pealo86 I use the Affinity suite and Acorn. Rarely need to open Adobe apps. Commented Jun 4, 2020 at 11:18

It's created by Core Sync which is /Applications/Utilities/Adobe Creative Cloud/CoreSync/Core Sync.app. When I killed both Core Sync and AdobeIPCBroker, they didn't come back (for that session, anyway).

FWIW, I found out what caused it to be created by using launchctl procinfo.

  • 2
    This doesn't work for me: It still comes back after killing everything. I also disabled, terminated, and unloaded every com.adobe. ... process and daemon. The only thing that finally worked was to delete it with sudo rm -rf AdobeIPCBroker.app. Who knows what the side effects are, but I don't care. (One side effect is that I'm looking to get rid of Adobe apps altogether.)
    – orome
    Commented Jun 4, 2016 at 12:20
  • 2
    Command+I from Activity Monitor can be used to locate the file for deletion.
    – orome
    Commented Oct 18, 2016 at 18:08
  • Actually deleting this doesn't even work anymore.
    – orome
    Commented Aug 18, 2021 at 17:12
  • Get the AdobeIPCBroker launcher info sudo launchctl procinfo <pid>, remove the launcher, repeat this operation several times. When Activity Monitor will not show AdobeIPCBroker anymore. Finally sudo rm -rf AdobeIPCBroker.app
    – Ax_
    Commented Aug 15, 2022 at 8:15

I did a Finder search for "adobeipcbroker" and dragged all three folders and app to the Trash, then emptied it, which worked fine for me on El Capitan.

  • This (and not the solutions below) now work for me (I think). Why does Adobe do this?
    – orome
    Commented Aug 18, 2021 at 17:15

This is what Adobe support say - "You need to close all adobe applications when not in use from the activity monitor at last close adobe IPC monitor." - "We suggest to consumer close all adobe applications then close adobe IPC broker. If they not do so then all process again comes up."

However, after killing all the other Adobe processes, the following just hangs there and even doesn't respond to the kill command

0 77 1 0 10:50pm ?? 0:00.04 /Library/Application Support/Adobe/AdobeGCClient/AGSService

Adobe support wasn't sure what that was.. That one can be removed by a sudo kill command.

-- Okay I'm yet to find what's not working.. so if you choose to do below, take extreme care & caution.

These processes seem to instantiate from the references under following folders: /Library/LaunchAgents /Library/LaunchDaemons

So, essentially if you backup and delete those links, you'll rid-off them. However once you start and Adobe product, still there's going to be a bunch of stale processes like "Core Sync", "Adobe Desktop Service", "CCXProcess", and "CCLibrary" left behind, even after you terminating the software.

However, they don't seem to automatically update the LaunchAgents and LaunchDaemons. So you're good again after a restart of Mac. There goes the "never restart, only sleep" choice! Core Sync and Desktop service seem to drain the battery a bit as well..

I really wish Adobe clean up their software.

So, there you go, a few ways to take care of Adobe processes..!! Good luck!!


The solution is to simply get rid of all Adobe software.

This worked for me and now I enjoy using (less expensive, better designed, better behaved, and easier to use) alternatives.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .