TOOLS / 06 / FLAGSHIP / STRUCTURED ENGINE V1

Data Transformer

Move structured data between JSON, CSV, TSV, YAML, TOML and XML. Preserve nested structure when possible or explicitly project it into a filterable table before export.

DATA TRANSFORMER / STRUCTURED DATA ENGINE V1OPEN FILE CSV READY

INPUT

→

OUTPUT

CONVERSION MODELNested objects/arrays are preserved when the target format can represent them.

SOURCE DATA137 BYTES

RFC-style CSV quoting / PARSE OK

TRANSFORMLOCAL

INFER CSV/TSV TYPESPRETTY JSONFILTER ROWS

PROJECT COLUMNS

nameenginestatusscore

OUTPUT / JSON399 CHARS

[
  {
    "name": "LENS",
    "engine": "File Intelligence",
    "status": "live",
    "score": 96
  },
  {
    "name": "WIPE",
    "engine": "Privacy",
    "status": "live",
    "score": 97
  },
  {
    "name": "QR Scan",
    "engine": "QR Intelligence",
    "status": "live",
    "score": 98
  },
  {
    "name": "DIFF",
    "engine": "Universal Diff",
    "status": "live",
    "score": 100
  }
]

TABLE PROJECTION / FIRST 100 ROWS4 ROWS

NO TABULAR COLUMNS

COVERAGE CONTRACT

JSON / CSV / TSV use strict deterministic parsers. YAML accepts maps, lists and scalars while rejecting anchors/tags/multi-document streams. TOML accepts tables, arrays-of-tables, dotted keys, arrays and inline tables; multiline strings are rejected. XML uses an XXE-safe element profile with attributes, text and repeated nodes; DTD/entities are rejected instead of silently changing data.

SOURCE CSVTARGET JSONNODES 21DEPTH 2MODE STRUCTURE

LOCAL / PRIVATENo upload

Parsing and serialization happen inside the browser. Source data is not sent to 2XBR.

FORMAT / V286 formats

JSON, CSV, TSV, YAML, TOML and XML are live with an explicit coverage contract. Unsupported advanced syntax stops with an error instead of being guessed.

SAFETY / LIMIT1.5 MB

The public utility has a deliberate browser limit and rejects XML DTD/entity declarations rather than exposing an unsafe parser surface.