Fix: Shopify CSV Import Failed, Error on Line 1

Cause 1: an invisible BOM before the first header name

If the file was saved as "UTF-8 with BOM", the first three bytes are an invisible signature (EF BB BF). Excel hides this completely, but Shopify's parser sees the actual byte sequence, and the first header cell effectively becomes Handle instead of Handle, which doesn't match the expected column name and fails validation.

Fix: re-save the file as plain UTF-8 (without BOM), or open it in a text editor and delete the invisible character at the very start.

Cause 2: curly ("smart") quotes instead of straight quotes

Excel and Word autocorrect straight quotes (") into curly quotes (“ ”) automatically, especially inside product description fields pasted from another document. A curly quote isn't recognized as a CSV field delimiter the same way a straight quote is, so Shopify's parser can misread where a field starts or ends.

Fix: find-and-replace curly quotes with straight ones in a plain text editor before uploading, not in Excel (which will just curl them again).

Cause 3: mixed line endings (CRLF and LF in the same file)

CSV files use either \r\n (Windows/CRLF) or \n (Unix/LF) to mark the end of a line. If different rows were edited on different operating systems (common when a file passes through Excel on Windows, then a Mac, then a script), it can end up with a mix of both, which confuses strict parsers, including Shopify's, right from the header row.

Fix: in VS Code, the line-ending format is shown in the bottom status bar (click it to switch between CRLF and LF for the whole file, then save).

Also check

• A trailing space or tab after the last header name (e.g. after "Image Alt Text")
• Your header row exactly matches Shopify's expected column names and casing, download Products → Import → Download sample CSV to compare directly
• The file is genuinely UTF-8 encoded, not saved as ANSI/Windows-1252

Errors that show up further into the import, not on line 1

Once the header row passes validation, a handful of other errors commonly show up on specific data rows rather than line 1, worth knowing so you don't mistake them for the same issue:

• Duplicate handles — every product needs a unique "Handle" value; two rows sharing one, intentionally for variants or by accident for two different products, produce a specific duplicate-handle error rather than a header failure.
• Invalid image URLs — the "Image Src" column needs a reachable, direct URL to an image file, a link to a webpage instead of the image itself, or a URL behind a login, fails silently or with an image-specific error, not a line-1 error.
• Price or inventory fields containing currency symbols or commas — Shopify expects a plain number in "Variant Price" and "Variant Inventory Qty" (e.g. 19.99, not $19.99 or 1,999), which is a per-row type error rather than a structural one.

Preventing this on your next import

Once a file passes, the same habits keep the next one from failing the same way:

1. Save exports as plain UTF-8 (no BOM), most spreadsheet apps offer this as an explicit "CSV UTF-8" save option separate from the default "CSV".
2. Write or paste product descriptions in a plain text editor first, then paste into the spreadsheet, this avoids autocorrect ever turning straight quotes into curly ones in the first place.
3. Keep the whole file's editing history on one OS where possible, or explicitly normalize line endings as a last step before uploading if it passed through more than one.
4. Re-download Shopify's sample CSV periodically, expected columns and formats do change between Shopify's product CSV versions.

Doing this in How To CSV

Paste the file into CSV Lint first to see exactly which of the three causes above applies (BOM, mixed line endings, or smart quotes are each flagged by name), then let Auto Fix strip BOM characters and normalize line endings automatically. See our dedicated guide on fixing Shopify CSV errors for product and inventory-specific issues beyond line 1.