Local ConverterAll tools

JSON · XML · TOML · YAML

Convert structured data while preserving nested objects and arrays. Use JSON · XML · TOML · YAML locally with practical instructions, output settings and format limits.

A practical guide

JSON · XML · TOML · YAML

Translate nested data between JSON, XML, TOML and YAML for a configuration or integration workflow. Choose both input and output syntax explicitly, then inspect the resulting structure before using it. Each format has different type and naming rules, so this is a data representation conversion rather than a promise of identical source formatting.

  • Convert a JSON configuration to YAML
  • Create JSON from supported XML data
  • Export a root-object configuration as TOML

How to use JSON · XML · TOML · YAML

  1. Provide the structured source

    Upload a supported text file or paste its contents, keeping the source within eight megabytes. Select the actual input syntax rather than relying only on its filename extension.

  2. Choose the destination syntax

    Select JSON, XML, TOML or YAML as output. Ensure the data can be represented there, including a root object for TOML and suitable element names for XML.

  3. Parse and create the result

    Run Create result to parse the source and serialize the data in the selected syntax. Invalid input or unsupported structures are reported rather than silently repaired.

  4. Compare the nested structure

    Download the output and check objects, arrays, text values and XML attributes. Validate it with the destination application’s schema or expectations before replacing a configuration file.

Understand the settings

Input syntax
Choose input syntax according to the result you need. Available choices: JSON; XML; TOML; YAML. The initial selection is JSON.
Output syntax
Choose output syntax according to the result you need. Available choices: JSON; XML; TOML; YAML. The initial selection is YAML.

A configuration from JSON to YAML

A JSON configuration contains nested service settings and an array of hostnames. Choose JSON input and YAML output, then convert. Check nesting, quoted strings and array values in the YAML before using it in the application that consumes the configuration.

Check your result

Choose a file or enter text where available. Review the settings, create your result and download the new copy. XML uses explicit attributes (@_) and text (#text) keys. TOML requires an object at its root. Dates are exported as ISO strings. Open the saved output in the app or workflow where you plan to use it. Check one representative result before repeating the same settings with more files. The original files stay unchanged.

What to know before you start

  • Files are processed on this device. Browser memory and engine-specific limits apply. Save results before reloading.
  • XML uses explicit attributes (@_) and text (#text) keys. TOML requires an object at its root. Dates are exported as ISO strings.
  • Upload one file with a combined size of at most 100 MB. The completed output must fit within 200 MB.
  • Pasted text and uploaded text have operation-specific UTF-8 byte limits. Productivity tools accept up to 1 MiB (1,048,576 bytes); non-ASCII characters can use several bytes each. If a file is selected, it takes priority over pasted text.
  • Selections and completed jobs stay available while you navigate inside this tab. Use My files to revisit results. Reloading or closing the tab clears the workspace; download results you want to keep first.

JSON · XML · TOML · YAML: common questions

How are XML attributes represented?

XML conversion uses explicit attribute keys prefixed with @_ and text keys such as #text where needed. Inspect these mappings in JSON or YAML output, since they represent XML structure rather than ordinary field names chosen by your application.

Can TOML represent a root array?

This tool requires an object at the root when producing TOML. A source whose top level is an array or scalar must be intentionally restructured before conversion rather than expecting the serializer to invent an appropriate object wrapper.

Are comments and source formatting preserved?

The workflow parses data and writes a new representation, so comments and original formatting are not the primary output. Review semantic values and destination conventions rather than expecting source indentation, quoting style or comments to survive unchanged.

What happens to date values?

Parsed date values are exported as ISO strings. Check the destination application’s expected date handling, because a textual ISO representation and a format-specific date type may behave differently when a configuration or integration loads the output.

Does JSON · XML · TOML · YAML upload files to another service?

Processing runs in this browser, on your device. Files and pasted input are not uploaded to a conversion server. The website and required engine assets must load first; large operations depend on available device memory.

Can I continue after changing pages?

Selections and completed jobs stay available while you navigate inside this tab. Use My files to revisit results. Reloading or closing the tab clears the workspace; download results you want to keep first.