The 4th image shows what Bridge thinks the next number should be.

The third image shows the results highlighted. I'm renaming both JPG and CR2 files, so the count should increase by 6, so when I select the next batch of images, I should see it fill in 131937, which would be the next number since the last renamed file is numbered 0311836. In the second image, I have to enter 31931 to get the correct sequence number to match the original file number (1931). In the first image, I have the files highlighted that I want to rename. Now it picks some random number that's of no use to me. When I'd go to rename the next files, G to M,, the Batch Rename would automatically apply 007 as the next starting number, so the first renamed file would be img007. Say, files A to F are renamed to img xxx, I would get img001 to img 006. Just keep in mind if you have millions+ files/items as it may take awhile to iterate all of them before any renames are carried out.When batch renaming files, Bridge used to automatically advance the sequence number to the next number after the current sequence, which let you select the next group of images and they would automatically get the next numbers in the sequence. Putting $() around a Get-ChildItem ensures that all of the currently existing files get returned first and are then piped into Rename-Item, rather than piped in dynamically without the subexpression operator. Instead of 'dir |' I can use: dir | where-object -filterscript 'dir -recurse' outputs all the files, folders and sub-folders. Notes: 'dir' is an alias of 'Get-ChildItem'. Using '|' will pipeline the output of 'dir' for the command that follows. You can use 'dir' to see all the files in the folder. Notice: address must incorporate quotes '' if there are spaces involved.

Type: 'PowerShell' and open the 'Windows PowerShell' command window.

Batch rename files