What is TOML / INI Converter?
TOML and INI Converter targets straightforward application settings and migration review. TOML root scalars and one table level map to INI keys and sections. Reverse import keeps values as strings instead of guessing ports, versions, booleans, or leading-zero identifiers. Deeper nesting, duplicates, and values without a clear representation are rejected, and the destination application must still validate the result. Common workflows include the following. Migrate simple service settings. Generate reviewable TOML from INI. Inspect section depth and string typing. 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 simple service settings.
- Generate reviewable TOML from INI.
- Inspect section depth and string typing.
How to use it
- Choose TOML or INI direction.
- Limit data to root scalars and one table level.
- Convert and resolve duplicate keys.
- Review strings and dates in the target 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 = 70
ready = trueExample 2
site=JSONLane
[release]
tools=70
ready=trueInput rules
- TOML supports root scalars and one table level here.
- INI sections and keys cannot repeat.
- Unrepresentable values 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 root scalars and one section level are supported.
Output rules
- INI imports remain strings.
- TOML tables become INI sections.
- Comments and layout are not retained.
- Output reflects only the current input, direction, and options; rerun after changing a mode or value instead of treating an earlier result as current.
- INI imports remain strings.
Limitations and cautions
- Only root scalars and one section level are supported.
- INI imports remain strings.
- Comments and source 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.