V3.37-beta.4: export in UTF-16 is written without BOM although “Write BOM” is enabled

Support
1

Hello,

After updating to Mp3tag v3.37-beta.4 (Oct 23 2026), my export file is saved as UTF-16 LE without a BOM, even though “Write BOM” is checked in Tools > Options > Export.

Details:

  • I export to a tab-separated text file with my own export template. The first line of the template is:
    $filename(tsv,utf-16)STATS$char(9)%_total_files%$char(9)%_total_size%$char(9)%_total_time%$char(9)%_date%
  • “Write BOM” was enabled before the update and still is.
  • I did not change any export setting. Until now, the same export produced a file starting with the UTF-16 BOM (FF FE).
  • The new file starts directly with the bytes 53 00 54 00 (the letters “ST” in UTF-16 LE), with no BOM.
  • This breaks software that relies on the BOM to detect the encoding.

Expected: a BOM at the start of the file, as before.
Actual: no BOM.

Could you please check whether this is a regression in the beta, (v3.37.beta.2, was exporting fine) or whether the behavior was changed on purpose? I’m happy to provide the full export template or a sample file if needed.

Thank you!

2

I just used a very basic export script and enabled BOM, wrote the export, then disabled BOM and wrote the file.
These are the results as shown in a hex editor:

grafik

grafik

which means that I get BOM written.

3

Ok. I accept that. But, in previous version v3.36 I had BOM written. Now I don't, even after re-installing v3.36. With BOM enabled I don't get it! And I've tried with CSV export, same problem. So maybe the problem is elsewhere. On my Windows 10 or something. Thank you.

4

HI again,

Found out problem is in mp3tag.cfg. If I delete it and restart program BOM is written.

However I loose al my customizations... Replacing old .cfg, problem returns. Any light? Please.

5

Do you have Append data enabled and the (possibly empty) target file already exists?

6

Yes!!! Thank you. No Append data enabled, but previous target file (not empty, previous list), existed. I've delete it, exported again, and BOM! There it was! Thank you!
(Did not understood why, previous file existed before this "bug". The exporting TSV is an incrementional, low frequence, file). But again! It worked! Solution found!