CSV and Excel mojibake should be debugged in this order: identify the real file encoding, decide whether the target needs a UTF-8 BOM, then verify delimiter, headers, quotes, and row column counts. Use file encoding inspection before changing field mappings, preview the CSV table after conversion, and only convert small synthetic samples to JSON for import checks. Real files stay local and are not turned into public result URLs.
CSV mojibake / Excel import / encoding repair
CSV and Excel mojibake import repair
A local-first workflow for Excel CSV mojibake, UTF-8 BOM decisions, GB18030, Big5, Shift_JIS conversion, delimiter checks, and safe pre-import review.
CSV mojibake import repairExcel CSV UTF-8 BOM importGB18030 to UTF-8 importBig5 CSV to UTF-8Shift_JIS CSV to UTF-8CSV encoding before importExcel CSV encoding issue
Separate encoding from table structure
Mojibake is often misdiagnosed as a CSV mapping problem. If Excel or an admin import reads UTF-8, GB18030, Big5, or Shift_JIS as the wrong charset, headers and values break before delimiter logic even starts.
- Must Do: inspect encoding and BOM before editing headers.
- Must Do: keep real customer spreadsheets, filenames, and import logs local.
- Should Do: test target import behavior with a short synthetic CSV first.
Common lookup scenarios
Fix Chinese, Japanese, or Korean text that becomes mojibake in Excel CSV
Check whether a legacy admin system expects UTF-8 with BOM
Convert GB18030, Big5, or Shift_JIS text before import
Preview delimiter, headers, quotes, and row counts before CSV to JSON conversion
Find invisible or fullwidth characters after encoding has been fixed
Recommended workflow
- Inspect file encoding and BOM state first
- Convert to the encoding expected by the target system
- Preview Excel CSV delimiter, headers, quotes, newlines, and column counts
- Convert a small sample to JSON only after characters and columns look correct
- Use Unicode inspection for invisible characters or fullwidth punctuation
Related tool entries
A local-first workflow for Excel CSV mojibake, UTF-8 BOM decisions, GB18030, Big5, Shift_JIS conversion, delimiter checks, and safe pre-import review.
File encoding viewer and converter
Inspect and convert local text file encodings such as UTF-8, UTF-16, GB18030, Big5, Shift_JIS, EUC-KR, and Windows-1252.
LookupToolChakanCSV table viewer and validator
Preview CSV as a table and validate delimiter, headers, empty rows, duplicate headers, and uneven column counts in the browser.
LookupToolChakanCSV template validator
Compare CSV headers with an import template to find missing required headers, extra columns, duplicate headers, and uneven rows in the browser.
LookupToolChakanCSV and JSON converter
Convert CSV to JSON or JSON to CSV in the browser with delimiter detection, header handling, and preview rows for imports and docs.
LookupToolChakanUnicode character inspector
Inspect each Unicode character with code point, UTF-8 bytes, UTF-16 units, character category, and hidden-character hints.
LookupToolChakanFAQ
CSV and Excel mojibake should be debugged in this order: identify the real file encoding, decide whether the target needs a UTF-8 BOM, then verify delimiter, headers, quotes, and row column counts. Use file encoding inspection before changing field mappings, preview the CSV table after conversion, and only convert small synthetic samples to JSON for import checks. Real files stay local and are not turned into public result URLs.
Should I fix encoding or delimiter first when Excel CSV import looks broken?
Fix encoding first if characters are unreadable. Check delimiter first only when characters are readable but columns are merged, shifted, or inconsistent.
Can real CSV rows be shared in a public result URL?
No. Real CSV rows often contain customer, order, address, email, or internal fields. Keep them local and use synthetic samples for public pages.
Continue with these topics
Searchable topic pages that group related tools, answer specific lookup intents, and make Chakan easier for search engines and AI systems to understand.
Unified social credit code format and check-digit guide
A local-first guide to the 18-character unified social credit code structure, GB 32100-2015 check digit, authority/category segments, and safe validation boundaries.
Open topicTDEE, BMR, sleep-cycle, and daily water-intake planning
A local-first planning topic that connects TDEE, BMR, BMI, healthy-weight range, sleep-cycle timing, and daily water-intake estimates without medical claims.
Open topicStock profit, dividend yield, savings-goal, compound interest, and inflation planning
A safe formula-based topic for stock profit, dividend yield, savings-goal backsolving, monthly compounding, retirement gaps, inflation-adjusted purchasing power, ROI, CAGR, and target-price planning.
Open topic