Shopify CSV UTF-8 encoding and ‘illegal quoting’ import errors

Shopify product CSV imports are text-parsing jobs. When encoding drifts from UTF-8 or when quote characters do not follow CSV rules, the importer throws errors like illegal quoting, truncated rows, or misaligned columns. Those failures are maddening because the spreadsheet UI often still “looks fine.” The fix is to treat the CSV as a text artifact, not a worksheet.

Shopify explicitly calls out formatting and encoding issues among common import problems. This page is a practical companion to that doc, not a replacement.

Why UTF-8 matters

Product data includes curly quotes, accents, trademark symbols, and dimensions from suppliers. If the file is saved as Latin-1, Windows-1252, or another legacy encoding, bytes shift and the parser reads garbage or halts on a malformed field. UTF-8 keeps those characters stable across editors and servers.

How to verify encoding before import

  1. After your final edits, open the CSV in an editor that shows encoding (VS Code, Nova, Vim).
  2. Confirm UTF-8 (without BOM if possible—some tools add a BOM that confuses downstream parsers).
  3. Search for stray “ smart quotes inside fields—they should be plain ASCII quotes or correctly escaped per CSV rules.

Illegal quoting: typical causes

  • Unescaped quotes inside a field. Fields containing quotes must wrap the whole field in double quotes and escape interior doubles by doubling them.
  • Line breaks inside a single cell without proper wrapping.HTML descriptions with newline characters belong in quoted fields.
  • Delimiter confusion. Shopify expects commas as delimiters in the standard product CSV. Editors that switch delimiters silently create unparseable rows.

Why Excel is a common culprit

Excel is built for calculation, not CSV fidelity. It reinterprets types, swaps delimiters per locale, and rewrites text on save. If your team must use Excel for intermediate work, treat that file as disposable: import into a pipeline that exports a known-clean UTF-8 CSV, or skip Excel for the final artifact. Details: Excel corruption.

Recovery workflow

  1. Re-export from Shopify if you still have clean source data in admin.
  2. If you must salvage the bad file, isolate one failing row in a minimal repro CSV.
  3. Trim HTML fields and SKU-heavy rows until the error disappears—then expand carefully.

FAQ

Google Sheets “fixed” my file—is that enough?

Sheets is safer than Excel for some issues but still changes formatting. Download as CSV and verify UTF-8 in a text editor before import.

Do compression or ZIP layers matter?

No—Shopify ingests the CSV itself. Zip is for transfer only; unpack before upload.

Why did a tiny edit break everything?

One unescaped quote shifts the parser’s idea of column boundaries, cascading errors for every subsequent cell on that row.

All guidesLaunchCSV