Use Delimited data and aligned columns without hiding data-shape changes
This tool helps you space columns for quick human reading, or turn consistently aligned text back into comma, tab, semicolon, or pipe-delimited rows. It is intended for terminal notes, documentation examples, issue reports, and quick visual comparisons. Paste a small representative sample first, choose the direction, and compare the visible result with the source before you use a larger file. The page never sends the working data to NexaCurrent, so ordinary conversion stays inside the current browser tab.
Try a small table with a header, short codes, longer names, and Unicode city values. The result area reports the number of data rows and lists the columns it read. Check the visual boundaries carefully because two or more spaces mark a new aligned column. If the two formats describe data differently, the page explains the exact compromise instead of simply announcing that the conversion succeeded. That review step matters whenever the result will feed another application.
Choose the delimiter and define clear column boundaries
Choose Delimited to aligned to create a compact table for notes or documentation. Select comma, tab, semicolon, or pipe to match the source. Choose Aligned to delimited for the reverse direction, and select the separator required by the destination. Two or more spaces define each aligned boundary, while a single space remains part of a value.
The aligned view measures wide East Asian characters and emoji by their displayed width so multilingual rows remain readable in a monospaced result. When downloading delimited output, ordinary UTF-8 works for most applications; the optional UTF-8 marker helps older spreadsheet programs recognize non-English characters.
Check the detected columns before downloading
Use the mapping preview to confirm how many columns were detected and where each heading begins. Two or more spaces mark an aligned column boundary, so free-form values containing repeated spaces can be ambiguous. If prose contains deliberate runs of spaces, keep it in a quoted CSV or TSV field rather than relying on the aligned-text direction.
Aligned text is intended for human reading, not as a replacement for a schema-aware data format. It does not carry field types, formulas, null markers, or quoting metadata. When converting back, inspect the row count and a few long or multilingual values, then open the downloaded delimiter format in its destination before discarding the source.
Keep multilingual columns visually aligned
Short codes, long labels, accented names, CJK text, and emoji are padded according to their visible width. This keeps columns readable in the result box and in a monospaced editor. The source still needs a consistent number of fields on every row; an incomplete row stops with an error instead of shifting later values into the wrong columns.
For the reverse direction, each column must be separated by at least two spaces. Values may contain single spaces, such as a person's full name, without creating another column. Empty fields and values containing deliberate repeated spaces are ambiguous in aligned text, so the converter asks you to keep those records as CSV or TSV instead of creating a result that cannot be reversed reliably.
Limits, errors, privacy, and a practical final check
Empty input, unclosed or misplaced quotation marks, inconsistent row widths, duplicate headings, ambiguous aligned boundaries, and oversized tables stop with a visible message. The page limits rows, columns, total cells, and input length so an accidental paste cannot freeze the tab. For a very large export, use a streaming desktop or command-line workflow.
Reset clears the input, result, mapping notice, warning, and download. Before sharing a converted file, open it in the intended destination, count the rows, and inspect values containing punctuation, repeated spaces, quotes, or non-English text. A successful conversion confirms consistent field boundaries; it does not prove that a private import rule will accept every value.