How to use this tool
- Choose the source delimiter and header mode.
- Select the output delimiter, quoting and line-ending preferences.
- Convert and check a few fields that contain punctuation before exporting.
How the operation works
The tool parses records first and serializes each field with the new delimiter. A field is quoted if it contains that delimiter, a quote or a newline; internal quotes are doubled. Quote-every-field and CRLF options support stricter import systems. A UTF-8 BOM can help some applications detect encoding.
Why delimiters must change as structure, not as characters
A spreadsheet exported with semicolons often arrives as a single column when a comma-based importer opens it. Global find-and-replace of every comma breaks any value that already contains punctuation. This converter parses each record first, then re-serializes fields with the new separator. Structure and content stay separate.
Quoted fields protect embedded delimiters. A field containing the target delimiter, a double quote or a line break is quoted automatically; internal quotes are doubled. Quote-every-field and CRLF options support stricter import systems that require consistent quoting or Windows-style line endings.
Choosing source and output formats
Comma (CSV) is the default interchange format. Semicolon is common in European locales where the decimal comma is also used. Tab (TSV) avoids delimiter clashes with prose. Pipe is frequent in shell pipelines and log exports. Select the source delimiter that matches the file you loaded—guessing wrong usually produces one oversized column or many empty fields.
Line endings: LF suits Unix tools and many APIs; CRLF suits Excel and Windows-oriented imports. A UTF-8 BOM can help legacy Windows applications detect encoding, but it is an encoding marker, not a visible header character. Some parsers strip it; others treat it as part of the first field.
Worked conversion examples
Input (comma): name,note Ada,"Hello, world" Sam,Plain Semicolon output: name;note Ada;Hello, world Sam;Plain
The comma inside “Hello, world” stays inside the note field because the field was quoted. Without quoting, the note would split into two columns and corrupt the table.
Pipe output of the same data: name|note / Ada|Hello, world / Sam|Plain. Tab output uses an actual tab character between fields. Inspect a few punctuation-heavy rows before downloading the full file.
Common conversion mistakes
Converting a file that already uses the target delimiter produces no visible change but can still alter quoting. Unquoted fields containing the source delimiter would already have been split incorrectly at load time—fix the source first.
Do not mix line-ending styles in one export. Do not strip a BOM unless the destination rejects it. Multi-character separators (for example ::) are not supported; split those with a record-aware script instead of a global replace.
When to use this tool in a pipeline
Typical flow: inspect with CSV Viewer, convert the delimiter here, adjust headers with CSV Column Editor, then convert with CSV to JSON or merge/split. Each step keeps original values; none guesses business meaning.
If the destination application documents a required delimiter and quoting style, convert to that specification and reopen the result in the destination before processing a larger batch.
A worked example
name,note Ada,"Hello, world"
With semicolon output: name;note Ada;Hello, world
Global find-and-replace changes commas inside values and corrupts tables. This converter separates structure from content. A BOM is an encoding marker, not a visible header character.
Processing and privacy
Delimiter conversion parses and re-serializes the table in the page; the file is not sent to a conversion service. Input stays in browser memory until you reset or leave the page. Copy and download run only when you choose them. No tool input is sent to a processing service. Website pages and scripts still make ordinary hosting requests; the privacy policy separates those from tool processing.
Frequently asked questions
Can I choose any delimiter?
This release supports comma, semicolon, tab and pipe. Multi-character separators are not supported.
Does the tool change the values inside fields?
No. Only structural delimiters and quoting change. Field text, spacing and case remain as loaded.
Why did my semicolon file load as one column?
The source delimiter was probably left as comma. Reload with semicolon selected, then convert or export as needed.
Should I keep the UTF-8 BOM?
Keep it if the destination application needs it to detect UTF-8. Remove it only when the importer treats the BOM as part of the first header.
Is a converted file safe to open in Excel?
Structurally yes if quoting and line endings match Excel’s expectations. Identifier columns can still be re-typed on open—import them as text when leading zeros matter.
How this tool was checked
Delimiter Converter was checked with fields containing the target delimiter, doubled quotes, embedded line breaks, CRLF output, a UTF-8 BOM and quote-every-field mode. See the testing method or report a failure.