100% Client-SideSecure

TONL to XML

Convert TONL to XML with our free online converter.

Quick Convert

Use the converter below or open in full converter with more options.

Example: TONL input and real XML output

The output below was generated by the same conversion code the converter uses, run on this sample when the page was built.

TONL input (245 characters)

#version 1.0
root:
  log:
    events[4]{latencyMs,level,service,ts}:
      42,info,auth,"2026-09-30T08:12:04Z"
      310,warn,billing,"2026-09-30T08:12:09Z"
      38,info,auth,"2026-09-30T08:12:15Z"
      1204,error,search,"2026-09-30T08:12:21Z"

XML output (577 characters)

<log>
  <events>
    <latencyMs>42</latencyMs>
    <level>info</level>
    <service>auth</service>
    <ts>2026-09-30T08:12:04Z</ts>
  </events>
  <events>
    <latencyMs>310</latencyMs>
    <level>warn</level>
    <service>billing</service>
    <ts>2026-09-30T08:12:09Z</ts>
  </events>
  <events>
    <latencyMs>38</latencyMs>
    <level>info</level>
    <service>auth</service>
    <ts>2026-09-30T08:12:15Z</ts>
  </events>
  <events>
    <latencyMs>1204</latencyMs>
    <level>error</level>
    <service>search</service>
    <ts>2026-09-30T08:12:21Z</ts>
  </events>
</log>

XML output is 136% larger than the TONL input. The same data is 337 characters as minified JSON and 572 as pretty-printed JSON. Sizes are character counts, not tokens: token counts depend on the model's tokenizer (see the tokenizer comparison).

TONL to XML: what changes

Reading TONL: TONL documents start with a #version line and wrap the data in root. The TONL encoder writes object keys in alphabetical order, so the original key order is not kept.
Writing XML: XML needs exactly one root element. Several top-level keys, or a top-level key holding an array, produce sibling roots that are not well-formed XML, which is why this sample is wrapped in a single key. Keys prefixed with @_ become attributes.

About TONL

TONL (Token-Optimized Notation Language) is a compact text format that maps one-to-one to JSON and ships with a query API, schema validation, and streaming. Savings are roughly 32-45% versus JSON in the TONL project's own measurements.

✓Lossless round trip to JSON
✓Query and aggregation API
✓Schema validation (TSL)
✓Streaming for large files

Full TONL Documentation →

About XML

Extensible Markup Language is a verbose but powerful format. Still widely used in legacy systems, SOAP APIs, and document formats.

✓Rich metadata
✓Namespaces
✓Validation schemas
✓Legacy support

Full XML Documentation →

Other Conversions

TONL to JSON TONL to TOON TONL to YAML TONL to TOML TONL to CSV TONL to Protobuf

Why Convert TONL to XML?

Use XML when working with legacy systems, SOAP APIs, or when you need rich metadata and validation schemas.

TONL to XML: Frequently Asked Questions

How do I convert TONL to XML?

Paste your TONL into the editor on json2toon.co. The tool detects the input and produces XML instantly, then you copy the result. Conversion runs entirely in your browser, so nothing is uploaded to a server.

Is the TONL to XML converter free?

Yes. Converting TONL to XML on json2toon.co is free with no account, signup, or usage limit. A free public API is also available for automated, programmatic conversion.

Why convert TONL to XML?

Convert TONL to XML with our free online converter.

What should I watch out for when converting TONL to XML?

XML needs exactly one root element. Several top-level keys, or a top-level key holding an array, produce sibling roots that are not well-formed XML, which is why this sample is wrapped in a single key. Keys prefixed with @_ become attributes.

Is my data safe when I convert TONL to XML?

Yes. The TONL to XML conversion happens client-side in your browser. Your source data stays on your device and is never sent to or stored on a server, which makes it safe for private or sensitive payloads.