Encoding and decoding
CSV Encoding and BOM Inspector
Understand why a CSV import displays unexpected characters.
Processed locally. Your input and output are never uploaded.
Tool overview
CSV Encoding and BOM Inspector tool overview
Inspect BOM markers, line endings, and byte-oriented clues in pasted CSV text. PasteTidy keeps the source and generated result separate so the transformation can be reviewed before copying or downloading.
CSV Encoding and BOM Inspector workflows
- Prepare csv encoding and bom inspector output for a repeatable workflow
- Review local results before publishing or importing
- Keep sensitive pasted content in the current browser tab
Use CSV Encoding and BOM Inspector locally
- Paste the source text or load the example.
- Choose the documented options.
- Review the result and any warnings before copying it.
CSV Encoding and BOM Inspector controls
- Options are explicit and affect only the local result.
- The output remains separate from the source for review.
- No input or output is placed in URLs or analytics.
CSV Encoding and BOM Inspector example
Before
๏ปฟname,value Ana,1
After
BOM: UTF-8 BOM Line endings: LF Columns: 2 Rows: 2
CSV Encoding and BOM Inspector limits and excluded claims
- Pasted JavaScript text cannot prove the original file encoding after decoding.
- Malformed or ambiguous input may require manual review.
- Large inputs remain subject to browser memory and shared worker limits.
Browse all encoding and decoding tools โ
Questions
CSV Encoding and BOM Inspector FAQ
Does CSV Encoding and BOM Inspector upload my input?
No. It runs locally in your browser without an upload endpoint.
Is the result authoritative?
Pasted JavaScript text cannot prove the original file encoding after decoding.
Can I review the source after processing?
Yes. The input remains separate from the generated result until you reset or replace it.