Storage Structure

An asset library on a local disk is composed of original resource files and essential management metadata folders. Understanding the physical layout of the library helps you better perform tasks such as backup, migration, and team collaboration.

Standard Directory Layout

Library Root (LibraryRoot)/
├── assets/            # Original resources (contains .png, .spine, .fbx, etc.)
├── assetlib.db        # Core database (stores unique ID, version, tags, and notes)
└── thumbnails/        # Thumbnail cache (stores automatically generated visual previews)

Core Component Description

1. Asset Database (assetlib.db)

The "brain" of the asset library, using the lightweight SQLite format. Its core responsibilities include:

• Metadata Storage: Records tags, notes, resolutions, and other non-physical attribute information for all files.
• Library ID (lib_guid): The "digital ID card" of the asset library, used for identity verification during cross-software navigation.
• Compatibility Version (lib_version): Identifies database compatibility, ensuring the data structure matches the current app version.

2. Thumbnail Cache (thumbnails/)

This directory stores various asset snapshots automatically generated by the system to provide an instantaneous browsing experience.

• Physical Path Alignment: The internal storage logic of thumbnails remains completely consistent with the physical hierarchy of the assets/ directory.
  • Example: If an original resource path is assets/UI/logo.png, its corresponding cache file will be stored at thumbnails/UI/logo.png.
• Transparent Maintenance: This mirrored design allows you to intuitively locate cache data for specific folders and significantly facilitates operations when configuring SVN ignore items or performing partial backups.

---

CAUTION

Risk Warning: Do not manually move, rename, or directly modify the assetlib.db file. Any illegal external modifications may result in the asset library not being recognized by the software or lead to metadata loss.