Table Chart Maker does not open Excel .xlsx or .xls files directly — it accepts only plain comma-separated text, parsed by an RFC-style state machine in your browser. The limitation is not a missing checkbox or a roadmap item; it is a deliberate engineering choice, because workbook files carry styles, formulas, multiple sheets, embedded objects, and conditional formatting that a small CSV parser is not designed to interpret, so the page intentionally adds no workbook parsing dependency at all. If your data currently lives in an Excel file, the path through is short — open the workbook, choose "CSV UTF-8 (Comma delimited) (*.csv)" from Excel's Save As menu, save once, and paste the resulting text into the generator. That short round-trip preserves every cell value you actually need, drops the workbook-specific layer the tool was never built to interpret, and keeps the data local to your browser throughout. The rest of this article walks through that conversion, the quoting rules the parser enforces once your data is in CSV form, and the checks that catch the most common Excel exports gone wrong.
What Table Chart Maker Actually Reads
Table Chart Maker is a browser-only CSV-to-SVG converter. You paste a header row followed by body rows, click generate, compare the preview to your source, and download the escaped SVG. Because the parsing happens locally in the page, the input must be plain text — specifically comma-separated UTF-8 text — and the page intentionally does not interpret Markdown tables, pasted HTML, XLSX workbooks, Google Sheets links, remote URLs, JSON objects, tabs, semicolon-delimited regional CSV, or arbitrary delimiter detection. Convert the source to comma-separated UTF-8 text first, then use the page.
The limits are tight on purpose so the parser stays safe and predictable. The tool enforces two through ten columns, one through fifty body rows, no more than 20,000 JavaScript characters of input total, and 120 Unicode characters per cell. The first record supplies column headings, every heading must contain text, and every later row must have exactly the same number of cells. Malformed input is rejected rather than silently guessed, which is why an Excel workbook cannot be passed through as a substitute — the workbook format is not on the accepted list, and there is no fallback layer that tries to convert it.
How to Move Excel Data Into Table Chart Maker
For a complete walkthrough of the Excel-to-table-chart workflow, the table chart from an Excel sheet guide covers the same path with screenshots. In condensed form, the steps are:
- Open your workbook in Excel, Numbers, Google Sheets, or LibreOffice Calc and narrow the sheet down to the rows you actually want charted.
- Choose File → Save As (or File → Download) and pick "CSV UTF-8 (Comma delimited) (*.csv)". On recent Excel builds on macOS that label is "Windows Comma Separated (.csv)" — pick the UTF-8 flavor. Avoid "CSV (Macintosh)" and the legacy "CSV (MS-DOS)" options, which can ship with different line endings and sometimes a stray BOM.
- Open the saved file in Notepad, TextEdit, or VS Code, copy the entire content, paste it into the Table Chart Maker input, and select Generate table chart.
- Compare the parsed HTML preview row-by-row and column-by-column against the source. Confirm the row count and column count match before downloading.
- Download the escaped SVG and inspect long or wide cells at the final display size before publishing anywhere.
The HTML preview is built with real React table elements, so headers and cells stay selectable, copyable, and structurally meaningful. That is the visual confirmation of parsed values, not an editable spreadsheet — there are no formulas, no sorting controls, no merged cells, no filters, and no automatic totals. Every value remains literal text.
CSV Quoting Rules the Parser Enforces
Once the data is comma-separated, the Table Chart Maker parser speaks the same quoting dialect Excel uses when "Save with quoting" is implicitly on for any cell containing a separator. Three rules cover almost every cell you'll need to round-trip:
- A cell may be wrapped in double quotes; inside the quote, commas and line breaks are kept as part of the cell, not interpreted as delimiters.
- A literal double quote inside a quoted cell is written as two quotes in a row, so "Said ""hello""" becomes the cell Said "hello".
- A quoted cell must begin with a quote and end with a closing quote followed only by a comma or a line break. Anything else is malformed and the row is rejected.
Under those rules, a cell such as "Ada, A." stays in one column because the comma sits inside the quotes. A row reference like He said ""yes"" renders as He said "yes" without breaking the row into extra fields. The same RFC 4180 dialect is what Excel applies automatically when you save with the comma-delimited option, so a clean export usually needs no further editing. For detail on when and why this matters with embedded commas, the commas in a table chart maker guide walks through the same rules with examples.
Why the Tool Stays Strictly CSV
There is a reason the page is built around plain text rather than file uploads. Workbook files such as .xlsx, .xls, .ods, and .numbers are ZIP-style packages containing XML, formula chains, style sheets, theme files, shared string tables, sometimes embedded images, and often metadata about print areas, named ranges, and defined tables. A page that accepted one would need a parser significant enough to process all of that — and significant enough to be a security surface worth auditing carefully.
The CSV-only path keeps the parser small enough to reason about, keeps your data on your machine (the page does not upload labels, values, notes, names, or generated artwork), and keeps the conversion losses visible: a literal text cell goes in, a literal text cell comes out, with no formula evaluation, no type inference, and no auto-recalculation. That predictability is the trade, and it is the reason the in-product FAQ entry is a flat "No, it accepts comma-separated text only and intentionally adds no workbook parsing dependency" rather than a roadmap promise.
Common Excel-to-CSV Pitfalls
A handful of Excel-specific behaviors tend to surprise first-time CSV exporters. The table below summarizes the symptom, the reason, and the fix before the data reaches Table Chart Maker.
| Pitfall | Why it happens | Fix before pasting |
|---|---|---|
| Header row shows invisible characters | Excel sometimes prepends a UTF-8 BOM (EF BB BF) when saving CSV | Save with the "CSV UTF-8" option, or strip the BOM in a text editor |
| Numbers lose $, %, or thousand separators | CSV stores the underlying value, not the cell format | Format the column as text in Excel first, or include the symbol in the raw data |
| Dates appear as integers such as 45292 | Excel writes dates as serial numbers in the CSV stream by default | Format the column as text first, or paste dates as ISO strings |
| File uses semicolons instead of commas | Some European locales default to list separator = ; | Re-export with English (United States) locale, or replace semicolons with commas in a text editor |
| Parser rejects an "extra" empty row at the end | Many spreadsheet apps append a blank line after the last record | Delete the trailing blank line in Notepad or VS Code before pasting |
If the input is rejected after you have cleared those issues, the most likely causes are a misaligned row (one cell too many or too few compared to the header), a quoted cell whose closing quote is not followed by a comma or line break, or content that exceeds the 20,000-character input ceiling or the 120-character per-cell ceiling. Adjusting any one of those will almost always let the parser through.
Features That Don't Carry Over From Excel
The preview and the downloaded SVG are visually rich but deliberately spreadsheet-free. There are no formulas, no sorting controls, no merged cells, no filters, no pivot operations, no inferred types, no hidden columns, and no automatic totals. Every value stays literal text, and the preview exists to confirm that the parser understood your source — not to replace the spreadsheet you exported from.
That keeps the round-trip lossless for plain tabular content such as price lists, schedules, feature comparisons, small directories, event summaries, scorecards, research snapshots, and social graphics where exact text matters more than any plotted trend. It deliberately loses workbook-specific machinery: live formulas, pivot aggregates, conditional formatting, named ranges, multi-sheet joins, and any chart object embedded in the workbook. Table Chart Maker is not built to replicate those; it is built to render a clean, escaped, downloadable table image from text you already have.
When a Different Tool Is the Better Fit
If the real goal is a plotted chart rather than a table, converting the Excel file just to feed a table chart is the wrong detour. Two adjacent tools can read the same comma-separated text and produce a different visual:
- Bar Chart Maker turns 2 to 30 label,value rows into a readable bar chart and exports a standalone SVG.
- Line Graph Maker turns labeled numeric rows into a clean line graph and exports the exact preview as an SVG.
Table charts shine when readers need to read every label and number exactly. Bar and line charts shine when readers need to feel the magnitude of a number at a glance. Pick the table when exact text is the message; pick a chart when magnitude is the message. Anything that needs the actual .xlsx file format read directly — formulas, multiple sheets, conditional formatting, pivot logic — will still need a workbook-aware tool, which Table Chart Maker intentionally is not.