‘Sandboxed’ apps (which conform to Apple’s stricter safety protocols, just like these on iOS) will certainly put all of their recordsdata inside ~/Library/Containers
(or ~/Library/Group Containers
. The subfolder for the app is often given the app’s identify, or bundle ID (e.g. com.firm.appname.)
So that you should not want to make use of lsof
, simply browse the Containers folder for the app’s named folder.
You may see that the contents are a mixture of “actual” folders, and aliases to allowed areas, like ~/Library/Fonts/
or the Desktop folder.
Nonetheless, non-sandboxed apps might retailer their recordsdata in any sub-folder of the consumer library immediately, together with:
Preferences
Utility Help
An app’s recordsdata and folders may use the app’s identify, or the bundle ID within the filename. Equally, it may not have any recognizable reference to the app in its identify.
I might even be cautious of ‘app cleaner’ apps, as they will miss recordsdata — or worse, delete the fallacious ones — simply as simply as you’ll be able to. Many have a foul status by way of aggressive advertising and exaggerated claims, notably encouraging the parable of the necessity for ‘common upkeep’.
For many apps, the full quantity of consumer information may be very small — often kilobytes. (Do not forget that on iOS, ‘app information’ additionally contains any paperwork within the app’s folder; however on macOS, it does not.)
For those who delete the app alone, these recordsdata do nothing greater than occupy a tiny little bit of disk area. They do not ‘sluggish your Mac down’ or in any other case harm something: they simply sit there, un-read, and unloved.