Vignar
Home / Guides / Data

Working with CSV and structured data

JSON, CSV, TSV, XML, and YAML represent data in different ways. Before converting, check the source structure and choose a target that can express the same information.

Vignar’s data converter supports JSON, CSV, TSV, XML, and YAML. It can parse a data file or text and convert between supported formats. This is useful for small configuration files, simple tables, and data interchange. It is not a database migration tool, and the result should be checked before it is used in production.

Understand the formats

JSON

Represents objects, arrays, strings, numbers, booleans, and null. Its nested structure is useful for APIs and configuration. Validate syntax and ensure keys are quoted.

CSV

Stores rows and columns as text separated by commas. Quoting rules matter when cells contain commas, quotes, or newlines.

TSV

Uses tab characters between fields. It can be convenient for spreadsheet copy-and-paste, but literal tabs inside cells need care.

XML

Uses named tags to represent a tree. Element names have naming constraints, and repeated values often need repeated child elements.

YAML

Uses indentation and punctuation to describe nested values. Whitespace affects meaning; use spaces consistently and review indentation after editing.

Prepare the input

  1. Keep an untouched copy of the original data.
  2. For JSON, check for missing commas, trailing commas, and unquoted keys.
  3. For CSV or TSV, verify the delimiter and ensure fields containing separators are correctly quoted or escaped.
  4. For YAML, use spaces rather than tabs for indentation and quote values that could be mistaken for numbers, booleans, or null.
  5. For XML, use a single root element and escape characters such as ampersands in text values.

Check meaning, not just syntax

A converted file can be syntactically valid while changing meaning. A CSV table cannot naturally represent arbitrary nested arrays and objects. Conversion may flatten values or represent nested data in a way that depends on the selected converter. XML element names also cannot represent every possible JSON key unchanged. Inspect sample records before converting a large dataset and compare totals, identifiers, empty values, and data types.

Safer workflow

Start with a small representative sample. Convert it, open the result with the intended application, and compare a few records from the beginning, middle, and end. For business-critical data, use a format-aware validator or your application’s own import preview. Vignar does not promise schema validation or application-specific compatibility.

Frequently asked questions

Why did a number turn into text?

Text formats often do not preserve a separate type for every value. Spreadsheet software may also infer types when opening a file. Check identifiers with leading zeros, large integers, and date-like strings carefully.

Which delimiter should I use?

Use the separator actually present in your file. A CSV file normally uses commas; a TSV file uses tabs. Changing the label without changing the data will misalign columns.

Vignar processes selected data in your browser and does not intentionally upload it to a Vignar server. Do not use a browser converter as a substitute for your organization’s secure handling requirements. See the Privacy Policy.

Open Vignar and choose Data.