What delimiters are
The character that separates one field from the next
A delimiter marks field boundaries in each record. Commas are common, but regional spreadsheets, databases, command-line tools, and data feeds may expect semicolons, tabs, or pipes. Conversion changes only those structural separators.
When conversion helps
Match the format an import or workflow expects
Use a comma-to-tab CSV conversion for a tab-separated import, semicolon-to-comma conversion after a regional spreadsheet export, or a pipe-delimited converter for systems that reserve commas inside ordinary text.
Supported formats
Four common separators, converted in any direction
- Comma: the conventional CSV separator
- Semicolon: common when commas are decimal marks
- Tab: compact and easy to paste into spreadsheets
- Pipe: visible in logs, exports, and data feeds
Common import problems
Wrong separators can make a complete file look broken
- Everything appears in one column. The importer expected a different separator.
- Text splits into extra fields. Unquoted values contain the chosen delimiter.
- Rows have inconsistent widths. A separator or closing quote may be missing in the source.
- Characters display incorrectly. The destination may not support the source encoding.
Examples
Common delimiter conversions
| Source | Output | Typical use |
|---|---|---|
| Comma | Tab | TSV import or spreadsheet paste |
| Semicolon | Comma | Normalize a regional export |
| Pipe | Comma | Open a data feed in common CSV tools |
| Tab | Pipe | Create a visibly separated text feed |
CSV Toolkit
Inspect, prepare, and clean files locally
FAQ
Questions about delimiter conversion
Does UtilityDock upload my file?
No. Your files never leave your computer. Detection, conversion, preview, and download all happen locally inside your browser.
Which delimiters can I convert?
UtilityDock detects and converts between comma, semicolon, tab, and pipe delimiters in any supported direction.
Will quoted values stay intact?
Yes. Quoted fields, escaped quotes, embedded delimiters, and line breaks inside values are parsed and serialized as valid delimited fields.
Does conversion change encoding or line endings?
No. UTF-8 or UTF-16 encoding, an existing byte-order mark, and every original record ending are preserved.
Why do I see an inconsistent-row warning?
The detected separator produced different field counts across sampled records. Conversion remains available, but you should inspect missing separators or malformed source rows.