YAML / TOML / ENV Config
Choose a supported direction; inspect every rejected value and floating-point notice before exporting.
Content is processed in this browser; no input is uploaded.
No type notices to display.
Result is out of date.
Config converter helps when a service expects another configuration format but its values must keep their meaning. A port written as 0080 in an INI file stays text; a JSON number does not silently become an INI string.
This page includes INI to JSON, JSON to Properties, plist to JSON and TOML to YAML. Twelve verified directions share one workbench. Unsupported pairs remain unavailable, so a format name in the menu does not promise arbitrary conversion.
Check meaning before moving settings
Config converter lists the paths that cannot be represented in the destination. A nested object aimed at Properties is rejected instead of flattened into dotted keys that may collide with existing names.
Each file receives its own result. A ZIP contains successful conversions and a complete report, including files that failed. A partial batch is clearly labelled instead of appearing fully successful.
INI starts with a section. Properties uses a flat key map. The tool does not guess a format from its extension or from a colon that could belong to several grammars.
Text updates after a 350 ms pause by default. Disable automatic conversion to use the button or Ctrl/Cmd+Enter. Batch mode always waits for an explicit run.
Inspect each rejected path and every binary64 notice. Downloads keep all report entries even when the visible list is paginated. ZIP names receive numeric prefixes to avoid collisions.
INI and Java Properties values remain strings. Leading zeroes, true-looking words and literal dotted keys are not interpreted as numbers, booleans or nested paths.
JSON and YAML numbers pass through a lossless syntax tree. TOML and plist real values use binary64 and get explicit notices. Integers outside the signed 64-bit range are rejected for TOML and plist.
Select up to 20 UTF-8 files of one source format. Download a ZIP with successful outputs and conversion-report.json. The numbered output names cannot replace that reserved report.
INI here represents an object whose values are section objects containing strings. Arrays and deeper objects cannot fit that structure, so their paths are reported and no result is exported. Choose JSON or YAML when your consumer needs arrays.
Yes. INI and Properties never infer value types. The characters 001 and false remain strings, while JSON input must already use quotes if the target requires strings. Config converter does not guess a conversion policy for you.
Comments, spacing and quote style are not carried into the new grammar. The normalization notice calls this out. Keep the original file if explanatory comments matter; converting back does not reconstruct them.
A plist data element is a byte sequence, not a JSON string. This version rejects both data and date elements with their paths, rather than inventing base64 or date-text conventions. Only the documented XML subset is accepted.
Yes. Batch mode takes up to 20 files with one chosen source format. Run it manually, inspect partial failures and download the ZIP. Successful outputs and the full per-file report are included, while failed files have no misleading output.
Need another supported case?
Config converter keeps the source available while you check destination constraints. Start with one file, then apply the same selected direction to a batch.
Review the consumer’s format contract before replacing a configuration.