WebToolsForAll

Tools / Data Converters

Structured data converter

Choose explicit formats for a bounded document conversion or structural view.

Input

0 UTF-16 code units

Inputs start empty. Load example fills them only when you choose it. Reset clears current inputs and results.

Import a local text file

Output

Flat records must have the same columns. CSV and TSV input cells stay strings.
More options: print and local draft
Optional local draft
Saving stores a plaintext draft in this browser on this device. Do not save secrets or use this on a shared device. Nothing is saved or loaded automatically. Reset does not delete a saved draft; use Delete local draft.
No draft has been loaded.
Work through the task
Convert, inspect or serialize a document using explicit source and output formats.
  1. Select both formats before entering the source. Use inspect actions for format, compact, validate or value-tree output.
  2. CSV/TSV import produces an array of string-valued records. XML uses the ordered node tree; it does not infer a flat object.
  3. Review the result before copying or downloading. Editing an input invalidates the previous result; keep an original if the transformation matters.
Example to check
A CSV table v followed by 007 converts to [{"v":"007"}], including the array wrapper.
Limits and output behavior
Source is limited to 100,000 characters. JSON/YAML/TOML have 10,000 values and 40 data levels; XML has separate node/attribute and element-depth guards. Comments, numeric spelling and other lexical formatting may normalize. YAML aliases/custom tags and TOML null values are unsupported. Table output requires compatible flat records and matching keys. Scalar stringification is an explicit choice and loses recoverable number/boolean types.
Troubleshooting
Confirm both selected formats, then read the source parser’s first error. CSV/TSV need a valid header/data table; XML needs its ordered node mapping. Unsupported cross-format types are rejected.
Questions
Does choosing a target format infer a flat XML-to-record mapping?
No. XML uses the documented ordered node tree. Table output requires compatible flat records with matching keys; conversions do not invent a schema.
Input and privacy
Processing runs in this browser. Inputs are not saved automatically. An explicitly chosen local draft, where offered, is plaintext storage on this device. Downloaded files, clipboard contents and browser extensions have separate retention behavior.