Chapter in this post:
The abbreviation “plist” stands for “Property List” and describes a file type that is used under macOS to save information from apps. On the Apple support page for developers you can find the following explanation (translated via DeepL):
About Information Property List files: A Property List File is a structured text file that contains essential configuration information for a bundled executable file. The file itself is usually encoded with the Unicode encoding UTF-8 and the content is structured with XML. The root XML node is a dictionary, the content of which is a series of keys and values that describe various aspects of the bundle. The system uses these keys and values to obtain information about your app and its configuration. Therefore, all bundled executables (plug-ins, frameworks, and apps) are expected to have an informational properties file.
The files that the Mac creates to store program information used to be pure XML files that humans could see and understand. Unfortunately, this had a major disadvantage, because the readability of the files made them very inefficient in terms of memory requirements.
For this reason, Apple introduced the XML-plist format with Mac OS X Jaguar (10.2), which is now significantly less memory-consuming.
With Mac OS X Lion (10.7) Apple has delivered a terminal command with the command “plutil” with which plist files can be converted into other formats, such as “readable” XML and JSON.
You can see how that works in the blog post from ScriptingOSX.com ...
Here is a sample command to convert a .plist file to readable XML:
$ plutil -convert xml1 /path/to/propertylist.plist
There are a few other formats that plutil offers as a target, but these can be displayed with the command "plutil -help".
There are several places you might come across plist files. Some apps have plist files in the / Contents / folder. You can see this when you right-click on an app and then select "Show package contents".
Otherwise you can also look in the following folders and their sub-folders:
Generally, yes. As far as I know, they are deleted and recreated with every Safe Mode boot when you use an app for the first time and then close it again. My reader Beatrix (developer of the software Mail Archiver X) but just wrote me that deleting does not work because the data is being held in the cache. This means that in order for the deletion to actually have an effect, you have to log out and log in again or restart the Mac immediately.
This means that the plist file usually does not contain any important information, but rather, for example, settings such as window positions, window sizes, the files last opened or the like.
There are also some posts on my blog that fix issues by deleting plist files, among other things:
Beatrix gave me the following app tip: With the "Pref's Editor"by Thomas Tempelmann, plist files from macOS or from other apps can be changed and also deleted in an easy-to-read table view. So if you need to do a little bit of work on a certain thing, you should use this tool (which is a GUI for the "defaults" command is) have found a fairly comfortable solution.
I stumbled across an interesting post on Stackexchange, which is about someone using the vi editor in the Port wanted to edit an app's plist file. However, this was acknowledged by macOS with an error message:
The file "Info.plist" could not be unlocked.
Simply translated: The file could not be opened for editing. The user therefore lacks the appropriate access rights.
After changing the access rights and the owner, via the information window in the Finder it worked. You can see exactly how it works here in the thread.
Jens has been running the blog since 2012. He appears as Sir Apfelot for his readers and helps them with problems of a technical nature. In his free time he drives electric unicycles, takes photos (preferably with his iPhone, of course), climbs around in the Hessian mountains or hikes with the family. His articles deal with Apple products, news from the world of drones or solutions for current bugs.