Very long text in a CSV cell: find and fix

Your import rejects some rows, or says a text field is too long. Text ends abruptly after import. Or one column holds far more text than the others, and one cell seems to contain several rows.

Why it happens. Platforms limit how much text a field accepts, and the limit differs by field. We have no confirmed value, so this post calls it your platform's limit; check the limit your platform states for each field. The common causes: a full page of product copy pasted into a short field, a description pasted into the title column, or several cells merged into one. A quote mark that never closes can also make everything after it read as one very long cell.

If the long cell holds parts of other rows, such as other SKUs or prices, the text itself is not the problem: a quote or a line break is. "Quotes and commas inside CSV cells: find and fix" and "Line breaks inside a CSV cell: fix split rows" explain those causes and their fixes, so they are not repeated here.

Step-by-step fix. 1. Save a copy of the original file and work on the copy. You should see two files with different names. 2. Open the copy in a spreadsheet. Add a helper column that counts the characters in the suspect column, then sort it from largest to smallest. You should see the longest cells at the top. 3. Read the longest cell. If it contains parts of other rows, a closing quote is missing. Add it where the cell should end, as in the quotes post above. After you reopen the file, the text should be back in separate rows. 4. If the text is genuinely too long, shorten it to the essentials. If your platform has another field for extra detail, move it there. The count in your helper column should drop below the limit your platform states. 5. If the text sits in the wrong column, move it to the right one and put the correct short value back. The long and short columns should now match their headers. 6. Delete the helper column. Save as CSV with the same separator and encoding as before. The file should have only its original columns. To keep track of what you shortened or moved, log each change (row, column, old and new text) as shown in "CSV correction worksheet: log each fix, recheck".

In the synthetic example below, DEMO-001 has its whole description pasted into the title cell, and DEMO-002's description opens a quote that is never closed, so DEMO-003 is read as part of that cell until the next quote mark.

Recheck. Reopen the saved file and confirm the row count matches your product count. Sort the suspect column by length once more and read the top cells. Then retry your import. A clean result does not guarantee that your platform accepts the file.

The free CSV check on this site does not measure text length, so it will not flag a cell that is simply too long: in our local test, a title and a description of several thousand characters each passed with no problems. It does help with the quote and line-break causes. If a quote is never closed, it stops with the message "A quoted value is not closed". If a line break without quotes splits a row, it reports the half-empty second row, for example an empty title or a price that is not a plain number. A missing quote that a later quote closes is not reported; the only hint is that fewer rows were checked than your file has. It looks at the first 20 data rows only.

What we're not sure about. The exact text limit for each field: check your platform's stated limit. Whether your platform rejects a too-long row or cuts the text. Whether line breaks or special characters count differently toward the limit. How shortened text looks in your listing: we have not tested this.