Short answer: paste the file, pick a direction. Errors come back with the line and column the parser stopped at, and lossy conversions are refused instead of applied.
The three places TOML and JSON disagree
- Dates. TOML has four date types; JSON has none. They become ISO strings going to JSON, and stay strings coming back.
- Null. TOML has no null. A JSON null is an error, not an empty value — the alternative is dropping a key you meant to keep.
- Heterogeneous arrays.
[1, "a"]is legal JSON and illegal TOML. The converter names the path rather than coercing the values.
Round-tripping
A TOML file without dates or comments survives JSON → TOML → JSON unchanged. Comments are the first casualty, because JSON cannot represent them; if a comment matters, keep the original file and use this page to inspect rather than to rewrite.
Checking the converted JSON against a contract? TheJSON Schema validator reports the exact path that fails.