Remote Asset Libraries let Blender discover assets stored on remote servers and download them only when needed. This enables integrated support for online asset services, better sharing of libraries, and an extended Essentials library while keeping Blender fully usable offline.
This is an important step towards the long-term goals of Blender’s asset system: providing a richer out-of-the-box experience and a common asset sharing workflow, where online asset services integrate directly into Blender’s built-in asset features, instead of every add-on implementing its own.
Using Remote Asset Libraries
Refer to the Blender Manual for instructions on how to use remote asset libraries. Note that using remote asset libraries requires Allow Internet Access to be enabled in the Preferences.
When internet access is enabled, the remote assets listings will automatically be updated once per day.
Hosting Remote Asset Libraries
Self-hosting remote asset libraries is simple and doesn’t require much technical knowledge. This allows small teams and individuals to share their libraries remotely. A guide on this can be found in the Blender Manual too.
Online Essentials
Blender already ships with the Essentials asset library, providing the brushes, node groups and other assets needed for a good out-of-the-box experience. Because they ship with Blender, however, their size has to remain modest.
Remote assets remove that limitation. Blender 5.2 LTS expands the Essentials library with optional online content including base meshes, materials, high-resolution HDRIs, compositing effects and more, without increasing Blender’s download size.
Offline-Mode Stays as First-Class Citizen
Internet access should never be required to use Blender. Remote asset libraries are an optional extension, while the bundled Essentials assets continue to be improved and expanded.
Disabling Allow Internet Access disables all remote asset libraries. Asset Browsers and Asset Shelves also provide an Offline Only filter to show only locally available assets. To make a remote library available offline, open it in the Asset Browser, press A to select all assets, then choose Download Assets from the context menu. Once downloaded, assets can be accessed fully offline too, even with Allow Internet Access disabled.
(Almost) No Curating Required
The system was built so that any directory containing assets can be processed by the remote listing generator and uploaded directly, without requiring special preparation.
Currently there is one important limitation: External dependencies are not supported yet. An asset must not link to other .blend files, or use external media files that are not packed into the .blend file. Every asset must be self-contained within a single .blend file. While it is possible to store multiple assets in a single file, importing any single asset from that file requires downloading the entire file.
No Dynamic Server Required
No special server software is required; a standard HTTP server is sufficient. Blender can generate a remote library listing together with exported preview images, all stored alongside the assets. The resulting directory can simply be copied to a web server.
A static HTTP server makes Remote Asset Libraries simple to host for individual artists and small studios. It is not necessarily the best solution for asset markets with huge numbers of assets. Large asset services will likely want assets to be discovered dynamically instead. One possible approach is to generate the remote library listings and endpoints dynamically. Either way, this wasn’t the focus of this project, as such service providers usually have more resources to figure this out than Blender does.
Remote Listing Generator
A remote library consists of JSON “listing” files describing catalogs and assets, exported preview images, and the asset files themselves.
Blender now includes a remote listing generator. For example, running blender -c asset_listing generate /home/myname/my_library generates all required listing files and preview images inside /home/myname/my_library.
Blender Version Compatibility
A Remote Asset Library may be accessed by users with different Blender versions. Some assets may only work in newer versions of Blender. Other assets may evolve over time, while users of older Blender versions should continue to receive earlier compatible versions.
For these reasons, the remote library listing supports specifying minimum and maximum Blender versions, so that the asset system can exclude incompatible or replaced assets. When creating an asset, you don’t know how long it will be supported. So by default, no maximum version is specified. The maximum supported version can be added later in the remote library listing, once an asset is known to be incompatible with newer Blender releases.
There are still a number of ways of improving the system further:
- Remote Asset Libraries as Extensions: Just like Add-ons and Themes, it should be possible to browse available asset libraries from an extensions platform from within Blender. Some work on this has already been done, and it might be supported soon. It is not yet clear whether extensions.blender.org will be able to host multiple asset libraries soon. An even bigger unknown is whether it can host custom asset libraries as well: this adds a lot of infrastructure and review overhead.
- Placeholders: Allow dragging and dropping an asset before downloading it. It inserts a “placeholder” data-block and replaces it with the downloaded asset once ready. The “download first” requirement seems to work well enough for now, so there are no concrete plans for this.
- Multi-file assets: As mentioned, assets have to be stored in self-contained .blend files with no dependencies to other files. Addressing this brings many technical challenges but should be done sooner or later. The remote library listing is already designed to support this. Hopefully, this can be part of a follow-up release, but it depends on the availability of individual developers.
- Hosting on online drives: Being able to just store a remote asset library on commonly used online drive services would make it even easier to share asset libraries using the remote library system. This has some unique challenges too. There are no concrete plans for this; complexity and, in fact, feasibility are unknown.
- Asset Versions, Variants and Representations: Versioning of individual assets (as in v1.0, v1.1, v2.0, …), variants (such as “Blue Car” vs. “Red Car”), variations (such as a number of trees, each with small differences), and representations (such as a texture in high and low resolution, a character with animation and simulation proxies, etc.) have some importance for remote asset services. For example some asset markets provide textures in a standard resolution, with opt-ins for a higher or lower resolution (= asset representations). Currently none of this is supported from within Blender, and services have to either display these assets as multiple assets, or provide different ways to download them. There are ideas to solve this in future, without concrete plans.
- Authorization hooks: Many online asset services need means to log in and/or authorize users. The simplest solution would be letting Blender take a authorization token that can be forwarded to download requests, just like extensions do it. There are no concrete plans for this yet, although it can be added easily if needed.
- Searching / filtering / browsing hooks: Some online asset services may require customizing the UI further than currently possible. As mentioned above, big asset libraries may also need dynamic ways to populate the asset browser and other asset UIs. The asset system will need some kinds of hooks for these. While a Python API for the asset system is planned, there are no concrete plans for these hooks yet.
Support Blender
Development requires dedicated design and development resources.
Donate monthly or one-time to help make this happen.
