产品指南 · 6 分钟阅读
UTF-8, BOM, and Excel: making CSVs open correctly on every desktop
When to use UTF-8 with or without a byte-order mark, how Excel on Windows interprets encodings, and how to validate handoffs to pipelines and Mac teammates.
发布于 2025年3月21日 · Table
UTF-8 is the default interchange encoding for modern stacks, but Excel on Windows historically preferred legacy code pages unless it detects a BOM (byte order mark) at the start of the file. A BOM helps Excel guess UTF-8; some Unix tools and strict parsers treat the BOM as an extra character in the first column header, so the "right" choice depends on your downstream consumer.
Practical rules
- For analytics and warehouses, prefer plain UTF-8 without BOM unless your Windows stakeholders insist otherwise.
- After export, open in our viewer and spot-check headers and first rows for stray characters or mojibake.
- Document your team's standard in a short internal note so contractors do not flip encoding per project.
When in doubt, validate the same file in two tools (browser viewer + target database loader) before promoting a file to production.