CSV to Delimited Converter Online Free

CSV to Delimited Converter

Comma-separated values are the default for many exports, but they are not the only delimiter that systems expect. European Excel locales often treat semicolon as the field separator. Analytics pipelines and Unix tools prefer TSV (tab-separated values). Legacy importers may demand pipe (|), caret, or another custom character. This free CSV to delimited converter rewrites a comma-separated grid into TSV, semicolon-separated, pipe-separated, or any single-character delimiter you choose — without retyping cells by hand.

Paste CSV or upload a .csv file, pick the target delimiter, and copy or download the result. Quoting is applied so that cells containing the new delimiter, quotes, or newlines stay intact as one field. Conversion runs entirely in your browser — your spreadsheet content is not uploaded to a server as part of the transform.

Below you will find how delimiter families differ, why regional Excel settings force semicolon CSV, how RFC 4180-style quoting works when you change separators, when TSV is safer than commas, how custom delimiters interact with escaping, privacy and client-side limits, and a full troubleshooting and FAQ section for real interchange workflows. Prefer Fixed Width to CSV when the source is positional text rather than delimited, and use the Online CSV Editor when you need to clean headers or drop columns before you re-delimit.

Key features

Converts standard comma CSV into TSV, semicolon-separated, pipe-separated, or a custom single-character delimiter.
Applies quoting rules so fields that contain the target delimiter, quotes, or newlines remain one logical cell.
Preserves header row and column order so the logical spreadsheet shape does not change with the separator.
Supports regional Excel workflows where semicolon is the expected list separator.
Accepts pasted CSV or file upload for the same client-side transform path.
Runs entirely in the browser so export contents are not sent to a server for the delimiter rewrite.
Produces copy-or-download-ready text for partners, Excel, and downstream CLI or ETL tools.

About the CSV to delimited text format

“CSV” loosely means a rectangular text file with a header row and records, but the separator between fields is a convention, not a universal constant. Classic US/UK exports use comma (,). Many Western European Excel installations use semicolon (;) because comma is already the decimal mark. TSV uses a tab character. Pipe-separated files use | between cells. Some warehouses and EDI feeds use other single characters entirely.

This converter parses your input as comma-separated CSV (honoring quoted fields so commas inside cells are not treated as boundaries), then serializes each row again using the delimiter you select. Cells that contain the target delimiter, double quotes, or line breaks are wrapped in quotes and internal quotes are doubled, following the same quoting rules spreadsheets and most parsers expect.

Changing the delimiter does not change the logical grid: column order, header names, and cell values stay the same. What changes is only the character that separates fields on each line — and which characters now require quoting. A cell that needed quotes for commas may not need them for tabs, and a cell with an embedded semicolon suddenly needs quotes when you switch to semicolon-separated output for Excel in France or Germany.

How it works

The converter reads your paste or file as CSV: the first row becomes headers, commas separate fields, and quoted segments may contain commas and newlines without splitting the cell. That parse step rebuilds an in-memory grid of strings — the true table — independent of any particular delimiter.

You choose the output delimiter (tab, semicolon, pipe, or custom). Each row is written back as text with that character between cells. If a cell contains the delimiter, a double quote, or a line break, the cell is enclosed in double quotes and any internal " is doubled to "" so parsers can round-trip the value.

The result is plain text in the new delimited dialect. You copy it into a .tsv/.txt/.csv file or download it for Excel and partners. The grid’s meaning is unchanged; only the wire format of field boundaries changes.

Common use cases

Preparing a US-exported CSV for Excel users whose regional settings expect semicolon as the list separator.
Converting comma CSV to TSV for paste into terminals, awk/cut pipelines, or tools that treat tabs as the field boundary.
Producing pipe-separated files for legacy importers, banks, or EDI-style batch jobs that reject commas.
Rewriting a vendor CSV with a custom delimiter required by an internal warehouse or middleware contract.
Normalizing mixed team exports so everyone shares one delimiter before merging sheets in the Online CSV Editor.
Round-tripping cleaned data back to a partner’s preferred separator after editing headers and rows locally.

How to use this tool

Paste your comma-separated CSV or upload a .csv file, and confirm the preview shows the expected columns.
Select the target delimiter: tab (TSV), semicolon, pipe, or a custom character required by your importer.
Convert and scan a few rows that contain commas, quotes, or the new delimiter for correct quoting.
Copy or download the output and, if needed, rename the extension (.tsv, .txt, or .csv) to match partner expectations.
Open a sample in Excel, Sheets, or your importer with the matching separator setting and verify row and column counts.

