/          All Posts       Projects       GitHub       More...

How to store Lightroom previews separated from the catalog

Lightroom splash screen

Lightroom is a very powerful tool, but for some reason, it's not possible to configure the location of a catalog's preview cache. They are always saved in a folder next to the associated catalog.

In my case, this is not ideal:

Fortunately, there is a solution!

Like other operating systems, Windows has the (not very widely known) ability to create symbolic links to files and folders.

Simply put, a symbolic link is a thing that looks and behave like a file or a folder, but actually points to another file or folder.

In our case, this allows us to move the preview cache to another location, without Lightroom noticing!

Step by step

Here is my Lightroom folder, with the default catalog: Lightroom folder

If your catalog is named Lightroom Catalog.lrcat, the preview cache folder will be Lightroom Catalog Previews.lrdata.

To do that, open a command prompt, and use the mklink command.

If you don't know how to open a command prompt, the easiest way is to go in your Lightroom folder, then type cmd in the address bar, and press enter.

Open a command prompt

The basic syntax is MKLINK [/D] Link Target. The /D flag is required when making a directory symbolic link.

In my case, I want to create a symbolic link named Lightroom Catalog Previews.lrdata pointing to the location I:\Lightroom Catalog Previews.lrdata, so the complete command I need to type (or copy paste) is: mklink /D "Lightroom Catalog Previews.lrdata" "I:\Lightroom Catalog Previews.lrdata"

Note: quotes are required around the paths if they contain spaces.

Execute mklink

If you did everything properly, you should end up with something like that:

Expected result

(the screenshot shows the properties of the symbolic link)

And voilà! Now you can start Lightroom and check everything still works as expected 🙂


Newer Older
0 comment

Formatting cheat sheet.
The current page url links to a specific comment.
The comment is shown highlighted below in context.

JavaScript is required to see the comments. Sorry...