Documentation — Install, migrate, verify

Requirements

• Blender 4.2 or newer.
• Permission to write backup files.
• Access to the original Asset Library folders, or a copy.
• A restart after restoring add-ons, preferences or startup files.

Installation

1. Download the extension ZIP — do not extract it.
2. Edit → Preferences → Get Extensions.
3. Extensions menu → Install from Disk → pick the ZIP.
4. Enable it if Blender doesn't, then press N → AssetLib tab.

Source machine

1. Install or update the add-on, open the AssetLib panel.
2. Confirm the registered libraries are correct.
3. Export Settings — libraries, and repositories if needed.
4. Include tokens only if you accept the risk.
5. Create add-on and preference backups.
6. Optionally back up the startup file, then copy everything across.

Destination machine

1. Install the add-on; connect or copy the asset folders.
2. Import library and repository settings.
3. Review missing paths and remap prefixes.
4. Restore add-on files → restart Blender.
5. Restore preferences → restart again.
6. Optionally restore the startup file, restart, then verify.

D:\Asset Library\Models   →  G:\Asset Library\Models
D:\Asset Library\Materials →  G:\Asset Library\Materials
D:\Asset Library\HDRIs    →  G:\Asset Library\HDRIs

Export Settings

Per library: name, path, import method, relative-path and enabled state. Per user-managed repository: name, module ID, remote URL, custom directory, enabled state, cache, startup sync, remote state and token usage.

Import Settings

Libraries match by name — existing entries update, missing ones are created. Repositories match on module ID, normalised remote URL, then name, which avoids duplicates. System-managed repositories are skipped. Old AssetLib-EXP-IMP and unversioned backups are normalised in memory; unknown newer formats are rejected before any change.

Access tokens are plain text

Token export is off by default. When enabled, the token is written into the JSON as readable text and may act as a bearer credential — protect that file like a password. Never commit it to a public repository, unsecured cloud folder or public support request. A migrated token may still expire, be revoked, or need renewed marketplace authentication.

.addonbackup

Add-on files

Includes user legacy add-ons, Extensions and recognised repository directories. Excludes this add-on, caches, hidden metadata and Blender’s bundled system extensions. Restore repositories first, then add-ons, then restart. Files only — not their preferences.

.prefbackup

Preferences

Contains userpref.blend: interface, themes, keymaps, input, file paths, library registrations, enabled add-ons and their preferences. Restoring writes userpref.before_restore_….blend first and takes effect after a restart.

.startupbackup — experimental

Startup file

Enable it in the add-on preferences to reveal the panel section. Save your defaults via File → Defaults → Save Startup File first. The archive is validated, a timestamped copy kept, and the restored file loads on the next launch — never over your open scene.

Older → newer Blender

The intended direction. Files and settings transfer, but the tool cannot rewrite an older add-on for a newer Python API — get a destination-compatible build from its developer where possible.

Newer → older Blender

Not recommended, and a newer userpref.blend is blocked outright. Settings JSON may still import, but individual properties are restored only where the destination Blender exposes them.

Asset availability

Registrations migrate, collections don’t. If the drive or share is offline, Blender keeps the registration but the library can’t be browsed until the files are reachable.