TSV Row Field Parser

Parse or format a single backslash-escaped TSV row, preserving empty cells and explicit control escapes; not a Markdown table parser.

Description

Parse or format a single backslash-escaped TSV row, preserving empty cells and explicit control escapes; not a Markdown table parser.

Decoding an escaped TSV row splits on raw tabs and preserves escaped tab content.

When to use this tool

Parse or format a single backslash-escaped TSV row, preserving empty cells and explicit control escapes; not a Markdown table parser.

Prepare the supplied row fields for this operation.
Compare the complete example with the representation used by your own input before carrying the result into another step.

How to use the tool and how it works

Enter row. Use the exact text syntax, units and index conventions explained below.
Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
Read result.cells. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.

Use the strict custom backslash decoder with tab delimiter. Return every cell, including empty ones, and reject invalid or dangling escapes.^[1]

Input field	Meaning and representation	Accepted input
row	row.	Text; at most 8,192 UTF-16 code units, subject to the grammar above

Output field	Interpretation
result	Object containing the named outputs below.
result.cells	The cells list in the ordering and representation described above.

json

{
  "input": {
    "row": "a\tb\\nc"
  },
  "output": {
    "result": {
      "cells": [
        "a",
        "b\nc"
      ]
    }
  }
}

Limitations and assumptions

No quote-based CSV/TSV dialect is recognized. A literal newline is not automatically a record boundary in this single-row operation.
Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.

Alternative or Complementary methods

Choose the exact text grammar before combining serializers and parsers. UTF-16 record lengths, raw separators and custom backslash escapes differ from byte framing, CSV, Markdown and spreadsheet semantics.

References

Tool behavior and example: TSV Row Field Parser — tool.io

Similar or alternative tools

TSV Row Field Formatter
Parse or format a single backslash-escaped TSV row, preserving empty cells and explicit control escapes; not a Markdown table parser.
Pipe Table Row Parser
Parse or format a single backslash-escaped pipe row, preserving empty cells and explicit control escapes; not a Markdown table parser.