• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.
  • 29 September 2026 It's Lightroom update time again. There are some minor features, as well as bug fixes, new cameras and lenses.
    See What’s New in Lightroom Classic 15.6, Mobile & Desktop (September 2026)?

Library module Photo missing in "All Photographs"

photopoeth

Member
Premium Classic Member
Joined
Aug 30, 2021
Messages
93
Location
Karlsruhe, Germany
Lightroom Experience
Power User
Lightroom Version
Classic
Lightroom Version Number
15.5.1
Operating System
  1. macOS 15 Sequoia
I have a mystery that I can't figure out here—maybe someone can point me in the right direction.

I happened to notice today that from 2 photos contained in a collection I'm examining, one doesn't appear in the 'All Photos' catalogue overview. I didn't apply any filters and I can't think of any reason why the "All Photos" collection would be limited, either. Both also show in the library folder, too. A total of 98 images have 'disappeared' (from this one collection alone).
The 2 images are of a different type - one is a TIFF and the other is a JPEG. The TIFF image appears in both the collection/folder and the 'All Photos' list, but the JPEG image is missing from my 'All Photos' overview.

Now I'm a bit suspicious of this, since I’d like to trust that 'All Photos' actually shows all the photos. I know there can sometimes be issues with stacks or virtual copies, but in this case these are just regular individual image, nothing special about them.

Please help me solve this mystery. Any idea anybody?
 
You have probably checked these.. just in case...
1. Make sure that the option to show all subfolder content is active.
2. There is a small hidden option if viewing the metadata filter grid.. top right hand corner someplace... the option I think is to show original, virtual or video. The virtual option may be inactive .. I know you said it is not a virtual image... but I would make sure all possible filters were turned off.. just to avoid hidden trip wires.

Does one of the images have all metadata cleared..

It is tricky with collections as an inadvertent tap of the B key can silently remove an item from a collection..
 
You have probably checked these.. just in case...
1. Make sure that the option to show all subfolder content is active.
2. There is a small hidden option if viewing the metadata filter grid.. top right hand corner someplace... the option I think is to show original, virtual or video. The virtual option may be inactive .. I know you said it is not a virtual image... but I would make sure all possible filters were turned off.. just to avoid hidden trip wires.

Does one of the images have all metadata cleared..

It is tricky with collections as an inadvertent tap of the B key can silently remove an item from a collection..
Thanks for your suggestions, but it didn' help. Checked 1. and 2. All Metaf´data is there. "B" will add/remove from the target collection, but the "All Photographs" is an automatic virtual collection provided by LrC that won't work as a target collection.
 
'All photographs' is what it says: All photographs, no exceptions. If you are sure the image isn't hidden inside a stack (choose 'Photos - Stacking - Expand All Stacks') and there is no active filter either, then there is something wrong. You could see if deleting the 'Catalogname Helper.lrdata' fixes it (Close Lightroom first, then delete it and start Lightroom again) or else if resetting the preferences does.
 
Triple check while in All Photographs:

1. Do the menu command Photo > Stacking > Expand All Stacks.

2. Make sure the menu item File > Library Filters > Enable Filters is unchecked.
 
OK... shame on me.

It really was a problem with the stacks feature. The photo was hidden in a stack with another photo and the stacks weren't expanded in 'All Photographs'.
I was sure I checked that beforehand, but it seems to have slipped my mind.
In any case, thanks for clearing up what turned out not to be such a big mystery after all!

All the best to you all, and have a great time!
 
No shame involved. LR Classic is a complicated power tool, and it's easy to overlook something. So it's always helpful to get additional eyes looking over your shoulder.
 
No shame involved. LR Classic is a complicated power tool, and it's easy to overlook something. So it's always helpful to get additional eyes looking over your shoulder.
I rarely use Stacks. I have never found a place for Stacks in my workflow. I wonder if issues like this one are part of the reason i have discouraged using Stacks?
 
Just waking up here in California and catching up. As with others, 'stacking' was my first thought. As others have mentioned you can "Exapand all Stacks" which works but can take several minutes or more if you have a lot of images in your catalog but then any effort you had put into stacking images would be lost. in 2022 I wrote a blog on this topic (and have since updated it a few times) which provides a better, and quicker method to "See all Photos - REALLY" which does not unstack images but alllows you to see them all with just a single click (see Solution 3 in the blog)

https://www.danhartfordphoto.com/blog/2022/4/lr014-lrc-tip01-all-photos-really
 
Just waking up here in California and catching up. As with others, 'stacking' was my first thought. As others have mentioned you can "Exapand all Stacks" which works but can take several minutes or more if you have a lot of images in your catalog but then any effort you had put into stacking images would be lost
Apparently you are not completely awake yet. :-) Expanding all stacks is very fast, and shows all the stacked images next to each other. It does not unstack them, so nothing gets lost. The opposite is ‘collapse all stacks’.
 
Yes, sorry about un-stacking vs. expanding - my bad. I probably didn't explain it well but if you expand all stacks, you do lose track of which stacks had been collapsed and which had been expanced and if you have expended effort to have some stacks expanded and some collapsed for some reason that effort will be lost.

I do diesagree on the time it takes. In the past (eg in 2022 when I was writing that blog) I experienced several minuutes to expand or collapse all stacks in my catalog of about 80,000 images at that time. Maybe that is better now - I haven't retested it since then.
 
It will depend on the number of stacks, and perhaps also on the average number of images in a stack. I have to admit that I do not create stacks in ‘All Photographs’ at all. I don’t see any advantage in doing that, exactly because ‘All Photographs’ is only all photographs if you expand all stacks, or better still: have no stacks at all. Stacking in ‘All Photographs’ will only lead to the kind of mistake that started this thread.

