Who it is forA Lightroom Classic user who wants to leave the subscription but keep years of edits, keywords and presets.
The problemRe-doing edits, keywords and collections by hand across a large catalog takes days.
The outcomeYour Lightroom Classic catalog's edits, keywords, labels, virtual copies and collections appear in Rembrandt, with a report of anything that could not come over.
What you need first
- A computer running macOS, Windows or Linux with a photo folder you want to edit
- A terminal for the Linux and self-host install commands
- A GPU with WebGL 2 support is helpful; the README says older graphics cards are supported at reduced working size
- Permission to open unsigned builds (System Settings › Privacy & Security › Open Anyway on macOS, More info › Run anyway on Windows)
Steps
- Install Rembrandt for your system from the Releases page or the Download table.
- Open Rembrandt and choose the Lightroom Classic import option under Bring your photos.
- Point the import at your Lightroom Classic catalog and let it run.
- Open the import report and note any items the README says cannot come over.
- Open a few migrated photos and compare their edits with Lightroom to confirm they look right.
Prompt for your agent
Using the repo thesnarkitecht/rembrandt, run a Lightroom Classic catalog import into Rembrandt for the catalog at <catalog-path>. Report the count of imported edits, keywords and collections, and list every item in the import report that did not come over.
Caveat. The README lists Print, Book, Slideshow, Web and Map modules, face recognition and Adobe's camera profiles as not here yet, so expect some Lightroom work to stay behind.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page