{{ summaryTitle }} {{ summaryValue }} {{ summaryLine }} {{ badge.label }}: {{ badge.value }}
Review the parsed table and warnings before using an output in another system.
{{ sourceStatus }}
Auto detect prefers comma when candidates tie; pin the separator when the source contract is known.
Examples include :: or ^; line breaks cannot be used as a field delimiter.
Pin the choice when the first source row could reasonably be labels or data.
Choose the format required by the next workflow; the parsed table and profile remain available for review.
Double quote is the interoperable default for spreadsheet-style delimited text.
This control is inactive when Quote character is None.
{{ workflowFeedback }}
Use 0 for all rows or 10–500 for a shorter on-screen review.
rows
Leave off when spaces are meaningful data.
{{ params.trim_fields ? 'On' : 'Off' }}
Leave off to preserve blank records in the converted output.
{{ params.skip_empty_rows ? 'On' : 'Off' }}
CSV, TSV, Markdown, and HTML continue to preserve text cells.
{{ params.detect_types ? 'On' : 'Off' }}
Valid date-only and offset-bearing date-time values remain in explicit ISO form.
{{ params.detect_dates ? 'On' : 'Off' }}
Leave off when an intentionally empty string differs from a missing value.
{{ params.empty_as_null ? 'On' : 'Off' }}
Leave blank for automatic labels. Duplicate and unsafe names are normalized with stable suffixes.
Review generated SQL against the destination dialect and schema before execution.
Use two names separated by a comma, such as records, record.
{{ values.converted_text || '' }}
JSON Converter Convert JSON or JSON Lines into tables and handoff text with record-path selection, flattening controls and warnings for sparse or risky data.
Tab-Separated Values (TSV) Converter Convert TSV and delimiter-separated text into typed table formats with local processing plus clear header, row-width and column-profile checks.
JSON to CSV Converter Turn JSON or JSON Lines into spreadsheet-ready CSV or TSV with controlled record selection, nested-value shaping and formula-risk warnings.
Extensible Markup Language (XML) Converter Turn XML into structured JSON or record-based tables with local parsing, record-path selection, whitespace controls, and schema checks.

Delimited text looks simple until a field contains its own comma, quote, or line break. A reliable conversion must decide where records end, which character separates fields, whether the first row contains names, and how missing or uneven cells should be represented. A visually tidy preview can still be structurally wrong if any of those assumptions are wrong.

CSV is a common exchange convention rather than one perfectly uniform dialect. Spreadsheet exports may use commas, tabs, semicolons, or pipes. Quotes can protect delimiters inside a value, and applications disagree about header rows, blank records, escaping, and type inference. The safest handoff keeps these choices explicit and checks row alignment before converting.

Delimiter
The token between fields. It may contain one to four characters here, except line breaks.
Quote character
A boundary that lets a field contain delimiters or newlines without splitting.
Header row
Optional field names used as record keys, table headings, XML names, or SQL columns.
Row shape
The number and order of fields in each record. Uneven rows need review because padding cannot recover missing meaning.

Type detection is another tradeoff. Turning true into a Boolean and 98.5 into a number helps structured output, but identifiers such as postal codes and account references should often remain text. Leading-zero integers are deliberately left as text. Dates are recognized only when type detection and ISO-date normalization are both enabled.

Conversion changes syntax, not trust. Generated HTML and XML escape markup characters, and SQL string values escape apostrophes, but the output is not checked against a destination schema or executed safely on your behalf. Spreadsheet programs may interpret cells beginning with formula characters as commands, so untrusted data needs a destination-specific formula-injection review.

How to Use This Tool:

Treat parsing as a review step before choosing the destination syntax.

  1. Paste, drop, or select one text file no larger than 2 MiB. The conversion accepts up to 500 data rows and 40 columns.
  2. Choose the Source delimiter, quote character, and quote-escaping rule. Auto detection tests comma, tab, semicolon, and pipe; pin the delimiter when the source contract is known.
  3. Set Header row to present or absent when the first row is ambiguous. Use column-name overrides only when the destination needs different safe identifiers.
  4. Enable trimming, blank-row removal, type detection, date recognition, or null conversion only when those changes match the downstream schema.
  5. Select the output format, then review the parsed rows, irregular-row warnings, column types, and empty-cell counts before copying or downloading the converted text.

