Rename .JPG to .jpg recursively

find /path/to/images -name '*.JPG' -exec bash -c 'mv "$1" "${1/%.JPG/.jpg}"' -- {} \;
Recursively rename .JPG to .jpg using standard find and mv. It's generally better to use a standard tool if doing so is not much more difficult.

By: sorpigal
2010-01-07 15:41:17

1 Alternatives + Submit Alt

What Others Think

find /path/to/images -name '*.jpg' -exec rename.ul .JPG .jpg {} + rename.ul is the util-linux rename command, widely available on linux systems, possibly named just 'rename' if not overridden by perl rename (prename). Also here I use the + form of -exec instead of \; so that find will launch rename.ul on many file names at once, using many fewer process spawns. With -exec bash -c mv ... you launch a shell process which launches a mv process just to rename one file. It works, but for performance, you'd be much better off writing a shell script, which is a very standard tool.
bwoodacre · 627 weeks and 5 days ago
Thanks sorpigal. This did exactly what I needed it to. I tried the other command but it failed. Maybe I had a typo. @ bwoodacre. I should have totally used + instead of \; Dooh!
Xinerama · 584 weeks and 2 days ago
Using the "-exec" option of "find" is not a good technique. Basically while it is running a command "find" is waiting, and not 'searching' for the next file. This is why piping the output of "find" into "xargs" is a better idea. The filename gets cached by the pipeline ready for "xargs" to use when ready, while "find" continues to search. See find -exec vs xargs Also look at commands like "mv_perl" whcih can rename multiple files in the one command. You can have "xargs" feed lots of files to each command, or just one one command per directory.
anthony · 584 weeks and 1 day ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: