Convert TXT to CSV Online

How to Convert TXT to CSV Online

1. Upload Your TXT File or Paste Text: Drag and drop a .txt transcript or subtitle export, click "Add Files" to browse, or paste lines directly into the editor. Parsing happens in your browser — nothing leaves your device. Batch is supported, so a whole folder of episode transcripts can be processed at once and downloaded as one CSV per source file.
2. Confirm Output Format: CSV is preselected as the target. The converter auto-detects whether your TXT is plain text (one line per caption or paragraph, no timestamps) or timecoded text (lines paired with HH:MM:SS or [00:01:23] markers). Plain text becomes a one-column-per-row dump with an auto-generated index; timecoded text is parsed into separate start, end, and text columns.
3. Review the Preview (Optional): Blank lines collapse to row separators, speaker labels like JOHN: or [NARRATOR] are preserved verbatim in the text column, and any mixed timestamp punctuation (.456, ,456, :456) is normalised. If your file has Windows-1252 mojibake at the source, re-save it as UTF-8 before converting — the output is always UTF-8.
4. Convert and Download: Click Convert. The .csv file downloads immediately as UTF-8 with comma separators and RFC 4180 quoting, ready to open in Excel, Google Sheets, Numbers, or any pandas / R / SQL import pipeline. No sign-up, no watermark, no email.

Why Convert TXT to CSV?

A .txt transcript is a flat sequence of words — easy to read, awkward to analyse. Every line is just bytes; there's no structure a spreadsheet can hook into. CSV (Comma-Separated Values, documented in RFC 4180) gives each line a row and each field a column, so a transcript becomes a table the moment Excel or pandas opens it. The conversion is the prerequisite for almost any downstream text analytics:

