# File name \>\>Tag results in corrupt track numbering

**URL:** https://community.mp3tag.de/t/file-name-tag-results-in-corrupt-track-numbering/60735
**Category:** Support
**Created:** [April 18, 2023, 3:58pm UTC](https://community.mp3tag.de/t/file-name-tag-results-in-corrupt-track-numbering/60735 "2023-04-18T15:58:32Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Goldie](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/e36b37/32.png) [@Goldie](https://community.mp3tag.de/u/Goldie)
#### Post date: [April 18, 2023, 3:58pm UTC](https://community.mp3tag.de/t/file-name-tag-results-in-corrupt-track-numbering/60735/1 "2023-04-18T15:58:32Z")

</div>

![Clipboard02](https://community.mp3tag.de/uploads/default/original/2X/3/34639808c44375888d3f57ce2776ba4c51de2e3a.jpeg)  
 ![Clipboard03](https://community.mp3tag.de/uploads/default/original/2X/7/75655a194d1309f039e3f2ca5f51c355a71a031a.jpeg)  
mp3tag v.3.20, clean installation today:

When copying track numbers from file name to tag and the numbers are three figures (like track no. 123) the numbers upto 008 are correct in Windows 10 File Explorer. Then comes another 008 and then a double 009 and this is repeated at 018, 019, 028, 029 and so on. The inbetween number are also affected by this behaviour. The track number ("spår") shown in mp3tag are curiously enough correct. I attach some example screen dumps.

I have not tested any other format like 01 or 0123.

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [April 18, 2023, 4:07pm UTC](https://community.mp3tag.de/t/file-name-tag-results-in-corrupt-track-numbering/60735/2 "2023-04-18T16:07:42Z")

</div>

As MP3tag shows the track numbers as they should be, I doubt that this is an MP3tag bug.  
See also here:

> [@Padding Track Num, Scrambled.](https://community.mp3tag.de/t/padding-track-num-scrambled/11740):
>
> Does padding of the track numbers affect how explorer and mp3 players reads the track number?(Padding being the prefixing with zeros to have a specific number of characters.) I used 'Bulk Rename Utility' ver 2.7.1.2 to rename a series of 150 mp3s that were named with the suffix of 'title disk\_track'; 01\_01 through 15\_10 to their sequential counterparts 001 through 150. The conversion worked and everything was fine. I then attempted to use mp3tag to cleanup the file attributes and set the trac…

or here

> [@Auto-Numbering Wizard works incorrectly by using leading zeros](https://community.mp3tag.de/t/auto-numbering-wizard-works-incorrectly-by-using-leading-zeros/56359/2):
>
> see this thread and look for the explanation on "octal numbers". It's a bug in the Windows explorer.

---

<div class="post-metadata">

### Author: ![Goldie](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/e36b37/32.png) [@Goldie](https://community.mp3tag.de/u/Goldie)
#### Post date: [April 18, 2023, 4:43pm UTC](https://community.mp3tag.de/t/file-name-tag-results-in-corrupt-track-numbering/60735/3 "2023-04-18T16:43:11Z")

</div>

@ohrenkino This indeed seems to be the reason for the corrupt track numbering in Windows File Explorer. I removed the zero padding and the problem disappeared 🙂 Thank you for your quick response! I have been using mp3tag for several years now and I have never observed this misbehaviour in Windows.

---

<div class="post-metadata">

### Author: ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)
#### Post date: [May 18, 2023, 4:43pm UTC](https://community.mp3tag.de/t/file-name-tag-results-in-corrupt-track-numbering/60735/4 "2023-05-18T16:43:50Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
