What is the problem or goal you're trying to solve or accomplish?
Exporting a Table chart as an image (kebab menu → Download → Download as Image) produces unreadable results when the table has many columns and/or rows. Confirmed on Superset.
Two failure modes depending on table shape:
Column squishing: image grows vertically to fit all rows but width stays fixed, so columns get compressed.
Column truncation: last column(s) get cut off at the image's right edge instead of squishing — data is lost from the export entirely.
Either way, the export fails to represent the full chart data.
How are you solving it currently?
No workaround within the image export flow. Current mitigations: use CSV/Excel export instead for large tables, or manually reduce visible columns before exporting.
What is your recommended solution?
Warn users before export if the table exceeds a readable column/row threshold.
Scale image width to keep columns above a minimum legible size (instead of only growing height).
As an alternative, paginate large exports across multiple images.