• Translation and localisation round-trips — Translators prefer CSV because each line lands on its own row with source text in one column and an empty target column for the translation. memoQ, Trados, Smartcat, and Crowdin all import CSV cleanly; after the translator delivers, you can re-export the column back to TXT or onward to subtitle formats.
• Reading-speed and length audits for captions — Broadcasters and streamers enforce per-second character limits (commonly 17 cps for adult content, 12 cps for children's programming). Once the transcript sits in a spreadsheet with start, end, and text columns, =LEN(text)/(end-start) flags any line that reads too fast.
• Searchable transcripts for podcasts, lectures, and meetings — A two-hour podcast transcript can be thousands of lines. In CSV form, filter-by-keyword and Ctrl+F find every mention of a name or term in seconds, and a timestamp column lets you jump back to the audio.
• Database and BI ingestion — Postgres COPY, MySQL LOAD DATA INFILE, BigQuery, Snowflake, and every BI tool consume CSV natively. Loading a year of customer-support call transcripts into a searchable database starts with a TXT-to-CSV pass.
• AI and ML training data prep — pandas, datasets, and Hugging Face loaders read CSV in one line. Researchers building speech-to-text fine-tuning sets, summarisation benchmarks, or speaker-diarisation datasets pair audio segments with text cells from the CSV.
• QA, redaction, and proofreading — Editors hate scrolling through a wall of .txt. In a spreadsheet they can sort by line length, filter by speaker, freeze the timestamp column, redact PII with find-and-replace, and tab through rows with the keyboard.

Need related tooling? Run the output through CSV to JSON when you want a list of objects instead of a table, audit length with Word Counter, or diff two versions of the transcript using Text Diff. To normalise UPPER/lower casing before delivery, Text Case Converter takes the same files.

TXT vs CSV — Format Comparison

Property	TXT (plain text / transcript)	CSV
Standardised by	No formal standard — generic plain text	RFC 4180 (informational)
File extension	.txt	.csv
MIME type	text/plain	text/csv
Structure	Free-form lines separated by newlines	One row per record, comma-separated fields
Timestamps	None by default; sometimes ad-hoc HH:MM:SS markers	Free-form column (kept as text by default)
Header line	Not applicable	First row is column names by convention
Quoting rules	None — every byte is data	Fields with commas, quotes, or CRLF wrapped in "…"; embedded " doubled to ""
Encoding	Anything — often UTF-8, sometimes Windows-1252 / ANSI / Shift-JIS	UTF-8 recommended; legacy tools sometimes default to CP1252
Line endings	LF (Unix) or CRLF (Windows) — accepted either way	CRLF per RFC 4180; LF accepted by most parsers
Tooling	Text editors, word processors, grep, awk	Excel, Google Sheets, pandas, SQL COPY, R, jq
Typical use	Notes, scripts, raw transcripts, READMEs	Spreadsheets, ETL pipelines, database imports

Input-Mode Quick Guide — What the Parser Does With Your TXT

Your TXT looks like…	Mode used	What the converter produces
One paragraph or sentence per line, no timestamps	Plain text	A single text column with a 1-based index column added; one row per line, blank lines skipped
00:01:23 Caption text (start only)	Timecoded — start only	Columns index, start, text; end is left blank (use next start − 1 in a spreadsheet if you need durations)
00:01:23 --> 00:01:26 Caption text	Timecoded — start and end	Columns index, start, end, text — exact 1:1 mapping
[00:01:23] Speaker: line	Timecoded with speaker	Columns index, start, speaker, text — speaker label split out from the body
Mixed . / , / : millisecond separators	Any timecoded mode	All normalised to HH:MM:SS,mmm in the output (SRT-style comma separator)
All-caps speaker block headings (JOHN: on its own line)	Plain or timecoded	Treated as a separate speaker column when the next non-empty line is dialogue

Frequently Asked Questions

My TXT has no timestamps — will the CSV still be useful?

Yes. In plain-text mode the converter emits two columns: index (a 1-based row counter it generates) and text (the original line, unchanged). That's already enough to filter, sort by length, run =LEN(text) audits, redact PII, or feed into a translation tool. If you need timestamps you'll have to add them yourself in the spreadsheet — there's nothing in a plain .txt file the converter can use to invent timings, and we don't want to fabricate data.

What CSV columns does the output file contain?

It depends on what the parser detected in your input. Plain text → index, text. Timecoded text with one timestamp per line → index, start, text. Timecoded text with start/end pairs → index, start, end, text. If a speaker label is present and consistently formatted (JOHN: or [NARRATOR]), an extra speaker column is added. The first row of the CSV is always a header naming the columns.

Will commas, quotes, and line breaks inside a line break my spreadsheet?

No. The converter follows RFC 4180 quoting rules: any field containing a comma, a double quote, or a CR/LF is wrapped in double quotes, and embedded double quotes are escaped by doubling (" → ""). Modern Excel, Google Sheets, LibreOffice Calc, Numbers, and the Python csv module all parse this correctly. If you open the raw .csv in a text editor and see fields wrapped in quotes, that's not a bug — it's the spec.

My CSV opens with garbled accented or CJK characters in Excel — what's wrong?

Almost always an encoding mismatch on Excel's side, not on the converter's. The output is UTF-8 without a byte-order mark, which is what Google Sheets, LibreOffice, Numbers, pandas, and Excel for Mac all autodetect. Excel on Windows still defaults to CP1252 when you double-click a .csv. Two fixes: (1) in Excel use Data → From Text/CSV and pick 65001: Unicode (UTF-8) in the dialog; or (2) re-save the file as UTF-8 with BOM in a text editor — the EF BB BF prefix flips Excel into UTF-8 mode automatically.

How does the parser decide where one row ends and the next begins?

Each non-empty line of your .txt becomes one CSV row by default. Multiple consecutive blank lines collapse to a single row separator (we don't emit empty rows). If your TXT was exported from a subtitle editor and uses blank lines as cue separators, that structure is preserved — each cue becomes one row, with multi-line cues joined into the text column using a single space.

What if my TXT uses Windows line endings or weird whitespace?

Both \r\n (Windows) and \n (Unix/Mac) line endings are accepted; the parser normalises both to a single newline before splitting. Tabs inside a line are preserved as literal tabs in the text column. Leading and trailing whitespace on each line is trimmed (Excel and pandas both strip it on import anyway). Zero-width and non-breaking space characters are kept verbatim — they sometimes carry meaning in Asian scripts and we don't want to lose them.

Can I get a row per word or per sentence instead of per line?

The converter outputs one row per line in the source TXT. If you want per-word or per-sentence rows, do the split after import: in Excel, =TEXTSPLIT(A2, " ") (Microsoft 365) gives one cell per word; in pandas, df["text"].str.split().explode() produces one row per word; for sentence boundaries, nltk.sent_tokenize is the standard. Splitting at conversion time would make assumptions about your language and punctuation we'd rather leave to a tool that knows your domain.

Is the CSV compatible with Google Sheets, Excel, and pandas out of the box?

Yes. UTF-8 encoding, comma delimiters, double-quote text qualifier, CRLF line endings, and a header row in line 1 is the most widely supported CSV dialect on the web. Google Sheets opens it directly from Drive; Excel opens it with Data → From Text/CSV; LibreOffice and Numbers double-click open; pandas.read_csv("file.csv") with no arguments works; psql \copy table FROM 'file.csv' WITH (FORMAT csv, HEADER true) works in Postgres.

Is anything uploaded to your servers?

No. The TXT is parsed and the CSV is generated entirely in your browser session — no upload, no account, no watermark, no rate limit. Closing the tab discards everything; we never see the contents of your file. That matters for transcripts of medical, legal, or HR conversations where confidentiality is non-negotiable.