FAQ: XLSX export fails with "The maximum length of cell contents is 32767 characters"

[openai0229]

Symptom

Exporting a query result to XLSX fails with this error:

The maximum length of cell contents (text) is 32767 characters

Cause

This is an Excel/XLSX worksheet format limit: a single cell can contain at most 32,767 characters. If any text value in the query result exceeds that limit, XLSX cannot represent the complete value and the export fails.

The database value itself is valid. This limit is independent of the database type, column type, and operating system.

Workarounds

• To preserve the complete value, export the result as CSV. Chat2DB writes the full text to the CSV file. Use a text editor or another long-text-capable data tool to verify the complete value, because opening the CSV in Excel still displays it through an Excel worksheet.
• If XLSX is required, shorten or split the value in the query so that every cell contains no more than 32,767 characters. Shortening causes data loss, while splitting changes the export structure.
• Chat2DB should not silently truncate oversized values by default, because a successful-looking export could hide data loss.

Scope

This error can occur whenever a single exported value exceeds 32,767 characters. It is not specific to MySQL, Windows, or TEXT columns.

Related issue: #1931

[openai0229]

Answer

This is an Excel/XLSX worksheet format limit: a single cell can contain at most 32,767 characters. If any text value in the query result exceeds that limit, XLSX cannot represent the complete value and the export fails.

The database value itself is valid. This limit is independent of the database type, column type, and operating system.

Workarounds

• To preserve the complete value, export the result as CSV. Chat2DB writes the full text to the CSV file. Use a text editor or another long-text-capable data tool to verify the complete value, because opening the CSV in Excel still displays it through an Excel worksheet.
• If XLSX is required, shorten or split the value in the query so that every cell contains no more than 32,767 characters. Shortening causes data loss, while splitting changes the export structure.
• Chat2DB should not silently truncate oversized values by default, because a successful-looking export could hide data loss.

This error can occur whenever a single exported value exceeds 32,767 characters. It is not specific to MySQL, Windows, or TEXT columns.

Related issue: #1931

[pirulij67-pixel]

Nombre

[pirulij67-pixel]

Symptom

Exporting a query result to XLSX fails with this error:

The maximum length of cell contents (text) is 32767 characters

Cause

This is an Excel/XLSX worksheet format limit: a single cell can contain at most 32,767 characters. If any text value in the query result exceeds that limit, XLSX cannot represent the complete value and the export fails.

The database value itself is valid. This limit is independent of the database type, column type, and operating system.

Workarounds

• To preserve the complete value, export the result as CSV. Chat2DB writes the full text to the CSV file. Use a text editor or another long-text-capable data tool to verify the complete value, because opening the CSV in Excel still displays it through an Excel worksheet.
• If XLSX is required, shorten or split the value in the query so that every cell contains no more than 32,767 characters. Shortening causes data loss, while splitting changes the export structure.
• Chat2DB should not silently truncate oversized values by default, because a successful-looking export could hide data loss.

Scope

This error can occur whenever a single exported value exceeds 32,767 characters. It is not specific to MySQL, Windows, or TEXT columns.

Related issue: #1931