How can I keep track of image files that Lightroom cannot import?
Asked 9/6/2017
4 views
2 answers
0
I created a very large gigapixel panorama that Lightroom refuses to import because the file exceeds its size limits. My photo library is organized in a single Lightroom master catalog, where I rely on ratings, keywords, and filters to find images later. If a file is not in Lightroom, I may effectively lose track of it.
What is a practical way to manage files that Lightroom cannot import? Is there a recommended workflow for keeping them associated with the rest of a Lightroom-organized library?
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
8y ago
2 Answers
2
Lack of support for more file types is an issue I wish Lightroom would address, at least for management if not for display and edits. I have GIF's and also some uncompressed video which has similar problems, and for video I have put together with audio tracks there are the input audio tracks I would like to keep with them.
I put mine in the same folder, and then name the folder in some way to indicate it has other items (in my case I put all such folders under a specific parent so I will be more careful with them).
The good news is that Lightroom is greedy on doing folder operations, so for example moving a folder to another drive will also move all the files inside it, whether or not they are ones in the catalog. Not just sidecar files, but any file in the folder. At least on Windows. I do not know if that's an accident or feature, but it is very handy.
And the idea of using a JPG as a placeholder of sorts, in which you can put all the metadata so you can search and sort and select, works well for keeping the items visible.
I've looked for better alternatives, but that seems to be the best bet. Especially (at least in 2015.12 on Windows) since it will manage the files during folder operations. That and press Adobe to add non-editable file support (wishlist form here).
Originally by user28109. Source · Licensed CC BY-SA 4.0
user28109
8y ago
0
Generated from our catalog & community — verify before relying on it.
A practical workaround is to keep the unsupported file in the same folder as related Lightroom-managed images and use the folder structure itself as the reminder.
From the community advice, Lightroom will still manage folder moves even for files it does not catalog, so if you move that folder in Lightroom, the unsupported file should move with it as well. To make this safer, use a clear folder naming convention or place such folders under a special parent folder so you know they contain files Lightroom cannot index.
Your downscaled proxy idea is also a sensible complement: import a smaller JPEG version into Lightroom with an obvious name so it can be keyworded, rated, and found through searches, while the full-resolution panorama remains in the same folder.
In short, the best practice here is:
- store the original unsupported file alongside related photos
- use a clearly marked folder or parent folder
- optionally import a small proxy image into Lightroom as a searchable placeholder
There is no plugin or built-in Lightroom feature mentioned here that fully catalogs files Lightroom cannot import.
Recommended products
UniqueBot
AI8y ago
Your Answer
Related Questions
How should I organize RAW files and JPEG exports in Lightroom on a laptop with limited space?
How can I match unorganized RAW files to an already organized JPEG library?
How can I migrate an old Aperture library to Lightroom Classic and preserve metadata after moving to Apple Photos?
Should I use separate Lightroom catalogs for RAW and JPEG, and will keywords stay in exported JPEGs?
How can I fix Lightroom seeing all Dropbox photos as new after the Dropbox folder path changed?