Text file guides

Remove the right byte-order mark from a saved text file

·

The first bytes of a saved file can mark its Unicode encoding. When two signatures overlap, the application's original save settings can tell you how many bytes to remove.

BOM Detector and Remover

Choose the source encoding when two signatures match

Select Load ambiguous example. The eight original bytes are FF FE 00 00 41 00 00 00. The report shows two matching prefixes before enabling the export.

If the file came from a UTF-16LE writer, choose UTF-16LE. The six output bytes are 00 00 41 00 00 00. The first zero code unit belongs to the payload. For a UTF-32LE source, choose UTF-32LE and compare the four output bytes 41 00 00 00.

Unicode FAQ on UTF encodings and the byte-order mark

Verify an unambiguous UTF-8 export

Open a UTF-8 source that starts with EF BB BF. In Original file bytes, the report identifies the three-byte prefix. Download bytes without BOM and check that the new file is three bytes shorter.

Compare the rest of the file with the source. The payload keeps its original encoding, line endings and any later U+FEFF characters.

Unicode FAQ on UTF encodings and the byte-order mark

Choose pasted text when you only have characters

Switch Input source to Pasted Unicode text, load the example and select Check pasted text. The tool removes one leading U+FEFF and returns the remaining characters.

Use the file mode when you need evidence about the source encoding. Pasted characters may already have been decoded or had a leading mark removed by the originating app.

Unicode FAQ on UTF encodings and the byte-order mark

Common questions

Does a missing BOM rule out UTF-8?

UTF-8 files can omit their BOM. Check the encoding information from the original application when the prefix is absent.

How many repeated marks are removed in one export?

One leading mark is removed per export. Other bytes stay where they were relative to the rest of the payload.

Sources

Put it into practice.

Related guides