What is CSV / Properties Converter?
CSV and Properties Converter uses row1.name paths to identify records and columns for small fixtures and reviewable configuration. Dotted-path parsing rebuilds consecutive row objects and rejects duplicate keys, conflicts, numbering gaps, and dangerous names. Common workflows include the following. Flatten CSV fixtures into Properties. Restore a table from row paths. Review escapes and dotted-path conflicts. 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 CSV fixtures into Properties.
- Restore a table from row paths.
- Review escapes and dotted-path conflicts.
How to use it
- Choose delimiter and direction.
- Check headers for conflicting dotted paths.
- Use row1.name paths for Properties input.
- Convert and resolve duplicates or conflicts.
- Review escaping and retained string types.
- 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
id,name,status
51,XML INI,develop
60,CSV Properties,readyExample 2
row1.id=51
row1.name=XML INI
row1.status=develop
row2.id=60
row2.name=CSV Properties
row2.status=readyInput rules
- CSV headers must be unique with no empty path segment.
- Properties must form consecutive row1 and row2 objects.
- Conflicts and dangerous keys 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 consecutive row1, row2 objects are accepted.
Output rules
- Cells become row-number and column paths.
- Values remain strings and use Properties escaping.
- Literal dotted headers cannot round-trip losslessly.
- Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
- Dots express nesting, so literal dotted headers can be ambiguous.
Limitations and cautions
- Only consecutive row1, row2 objects are accepted.
- Dots express nesting, so literal dotted headers can be ambiguous.
- Values remain strings and complex types are not inferred.
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.