Interpreting Results:

The parsed table is the main correctness check. Confirm that quoted delimiters stayed inside their fields, every column shifted into the intended position, and the detected header is genuinely a header. An Irregular row count greater than zero means shorter records were padded with empty cells to match the widest row; the converter cannot know whether the missing value belongs at the end or elsewhere.

  • Compare Requested delimiter with Resolved delimiter whenever auto detection was used.
  • Review column types before using JSON or SQL output. A dominant type summarizes the column; it does not prove every cell follows that type.
  • The completeness chart shows at most the 12 columns with the most empty cells. The column profile retains all columns.
  • Open generated output in a safe review context. Do not execute SQL or allow untrusted spreadsheet formulas merely because parsing succeeded.

Technical Details:

Delimited parsing is a stateful scan. A delimiter or line break ends a field only while the parser is outside a quoted field. Repeated quote characters or backslash escapes can represent a literal quote according to the selected policy. Newlines are normalized before scanning, but spaces remain data unless trimming is enabled.

Transformation Core:

StageGoverning behavior
Resolve dialectUse the pinned delimiter or score comma, tab, semicolon, and pipe from the first 20 parsed rows. Ties keep that candidate order, so comma wins an equal score.
Parse recordsHonor the selected quote and escape policy, optionally trim field edges, optionally skip rows whose cells are all blank, and reject an unclosed quoted field.
Set shapeThe widest row defines column count. Shorter rows are padded on the right, then the selected or detected header policy separates field names from data.
Normalize namesUnsupported characters become underscores, leading digits gain a column_ prefix, blank names receive numbered fallbacks, and duplicates receive numeric suffixes.
Convert valuesOptional detection recognizes Booleans, null-like words, finite numbers without ambiguous leading zeroes, and valid ISO-style dates when date recognition is enabled.
SerializeRows are emitted as delimited text, JSON records or arrays, JSON Lines, Markdown, HTML, XML, or SQL INSERT syntax using format-specific escaping.

Rule Core:

Auto header detection is intentionally conservative. It requires at least two rows, a nonempty first row, unique case-insensitive labels, and label-like first-row text. It then needs either a familiar heading such as id, name, or date, or a type contrast in which later sample cells look numeric, Boolean, or date-like while the first row does not.

ConditionResult
Empty source or no detectable separatorConversion stops; add records or pin the delimiter.
Unclosed quoted fieldConversion stops; correct the quote or escape setting.
More than 500 data rowsConversion stops. A detected header is not counted as a data row.
More than 40 columnsConversion stops.
Preview limit0 shows all rows; otherwise use a whole number from 10 through 500.
Custom delimiterOne to four characters with no carriage return or line feed.

CSV and TSV output use double quotes when a field contains the destination delimiter, a quote, or a line break, and embedded double quotes are doubled. Blank records inside the source remain unless skipping is enabled, while trailing empty lines are discarded. HTML and XML escape markup-sensitive characters. SQL output quotes identifiers and string literals, but it neither creates a schema nor provides a safe execution boundary. JSON Lines writes one JSON object per line.

Privacy and Safety Notes:

Source text is processed in the browser, excluded from shareable settings, and not persisted by the converter. Reloading replaces it.

  • Do not paste secrets unless the device, browser profile, clipboard, and surrounding environment are trusted.
  • Generated HTML, XML, and SQL are inert text here. Review them before insertion into a page, parser, or database.
  • Formula-like spreadsheet cells are not neutralized. Apply the receiving spreadsheet application's current defensive policy before opening untrusted output.

Worked Examples:

Semicolon export with decimal commas

A regional spreadsheet export may use semicolons between fields so values such as 12,50 remain intact. Pin Semicolon instead of trusting a mixed sample. Confirm the parsed table has the expected columns before producing JSON or standard comma-delimited output.

Identifiers kept as text

With type detection enabled, 001 remains text because converting it to the number 1 would discard meaningful zeroes. Values such as true and 5 can still become Boolean and numeric values in JSON, while an empty cell becomes null only when that option is enabled.

References: