Compare every cell in the HTML preview with the source CSV before downloading the SVG; this is the reliable way to separate a parsing mistake from a display issue.
A result can also look wrong when a comma was read as a separator, a long label was shortened for the image, or a wide table became difficult to read. The Table Chart Maker converts small comma-separated data sets entirely in the browser, and the page does not upload the CSV values. Work from the source CSV to the preview and then to the downloaded asset rather than trying to repair the finished image.

Identify where the mismatch starts
Separate the process into three layers: the source CSV, the parsed HTML preview, and the rendered SVG. If a value is wrong in the preview, the CSV structure is the problem. If the preview is correct but the SVG looks wrong, focus on image truncation, column sizing, fixed row height, or the way the destination application displays SVG files.
| Symptom | Likely cause | Correction |
|---|---|---|
| A value has split across columns | The source cell contains a comma but is not enclosed in double quotes. | Quote the complete cell and regenerate the chart. |
| Generation rejects the CSV | A heading has no text, a row has a different number of cells, or a quoted field is malformed. | Repair the source record because the parser rejects malformed input rather than guessing. |
| The preview is correct but an SVG label is shorter | Displayed image values are shortened after 30 Unicode characters. | Recognize this as an export difference; the preview retains the complete parsed value. |
| The SVG looks crowded or extremely wide | Column widths are bounded and rows use a fixed height. | Inspect the file at its final dimensions and shorten labels or reduce the number of source columns if appropriate. |
| Markup appears as visible characters | Cell contents are treated as literal text. | No security correction is needed because script-looking markup is not active markup. |
Begin with a short representative sample when possible. A small extract makes it easier to identify the record or field causing shifted columns, missing values, or inconsistent row widths before working with the complete data set.
Correct the result in the Table Chart CSV Table Maker
- Keep an editable source CSV. Convert the source to comma-separated UTF-8 text with one header row followed by the data rows. The first record supplies the column headings, so keep that row separate from the records you want shown as body content.
- Confirm the data fits the supported limits. The tool accepts two through ten columns and one through fifty data rows. Total input is limited to 20,000 JavaScript characters, and each cell can contain up to 120 Unicode characters.
- Repair CSV quoting. Wrap the complete cell in double quotes when it contains a comma or line break, and represent a literal quote inside a quoted field with two double quotes. A quoted field must begin with a quote, and only a comma or line break may follow its closing quote. For example, "Ada, A." stays in one column, while "Said ""hello""" becomes Said "hello". CRLF and LF line endings are supported.
- Check headings and row widths. Every heading must contain text, and every later row must have exactly the same number of cells as the header. Do not add separators to make an uneven row appear aligned; correct the original record instead.
- Select Generate table chart. If malformed input is rejected, inspect the cited formatting issues and return to the source CSV. The tool will not guess where missing cells, extra commas, or broken quotes belong.
- Compare the HTML preview with the source. Check the headings, row order, spelling, values, number of rows, and number of columns. Compare every cell rather than checking only the first few records, since the preview displays the complete parsed value and is the main confirmation that the CSV was interpreted correctly.
- Download and inspect the escaped SVG. Download the file only after the preview agrees with the source. Open the SVG at its intended display size and review long, wide, or condensed cells before publishing it.
For more examples of valid quoting, see the guide to handling commas and literal quotes in CSV cells.
Understand the preview and SVG differences
Once the preview matches the source, any remaining difference may be part of the intended export behavior. The HTML preview and the SVG image are not identical representations, even though they come from the same parsed table.
| Aspect | HTML preview | Downloaded SVG |
|---|---|---|
| Cell text | Retains the complete parsed cell. | Shortens displayed values after 30 Unicode characters. |
| Structure | Uses real HTML table elements, so headings and cells remain selectable. | Uses SVG rectangles and text. |
| Primary purpose | Confirms parsed values and row alignment. | Provides a standalone, scalable table image. |
| Editing behavior | Acts as visual confirmation rather than a spreadsheet. | Acts as a static image with no editable cells or spreadsheet controls. |
The preview does not provide formulas, sorting, merged cells, filters, pivot operations, inferred types, hidden columns, or automatic totals. Every value remains literal text. This means the tool will not convert a date, currency label, identifier, or number into a guessed data type.
Text is also handled as content rather than active markup. Script-looking strings appear as visible text, and strings in the SVG are XML-escaped. Invalid XML control characters are replaced when the image is created. If a preview value contains something unexpected, check the corresponding source cell rather than expecting the generator to reinterpret it.
Check the downloaded SVG at its final size
The export is a self-contained SVG with an explicit width, height, viewBox, image role, accessible label, system-style Arial text, and fixed colors. It can be opened in a browser, presentation editor, design application, or vector-capable document workflow, subject to that program's SVG support.
- Compare spelling and row alignment with the original CSV.
- Look for image labels cut at the 30-character display limit.
- Check whether very wide columns require horizontal scrolling.
- Test whether condensed text remains readable at the final embedded size.
- Verify color contrast in the destination because the SVG uses fixed colors.
- Check the final physical dimensions rather than judging only a large preview.
The image does not guarantee print accessibility. If the destination program handles SVG differently, open the downloaded file directly as a separate check. Keep the source CSV as the editable record because nothing generated by the page is retained after the tab is closed.
Decide whether a table chart is the right output
A table chart is most useful when the exact wording of labels and values matters more than a plotted trend. It can present a scorecard, schedule, feature comparison, small directory, price list, event summary, research snapshot, or social graphic without assigning meanings to the values.
If the result looks wrong because you expected a trend, the issue may be the chart type rather than the CSV. A bar or pie chart may communicate numeric magnitude more quickly, while a Gantt chart may better represent tasks with start and end dates. The tool does not infer a suitable visualization from the data. You can compare table, graph, and Gantt approaches before changing the source format.
Run a final correctness check
Before publishing, confirm each of these points:
- The original CSV remains available as the authoritative editable file.
- The source has one valid header row and uniform row widths.
- Cells containing commas or line breaks are properly quoted.
- The row and column counts fall within the supported ranges.
- Every preview cell agrees with the source.
- Any shorter SVG label is understood as the documented 30-character image limit.
- The final SVG remains readable and aligned at its publication size.
If the source and preview agree, the parsing stage has been confirmed. If only the downloaded asset looks wrong, check truncation, dimensions, column density, and destination rendering rather than changing the underlying values. When a source correction is required, make it in the CSV, regenerate, compare every preview cell again, and download a fresh SVG.