Inspect a property list as readable JSON on Mac
A property list may be stored as XML or in a binary format that a text editor cannot display usefully. Lemora can read either and write an indented JSON copy for inspection. Use that copy to understand the keys and values while keeping the original plist as the authoritative source.
Make a readable copy without replacing the plist
- Locate the property list in Finder. If it belongs to a project or configuration package, keep the original in place and work from a copy you can identify.
- With Lemora running, select the plist and press Shift-Command-E. Choose JSON on the Convert page.
- Open the saved .json file in a text editor and inspect its keys, arrays and values.
- Pay particular attention to dates and data values, which are represented as strings in the JSON copy.
- Keep the JSON as a reference. Do not replace the application's plist with it unless that application explicitly accepts JSON configuration.
Results are saved beside the originals when folder access is available, or in Downloads/Lemora otherwise. Source files are never overwritten.
Where to find these actions
- Convert → JSON (Convert to JSON): The web's data format, neatly indented. Key order is kept.
- Tools → Tidy: Lay it out neatly, in the same format.
What you get
An indented JSON inspection copy
Property list dates become text timestamps and binary data becomes base64 text. This representation is useful for reading, but it does not preserve every plist type for a round trip.
Works with: Readable binary or XML property list files saved in Finder.
A readable representation is different from the original format
Both XML and binary plists can store structured values. JSON makes much of that structure convenient to inspect in a text editor, but it has a different type system. A successful conversion means the copy was written; it does not mean every application that expects the plist can consume the JSON.
Dates and data need special attention
Lemora represents plist dates as ISO-style timestamp strings and binary data as base64 strings. Those strings describe the values, but they are no longer plist date or data types inside the JSON file. Converting that JSON back should not be treated as an exact restoration of the original typed values.
Key order is not a record of the original file
Property lists do not provide the same ordered-key model as the JSON reader. Lemora sorts plist dictionary keys when building its readable representation. Use the output to inspect relationships and values rather than to infer how the original file was authored or ordered.
Keep configuration changes separate from inspection
Reading a converted copy is a reversible way to investigate a file. Editing a live configuration is a different task: an application may require particular types, keys or values. Check its documentation and use an appropriate editor when making changes. Do not assume a conversion tool validates the application's configuration rules.
Check for private values before sharing an example
A readable configuration can contain local paths, account details or tokens. Review the actual values before attaching the JSON to an issue or sending it to someone else. A small, edited example may explain the structure without disclosing the whole configuration. Conversion itself runs locally on your Mac.
Questions
Can it read a binary plist?
Yes. Lemora's property list reader accepts binary and XML property lists, then writes a separate JSON result.
Is the JSON a backup that preserves every plist type?
No. Keep the original plist. Dates and binary data are represented as text in the JSON copy.
Can Tidy make the property list readable instead?
Tidy writes the same data format in a readable form; for a plist it writes XML. Choose JSON when you specifically want a JSON inspection copy.
Try this workflow on your Mac
Download Lemora on the Mac App Store Free to try: every feature for your first 25 actions. macOS 15 or later.