PureRef and an Organizer in One App: When to Consolidate

Keep two apps when you genuinely benefit from each specialist: PureRef for the active reference board and Eagle, Allusion, or another manager for the library. Consolidate when repeatedly moving images between the library and board has become the problem. refern combines both surfaces in one connected desktop workspace.

The goal is not to eliminate a tool for its own sake. It is to remove a handoff only when the handoff costs more than the specialist advantages.

Why the two-app workflow exists

PureRef and Eagle solve different jobs.

PureRef is a focused spatial board. It offers groups and hierarchy, names, notes, comments, drawing tools, image controls, and a polished always-on-top workflow. PureRef Personal can cost $0 for non-commercial use, so it is difficult to beat when a board is all you need.

Eagle is a managed creative-asset library. It centers folders, tags, ratings, search, broad previews, and plugins rather than a PureRef-style spatial overlay.

Allusion is another library-side option. It displays images from watched folders and adds hierarchical tags and combined search filters. Its latest official release is 1.0.0-rc.10 from February 2023, so current-system compatibility should be tested. The old release date is a concern, not proof that every build is unusable.

The split is rational:

• PureRef answers “what should stay visible while I work?”
• A library manager answers “where is the reference I saved before?”
• Two apps preserve each product's focused interaction model.

What the handoff costs

The dual-app setup becomes friction when:

• Library metadata and board structure do not travel together.
• You repeatedly search in one app and arrange in another.
• The same reference exists in multiple project boards without a reusable library relationship.
• Backup and storage rules differ between the library and scene files.
• You cannot easily answer which boards use a particular image.

None of these makes a two-app setup inherently bad. If the handoff is rare, or Eagle's preview breadth and PureRef's exact canvas feel both matter, keeping both is a sound decision.

File handling is different in each app

Older comparisons often flatten the storage differences into inaccurate slogans. The current boundaries are:

Eagle: imported media is copied into an Eagle-managed library. If source originals are retained, the media exists in both locations. Total storage is not always an exact two-times multiple because generated data and later source-file handling also matter.

PureRef: scenes are saved as .pur files. Local images are embedded by default, but PureRef 2.x can link them to existing disk paths. Its default documented performance mode caches image data on disk.

Allusion: watched-folder setup uses images at their existing paths. It is not universally read-only because a user-initiated metadata export can overwrite existing file keywords.

refern: a normal workspace indexes existing files in place. Explicit imports and copy actions can create files. The workspace keeps a SQLite catalog and generated thumbnails in an associated data location, which can be configured.

How refern connects the library and canvas

refern's library supports folders, hierarchical tags, ratings, descriptions, source URLs, saved searches, color and visual-similarity retrieval, duplicate detection, and browser capture for Chrome, Firefox, and Safari.

Its infinite canvas supports layers and groups, text, shapes, drawing, crop, image adjustments, pin-to-top, window transparency, and mouse clickthrough. Images placed on a canvas remain connected to their library entries, and relationships can link images, folders, groups, and canvases.

That connection is the practical reason to consolidate. The same item can be found through the library, arranged spatially, and traced back from a canvas without exporting it to a separate board system.

Core library, canvas, search, viewing, and study workflows keep the working library local. Some explicit actions use the internet, including license activation, updates, optional model downloads, feedback, web capture, and PureRef imports with web sources. Describe this as a scoped local-first boundary rather than as complete network independence.

Where PureRef and Eagle still win

PureRef remains the better choice when:

• You want the most focused board workflow.
• Personal non-commercial cost needs to be $0.
• Existing keybindings and canvas habits are valuable.
• Scene-level organization is enough.

Eagle remains the better choice when:

• Broad creative-file preview coverage is essential.
• Font workflows or plugins are part of the pipeline.
• A managed-copy library fits the team's storage and backup process.
• You do not need Linux or an integrated canvas.

refern is newer and has a smaller community. It does not match Eagle's preview breadth or plugins, and it does not yet offer cloud sync, collaboration, mobile access, or a plugin ecosystem. Consolidation should be based on the connected workflow, not on pretending those differences do not exist.

Migration boundaries

From Eagle

refern's Eagle importer has full parity across its supported transfer surface: supported nested folders, folder metadata, item tags, ratings, source fields, annotations, comments, media, and repeated placements.

It copies the first media placement and creates linked database placements for later locations of the same item. Password locks, saved smart-folder rules, arbitrary plugin-owned data, and unsupported media are outside the supported surface. Keep the source Eagle library as a backup while checking the result.

From PureRef

In refern 1.7.0, the importer rebuilds PureRef 2.x boards, including 2.1.3 boards, as editable canvases. The board's core content, layout, and positions transfer correctly, including supported images, notes, drawings, groups, nested placement, transforms, scale, visible group containers, and note fills.

Small property-model differences remain:

• Separate text-run and container backgrounds map to one refern text-container background.
• Font families map to refern's canvas typeface.
• Rich-text runs convert to the closest supported styling.
• Note-background alpha is not preserved.
• Irregular crops can become axis-aligned bounding boxes.

Eligible local sources already in the destination workspace can be reused. External local sources are copied, and web sources are downloaded. The owner describes overall fidelity as approximately 90 percent, but this is a qualitative estimate rather than a weighted benchmark.

When to consolidate

Consolidate if:

• Moving references between the library and board happens throughout the day.
• Cross-project search, tags, and source tracking matter.
• You want canvas placements connected to their library entries.
• Normal in-place workspace indexing fits your file organization.
• Image and video references are the core asset types.

Keep the specialists if:

• PureRef's exact board interaction is important.
• Eagle's previews, fonts, or plugins are essential.
• A $0 personal setup is the priority.
• Your boards are temporary and the library-to-canvas handoff is rare.

Next step

If the handoff between library and canvas is your recurring problem, test the full workflow during refern's 30-day trial. The license costs $35 one-time, and updates are currently included.

See refern vs PureRef, refern vs Eagle, and how to migrate from PureRef.