Adobe’s release notes list Lightroom Classic 15.6; that identifies the version, not a special migration method. Check Adobe’s Lightroom Classic release notes.
Symptom: Your Windows catalog is needed on a Mac, but you are unsure whether to copy it or keep using Windows.
Fastest route: For a one-off Mac task, evaluate a backed-up, separate catalog copy on a remote Mac. If Mac is becoming your regular workstation, plan to move the catalog and originals, then verify every folder link.
This guide is for Windows photographers who want to edit a batch on a Mac, photographers and retouchers moving their regular workflow, and creative teams deciding who owns the catalog, originals, and final delivery.
SECTION 01Catalog continuity: what a copy preserves
A Lightroom Classic catalog is a record of your photo workflow, not a container holding all your original image files. It stores information such as edits and organization details; the original photos remain separate files. Adobe explains this separation in its Lightroom Classic catalog basics.
That distinction determines what “copy the catalog” actually means. A catalog copy can carry forward edits, ratings, keywords, and collection organization recorded in that catalog. It does not automatically bring along the original photos if they are stored elsewhere. Nor should you treat previews as a backup of the original files.
Before moving anything, identify the catalog you intend to use and where its related files are stored. Adobe’s catalog creation and movement guidance describes the catalog file and associated items. Check the actual catalog folder on your Windows computer rather than guessing from a shortcut or from where Lightroom Classic appears in your applications list.
Then confirm that you have a usable backup. Adobe describes catalog backup options in its catalog backup guidance. A catalog backup and an originals backup are separate safeguards: verify both. If the photos live on another drive, cloud storage, or a shared location, confirm that the files themselves are included in a separate copy or can be reached from the Mac.
Copying an existing catalog is usually the better starting point when you need to continue the same project. Creating a new catalog and importing the originals again may make the files visible, but it does not by itself reproduce the old catalog’s edit history and organization. If continuity matters, test a copy of the existing catalog before considering a fresh import.
SECTION 02Original access: full files, external storage, and Smart Previews
A visible thumbnail does not prove the original is available. Lightroom Classic may display a preview saved in or alongside the catalog even when the connected drive holding the source photo is offline. That can make a catalog look ready when it is not.
Check the distinction before choosing a workflow:
- Originals available: The Mac can access the full image files, either on its local storage or on a supported connected drive. This is the clearest setup for work that depends on the source files.
- Originals on external storage: Confirm the drive is connected to the computer running Lightroom Classic and that the expected folders are present. A folder that was mounted on Windows may have a different location or name on Mac.
- Originals unavailable, Smart Previews available: Adobe documents editing with Smart Previews while originals are offline. This can support an offline editing workflow, but a Smart Preview is not the full original file. Do not treat it as a substitute for the originals or as proof that they have been transferred.
This is a practical decision point, not just a storage detail. If you need full-resolution files for your planned output, confirm access to the originals before you start. If you only need to make edits that can be completed with Smart Previews, test the intended export and handoff on a copy before relying on that workflow.
Important: Keep a separate copy of the original photos. A catalog backup protects catalog information; it does not automatically make the photo library recoverable.
SECTION 03Folder links: estimating recovery work
Moving a catalog from Windows to Mac can change the paths Lightroom Classic uses to find folders. The catalog may open and retain its edits, while some or all photos show as missing because the recorded Windows location is not the Mac location.
Treat these as separate cases:
- The catalog will not open: Check that you selected the catalog file you copied and that its related files are available. Do not start rebuilding the library before confirming you are opening the intended copy.
- The catalog opens, but photos are missing: Check whether the originals exist at the new location. If they do, reconnect the relevant folder in Lightroom Classic. Adobe’s instructions for locating missing photos explain how to locate files and folders.
- The originals were never copied: Relinking cannot restore absent files. Transfer or recover the originals first, then reconnect the catalog to their current location.
Use a representative folder to estimate the work before reconnecting a large library. Check whether a parent folder can be located so Lightroom Classic can resolve its child folders, then review a sample of photos from different folders. Do not assume that fixing one visible folder has repaired every location recorded by the catalog.
The same check helps you distinguish a path problem from a missing-file problem. If the Mac cannot browse to the original photo outside Lightroom Classic, the immediate task is to make that file available. If the file is present but Lightroom Classic cannot find it, the task is to correct the catalog’s folder reference.
SECTION 04Storage location: active catalog versus photo files
The location rule for the catalog is different from the location choices for originals. Adobe says an active Lightroom Classic catalog should not be stored on a network location. Review Adobe’s catalog storage guidance before setting up a shared workflow.
That means you should not put the Windows master catalog on a network share and expect multiple computers to open it as though it were a local working catalog. Keep the active catalog on storage local to the computer running Lightroom Classic. You can manage original photo files separately, but still need to verify that the Mac can access them and that Lightroom Classic can resolve their paths.
Remote access adds a question that a normal local migration does not: where does the active catalog actually reside while Lightroom Classic is running? Do not infer the answer from the fact that you can see a desktop remotely. Confirm the remote environment’s storage arrangement and keep the working catalog on storage that functions as local storage to that Mac. A network folder visible inside the session is not automatically an appropriate catalog location.
This is also why remote Mac use is not the same as sharing a Windows catalog over a network. You are using Lightroom Classic in a separate Mac environment, with its own working storage and access to the files. Verify that arrangement before copying a production catalog or photo library.
SECTION 05Choosing a workflow by the work you need to do
| Decision metric | Separate catalog copy on a remote Mac | Full migration to a Mac you use regularly |
|---|---|---|
| Catalog continuity | Preserves the copied catalog’s recorded edits and organization; changes must be reconciled with the master | Makes the migrated catalog the working library, provided you open the right copy |
| Original-photo access | Bring or connect only the files required for the task, then test access | Organize and transfer the library so the Mac can reach the originals consistently |
| Link recovery | Expect path checks for the selected folders; scope the task before editing | Plan to reconnect affected folders and verify the library after transfer |
| Storage responsibility | Decide where the temporary catalog and exports live, and who returns changes | Define the Mac as the working location and maintain backups for catalog and originals |
| Best fit | Occasional Mac-only work with a clear handoff | Regular Mac editing where one maintained library is the goal |
A separate copy limits the impact on your Windows master, but it creates a handoff obligation. Edits made on that copy do not automatically become part of the Windows catalog. A full migration reduces the need to alternate between platform copies, but requires a more complete transfer and a reliable check of original-file links.
Decision conditions
- If you only need Mac for one isolated task, and you can back up the catalog, supply the required originals or Smart Previews, and agree how changes return, choose a separate catalog copy for evaluation.
- If you will keep editing the same library on Windows and Mac, do not treat two active copies as one shared catalog. Define a single master and a controlled transfer process, or choose one primary workstation.
- If Mac will become your regular editing environment, plan a full migration of the catalog and originals, then verify the folder links before you retire the Windows workflow.
- If the remote environment’s catalog storage location is unclear, pause. Confirm that the active catalog will be stored locally to the remote Mac before using it for real work.
- If the originals are unavailable and no suitable Smart Previews exist, do not begin on the assumption that catalog previews will support the required output. Make the source files available first.
SECTION 06Migration checks: a controlled handoff
Use a small, representative job before you move your full workflow. The goal is to catch missing files, lost organization, and export problems while the Windows master is still intact.
- Choose a test project. Pick a folder that represents your real work, including the kinds of edits, keywords, and subfolders you rely on. Avoid using the only copy of a live job.
- Back up both sides. Back up the catalog and separately confirm that the original photos are protected. Record which catalog copy is the master so you do not confuse a test copy with your working library.
- Copy the catalog for the test. Close Lightroom Classic before moving or copying the catalog. Place the test copy in storage that the Mac can access and that is suitable for an active local catalog.
- Make the source files available. Copy the originals needed for the test or connect the storage that contains them. If you plan to work with Smart Previews while originals are offline, confirm that this fits the intended edits and delivery.
- Open the test copy on the Mac. Check that the expected edits, ratings, keywords, and collections appear. If folders are missing, first establish that the originals exist, then reconnect the correct folder locations.
- Export and review the result. Export a representative image and inspect the output against your delivery requirements. A catalog that opens successfully is not yet an accepted workflow if the required original files are unavailable or the export is wrong.
- Test the return path. Decide how changes will reach the Windows master. Do not assume that editing a separate copy updates the original catalog. Agree who will manage the handoff and how the final export and catalog changes will be identified.
- Accept or stop. Continue only if the catalog details, original access, folder links, export, and handoff all pass. If any part fails, fix that part before moving more work.
Adobe’s photo import documentation is useful when checking how files enter a catalog, but importing originals is not a replacement for preserving the catalog that contains your existing edits and organization.
SECTION 07Remote Mac or full move: the practical trade-off
For a temporary task, remote Mac access can avoid changing your Windows master or moving your entire photo library. It is most suitable when the job is contained, the required files can be made available, and you can test catalog storage and the return of deliverables. The trade-off is that you must manage a separate working copy and deliberately reconcile its results.
A full move is a better fit when Mac will be your regular editing machine. You can establish one primary catalog and a consistent originals location, but you take on the work of transferring files, reconnecting paths, and validating backups. If you are comparing temporary access with a longer-term setup, check the available MACNOX plans only after you have established the storage and handoff requirements; a plan does not remove the need to verify where your catalog resides.
The wrong choice usually comes from treating the catalog as the photo library, assuming previews prove that originals are available, or placing an active catalog on network storage. Decide who owns the master catalog before editing, and keep the originals protected independently.
SECTION 08Frequently asked questions
How do I move a Lightroom Classic catalog from Windows to a Mac?
Back up the catalog first, then copy the catalog and its related files to storage the Mac can access. Copy the original photos separately unless they are already available there. Open the copied catalog in Lightroom Classic, then use the folder panel to locate missing folders if the old Windows paths no longer match. Test edits and exports before changing your main workflow.
Can Windows and Mac use the same Lightroom Classic catalog?
You can move a catalog between platforms, but do not treat a network share as a safe place to run an active catalog. Keep the working catalog on storage local to the computer running Lightroom Classic, and move or copy it between systems only when the application is closed. Coordinate which copy is authoritative so edits made on separate copies do not diverge.
Why are my Lightroom Classic photos missing after switching to Mac?
A catalog can retain edits and previews while its recorded Windows folder path no longer points to the originals on the Mac. First confirm that the original files were actually copied or mounted. If they exist, use Lightroom Classic's folder-location controls to reconnect the correct folder. If they were not copied, relinking cannot restore them; recover or transfer the originals first.
Do I need to migrate my whole catalog for a one-time Mac edit?
Not necessarily. For an isolated task, a backed-up working copy of the catalog and only the required originals may be easier to control than changing your main library. Agree in advance how edits, keywords, exports, and final files will return to the Windows master. If changes must merge seamlessly or the Mac will become your regular workstation, assess a full migration instead.
If your current Windows setup means you cannot use the Mac workflow required for a job, a full migration may impose unnecessary file-transfer and relinking work, while a shared network catalog is not a safe shortcut. For a contained edit, first validate a separate catalog copy in a remote Mac environment and confirm the export and handoff. If that test fits your needs, you can review MACNOX remote Mac access; if Mac becomes your regular workstation, use the migration checks above to plan a complete move instead.