Your pictures are there twice when you use Eagle

Eagle's workflow is import-based: you point it at a folder, and it copies every image into its own library structure. That move buys you a single, portable database that stays consistent — you do not have to hunt across your whole drive to find everything you rated and tagged. The cost is that your disk now holds two complete copies of the same collection. Import a fifty-gigabyte reference library, and you need another fifty gigabytes to hold the Eagle copy. That duplication is not a bug; it is how Eagle works.

The cause: import, not index

Most reference managers that exist in 2026 take the import path. Your files arrive from somewhere, the app copies them into a central library, and thereafter the app is the source of truth about what you have. That design gives you:

• A single, consistent library you can back up as one unit
• Files organised into the app's folder structure instead of yours
• Guaranteed that every file in the database actually exists in the library (no orphaned records)

It also guarantees you have two copies of everything the moment you import. An app cannot simultaneously store files in a folder it controls and leave them where they were. One or the other is the original, and the other is a copy.

Coii Ref uses the index path instead: it points at the folders you already have, reads what is there, and never moves or renames a file. The database lives beside your files in the workspace folder, not replacing them. The folders stay yours. The app records what it has read — dimensions, EXIF, colour, the tags you gave it — but the files themselves are untouched, so you still have one copy of the collection, not two.

How to reclaim the disk space

If your Eagle library has grown too large, you have three options.

Keep the library and delete the originals. If you imported from a single source folder and you trust the import was complete, you can delete the originals and reclaim half the space. The Eagle library becomes your only copy, which means you have lost the independence to open a file in another app without exporting. It also means if you ever want to leave Eagle, the export step is mandatory. But the space saving is immediate.

Export everything and delete the library. Select all, export to a folder — most reference managers can do this — and the original files are reconstructed on disk. Then delete the Eagle library folder. You get back one copy worth of space, and your files return to normal Finder organisation, but the process is slow and the files may be renamed or reordered depending on the export options.

Copy the library to external storage. If your internal drive is full but you have external storage, a large library can live there. The overhead is slower access times (external drives and fast external SSDs are still slower than internal) and the risk that the drive is not connected when you want to use the app. For archival storage of a library you do not use every day, it is a valid trade.

How to avoid it going forward

The fundamental insight: a reference manager that copies files is always going to double your storage burden. That is not a failing of Eagle specifically; it is a consequence of the import design every large reference manager except Coii Ref has chosen. Eagle does it honestly — the library is there, the files are there, the duplication is real — whereas some apps hide the copy in cloud storage or charge you for it by subscription.

If storage is a constraint for you, an index-based manager like Coii Ref saves space at the cost of more constraints: you have to manage the folders yourself, and moving a file in Finder is moving a file in the database too. For a collection that lives on four external drives, that flexibility is the whole point. For one that is tidied up regularly and lives in one place, it is overhead. The trade is real.

Alternatively: until a collection reaches the point where clicking through a folder stops working — usually somewhere north of ten thousand images — Finder alone costs nothing, takes no duplicate space, and is honest about what it does.

If you are coming from another import-based app with a large library, the migration to Coii Ref is slowest on the first index pass (a fifty-thousand-image folder can take an hour) but it saves gigabytes permanently. The indexed files stay where they are. The ratings, tags and notes travel across via the importer by matching relative paths. Then you keep or delete the original app's library folder depending on whether you trust the migration is complete. If you run both in parallel for a week first, the answer is usually clear.

The honest complexity: index-based management is newer and less familiar in this category, so the learning curve is real. A Coii Ref workspace is more portable than a traditional library — copy the folder to another drive and everything works — but you have to think of it as a unit to back up, not as something the app takes care of. If you already think of your reference library as a folder that belongs to you and lives in your backup system, the switch is straightforward. If you think of it as something the app manages, the mental model is inverted, and it is worth trialling before you commit.

Why the import-based design persists

You might wonder why every other reference manager chose the import path if it has this obvious cost. The answer is that there are real benefits to it: a central, curated library is simpler to understand. You know exactly what you have because the app is the single source of truth. Files arrive from unpredictable places — Downloads, emails, the browser, a phone — and the app gives them a home. For users who think of their reference library as something the app manages rather than a folder they happen to point it at, that centralization is the whole point.

The flip side: if you already have folders and you want to search inside them without the app adopting them, you are out of luck. If you have terabytes of references across external drives that you do not want to consolidate, the app will require space for copies. If you want to back up your library alongside your files and let the backup system take care of it, the duplication means twice the storage to restore.

Coii Ref is betting that a growing number of users fall into that second group — people who have come to prefer local folders and version control systems and who understand that a workspace is a thing they back up as a unit. If you were already using folders before you started collecting references, the switch is straightforward.

A worked example: migrating a 40 GB library

A typical scenario: you have been using Eagle for three years. Your reference collection has grown to 40 GB across multiple external drives. You are ready to try a different approach.

In Coii Ref, you would not migrate it all to one place. Instead, you would create a separate workspace for each drive. Point Coii Ref at the first drive's reference folder, let it index (take a coffee break; forty thousand images take time), then repeat for the other drives. Your tags, ratings and notes come across from the Eagle importer by path matching, and you can run both apps for a week to verify nothing was lost. Once you are confident, you delete the Eagle library folder and reclaim forty gigabytes.

The storage saving is permanent: one ten-gigabyte drive is three gigabytes of Coii Ref index plus seven gigabytes of originals, not the twenty gigabytes you were paying before (ten for originals, ten for the Eagle library copy).

If you decide to go back, your originals are still on disk, and the Eagle library can still be read if you kept it. You have not locked yourself in. That is the fundamental design difference: Coii Ref cannot trap you the way an import-based library can, because the files were never in its hands to begin with.

The long-term math on duplicated storage

A fifty-thousand-image library is substantial. If each image is one megabyte on average (a reasonable estimate for photographs at web resolution), the originals weigh fifty gigabytes. The Eagle copy is another fifty gigabytes. That is one hundred gigabytes of total storage consumed for one conceptual library. If you have that much content, your drives are probably expensive, and dedicating half of that expensive real estate to duplication is a meaningful cost.

For a Coii Ref workspace, the same fifty thousand images need the fifty gigabytes for originals, plus roughly three to five gigabytes for the database, thumbnails and canvas proxies, depending on image resolution and whether video is involved. That is fifty-five to fifty-five gigabytes for the complete workspace. The savings are permanent and grow with every image you add.

This is also where external storage architecture makes a difference. If you keep your references on four two-terabyte external drives scattered across your desk, studio and office, Coii Ref's per-workspace design suits you better than Eagle's centralised approach. Each drive gets a Coii Ref workspace, and each workspace stays independent. A backup of one drive backs up the complete reference library on that drive. Moving a drive to another Mac or to cold storage for archival requires no export process — it just works because the workspace is a folder.

Eagle would require consolidating those four drives into one space, or creating four separate Eagle libraries and managing them as separate entities with no cross-library search. For workflows that already think in terms of drives and folders, that is a regression.

The bottom line is straightforward: if storage is limited and you have a large reference library, the duplication is a real cost you pay every month for the life of the library.

Also worth checking: what happens to your library if the app shuts down, and the comparison with refern if you are considering other apps — refern's import process has different trade-offs. And best reference apps that don't copy your files covers the full landscape of index-based managers if you want options.

Otherwise: the comparison is longer. Does Eagle copy your files answers the question directly. The 30-day trial comes with every feature and no card required. If storage is the problem, an app that does not duplicate files is worth an evening.