Eagle Doubles Your Disk Space: Why, and What to Do (2026)

By refern. Last updated: June 2026.

Eagle doubles your disk space because it copies every imported file into a proprietary .library folder. This is a design choice, not a bug. Your originals stay wherever they were, and Eagle stores a second full copy inside the library. For every 100 GB of references you import, you use 200 GB of disk.

This page explains exactly why this happens, what you can and cannot do about it inside Eagle, and how to avoid the problem structurally if you are willing to consider a different tool.

Why Eagle Copies Your Files

Eagle uses a self-contained .library folder to store everything it manages: your files, metadata, thumbnails, and its own database. When you drag an image into Eagle, import a folder, or save via the browser extension, Eagle physically copies each file into that folder.

Eagle's own support documentation acknowledges this is a common source of confusion, noting a FAQ entry specifically titled "Why does the Eagle library take up more disk space than the actual files?" [AlternativeTo user feedback and Eagle support materials confirm this is the top structural complaint among users.]

The reason Eagle copies rather than links is deliberate. Eagle was designed to be a portable, self-contained library you can move as a single folder. Keeping everything inside .library means the library is always complete and self-referencing. If originals were stored elsewhere, moving the library would break the links to those files.

This is a reasonable trade-off for some workflows. For others, especially those with large collections already organized in folders, or those working from external drives or project directories, it creates a disk usage problem that compounds every time new files are added.

What You Can (and Cannot) Do About It Inside Eagle

Eagle does not offer a non-copying mode, but there are ways to manage the footprint.

Option 1: Delete the originals after importing

Once Eagle has copied a file into its library, you can delete the original. Eagle holds the only copy and you reclaim the space the original occupied. The library becomes your primary storage.

This works if you are comfortable with Eagle being the single source of truth for those files. The downside: your files are now inside Eagle's proprietary .library format. If you ever stop using Eagle, you need to export files back out. Eagle does support export, but the extra step adds friction you would not have with a tool that never touched your originals.

Option 2: Use Eagle's move mode on import

Eagle offers both copy and move on import. Move relocates the original file into the library folder rather than duplicating it. Total disk usage does not increase, because the original is gone from its starting location.

The downside is the same as Option 1: your files are now inside Eagle's library format, inaccessible through your normal folder structure without going through Eagle.

Option 3: Store the Eagle library on a separate drive

You can point your Eagle library at a secondary drive so the duplicates do not eat your primary SSD. Eagle lets you choose the library location when creating a new library.

This keeps the doubling off your main disk, but you are still storing duplicates. If the secondary drive is slower, Eagle's thumbnail and search performance may degrade.

Option 4: Import selectively, not comprehensively

Import only the assets you are actively using in Eagle and keep the rest outside it. This limits disk growth but also limits what Eagle can search and organize, which undercuts the reason to use it in the first place.

What Eagle cannot do

Eagle does not have a mode that indexes your existing files in place without copying or moving them. The library copy model is fundamental to how Eagle works, and Eagle's documentation describes it as "the safest approach" for library integrity. This is not expected to change.

The Structural Fix: Use a Tool That Indexes in Place

If you do not want your disk space doubled, the real solution is a tool that reads your existing folder without touching your files.

refern is a local-first desktop reference manager for artists that indexes files in place. When you open a folder as a workspace in refern, it builds a local SQLite index and stores only small WebP thumbnails in a refern-thumbnails/ subfolder. A refern-db.sqlite sidecar file holds all the metadata. Your original files are never moved, never copied, and never locked into a proprietary format.

Eagle is genuinely strong in areas refern does not match: font management, 99 to 108 file format previews, a mature plugin ecosystem, and AI auto-tagging via its AI Action plugin. If those features matter more to you than disk efficiency, Eagle may still be the right choice even with the disk duplication. The table above is a fair picture of both sides.

How refern Works Without Copying Files

When you create a workspace in refern, you point it at an existing folder on your disk. That folder can be your Lightroom exports folder, a project directory, an external drive, or any folder structure you have already built.

refern scans the folder, builds a fast SQLite + FTS5 full-text search index, and stores small WebP thumbnails in a refern-thumbnails/ subfolder inside your workspace. A refern-db.sqlite sidecar file holds all the metadata. Your original files are not touched. They stay in exactly the same place, with the same filenames, accessible to any other application.

The result: a searchable library with 14-plus search operators, color search by hex, local image-to-image visual similarity search, duplicate detection, hierarchical tags, ratings, smart folders, and a relationship graph view, all without duplicating a single byte of your originals.

One user with 27,000 images confirmed the library runs smoothly. refern's streaming indexer is designed to scale without loading everything into memory at once.

What Else Is Different About refern

Fixing the disk duplication problem is the main reason this page exists, but there are two other gaps that Eagle users frequently hit.

Infinite canvas. Eagle has no canvas or moodboard mode [Eagle dossier, confirmed]. refern includes an infinite canvas with layers, groups, text, shapes, freehand drawing, non-destructive image crop, and a pin-on-top overlay mode that replicates the PureRef workflow. You can drag directly from your library onto a canvas without switching applications.

Relationship graph view. Eagle has no way to visualize connections between files [Eagle dossier, confirmed]. refern tracks typed links between images, canvases, folders, and groups, and surfaces them in a navigable graph view. This is useful for artists who want to trace where a reference came from, which canvases it appears on, or how sets of related images cluster together.

These are real shipped features in refern, not roadmap items. They are not the solution to the disk problem on their own, but they are worth knowing about if you are evaluating alternatives.

Migrating from Eagle to refern

refern includes a built-in Eagle importer. It reads your Eagle library folders, tags, ratings, source URLs, and notes. After import, your files are indexed in place in a refern workspace without being copied again.

If Eagle made copies of your originals and you want to reclaim the space from those copies, you can safely delete the Eagle .library folder after confirming your files are fully indexed in refern. Your originals are untouched by the migration process.

For a full walkthrough, see the guide to migrating from Eagle to refern.