Example

Input CSV (comma)

Name,City,Notes
Ada,London,"Hello, world"
Grace,New York,OK

Output (semicolon)

Name;City;Notes
Ada;London;"Hello, world"
Grace;New York;OK

Tips for best results

Choose semicolon when the audience will open the file in Excel with European (or other) locales that use comma as the decimal separator.
Prefer TSV when cells contain many commas (addresses, prose) and you want fewer quoted fields in the output.
Never pick a delimiter that appears constantly inside your data without quoting — the converter quotes, but noisy delimiters still hurt hand review.
Spot-check cells that contain quotes, newlines, or the new delimiter after conversion — those are the quoting edge cases.
Clean blank columns and messy headers in the Online CSV Editor before re-delimiting so every consumer sees the same schema.
If the source is space-aligned positional text, use Fixed Width to CSV first; delimiter conversion alone cannot invent column cuts.
Keep a copy of the original comma CSV until row counts and a few edge rows match in the target format.

Common errors and how to fix them

Excel shows every row as a single column after I download semicolon-separated data.: Your Excel locale may still be expecting commas, or you opened the file by double-click instead of Import. Use Data → From Text/CSV (or Text Import) and set the delimiter to semicolon explicitly. Conversely, if you left the file as comma-separated for a semicolon locale, switch this tool to semicolon output so Excel’s default list separator matches.
A cell that contains the new delimiter splits into extra columns in the target system.: Fields containing the output delimiter must be quoted. Re-convert with this tool rather than hand-splitting lines. If a downstream system ignores quotes, pick a rarer delimiter or ask the partner to enable RFC-style CSV parsing.
Tabs disappeared and columns merged after I pasted TSV into email or a rich-text doc.: Many rich-text surfaces convert tabs to spaces. Paste into a plain-text editor, terminal, or spreadsheet import dialog instead. Prefer downloading a .tsv file over copying through formatted mail when fidelity matters.
Quotes appear doubled or look “wrong” in the output ("" inside cells).: Doubled quotes inside a quoted field are correct CSV escaping for a literal quote character. Spreadsheet apps display a single quote when they parse the file. If you see raw "" in Excel, you may have imported as plain text without a CSV parser — use the text import wizard with the right delimiter.
My source “CSV” was actually fixed-width or already pipe-separated, and columns are garbage.: This tool expects comma-separated input with standard quoting. For column-aligned reports, use Fixed Width to CSV first. If the file is already pipe- or semicolon-separated, open or normalize it to a true grid (for example via the Online CSV Editor or a matching import) before choosing a new delimiter here.
Line breaks inside a cell break the row when a partner’s script splits on newlines only.: Multiline fields are valid when quoted, but naive line-split scripts ignore quoting. Ask the partner to use a proper CSV/TSV parser, or flatten newlines in the Online CSV Editor before re-delimiting if their stack cannot handle multiline cells.

Best practices

Match the delimiter to the consumer: semicolon for many EU Excel users, tab for CLI pipelines, pipe only when the contract says so.
Document the delimiter and encoding (UTF-8) in the same README or email as the file so recipients do not guess.
Curate the grid in the Online CSV Editor — drop junk columns, fix headers — then convert once to the partner delimiter.
Validate with row counts and a checksum on a key column after the other side imports, not only by “it opened.”
Avoid exotic multi-character delimiters; stick to a single character most parsers understand.
Keep the canonical working copy as comma CSV or a spreadsheet, and treat other delimiters as export dialects.
When data started as fixed-width, convert to CSV with Fixed Width to CSV before any delimiter rewrite so boundaries are real fields.

What CSV to delimited conversion actually does

Delimiter conversion is a serialize-after-parse operation. The tool first interprets comma-separated text as a table of cells, respecting quotes. It then writes that same table using a different separator character between fields.

You keep labels and values. You do not keep Excel number formats, formulas, or workbook styles — those never lived in the CSV text. The job is interchange between systems that disagree on what character means “next column.”

The tool does not invent schema, detect the input delimiter automatically across every dialect, or fix broken rows. Feed it well-formed comma CSV (or clean it first); choose the output delimiter your audience requires.

When to change delimiters (and when not to)

Change delimiters when a named consumer requires it: regional Excel, a TSV-only loader, a pipe-separated bank file, or a custom middleware contract. The logical data is already correct; only the wire format must match.

