Apple Photos is designed around a single principle: the app owns your photo library. You do not interact with files; you interact with the Photos app, which manages files for you. This design has advantages—everything is organized in one place, metadata is always attached—but it has one major consequence: you cannot access your original files directly.
When you import photos into Photos, the originals are moved or copied into a library file—a folder-like object that lives in ~/Pictures/Photos Library.photoslibrary/ but that Finder treats as a single file. Inside that library is a folder structure containing every original photo you have ever imported. But those files are named with random hashes: DCIM/123ABC/IMG_0123.JPG becomes 2023/01/Photos Library-19/originals/A5F3C91D-123A-456B-7890-ABCDEF123456.jpg.
The Finder cannot browse that structure meaningfully. Only Photos can read the mapping between the hash-named file and the metadata that makes it findable. Every other app on your Mac—editors, backup tools, organizers—can only work with photos that Photos explicitly exports to a different location.
The cause: the library design
Photos is a database-centric app. Rather than pointing at a folder of images and reading the files there, it imports images into its own managed library. The reasons are reasonable: centralized metadata storage, fast searching, the ability to edit without modifying originals, and a simpler user experience where everything is in one place.
But that design has a cost. The original files are no longer files in the normal sense. They are database entries that happen to have actual image data stored in the Photos library. You cannot copy them, move them, or use them from other apps without explicitly exporting them out of the library.
The Photos library is also a single point of failure. If the library gets corrupted, or if you want to work with your photos in a different tool, you have to export the entire thing—a process that can take hours for a library of fifty thousand images and is also a process that can lose metadata.
~/Pictures- Photo Shoot
- Reference
- Web Exports
- coii-thumbnailswritten by Coii Ref
- coii-proxieswritten by Coii Ref
- coii.dbwritten by Coii Ref
Symptoms and when they appear
You may hit this problem when:
- You want to use a different photo editor to batch-edit your reference photos, but the originals are locked inside Photos and that editor cannot see them.
- You want to back up your photos to an external drive or a cloud service, but you have to export them out of the Photos library manually rather than simply copying your photo folder.
- You switch to a different photo management app and realize that "import from Photos" requires exporting your entire library first, a process that can take days for a large collection and may lose custom metadata.
- You have old photos in Photos and new photos in a regular folder, and you want a single reference manager that can see both. Photos can only see its own library. Other apps can only see the exported versions.
- You delete a photo from Photos by accident and realize you cannot find it by browsing the library folder; you have to recover it from Time Machine.
The severity depends on your library size and how many other apps you work with. A Photos library of one thousand images is easy to export if you ever need to leave. A library of one hundred thousand images is a weekend-long process that may have false starts.
Why this matters for reference workflows
Reference managers exist precisely because raw folders do not scale. But Photos takes the opposite approach: it scales the database (one central library) at the cost of hiding the files.
For a reference workflow, this creates a mismatch. You want your reference images organized and searchable. Photos provides that. But you also want to use reference images with multiple tools—comparing in a color reference app, batch-editing with a script, syncing to another Mac. Photos prevents all of that because other apps cannot see the originals.
A reference manager that worked with Photos' exported copies would be possible, but those copies are disconnected from Photos' metadata. Ratings, keywords, and edits in Photos do not travel to the copies. Any reference system built on top of Photos is building on a disconnected view of your data.
Workarounds within Photos
If you stay in Photos, your options are limited:
Organize in Smart Albums instead of folders. Smart Albums are saved searches that group photos by criteria you set. This does not solve the file access problem, but it can organize your reference library in ways the folder structure alone cannot.
Export to a folder for use with other apps. Before using a photo in another app—a color reference manager, a script, a batch processor—export it from Photos to a working folder. You now have two copies: one in Photos and one elsewhere. Keeping them in sync is a manual process.
Keep originals outside Photos and only import copies. If you store high-resolution originals in a regular folder on disk and import low-resolution proxies or edited versions into Photos, you keep control of the originals. But this requires a file management discipline: every time you acquire a new image, you must save it outside Photos and then import it.
The reality is that none of these allow the seamless integration a reference workflow needs. You either give up file access or you give up Photos' organization.
Why Coii Ref works with your originals
Coii Ref does not import or copy anything. You point it at a folder of images—the same folder where your images already live—and it indexes them in place. The originals stay in the Finder, in your backups, and available to any other app you want to use.
When you tag an image or write notes on it in Coii Ref, that metadata is stored in files Coii Ref writes beside your images—a sidecar database, embedded keywords, or a manifest file in your folder. Other tools cannot read Coii Ref's database, but they can read your original files. Coii Ref cannot prevent another app from using the same images.
The key difference: Coii Ref adds a reference system on top of your existing files, rather than moving the files into its own system. Your files remain files in the Finder. The reference metadata is stored separately and is never the only copy.
This matters because you can use multiple tools on the same image: a color reference manager that reads from the same folder, a backup solution that can see all files, and another Mac that can index the same network share. The metadata from each tool stays independent, but the files are always accessible.
What to check before locking originals in a library
If you are considering switching to Photos or committing your reference library to Photos:
How many other apps do you use on the same images? If you only ever work in Photos and occasionally share images via email, the library system works fine. If you batch-edit with scripts, use specialized color tools, or work with the Finder directly, Photos becomes a bottleneck.
What metadata matters to you? Photos' keywords and ratings are well-supported. Custom descriptions, structured metadata, or metadata created by other apps is lost or complicated when working with an imported library.
How often do you need to leave? Photos' export system gets slower as the library grows. A fifty-thousand-image library that you never leave is fine. A library you export from frequently, or that you might migrate away from in five years, has a higher cost to leaving.
For reference libraries in particular, the inflexibility of the library system is a risk. Reference imagery is often used across projects, compared with other tools, and backed up to multiple systems. A system that hides originals from those workflows is fighting against the work.
Migration path
If you have a Photos library and want to switch to a reference manager that keeps your originals accessible:
Export your entire library from Photos (File > Export). Choose "Unmodified Original" if available, to get the originals without any Photos edits baked in. Choose a folder on your Mac. The export will take time for a large library, but when it is done, you have a folder of original image files in the Finder.
Point Coii Ref at that folder, and every image appears in the reference manager with a searchable database. The originals stay in the Finder, accessible to other tools. Ratings and keywords from Photos do not transfer—that is a limitation of the library export—but every new tag and rating you create in Coii Ref is editable and portable.
You can keep Photos installed and working with the library for anything else you use it for. Coii Ref works with the exported originals, and the two can coexist while you trial the difference in workflow flexibility.
When library-based photo management becomes a cost
Photos is an excellent tool for casual photography: you have hundreds of nice photos, you organize them by date, you search them by keyword occasionally, and you share them with family. The library system is invisible and everything just works. For personal photo collections used only within Photos, the tradeoff makes sense.
Photos is not well-suited to reference workflows where the images are working material, not personal archives. A reference library has different demands: you have thousands of images across many projects, you need to access them from multiple tools, you back them up to multiple systems, and you may migrate to a different manager in the future. In that context, the library system is a constant constraint—not a convenience, but a limitation you work around constantly.
The metadata you create in Photos—ratings, keywords, edits—becomes trapped inside the library. If you ever need that metadata in another tool, exporting is a one-way trip. Changes you make later in Photos do not sync to the other system. Your metadata becomes duplicated and divergent, which is the opposite of organization.
For a reference library of any size, the cost of locking your originals away is higher than the cost of managing files in regular folders. A system that requires you to decide in advance whether files are personal or professional, archive or working material, makes less sense the moment your needs change. And with creative work, they always change.
Coii Ref provides the organization and search you need without that constraint. It works alongside your existing files and tools rather than requiring you to commit your files to a single system in exchange for organization. The organization is portable, the files are portable, and the metadata is portable. You can change tools whenever you want without an expensive export process or metadata loss.
For photographers and designers moving from casual to reference-heavy workflows, understanding the cost of a library system matters. The 30-day trial works with images in folders you already have, adding organization without moving or copying anything. You keep control of the files, the metadata, and the choice of tools.
When you decide you are ready to use a reference system that respects your files, image organizer that doesn't move your files covers the specific advantages of folder-based organization. And best reference apps that don't copy your files shows the full landscape of apps that keep your files accessible.
A reference library is often the first time a photographer or designer needs to work across multiple tools. You might be using color reference software, backup solutions, or simply accessing files from multiple Macs on a shared drive. Does Eagle copy your files explains the storage trade-off one popular competitor makes. And if you are moving a library, reference organizer for motion designers and reference app for concept artists show how different professions structure their reference systems.