Fix SharePoint List Creation Error Unexpected Token C in JSON from Excel
Question details
Users need to resolve a JSON parsing error that blocks the creation of a SharePoint list from an uploaded Excel spreadsheet.

- Product
- SharePoint / Excel
- Device & OS
- not provided
- Scenario
- Attempting to create a new SharePoint list by importing a dataset directly from an Excel spreadsheet.
- Observed behavior
- SharePoint displays the error 'Unexpected token C in JSON at position 0' and incorrectly states that the list already exists, causing the import process to fail.
Check the total number of columns in your Excel spreadsheet, as exceeding SharePoint's internal 8,000-byte row limit is the primary cause of this import failure.
Reduce Excel Columns and Restructure Data
Optimize your Excel spreadsheet by reducing the number of columns to comply with SharePoint list size limits.
When importing an Excel file, SharePoint converts each column into a corresponding SharePoint list column. Spreadsheets containing a large number of columns (such as over 250) can easily exceed SharePoint's internal 8,000-byte row limit. This triggers the 'Unexpected token C in JSON' error and aborts the creation process.
Open your problematic Excel spreadsheet and review all active columns containing data.
Identify and delete any non-essential, blank, or formatting-only columns, especially those at the far right of your dataset.
Consolidate data where possible to minimize the overall column count. If your file contains hundreds of columns, aim to reduce it significantly.
Select the empty columns to the right of your data, right-click the headers, and select 'Delete' to ensure no hidden formatted cells are being processed as empty columns.
Save the optimized Excel file and restart the 'Create list from Excel' process in your SharePoint site.

Clean Up Your Spreadsheets Effortlessly with WPS Office
While SharePoint list errors often require structural changes to your data, WPS Office provides a free, lightweight, and highly powerful alternative for managing, cleaning, and optimizing your complex Excel datasets before uploading.

Frequently Asked Questions
Why does SharePoint say the list already exists when I get this JSON error?
The 'already exists' message is often a false flag caused by a backend crash. When the import process fails due to exceeding the byte limit, SharePoint may leave behind a corrupted, invisible, or partial instance of the list. Subsequent attempts to use the same name trigger the false error.
What is the maximum number of columns I can import into a SharePoint list?
While SharePoint theoretically allows up to 276 single-line text columns, the actual limit depends on the data type. The total combined data per row cannot exceed 8,000 bytes. Complex columns like multi-line text, choices, or lookups consume significantly more bytes, drastically reducing the total number of columns you can successfully import.
Does saving the Excel file as a CSV fix the unexpected token C error?
Saving as a CSV generally strips out hidden formatting that might be interpreted as empty columns, which can sometimes resolve the issue. However, if your dataset genuinely has too many active columns exceeding the byte limit, converting to CSV will not bypass SharePoint's row limit restrictions.