Skip conversion when both sides already agree on comma CSV — extra hops only add risk. Skip when the file is not delimited at all (fixed-width print files); use Fixed Width to CSV instead. Skip when the real problem is dirty headers or merged junk columns — clean those in the Online CSV Editor first.

A practical pattern: keep an internal canonical CSV, generate partner-specific delimited exports on demand, and never hand-edit separators inside quoted fields.

Good fit: EU Excel semicolon files, TSV for shell tools, pipe files per vendor spec.
Poor fit: guessing delimiters on corrupt text, “fixing” positional reports with a new separator.
Clean first: blank headers, extra trailing commas, inconsistent column counts.

Comma, semicolon, tab, and pipe — the common dialects

Comma is the lingua franca of downloads labeled .csv in US-centric software. It collides with decimal commas and with prose that contains list commas, which is why quoting exists.

Semicolon is the usual Excel “CSV” dialect when the OS locale uses comma for decimals. Many European users double-click a semicolon file and see proper columns, while a comma file lands in one column.

Tab (TSV) rarely appears inside ordinary cell text, so TSV often needs less quoting than comma CSV. Pipe is popular in legacy feeds because it is visible and uncommon in names — until someone puts a pipe in a note field, at which point quoting matters again.

Regional Excel and the semicolon list separator

Excel does not always treat comma as the field separator. In locales where the decimal separator is a comma, Excel commonly uses semicolon as the list separator for CSV open/save. Shipping a US comma file to those users produces a familiar failure: one column per row, commas visible inside the cell.

This converter’s semicolon mode exists for that handoff. Parse as comma CSV on your side, emit semicolon-separated text, and tell recipients the file uses semicolons — or have them use the import wizard if their Excel build still disagrees.

Remember that Excel may still reinterpret dates and leading-zero IDs after open. Delimiter choice fixes column splits; it does not disable spreadsheet type guessing. Format critical ID columns as text on import when needed.

Quoting rules when the delimiter changes

Under common CSV rules (aligned with RFC 4180 practice), a field is quoted when it contains the delimiter, a double quote, or a CR/LF. Inside a quoted field, a literal quote is written as two quotes.

After you switch delimiters, the set of cells that need quotes changes. A Notes value of Hello, world needs quotes in comma CSV; in tab TSV it may not. A value containing a semicolon needs quotes in semicolon mode even if it never needed them before.

Do not strip quotes “to make the file cleaner” by hand. Naive cleanup breaks the next parser. Trust the converter’s quoting, then verify in a real spreadsheet or a proper CSV library.

TSV for pipelines and paste workflows

Tabs separate fields in TSV. Many Unix tools default to tab for cut, paste, and sort field operations. Data scientists often prefer TSV when columns include free text with commas.

The hazard is invisibility: tabs do not show clearly in every editor, and some web forms collapse them. Prefer file download for anything beyond a quick terminal paste, and confirm column counts with a proper parser or spreadsheet import.

If your “TSV” was actually spaces padded into columns, you have fixed-width data — use Fixed Width to CSV, not delimiter conversion.

Custom delimiters and contract formats

Some partners specify a rare delimiter (for example ^ or ~) to reduce collisions with prose. This tool supports a custom single-character separator for those contracts.

Pick a character that does not appear in your data if the partner’s parser is quoting-blind. If they implement full CSV quoting, any single character can work, but review still gets harder as the delimiter becomes more common in text.

Avoid multi-character separators (like ::) unless you control both ends with a custom parser — most spreadsheet and ETL tools expect one delimiter character.

Headers, empty fields, and multiline cells

The header row is rewritten with the same delimiter as data rows. Keep header names free of the target delimiter when possible so humans can read the first line without counting quotes.

Empty fields become consecutive delimiters (for example a;;b in semicolon mode). That is valid and means an empty cell. If empties confuse a partner, fill placeholders in the Online CSV Editor before converting.

Multiline cells remain multiline inside quotes. That is correct for Excel and good parsers, and fatal for scripts that split only on newlines. Know your consumer before you preserve embedded breaks.

Client-side conversion, privacy, and size

Parsing and re-serialization run in your browser. Spreadsheet content is not sent to Convert CSV servers as part of the delimiter conversion. Site analytics and advertising follow the privacy policy separately from the transform itself.

Very large files can slow the tab. Slice or pre-filter huge extracts before converting if the browser becomes unresponsive.

