Encoding repair
Shopify CSV UTF-8 Converter
Convert and clean a Shopify product CSV so accented characters, symbols, and product descriptions do not corrupt during import.
Browser-side scan
Drop a Shopify product CSV
No CSV selected
Encoding errors can damage titles, descriptions, vendors, tags, and option values. This page focuses on safe UTF-8 cleanup while clearly flagging characters that may already be corrupted.
Import blockers
Common causes this scan checks
- The file includes a UTF-8 BOM marker before the first header.
- A spreadsheet export used a regional CSV encoding instead of CSV UTF-8.
- Replacement characters appear where original text was already damaged.
- Mixed CRLF and LF line endings make row parsing harder to review.
Workflow
How to use the cleaned CSV
- Scan the file for BOM markers, replacement characters, and line-ending issues.
- Export a cleaned CSV UTF-8 copy for safe structural fixes.
- Manually review rows with damaged characters because the intended text may be lost.
- Use CSV UTF-8 export settings when saving future spreadsheet edits.
Auto-fix policy
What the export can safely change
- Removes the UTF-8 BOM from the first header.
- Normalizes line endings so rows serialize consistently.
- Preserves valid accented characters and symbols already present in the file.
- Flags replacement characters for manual review instead of guessing the original text.
FAQ
Shopify CSV questions
Why does UTF-8 matter for Shopify CSV imports?
Encoding affects product titles, descriptions, options, vendors, and tags. Corrupted text can import permanently into the catalog.
Can corrupted characters always be recovered?
Not always. If the original characters were already replaced before upload, the tool can flag the issue but may not know the intended text.
Should I use CSV UTF-8 in Excel?
Yes. Exporting as CSV UTF-8 is usually safer than a default regional CSV format.