Processed in your browser

XML / Properties Converter

XML objects flatten into dotted keys and repeated elements become JSON text. Properties import rebuilds structure and must ultimately provide one XML root key.

Processed in your browser
0 / 1,000,000
Converted output

Tool guide

What is XML / Properties Converter?

XML and Properties Converter bridges Java settings, resource keys, and hierarchical documents. XML objects flatten into dotted paths and repeated elements become JSON text. Reverse conversion rebuilds nesting with one root key while rejecting duplicate paths, conflicts, and prototype-pollution names. Common workflows include the following. Flatten XML configuration into properties. Generate hierarchical XML from Properties. Review dotted paths and repeated elements. 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

  • Flatten XML configuration into properties.
  • Generate hierarchical XML from Properties.
  • Review dotted paths and repeated elements.

How to use it

  1. Choose a conversion direction.
  2. Review attribute and repeated-element mapping.
  3. Confirm dots represent nested Properties paths.
  4. Convert and resolve duplicates or conflicts.
  5. Review arrays and retained string types.
  6. 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 lang="zh-CN"><name>JSONLane</name><release><tools>60</tools></release></site>

Example 2

site.name=JSONLane
site.release.tools=60
site.release.status=verified

Input rules

  • XML must be safe and complete.
  • Properties paths cannot duplicate or conflict.
  • Reverse output must have one root key.
  • 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.
  • Arrays and repeated elements export as JSON text.

Output rules

  • Nested objects use dotted paths.
  • Arrays and repeated elements become JSON text.
  • Properties values remain strings.
  • Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
  • Properties values do not automatically recover numeric or boolean types.

Limitations and cautions

  • Arrays and repeated elements export as JSON text.
  • Properties values do not automatically recover numeric or boolean types.
  • Reverse conversion must create one valid XML root key.

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.

FAQ

Is XML or Properties content uploaded?

No. Parsing, conversion, and output generation remain in the current browser tab.

Is every round trip lossless?

No. Comments, layout, type systems, and binary capabilities differ, so the page lists areas that require review.

Why can valid input still be rejected?

The destination may not have a safe, unambiguous representation. Dangerous keys, unsafe integers, excess depth, and ambiguous mappings are rejected.

How are repeated XML elements exported?

Arrays are stored as JSON text rather than split ambiguously on commas.

Do dots always mean nesting?

They do on import, so literal dotted names cannot be distinguished losslessly.

Do Properties comments enter XML?

No. Parsing retains keys and values only.

Updated: 2026-08-09