Smart previews for culling: fast, but know the catch

Smart previews let you pick photos with the drive holding your originals sitting at home. Adobe's own example: 500 raw files taking 14 GB produced smart previews totaling 400 MB. That is a genuine speed trick. It is also a smaller file, which means there is exactly one judgment you should not make from one. Here is the honest version.

What a smart preview actually is

A smart preview is a stand in. Adobe describes it as a lightweight, smaller file format based on the lossy DNG format. Lightroom Classic builds one alongside your original, stores it next to your catalog, and can use it in place of the original when the original is not reachable.

The size difference is the whole point, and Adobe's own smart previews documentation gives a worked example: 500 raw images from a high end camera occupying 14 GB on disk produced smart preview files totaling 400 MB. That is a small enough footprint to carry a whole wedding on a laptop with nothing else attached.

What Adobe promises with them is specific. You can continue to work with your smart preview files even when the device containing your original photographs is disconnected, and you can perform all the edits you would perform on the original. Notice what that sentence covers and what it does not. It is a promise about your edits being valid. It is not a promise that a small file shows you everything a large one does.

Three ways to build them, two ways to get rid of them

Adobe documents three routes to building smart previews in Lightroom Classic, and the one you choose is really a question of when you want to spend the time.

• At import. In the Import window, in the File Handling section on the right, select Build Smart Previews. Your import runs longer. Everything afterward is quicker.
• After the fact. Select the photos you want, then Library > Previews > Build Smart Previews. This is the one to know, because it lets you build them for one folder rather than an entire catalog.
• When exporting a catalog. File > Export as Catalog, then select the Build/Include Smart Previews checkbox. This is how a travelling catalog gets made: the catalog and its proxies go on the laptop, the originals stay on the drive at home.

To get rid of them, either select the photos and choose Library > Previews > Discard Smart Previews, or click the Original + Smart Preview status under the Histogram in Library or Develop and choose Discard Smart Preview from there. Worth doing at the end of a season, because the smart previews file grows quietly and Catalog Settings will show you how much disk space it is using.

They live in a file named [Catalog Name] Smart Previews.lrdata, in the same folder as your catalog. If you followed the advice in setting up Lightroom Classic for culling speed and put your catalog on the internal SSD, they are already on the fastest disk you own, which is exactly where you want them.

The status line that tells you what you are looking at

This is the most useful thing in this article and almost nobody looks at it. Underneath the Histogram, in both Library and Develop, Lightroom Classic tells you which version of the file is on screen right now. Adobe lists the states.

Get into the habit of glancing at that line before you flag anything at full zoom. It takes half a second and it is the difference between a considered decision and a guess you did not know you were making.

Where a smart preview will mislead you

Here is the trade off stated plainly, because most articles on this topic skip it. A smart preview is a smaller file than your original. It has fewer pixels. When you zoom in on a smart preview and decide a frame is sharp, or decide it is not, you are making a judgment about fine detail using a version of the photograph that does not contain all of that detail.

Both errors are real and both cost you. You can keep a frame that looks acceptably sharp in the proxy and turns out soft at delivery size. Worse, and more common, you can pass over a frame that looked slightly soft in the proxy when the original was actually fine, and nobody ever finds out because that photograph simply never appears in the gallery.

Adobe clearly takes this seriously. There is a preference in Lightroom Classic called Use Smart Previews instead of Originals for image editing, which tells Lightroom to work from proxies even when the originals are right there. Starting with the June 2025 release, Adobe shows a warning dialog at startup when that preference is switched on. A vendor does not add a startup warning to its own performance feature unless enough people were being caught out by it.

None of this makes smart previews bad. It makes them a proxy, which is what they were always advertised as. The mistake is not using them, the mistake is forgetting which file you are looking at when a decision gets close. This is one instance of a broader point we make in why your best photo is rarely your sharpest: sharpness is a threshold to clear, not a score to maximize, and it deserves less of your attention than the frame in front of you does.

The routine that uses them without getting caught

Split the work by what each judgment actually needs. Almost everything you decide on a first pass survives a smaller file perfectly well. One thing does not.

So the routine is two passes. Pass one, drive disconnected. Go through everything on smart previews at fit view, flagging on moment and eyes and dropping the obvious near duplicates. Fast, portable, and no waiting on an external drive spinning up. Pass two, drive attached. Reconnect, confirm the Histogram says Original, and go back through the shortlist only at 1:1 for the focus calls. That second pass is short because you are looking at hundreds of frames rather than thousands.

The burst row is the one that catches people. Sorting eight frames of the same moment is the most repeated decision in the whole job, and the last step of it is always a focus comparison. Do the narrowing on proxies, do the final pairing on originals. We work through the ordering of that decision properly in choosing the best frame from a burst.

When smart previews are worth it, and when they are not

They earn their build time in three situations.

Your originals live on an external drive. This is the main one. If your archive is on a drive that is not always plugged in, smart previews mean the catalog stays useful without it. That alone is worth the disk space.

You work away from your desk. A laptop with the catalog and its proxies can hold a season's work. Export the catalog with smart previews included, take the laptop, do the first pass wherever you actually are. If that is your situation, culling on location covers the rest of the kit around it.

Your machine is struggling. A smaller file is less work to decode. On older hardware, moving through a folder of proxies can be noticeably smoother than moving through 45 megapixel raws, though it is worth diagnosing the actual cause first rather than assuming, and why Lightroom feels slow when you cull goes cause by cause.

And the case against. If your originals sit on the internal drive of a reasonably current machine, smart previews mostly buy you build time you did not need to spend. Standard previews at the right size, set once, already make the grid quick. Building smart previews for every photo you own, forever, is a habit that quietly eats a lot of disk for a benefit you are not collecting. Build them per folder, when a folder is actually going somewhere.

What smart previews do not do

They make frames appear faster. They do not reduce how many frames you have to judge. That distinction is the whole thing, and it is easy to lose sight of when a folder suddenly scrolls smoothly.

A wedding is typically 2,000 to 4,000 raw frames and something like 400 to 800 delivered. Whether those frames are proxies or originals, you are still the one looking at every one of them and deciding. A UK survey of more than 300 wedding photographers, reported by PetaPixel, put culling at 11 percent of working time against 4 percent spent shooting. Proxies do not change that ratio much, because the cost is in judgment rather than rendering. If that is your bottleneck, the honest answer is that Lightroom settings are the wrong lever entirely, and what Lightroom genuinely cannot do for selection is the fairer place to start.

Which is where we come in, stated honestly. Kepla is building an app that makes the technical first pass for you and hands back a shortlist, so a 2,000 frame wedding opens as roughly 800 candidates instead of the whole card. It marks its picks and nothing else: no file is ever deleted, moved or renamed, and every frame it did not pick stays exactly where it was, one tap away. The first pass happens on your iPhone or iPad on the drive home, and the same shoot opens on the Mac for the comparisons that need a big screen and real pixels.

That app is still being built. The part of Kepla that works today is the booking page, live and free while we build, and it is the only piece we will claim is finished.

FAQ