Photo workflow Tip: The Lightroom XMP default setting

Many photographers, including us at Mountain Moments, use Lightroom.

An important basic setting, perhaps the most important setting in Lightroom, is strangely only known and used by a few photographers. For years ignorance of this one little setting hasn’t been a problem, but suddenly: the software refuses the service; time to upgrade that PC because the hardware has to be defective or could it be the operating system creating problems?

In the last place you look for a solution you will find out that the following basic setting in Lightroom can ensure the future survival of your photos by working with XMP files and saving them externally.

If you have not yet dealt with how all your image edits are saved, the name XMP file probably doesn’t mean anything to you.

XMP files store all the changes you make to an image and stores them in a small reference file that only needs a few kilobytes of disk space. Sure, Lightroom itself does that in the catalogue, but the data is only readable for Lightroom and only in your catalogue as a whole. What if you need to reinstall light room on a new PC, or perhaps you sometimes work between home and the office, changing between different instances of Lightroom or another program all together?

An XMP file is saved as a separate file for each image. The file names are also identical. This makes them easier to retrieve, use and backup. XMP files can also be read and used by many other programs, making collaboration a much easier affair.

In this article you will learn what an XMP file is and why it makes sense for you as a photographer.

Update #4: XMP files in Lightroom Classsic CC and Lightroom CC – info near the end of the text.

Instructions Lightroom Basic Setting: How to Save XMP Files

Why the XMP files are not saved in Lightroom by default is a mystery to us. It can only be explained by the increased usability of a relatively slow program, and of course the fact that Adobe wants to retain its users by not enouraging the use of competiting software. At the end of the day its great for Adobe, but doesnt quite serve us and so we need do adjust this for our convenience.

Storing the XMP files externally is very easy, and only needs to be done once per installation of Lightroom and takes less than 10 seconds:

• In the menu bar, go to “Edit” and click on “Catalog settings”.
• In the appearing control panel, select the third tab “Metadata”.
• Select “Save changes automatically in XMP”.
• Click on “OK”.

And Voila, it’s done!!!!

All your image data and the changes you made to the images in the Lightroom catalog are now also stored, externally, in your respective image folder as XMP files.

You have successfully mastered the most important Lightroom setting to save those essential XMP files.

This won’t bring you any advantages yet, but the next software or hardware change and a computer problem will come as sure as the Amen in the Church. When the time comes, you’ll be eternally grateful and won’t have to spend days importing non-functioning Lightroom catalogues.

This technique avoids redunancy, and expands your safe and meaningful workflow. Your Mountain Moments Team wishes you happy photography.

Would you like to learn more about basic knowledge and best practices of simple image processing? Take a look at our current outdoor photography workshops, and learn pro photography in nature as an all round fun experience.

UPDATE #3: Save XMP File in Lightroom Classic CC

As almost already integrated in the product name, the current Lightroom Classic CC also offers the option of storing XMP files and thus the edits of a raw file externally.

Where you can find the setting: Also in Lightroom Classic CC you will find the magic tick under “Edit – Catalog Settings – Metadata”.

UPDATE #4: XMP File in Lightroom CC

As of November 2018, we are not aware of any possibility to externally manage XMP files in Lightroom CC. If you know a solution to backup XMP files externally, please share your knowledge with us and all other photographers dealing with this problem in the comment section below. Thank you.