Excel to Text

Data

Extract plain text from Excel with tab or custom delimiter output and batch sheet processing. Choose tab or a custom delimiter process several sheets at once.

No file chosen

About Excel to Text

This Excel to text extractor uses SheetJS to pull plain text from xlsx and xls spreadsheets locally in your browser. The output uses tab or custom delimiters for columns and newlines for rows, producing flat text that any text editor can open. You can select a specific worksheet or batch process multiple worksheets, exporting each one independently. Plain text gives up nearly all visual styling in exchange for extreme versatility. It imports into legacy systems that cannot read Excel, feeds shell pipelines that search with grep or awk, and drops into version control where git diff shows each cell-level change. SheetJS converts Excel date serial numbers to readable ISO 8601 strings and renders numbers, dates, and percentages as text. Confirm date and percentage formatting is what you expect before exporting so values do not silently change meaning. Because everything runs locally and is discarded when you are done, sensitive spreadsheets stay on your device. Alignment depends entirely on a monospace font, which is the first premise to confirm. In a monospace font each Latin character is one cell and padding by character count aligns columns; Chinese characters usually occupy two, so padding by count misaligns mixed text. Pad by display width instead, and state which font the output needs, or the recipient opens it in another font and everything shifts. Newlines and tabs inside cells are the other common source of broken alignment. Tables often carry manual line breaks for layout, and on export they read as real newlines, splitting one record across two lines and collapsing the columns. Decide whether to keep, replace or escape them, and document the rule so downstream knows how to restore the data. Against a spreadsheet format, plain text wins on zero dependencies and direct pasting: no spreadsheet software required and no version effects. The cost is losing types and formatting, with numbers and leading zeros becoming plain strings. It suits log comparison, code inlining and quick checks, and not deliverables that need types or formulas; the test is whether downstream must keep computing. Column and total widths should match the purpose. For terminal viewing the total should stay within common widths or lines wrap and alignment breaks; for document pasting keep lines short enough that editors do not soft-wrap them. Set a width cap from the longest column and truncate with a marker rather than letting one field stretch the row. Finally, open the file once in a clean editor before delivery. Editors disagree about tab width, trailing whitespace and the final newline, so what looks right in your own setup can shift elsewhere. Making verification in the target environment the last step of the export avoids a great deal of "it works on my machine" correspondence. One more premise is easily missed: text export is usually one-way, since importing it back requires re-deriving delimiters and alignment that the export has flattened. Confirm before exporting that this is an endpoint format rather than an intermediate one; if downstream still processes it, a tabular format fits better and plain text belongs to reading rather than reprocessing.

How It Works Internally

Text export simulates table layout with alignment and control characters. The premise is a monospace font: padding by character count aligns only there, and since a CJK character usually occupies two columns while a Latin one occupies one, padding by character count misaligns mixed text and needs display width instead. Newlines and tabs inside cells also break the alignment.

InputAligning the Chinese column 名 称 (two wide characters) and ab
OutputPadding by character count misaligns the CJK column, since a Chinese character is two columns wide; pad by display width instead

Measured on This Page

Cell-exactThe first sheet matches exactly: Chinese preserved, blank cells stay blank, 3 and 3.5 keep their values, the string 007 does not become 7
Sheet switchingSecond yields only/1 and Empty yields nothing — switching really re-converts
Special charactersCells containing tab, newline or quote are quoted per CSV rules: "with<TAB>tab", "with<LF>newline", "with""quote"
DelimiterTabs between columns and newlines between rows, so it pastes straight into Excel or Sheets
Empty sheetAn empty sheet yields an empty string without error

The output is TSV rather than plain text, so tabs and newlines inside cells must be quoted or pasting back into a spreadsheet shifts columns — and the quoting is there (measured: "with<TAB>tab"). That follows the RFC 4180 CSV convention with a tab delimiter. One practical warning: cells containing newlines usually survive a paste into Excel, but code that splits on tabs alone will mis-parse them — parse quotes properly.

How this was measured: An xlsx with four sheets (Chinese text, blank cells, numbers, a leading-zero string, and cells containing tab/newline/quote) was generated with openpyxl, uploaded, and the output compared cell by cell against what was written; sheets were switched through the select element to check re-conversion. · Measured 2026-10-30

How to Use

  1. Open "Excel to Text"
  2. Choose an xlsx, xls or csv file to upload
  3. Pick the worksheet you want when the file has several
  4. Rows become tab-separated plain text automatically
  5. Use the copy button and paste into another spreadsheet

Use Cases

  • Command-line processing — Convert Excel data to tab-separated text for searching and processing via grep, awk, and sed.
  • Legacy system import — Transform Excel data to plain text for import into legacy systems or AS400 terminals that do not support Excel.
  • Version control diff — Convert Excel config data to text for Git management, using diff to track each data change.
  • Quick data preview — Extract Excel content to plain text for quick browsing without installing Office software.
  • Log format conversion — Convert Excel-maintained error code tables to text for embedding in log analysis scripts as reference.
  • Pre-import validation — Export data to plain text before a database load so you can verify column alignment in a terminal.

FAQ

What delimiter does the output use?

Tab is the default column delimiter; you can customize it to comma, semicolon, pipe, or any character. Newlines separate rows.

How are dates displayed?

SheetJS converts Excel date serial numbers to ISO 8601 text strings (e.g. 2024-01-15) for readability.

Can it handle multiple worksheets?

Yes. You can select a specific worksheet or process all worksheets, each output as an independent text block.

What information is lost in plain text?

Plain text does not preserve cell styles, formulas, charts, or merged cells; only data values and row-column structure are retained.

Will very large workbooks be slow?

Parsing runs locally and stays smooth for hundreds of thousands of cells; for huge workbooks export worksheet by worksheet and watch browser memory.

Are the files uploaded?

No. All parsing runs locally via SheetJS and the file is discarded when you are done, never leaving your device, so sensitive tables are safe.

Leading zeros disappeared from codes like 001 — why?

That is Excel, not the converter: Excel stores 001 as the number 1 and the tool exports stored values. Format the column as text in Excel before exporting, or prefix entries with an apostrophe when entering them.

Line breaks inside cells turn into strange characters?

Alt+Enter newlines export as real line breaks and look odd in single-line editors. Replace them with spaces or a custom separator for single-line output, or paste into a multi-line target such as a Markdown editor.