Encoding issues in CSV/JSON: UTF‑8, BOM, and weird characters

What problem this page solves

Fix encoding issues like UTF‑8 BOM, strange header characters, and broken symbols in CSV/JSON. Convert locally and validate output (no upload). This is a “problem intent” page: it’s meant to help you fix a real issue quickly, then point you to the right no-upload tool for the job.

Common causes (quick mental model)

• Input shape mismatch: the data is valid, but not in the structure the converter expects.
• Formatting/escaping: quotes, delimiters, or special characters are not escaped correctly.
• Hidden noise: extra prefixes/suffixes from logs, BOM/encoding artifacts, or copied whitespace.

Practical steps (fast workflow)

1. Validate the input format first (syntax before structure).
2. Convert locally and inspect a small sample (first rows/items) before exporting everything.
3. Export via Copy/Download and verify the output shape matches your downstream use.

Privacy-first note

If your data contains customer records, internal IDs, or tokens, avoid online upload-based tools. All processing happens locally in your browser. Files are never uploaded.

Practical checklist (fast)

If you’re stuck, use this quick checklist to narrow the problem before you try “random fixes”. Start by validating the input format (syntax first), then confirm shape expectations (array vs object, headers vs rows). Convert a small sample, inspect the output, and only then export the full result.

• Validate: confirm the input is strict JSON/XML/CSV (no stray characters).
• Confirm shape: arrays vs objects; headers vs row lengths; repeated tags vs arrays.
• Test a sample: first 20–50 rows/items are enough to detect parsing issues.
• Export: copy/download the output and re-check it in the consumer (script/spreadsheet/API).

This workflow is privacy-first by design: All processing happens locally in your browser. Files are never uploaded.

FAQ

How can I confirm the tool is no-upload? Open your browser DevTools → Network and perform conversion. Your input should not be sent anywhere.

What if the output “looks wrong”? It’s usually a delimiter/shape issue. Validate, then re-check headers/arrays and repeat conversion.

Local verification snippet

Run a quick local check before export/convert:

const text = input.trim();
const value = JSON.parse(text);
console.log(Array.isArray(value) ? 'array' : typeof value);