What is XML / Plist Converter?
XML and Plist Converter connects generic XML documents with Apple's restricted data serialization. Generic XML first enters the object mapping and then becomes XML Property List 1.0. Reverse conversion accepts only supported dictionaries, arrays, and scalars and never loads external DTDs or entities. Common workflows include the following. Generate Apple configuration from generic XML. Convert Plist to generic XML structure. Review dictionaries, arrays, and null compatibility. The page also documents input boundaries, output behavior, and practical cautions so you can review the result before putting it into an application, configuration, test, or production workflow.
When to use it
- Generate Apple configuration from generic XML.
- Convert Plist to generic XML structure.
- Review dictionaries, arrays, and null compatibility.
How to use it
- Choose generic XML or Plist direction.
- Confirm values use supported Plist types.
- Load examples to inspect dictionaries and arrays.
- Convert and resolve null or key/value errors.
- Validate output in the Apple target environment.
- Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.
Runnable examples
The “Example 1” and “Example 2” buttons load the matching inputs. They cover different structures, directions, or boundaries and can be run directly in the workspace.
Example 1
<site><name>JSONLane</name><release><tools>60</tools><ready>true</ready></release></site>Example 2
<?xml version="1.0" encoding="UTF-8"?>
<plist version="1.0"><dict><key>site</key><dict><key>name</key><string>JSONLane</string><key>tools</key><integer>60</integer></dict></dict></plist>Input rules
- Generic XML rejects DTD and ENTITY declarations.
- The Plist root must contain one value.
- Null and unsafe integers are rejected.
- Text input is counted before processing and is limited to 1,000,000 characters on this page; file modes apply the separate file limit shown in the workspace.
- Only XML Plist is supported, not binary Plist.
Output rules
- Plist output uses XML Property List 1.0.
- Reverse XML uses the object mapping.
- Dates, data, and mixed content need review.
- Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
- An empty XML element may map to null, which Plist cannot represent.
Limitations and cautions
- Only XML Plist is supported, not binary Plist.
- An empty XML element may map to null, which Plist cannot represent.
- Dates, data, namespaces, and mixed content require review.
How your data is handled
All parsing, format conversion, Base64 work, and intermediate data remain in the current browser tab. JSONLane does not upload the input or retain it after refresh or close.