I do use stacks in normal collections for HDR, panorama, focus stacks, virtual copies, and images sent to Photoshop, so quite a bit. Sometimes I need to use expand all stacks in a collection, and so far it always has been instantaneous. No delay, but of course my normal collections do not contain tens of thousands of images (my catalog is 215,000 images in total, in perhaps 100 collections) so maybe I’ve been lucky in that respect. I never counted the number of stacks that were expanded or collapsed again.

I see no use at all for expanding some stacks and collapsing others, so that is never a problem for me. All my stacks are collapsed (so it really resembles a stack, not just grouped images), except for the one I’m working in at that moment.
 
One reason why I don’t want stacks to remain expanded: stacks sort by their top image, but the contents of a stack does not sort. That means that several expanded stacks next to each other can become very confusing, because the images might be sorted randomly as a result.
 
Stacking done in folders show up in All Photographs and vice-versa. So, if you use stacking in folder you "All Photographs" is alredy no longe all Photographs if some of those stacks are collapsed.

I do a fair amount of stacking in my folders. And in many cases I have reasons to leave some stacks collapsed and some expanded. For example I leave a stack of image that I want to do an HDR or Panorama merge on expanded till I do that operation and then I collapse the stack with the merged image on top. Yes I know I can also use collections or keywords for the same purpose. I just find using stacks for this more convenient in my workflow.

I'm not sure I'd characterize the order of images inside a stacks as "random". They are in "stack order". Initially, when the stack is created, 'stack order' is whatever the order was in the gird/filmstrip of the images being stacked. Later the user can re-arrange them into any order they want.
 
Stacking done in folders show up in All Photographs and vice-versa. So, if you use stacking in folder you "All Photographs" is alredy no longe all Photographs if some of those stacks are collapsed.
Yes, I realise that. I think that’s a major design flaw. ‘All Photographs’ should not support stacks in my opinion, or at least not automatically inherent them from folders. That would avoid this problem. For me, that’s not an issue however. I use folders only for storage, nothing else, so I never do any work in folders and therefore never create a stack in a folder.

I'm not sure I'd characterize the order of images inside a stacks as "random". They are in "stack order". Initially, when the stack is created, 'stack order' is whatever the order was in the gird/filmstrip of the images being stacked. Later the user can re-arrange them into any order they want.
True, but that is where the confusion can start. One stack may have been created when the images were sorted by name, another stack was perhaps created while the grid was in some custom order. Every problem is solvable, that is not my point. My point is that I regularly see questions like the start of this thread, where people can’t find images because they are buried in stacks and may also not be in the order you initially expect them to be when you look at an expanded stack. Do not forget that you can also drag images into a stack, so that is another way they can end up in an unexpected order.

If you strictly work the way Lightroom was designed, so folders are only for storage, while collections, smart collections and metadata are for organizing, then you’ll avoid many of these problems. If you can’t find an image (perhaps it wasn’t added to that collection by mistake, or removed by mistake), then one trip to ‘All Photographs’ will make you quickly find it as long as it’s in the catalog.
 
. ‘All Photographs’ should not support stacks in my opinion, or at least not automatically inherent them from folders

I agree that "All Photographs" should be what it says and the way it is now does cause confusion. But I do get value by having All Photographs mirror folder stacking. My vote would be to name it something different such as "All Folders" and to have a toggle on the screen to include/exclude images burried in stacks.

One stack may have been created when the images were sorted by name, another stack was perhaps created while the grid was in some custom order.

You are also correct in noting that the stack order on one stack may be different than the stack order on another but the same is true for folders and collecitons as well. For example, one collection can be in File Name order with another in Capture date order and a third in custom order. So, in that regard it is consistent and I like consistency.

If you strictly work the way Lightroom was designed, so folders are only for storage, while collections, smart collections and metadata are for organizing, then you’ll avoid many of these problems.

In my experience, as many people use Folders as a top level organization tool than don't. Whether in 2005 or 2006 the design principle was one way or another is speculative and one could credibly argue both ways, but that distinction is not really relevent. What is relevent is that the Folder Panel promenintly exists and a large portion of the LrC user base does rely on folder structures for at least some part of their image management toolkit.
 
I rarely use Stacks. I have never found a place for Stacks in my workflow. I wonder if issues like this one are part of the reason i have discouraged using Stacks?
Whereas I use stacks all the time in my workflow (but admittedly get tripped up now and again when a stack ends up (via user error) open or closed when I want it in the opposite state.

My workflow, particularly with my 12000 scanned images, involves using external editors for doing things that LrC can’t and then final processing in LrC. So there are derivative files of the same image, and I stack them all together since I neither need nor want to see those derivative files when I’m working on my final pass in LrC.
 
I agree that "All Photographs" should be what it says and the way it is now does cause confusion. But I do get value by having All Photographs mirror folder stacking. My vote would be to name it something different such as "All Folders" and to have a toggle on the screen to include/exclude images burried in stacks.
I would definitely not vote for that. 'All Photographs' is easier to understand, and 'All Folders' already exists, providing you have a single top folder...

You are also correct in noting that the stack order on one stack may be different than the stack order on another but the same is true for folders and collecitons as well. For example, one collection can be in File Name order with another in Capture date order and a third in custom order. So, in that regard it is consistent and I like consistency.
The difference is that this is only true if you view those collections/folders one at a time. We are talking about viewing multiple expanded stacks at the same time however, so you should compare that to viewing multiple collections/folders at the same time as well. If you select multiple collections/folders, then you'll see one grid with one sorting order, not one grid with the images of each collection/folder sorted differently. And so you can never get confused like you can if you view multiple expanded stacks next to each other.
 
Back
Top