What is INI / Properties Converter?
This browser-local converter handles INI 与 Properties for configuration migration, fixtures, and format review. It parses the complete input before producing a destination document and rejects structures that cannot be represented safely or unambiguously instead of guessing. Comments, source layout, and some type information may not round-trip, so the destination application must perform the final validation before production use. Common workflows include the following. Migrate configuration fixtures. Generate API test payloads. Review structural differences between formats. 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
- Migrate configuration fixtures.
- Generate API test payloads.
- Review structural differences between formats.
How to use it
- Choose a direction and review the format contract.
- Paste a complete source document or binary Base64 value.
- Convert, read warnings, and inspect the generated structure.
- Validate the result in the destination application.
- Load one of the realistic examples first to verify the selected options and processing direction before replacing it with your own data.
- Review the output, status message, and documented limits; copy, download, or continue only after the result matches your expectation.
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=JSONLane
[release]
tools=80
ready=trueExample 2
site=JSONLane
release.tools=80
release.ready=trueInput rules
- Input must be one complete valid source document.
- Binary input must be complete standard Base64.
- Conflicting, dangerous, or unsafe values are rejected.
- INI and Properties values are treated as text.
- 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.
- Values remain strings.
Output rules
- Output is normalized for the destination format.
- Binary bytes are displayed as Base64.
- Comments and source layout are not retained.
- Review the result against the destination application's rules.
- Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
- Conflicting dotted paths are rejected.
Limitations and cautions
- Values remain strings.
- Conflicting dotted paths are rejected.
- Comments and original layout are not retained.
How your data is handled
All parsing, 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.