Choose a converter by your input and output
Start with the format you have and the format or representation you need. CSV JSON Converter and JSONL CSV Converter work in both directions. Use the first for JSON and CSV, or the second when your records are JSON Lines and you need line-level handling.
For a delimited table that already has the right kind of data but the wrong separator, use Delimiter Converter. It covers comma, tab, semicolon, pipe, and custom delimiters, with controls for quoting, escaping, and null handling. One-way format changes include CSV to Excel Converter, CSV to XML Converter, and Parquet to CSV Converter.
For configuration or document formats that need to become JSON, choose XML to JSON Converter, YAML to JSON Converter, or TOML to JSON Converter. These converters operate toward JSON; they do not convert JSON back to XML, YAML, or TOML. If your task is text encoding rather than format conversion, use Base32 Encoder / Decoder or Base64 Encoder / Decoder.
Convert CSV, TSV, JSONL, and Parquet data
Choose based on the structure of the source and how much control you need over the destination. CSV JSON Converter supports nested-object flattening and un-flattening, array handling, selectable fields, and type inference. JSONL CSV Converter adds line-level error reporting and policies for nested values, headers, nulls, duplicate columns, and type inference.
Use Delimiter Converter when the main change is the dialect of an existing table. Use CSV to Excel Converter when the destination is an XLSX workbook; it provides delimiter and encoding detection, a preview, column types, and multi-sheet output. Use CSV to XML Converter when the destination is XML and you need delimiter, encoding, quoting, column mapping, name sanitization, and indentation controls.
Use Parquet to CSV Converter for Apache Parquet input. It exposes column order, delimiter, quoting, encoding, null, date, decimal, binary, and nested-value choices. A tabular output may represent nested values or source types differently, so review those choices before exporting.
Convert XML, YAML, and TOML documents to JSON
Choose the converter that matches the document syntax. XML to JSON Converter provides attribute-handling choices, selectable root paths, pretty or compact output, and input encoding choices. YAML to JSON Converter provides multi-document policies, pretty or compact output, and indentation choices. TOML to JSON Converter turns TOML configuration content into nested JSON with pretty or compact output and indentation choices.
All three are one-way converters toward JSON. Format-specific details may need review when they are mapped into JSON, especially when the source contains multiple documents, attributes, or other structures that do not have a direct equivalent.
Encode text with Base32 or Base64
Base32 and Base64 are text-encoding tasks, not encryption or compression. Both pages provide automatic, encode, and decode modes. Base32 Encoder / Decoder uses the RFC 4648 alphabet with letters A–Z and digits 2–7. Base64 Encoder / Decoder supports standard and URL-safe Base64 variants, so choose it when the receiving context specifies one of those forms.
Review conversion options before exporting
After choosing the source and destination, inspect the controls provided by that specific converter. Depending on the workflow, you may need to set delimiters, quoting, encoding, nesting, attributes, multi-document handling, indentation, nulls, or type formatting. The tools provide previews, parse or validation errors, or result workspaces according to the tool.
Review the result before using it elsewhere. A successful conversion does not prove that the output matches your intended schema or business meaning. In particular, check delimiter and null handling, nested-value policies for JSONL, Parquet type-loss choices, and YAML multi-document handling. The conversion direction and destination format determine which information can be represented directly.