About

Converting tabular data into a portable image format eliminates rendering inconsistencies across platforms. A CSV file displayed in one spreadsheet application may appear different in another due to varying default column widths, font stacks, and locale-specific delimiter interpretation. This tool parses raw CSV input according to RFC 4180 rules - handling quoted fields containing commas, escaped double-quotes (""), and multi-line cell values - then renders the data onto an HTML Canvas at a configurable pixel density (1×, 2×, or 3× scale factor). The output is a deterministic pixel grid: same input always produces the same image. Limitation: extremely wide tables (beyond 200 columns) may exceed browser canvas size limits, which vary by engine (Chromium caps at 16384px per axis).

Column widths are computed by measuring every cell's text content via measureText and selecting the maximum per column, clamped between a floor of 40px and a ceiling of 300px (logical pixels before scaling). This prevents a single long string from collapsing the rest of the layout. Row height adapts to wrapped text. The resulting image can be exported as PNG (lossless, larger file) or JPEG (lossy, smaller file at 92% quality). Pro tip: use 2× scale for documents intended for print or Retina displays; 1× is sufficient for web embedding where bandwidth matters.

Formulas

The image dimensions are computed from the parsed data grid. Let C be the number of columns, R the number of rows (including header), w_j the computed width of column j, h_i the height of row i, p the cell padding, and s the scale factor.

W_canvas = s ⋅ ( C∑j=1 w_j + 2p )

H_canvas = s ⋅ R∑i=1 h_i

Each column width w_j is determined by:

w_j = clamp(w_min, max(measureText(cell_i,j)) + 2p, w_max)

Where w_min = 40 px, w_max = 300 px, and p = 12 px by default. The clamp function prevents degenerate layouts. For cells exceeding w_max, text wraps and h_i increases by lineHeight per additional line. The scale factor s multiplies all coordinates and font sizes, producing a higher-resolution output without changing visual proportions.

Reference Data

Delimiter	Symbol	Common Source	RFC Standard	Notes
Comma	,	Most CSV exports	RFC 4180	Default in US/UK locales
Semicolon	;	European Excel exports	Non-standard	Used where comma is decimal separator
Tab	\t	TSV files, clipboard paste from Excel	IANA text/tab-separated-values	Rarely appears inside cell data
Pipe	\|	Database dumps, log files	Non-standard	Good for data containing commas
Export Format Comparison
PNG	-	Lossless raster	ISO/IEC 15948	Larger file, pixel-perfect quality
JPEG	-	Lossy raster	ITU-T T.81	Smaller file, slight artifacts on sharp edges
Scale Factor & Effective DPI
1×	-	Web / messaging	-	96 DPI effective
2×	-	Retina / presentations	-	192 DPI effective
3×	-	Print / high-res archival	-	288 DPI effective
Canvas Size Limits by Browser Engine
Chromium	-	Chrome, Edge, Opera	-	Max 16384×16384 px
WebKit	-	Safari	-	Max 16384×16384 px
Gecko	-	Firefox	-	Max 32767×32767 px (but ~472M total pixels)
Common CSV Encoding Pitfalls
BOM	\uFEFF	Windows Notepad, old Excel	Unicode 3.0	Invisible char at file start; must strip
CRLF vs LF	\r\n vs \n	Windows vs Unix	RFC 4180 mandates CRLF	Parser should handle both
Escaped Quote	""	Any quoted field	RFC 4180 §2.7	Two consecutive double-quotes = one literal

Frequently Asked Questions

Per RFC 4180, any field containing the delimiter character, a double-quote, or a newline must be enclosed in double-quotes. The parser enters a "quoted mode" when it encounters an opening double-quote and only exits when it finds a closing double-quote followed by a delimiter or end-of-line. Two consecutive double-quotes inside a quoted field are interpreted as a single literal double-quote character. This means a cell value like "Smith, John" is correctly parsed as one field containing Smith, John.

The converter determines the maximum column count across all rows. Rows with fewer columns are padded with empty strings to match this maximum. This prevents rendering errors where some rows would be narrower than others. A warning toast is shown indicating the inconsistency, but the image is still generated. This behavior is intentional - real-world CSV exports from legacy systems frequently have trailing delimiter issues.

Presentation software (PowerPoint, Google Slides, Keynote) often scales images to fit slide dimensions. If the source image is at 1× scale (96 DPI effective), upscaling causes interpolation blur. Use 2× or 3× scale factor before export. At 2× scale, a table that renders at 800×400 logical pixels produces a 1600×800 pixel image, which remains sharp when displayed at the original logical size on a Retina display or when downscaled by the presentation software.

The tool enforces a soft limit of 10,000 rows and 200 columns to prevent browser tab crashes. The actual hard limit comes from the HTML Canvas maximum dimensions, which vary by browser engine: Chromium-based browsers cap at 16,384 pixels per axis, Firefox at 32,767 pixels per axis (with a total pixel budget of ~472 million). At 2× scale with a 14px font and 12px padding, each row consumes roughly 44 effective pixels, meaning approximately 186 rows fit within the Chromium limit per axis at 2× scale - but the canvas extends vertically as needed up to that ceiling.

PNG uses lossless compression and excels at sharp edges, solid colors, and text - exactly what a table image contains. File sizes are larger but quality is perfect. JPEG uses lossy DCT-based compression optimized for photographs; it introduces visible artifacts around high-contrast boundaries like text edges and grid lines, especially at lower quality settings. For table images, PNG is almost always the correct choice. JPEG is offered as a fallback when file size is critical (e.g., embedding in email where attachment limits apply). The tool uses 92% JPEG quality to minimize artifacts.

Yes. When you copy cells from Excel, Google Sheets, or LibreOffice Calc, the clipboard contains tab-separated text. Set the delimiter option to "Tab" before pasting, or use the auto-detect feature which checks the first line for the most frequent delimiter candidate. The parser treats the tab character (Unicode U+0009) identically to any other delimiter. Note: if your data also contains literal tab characters within cells (rare but possible), those cells must be double-quoted in the source, per the same quoting rules as comma-delimited CSV.