Customer lists, payroll, and credentials remain sensitive even when processing is local. Treat downloads and pastes with the same care you would give the original export.

Fixed-width versus delimited — do not confuse them

Delimited files mark field ends with a character. Fixed-width files mark field ends by character position and pad with spaces. They look similar in a monospace font and are completely different formats.

If columns only line up because of padding, delimiter conversion will not recover fields. Use Fixed Width to CSV to obtain a real comma grid, then use this tool if you still need TSV, semicolon, or pipe for the next system.

Tabs can fake a “columnar” look when editors expand them to spaces. Check for real tab characters before choosing Fixed Width to CSV versus a TSV path.

Typical handoff workflows

EU Excel handoff: receive comma CSV from a US SaaS, convert to semicolon, email a .csv that opens correctly on double-click for the recipient locale.

Data engineering: convert to TSV, compress, and land in object storage for a loader that defaults to tab.

Legacy finance: emit pipe-separated text matching a bank’s batch template after cleaning columns in the Online CSV Editor.

Migration: normalize every vendor’s dialect into comma CSV for storage, then re-delimit only at the edge when an old importer still demands pipes or semicolons.

Quality checklist before you send the file

Confirm the chosen delimiter matches the written contract or Excel locale. Spot-check quoted fields that contain the delimiter. Confirm row count equals the source.

Open with the same method the recipient will use (double-click versus import wizard). Verify UTF-8 if you use non-ASCII names.

Delimiter documented for the recipient.
Quoted fields round-trip in Excel or a CSV library.
No accidental fixed-width source treated as CSV.
Headers unique and stable.
Canonical comma copy retained for the next regeneration.

Related tools and next steps

Need to turn a mainframe-style positional report into CSV first? Use Fixed Width to CSV, then return here to produce TSV or semicolon output. Need to rename columns, delete fields, or fix empties before a partner export? Use the Online CSV Editor, then convert delimiters once.

From the same clean grid you can also move into Markdown, HTML tables, Excel, or SQL with the other converters on this site — delimiter choice is only one edge of the interchange story.

Frequently asked questions

Which output delimiters are supported?

Common choices are tab (TSV), semicolon, and pipe, plus a custom single-character delimiter when a partner specifies one. Input is treated as comma-separated CSV with standard quoting.

Why do European Excel users need semicolons?

In many locales the decimal separator is a comma, so Excel uses semicolon as the CSV field separator. Comma files then open as one column; semicolon files match Excel’s default list separator.

How does quoting work after I change the delimiter?

Fields that contain the new delimiter, double quotes, or newlines are wrapped in double quotes, and internal quotes are doubled. Which cells need quotes depends on the delimiter you choose.

Is my CSV uploaded to a server?

No. Conversion runs in your browser. See the Privacy Policy for separate site analytics and advertising practices.

What is the difference between TSV and CSV?

Both are delimited tables. CSV typically uses commas; TSV uses tab characters between fields. TSV often needs less quoting when cell text contains commas.

Can I convert pipe-separated or semicolon files as input?

This tool expects comma-separated input. Normalize other dialects to a grid first (import into a spreadsheet or editor, or use a matching import path), then export or paste as comma CSV before choosing a new output delimiter.

My file looks aligned but delimiter conversion fails — why?

It may be fixed-width text (spaces for padding) rather than delimited fields. Use Fixed Width to CSV to recover columns, then optionally convert to TSV, semicolon, or pipe here.

Why do I see "" inside quoted fields?

That is standard escaping for a literal quotation mark inside a quoted CSV/TSV field. Proper parsers display a single quote; they do not treat "" as four characters of payload.

Will Excel still mangle dates and ID columns?

Possibly. Changing delimiters only fixes how columns split. Excel may still auto-convert values. Use text import options or format columns as text for IDs with leading zeros.

When should I use the Online CSV Editor first?

Use it when headers are messy, columns must be dropped or reordered, or empty values need placeholders — then run delimiter conversion once on the cleaned grid.

Can I use a multi-character custom delimiter?

Stick to a single character. Spreadsheet tools and most ETL parsers expect one delimiter character; multi-character separators need custom code on both ends.

Does changing the delimiter change my data values?

No. Values and column order stay the same. Only the separator character between fields (and which fields are quoted) changes for transport to another system.

For more background on data formats and conversion workflows, read our format guides or browse the converter blog for step-by-step walkthroughs linked to each tool.

CSV to Delimited Converter

Input

Output Preview