XnView Software

Hello,

I really like the batch rename feature in XnView, especially the ability to rename files based on their EXIF shooting date using the pattern {EXIF:Date Taken [Y-m-d_H-M-S]}. It’s very useful for organizing photos by the time they were taken.

However, there’s a small issue when working with modern mirrorless cameras that can shoot many photos within the same second. Since these photos are often taken in bursts, multiple images may share the same timestamp down to the second — even though they actually have different millisecond (ms) values in their EXIF metadata.

Currently, it seems that XnView’s batch rename tool doesn’t recognize or use the millisecond (ms) value from the EXIF data. As a result, when I try to rename many burst photos by EXIF date, I often get filename conflicts — the software prompts me that some files already exist and asks whether to overwrite them.

In fact, these files are not duplicates; they were simply taken within the same second.
It would be great if XnView could support reading and including EXIF milliseconds (ms) in the rename pattern to avoid this problem.

Thank you for considering this suggestion!

1. there are tags exist:
{EXIF:SubSecTime}
{EXIF:SubSecTimeOriginal}
{EXIF:SubSecTimeDigitized}

2. there is Duplicate setting exist, to solve name conflicts

3. there is no Overwrite dialog when name conflict happens, app just show error

1q2w3e wrote: Sun Nov 02, 2025 5:58 am when I try to rename many burst photos by EXIF date, I often get filename conflicts — the software prompts me that some files already exist and asks whether to overwrite them.

are you bot?

@user0

Reply:
Thanks again for your reply!
I tried your suggestion using these tags:
{EXIF:SubSecTime}, {EXIF:SubSecTimeOriginal}, and {EXIF:SubSecTimeDigitized} — but unfortunately, they don’t give me the result I want.
I’m using photos shot on a Fujifilm camera, and processing them on macOS with XnView. When I include those tags in the batch rename pattern, the filenames just end up with meaningless numbers like _1, _2, _3, instead of the actual millisecond values from EXIF.
That’s why my real suggestion is to make it simpler — to allow an extended pattern like this:
{EXIF:Date Taken [Y-m-d_H-M-S-MS]}
This would be a clean and direct way to include milliseconds (ms) right after the seconds, without combining multiple tags.
Also, I remembered something about the overwrite message I mentioned earlier. It doesn’t appear during “Batch Rename”, but rather during this process:
File → Import and Sort → New filename
When I move photos into a folder and rename them at the same time, if multiple burst shots share the same second but have different milliseconds, XnView shows a “file already exists — overwrite?” prompt.
That’s exactly the case I’m hoping could be avoided if milliseconds were supported in the rename pattern.
Thanks again for your patience and your great software!

And no, I’m not a bot — just someone who really likes XnView but isn’t very good at English, so I used a bit of help with translation.
Thanks again!

so you are talking about Import&Sort dialog, not Batch rename
you can use # enumerator there, but it will be applied to all files, not just duplicates

1q2w3e wrote: Mon Nov 03, 2025 6:23 am That’s why my real suggestion is to make it simpler — to allow an extended pattern like this:
{EXIF:Date Taken [Y-m-d_H-M-S-MS]}

DateTime tags have second precision
SubSec tags have milliseconds/nanosecond(non-standard) precision

1q2w3e wrote: Mon Nov 03, 2025 6:23 am {EXIF:SubSecTime}, {EXIF:SubSecTimeOriginal}, and {EXIF:SubSecTimeDigitized} — but unfortunately, they don’t give me the result I want.
I’m using photos shot on a Fujifilm camera, and processing them on macOS with XnView. When I include those tags in the batch rename pattern, the filenames just end up with meaningless numbers like _1, _2, _3, instead of the actual millisecond values from EXIF.

check what data is in subsec tags