Asset
Shadow currently imports common images and videos from Photos or Files. Images include JPEG, PNG, GIF, BMP, TIFF, WebP, and HEIC/HEIF; videos include MP4, MOV, and M4V. Preview support also depends on system codecs.
Guide
Guide
Shadow is a visual asset library for iPhone and iPad. Collect images and videos, organize them with folders, tags, notes, ratings, and colors, and keep working with libraries stored locally, on external storage, or in supported cloud drives. Shadow also supports the Eagle library format, extending desktop collections to mobile.
Quick start
You do not need to understand every compatibility and sync detail before you begin. Complete this small workflow first:
- Open Shadow. Use the built-in default library, or create or open another library.
- Import a few images or a video from Photos or Files.
- Create a folder, move or add assets to it, then add tags and notes.
- Search for a filename, tag, or note, then try color, shape, rating, and format filters.
- After the local workflow makes sense, connect an existing Eagle library or a cloud library in Baidu Netdisk or Google Drive.
Different layouts, nearly the same capabilities
iPhone uses a home screen, collection pages, and a bottom toolbar. iPad uses a sidebar, asset grid, and larger detail panel. Device-specific paths are called out below.
1. Introduction
Shadow is not just a place to pile up files. It keeps assets browsable, searchable, organized, and portable on mobile devices. You can build an independent Shadow library, read and write compatible Eagle libraries, or index a large remote library and fetch thumbnails and originals only when needed.
1.1 Core concepts
Library
A collection of original files and organization data such as folders, tags, notes, ratings, and source links. A project, client, or long-running theme can each have its own library.
Index
The searchable catalog Shadow builds from asset lists, folder relationships, and metadata. Importing a cloud index does not mean every original file has been downloaded.
Cache
Thumbnail or original-file copies stored on the device to speed up cloud browsing. Regular cache cleanup does not delete cloud files, but resetting a local index removes unsynced local change records.
1.2 Relationship to Eagle workflows
Shadow supports Eagle's `.library` directory structure and `.eaglepack` exchange packages. Existing Eagle users can keep high-volume collection and organization on desktop, then use mobile for lookup, presentation, review, and light editing. Everyone else can use Shadow as an independent asset manager.
- Read assets, folder hierarchies, tag groups and tags, notes, ratings, source links, and existing color information.
- Open a complete `.library` from local or external storage, and import or export `.eaglepack` packages.
- When the library is writable, edit names, notes, source links, tags, ratings, and folder assignments.
- Writes aim to preserve Eagle structure, but the format may change between Eagle versions. Back up and validate important libraries first.
Independent product
Shadow is not an official Eagle product. Eagle is mentioned only to describe format compatibility and workflow interoperability. Compatibility is not a substitute for a verified backup.
1.3 What Shadow adds
A real mobile entry point
Dedicated iPhone and iPad layouts support quick lookup, on-site selection, client presentations, and relaxed review away from a desk.
No Eagle prerequisite
Create and manage libraries entirely inside Shadow. Eagle support is a compatibility feature, not an onboarding requirement.
On-demand access to large libraries
Cloud libraries index structure first, then cache thumbnails and originals as needed instead of filling the device with the entire library.
2. Asset sources
“Source” can mean where the library lives or where new assets come from. Choose the library location first, then choose an import method.
| Library source | Best for | Main behavior | Watch for |
|---|---|---|---|
| Default Shadow library | First use, quick collection, reliable offline access | Managed by the app and always kept in the library list | Uses device storage; export backups regularly |
| Local or external storage | New standalone libraries, existing `.library` packages, large external drives | Stable access and direct full-library writes | Do not disconnect during reads or writes; confirm the volume is writable |
| Baidu Netdisk | Cross-device access, large libraries, originals on demand | Imports an index first, caches thumbnails and originals as needed, syncs manually | Depends on networking, the provider account authorization, and provider APIs |
| Google Drive | Cross-device access, large libraries, originals on demand | Imports an index first, caches thumbnails and originals as needed, syncs manually | Depends on networking, the provider account authorization, and provider APIs |
Ways to add content to the current library
- Photos: choose images or videos from the system photo library.
- Files: choose supported images or videos, or import a local folder in bulk.
- Cloud: choose assets or a folder from connected Baidu Netdisk or Google Drive storage; large jobs show import progress.
- Eaglepack: import a `.eaglepack` and merge its assets and folder structure into the current library.
Importing means copying content into the current library and building searchable records, not merely opening a file. Bulk imports, cloud downloads, and indexing can take time.
3. Features and operations
3.1 Create and open libraries
Create a local library:
- Open the library menu and choose to create a library.
- Choose the local source, enter a recognizable name, and select a location in the system file picker.
- Open the new empty library, then add assets or folders.
Create a cloud library: choose Baidu Netdisk or Google Drive and a remote location. Shadow first creates an editable local working copy; the remote library is created on the first manual sync, and later changes are published the same way.
Open an existing local library:
- Choose to open a library, then choose the local source.
- Select the complete `.library` package in Files. Do not enter the package and select only `metadata.json` or the `images` folder.
- Wait while Shadow reads the structure and builds an index. The first load of a large library takes longer than later visits.
Import an existing cloud library: connect Baidu Netdisk or Google Drive, select the complete `.library` directory containing `metadata.json` and `images` in Shadow's cloud browser, and start the import. Before it begins, choose whether Shadow should open the library automatically after the import finishes. An incomplete library shows a resume-index-import action in the library list.
Library list actions
Switch, update, or rename libraries from the list. Local libraries can also export assets or a complete `.library`. Removing a library from the list removes only Shadow's saved entry, not the files at their original location. The default library cannot be removed.
3.2 Add assets
- Open the target library and folder. Create a folder first if needed.
- Use the add button and choose Photos, Files, Import Folder, or Import Eaglepack.
- Complete the system or cloud selection and watch the in-app import progress.
- Review any failure message. Cloud folder imports may partially succeed, allowing the remaining items to be retried.
An asset imported into a folder still belongs to the whole library; the folder is an assignment. One asset may belong to multiple folders. “Move to” replaces existing folder assignments, while “Add to” keeps them and adds more.
Do not force-quit during an import
Shadow can keep showing an active task inside the app, but iOS does not guarantee that work continues after a force-quit. For large imports, use stable networking and power, and wait for a clear completion state.
3.3 Browse and inspect assets
iPhone
The home screen shows All Assets, quick categories, folders, and Trash. In a collection, use Browse Tools for filters and Search for lookup. Tap an asset for a full-screen detail view.
iPad
The sidebar groups All Assets, Favorites, Tags, folders, Uncategorized, and Trash. The main area is an asset grid, and the detail view uses the larger screen for preview and metadata together.
- Grid: browse thumbnails by folder or quick category. First-time cloud thumbnails need a connection.
- Detail preview: view images or play video. Images support preview zoom, pan, and rotation, plus previous/next navigation.
- Information: inspect name, dimensions, format, tags, folders, rating, notes, source link, and colors.
- Share and save: use the system share sheet or save to Photos when allowed. Cloud originals are downloaded to local cache first.
- Favorites: a fast local shortcut on the current device. Favorites are stored in Shadow preferences, are not written to Eagle metadata, and do not automatically sync to another device.
3.4 Search and filter
Keyword search matches the asset name, original filename, tags, and notes. On iPhone, search either the whole library or the current collection.
| Condition | Purpose | Tip |
|---|---|---|
| Keyword | Find names, tags, or note text | Start with a short, specific term |
| Tags | Filter by subject, use, project, or style | Multiple tags usually narrow the result |
| Color | Find images with a similar dominant color | Pick a color or enter Hex, then adjust match accuracy |
| Shape | Show landscape, portrait, or square assets | Useful for layout and aspect-ratio selection |
| Rating | Show assets at or above a star level, or unrated assets | Star filters use a minimum rating |
| Format | Show selected image or video extensions | The list comes from the current library |
Recommended order: confirm the scope, enter a keyword, then add one or two filters. If nothing remains, clear all conditions and restore them one at a time to identify the over-restrictive filter.
3.5 Organize and edit
- Single asset: edit its name, notes, source link, tags, rating, and folders in the detail view. Changes auto-save after a short pause; check save status before leaving.
- Batch selection: long-press or enter selection mode to move, add to more folders, add tags, favorite, export, or move items to Trash.
- Folder management: create, rename, reorder, and change hierarchy. Confirm where contained assets should end up before deletion or restructuring.
- Tag management: create tag groups and tags and maintain existing names. Uncategorized tags come from assets themselves; an empty uncategorized tag cannot exist independently.
- Trash: normal deletion moves assets to Trash. Reassign folders to restore them. Emptying Trash permanently deletes its contents and cannot be undone.
If a library is not writable or its cloud state makes a write unsafe, editing is disabled or Shadow asks you to resolve sync first. Do not edit the internal library structure in Files at the same time.
3.6 Backup, export, and sync
Complete library backup
Export a complete local `.library` with originals and organization data. Use it for migration, archiving, or a restore point before important changes.
Originals or Eaglepack
Export selected original files or package selected assets as `.eaglepack` for compatible workflows. Bulk cloud export may depend on cached files and current capabilities.
Cloud sync
Sync publishes local changes to remote storage. Update Library reads remote changes and rebuilds the local index. They are opposite directions, not interchangeable actions.
- Keep at least one recoverable, separately stored, verified backup of an important library.
- Do not disconnect external storage during writes, or edit on another device before cloud sync completes.
- Before writing to an established Eagle library for the first time, test a small copy and verify it on desktop.
4. Cloud library details
4.1 Why cloud libraries exist
Cloud libraries are not only a way to save device storage; they are also an effective foundation for managing one library across devices. The remote library becomes the shared source, while explicit Sync and Update Library actions control direction so iPhone, iPad, and desktop sessions can hand work off in sequence.
Cross-device consistency
After editing on the current device, Sync publishes local changes to the cloud. Before another device begins work, Update Library reads the newest remote state. This is not invisible real-time bidirectional sync; it is a directional workflow with conflict checks.
On-demand access for large libraries
Shadow separates remote access into index, thumbnail, and original layers. A small index establishes folders and search first, thumbnails arrive as you browse, and an original downloads only when you view, share, or edit that asset.
Different from a mounted drive or synced cloud folder
Eagle and many asset managers can open libraries stored in iCloud, a synced cloud folder, or a mounted drive. This is a mature and direct desktop workflow in which the operating system or drive client makes local files available to the app. Shadow takes a different approach for mobile devices: it builds a cloud index through the provider API and downloads thumbnails and originals on demand, without requiring the whole library to land on the device first. Shadow still keeps a necessary local index and caches accessed content; originals needed offline must be cached in advance.
Why Shadow connects directly to cloud storage
Direct Baidu Netdisk and Google Drive connections let Shadow control both what is downloaded and how changes are synchronized. Indexes, thumbnails, and originals use separate cache layers whose storage can be inspected and cleared. Changes to tags, folders, metadata, and asset files are written back as library operations. Another device can then use Update Library to read those remote changes and rebuild its local index.
The cloud library therefore remains interoperable with compatible desktop workflows while becoming an on-demand, editable, and updatable mobile library on iPhone and iPad. This is not invisible real-time background sync: explicit Sync and Update Library actions control direction, report progress, and check for potential conflicts.
4.2 Supported providers
- Baidu Netdisk: currently available for authorization, native directory browsing, cloud library creation or selection, index import, on-demand caching, and manual sync.
- Google Drive: currently available for authorization, native directory browsing, cloud library creation or selection, index import, on-demand caching, and manual sync.
When you connect Baidu Netdisk or Google Drive, Shadow uses the authorization scope you grant to browse the root, locate an existing `.library`, read its descendant files, and create or synchronize library content. This access is used only for library actions initiated by the user, and files are not transferred to a Shadow-operated server.
4.3 Import, update, sync, and consistency
| Action | Direction | Use it when |
|---|---|---|
| Import | Cloud → local index | Connecting a remote library for the first time |
| Update Library | Cloud → local index | Another device changed the remote library and Shadow needs the latest state |
| Sync | Local changes → cloud | Publishing edits made in Shadow back to the drive |
Shadow is not a real-time bidirectional sync drive. Before syncing it checks local changes, remote state, and potential conflicts. If remote content changed during local work, Shadow may ask you to keep the cloud version or continue with the local version. When a plan contains remote deletion or structure operations that the current version cannot safely perform, follow the sync preview and warning.
Sync before updating
Update Library may be blocked while unsynced local edits exist, preventing a remote index from overwriting local work. Sync or resolve the conflict first, then read the new remote state.
4.4 Cache management
Adjust the original-file cache under Settings → Cloud Original Cache Limit. The default is 10 GB. This limit controls device usage, not the total cloud-library size. A cloud library's cache screen also reports and clears indexes, thumbnails, and originals separately.
- Clear originals: keeps the index, metadata, and thumbnails. Full assets download again when opened.
- Clear thumbnails: keeps the index and cached originals. Grids and covers fetch or regenerate thumbnails.
- Reset local index: removes the device index, mirror, sync state, and caches, then requires a new import. It also clears unsynced local change records, so confirm first.
Regular cache cleanup does not delete remote Netdisk files. If space is the problem, clear originals first. Reset the index only after repeated index failures and after confirming that no unsynced edits remain.
4.5 Recommended multi-device workflow
- Choose one device as the current editor; keep other devices in browse-only use.
- Complete a small, coherent set of edits, such as one folder or one batch of tags.
- Review the sync plan in Shadow and finish sync. Wait for an explicit success state.
- If desktop uses a cloud-drive client, wait for that client to finish before opening the library in Eagle.
- On another iPhone or iPad, run Update Library before beginning the next editing session.
The safest rule is “one writer, finish sync, then update elsewhere.” Do not let Eagle, two Shadow devices, and a drive client all modify the same library simultaneously.
5. Troubleshooting
A library will not open or appears empty
Select the complete `.library` directory containing valid `metadata.json` and `images` entries. Check external storage connection, path changes, and permissions. For cloud libraries, confirm authorization and resume cloud index import from the library list if needed.
First import is slow or progress appears stuck
Large libraries require metadata traversal and indexing; Baidu Netdisk and Google Drive both depend on networking and provider API availability. Keep Shadow in the foreground with stable networking and power. Retry a reported failure, but do not repeatedly reset the index.
Thumbnails are blank or an original keeps loading
Check the connection and confirm that the corresponding Baidu Netdisk or Google Drive account is still authorized. First display may download or generate cache. Retry the detail view. For a single failure, verify the remote file still exists; for persistent whole-library issues, clear thumbnail cache before considering an index reset.
Search cannot find an asset that exists
Keywords match names, original filenames, tags, and notes. Confirm the search scope, then clear color, tag, shape, rating, and format filters. Update the cloud index if another device made the change.
Editing is disabled or a change will not save
Check write permission, read-only external storage, and unresolved cloud sync state. Detail fields use delayed auto-save; pause briefly and check save status before leaving.
Favorites do not appear on another device
Favorites are a device-local Shadow shortcut and are not Eagle metadata. For cross-device organization, use folders, tags, or ratings.
Sync fails or reports a conflict
Stop editing elsewhere, restore connectivity, and retry so completed work remains. Choose the latest trusted cloud or local copy when resolving a conflict. If uncertain, create a recoverable copy before deciding.
The cache uses too much storage
Lower the cloud original cache limit in Settings or clear originals for the affected library. This preserves the index and remote files; full assets download again next time.
How should I report a problem?
Visit Support and include the Shadow version, iOS/iPadOS version, device model, library source and approximate size, cloud usage, exact steps, error text, and screenshots. Do not send private original files.