Byte Order Mark Inspector

Inspect raw file prefixes for UTF-8, UTF-16 and UTF-32 byte order marks without decoding or uploading the file.

Choose a local file. Only its first four bytes are read; the file is never uploaded, decoded or modified.

Inspect a file before choosing a decoder

A byte order mark is a recognizable sequence at the beginning of a file. This inspector compares the first four raw bytes with five common Unicode signatures: UTF-8, UTF-16 little endian, UTF-16 big endian, UTF-32 little endian and UTF-32 big endian. It does not decode the remaining content or guess an encoding from readable words.

How to use the report

Choose a local file and press Inspect. The JSON report includes the complete file size, up to four prefix bytes in hexadecimal, the matching signature and the number of signature bytes. Download the report to keep those observations alongside an import error or support ticket. The original file is unchanged.

The example file contains four bytes: EF BB BF 41. Its report identifies a UTF-8 signature of three bytes and a total size of four. The last byte represents A in UTF-8, but this tool only reports the prefix; it does not validate that interpretation throughout a real file.

Why the longest signature comes first

FF FE 00 00 matches the UTF-32 little-endian signature. Its first two bytes also match UTF-16 little endian, so checking the longer prefix first avoids reporting the shorter match. This is still a signature comparison: unusual binary data or a UTF-16 file beginning with a null character can share these bytes. Use the producer's format specification when the distinction matters.

Limits and missing marks

Only four bytes are read, even for a large file. Empty files and incomplete signatures return none; EF BB alone is not a complete UTF-8 signature. No recognized mark does not establish ASCII or UTF-8. Many correctly encoded text files have no mark, while an arbitrary binary file can begin with the same sequence. Legacy signatures outside the five listed formats are not detected.

Use the UTF-8 byte inspector for already-decoded text. Pasting text cannot reliably preserve evidence about its original file bytes, which is why this inspector accepts a file instead. Do not remove a signature solely because it exists; first check what the receiving application expects.