NEOLearn

Assets

How the NEO engine loads files such as models, images, sounds and data into your game, and the pages that cover each part of the asset system.

Updated October 20, 2026

On this page

An asset is data your game loads from a file or makes at runtime: a mesh, an image, a sound, a glTF model, an animation clip or your own data type. The engine's asset system reads the file in the background, turns it into a Rust value and stores it, and your code refers to it through a small handle.

This section is for creators who write Rust game code. For how the Studio uploads and stores your game's files on NEO, see Assets.

How it fits together#

PartWhat it is
AssetServerA resource that starts loads. asset_server.load("models/crate.glb#Scene0") returns a handle straight away and loads in the background.
Handle<T>A reference to an asset of type T. It keeps the asset alive while any strong handle exists.
Assets<T>A resource holding every loaded asset of type T. Look an asset up with its handle.
AssetEvent<T>A message sent when an asset is added, modified, removed or fully loaded.
AssetLoaderTurns bytes into an asset. The engine has loaders for glTF, images, audio, fonts, shaders and world files; you can add your own.
Asset sourceWhere bytes come from: the assets/ folder by default, or another folder, embedded data or a custom reader.
src/main.rs
use neo::prelude::*;

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .add_systems(Startup, setup)
        .run();
}

fn setup(mut commands: Commands, asset_server: Res<AssetServer>) {
    commands.spawn(Camera2d);
    // loads assets/textures/crate.png in the background
    commands.spawn(Sprite::from_image(asset_server.load("textures/crate.png")));
}

Pages in this section#

PageWhat it covers
Loading assetsAssetServer::load, paths and labels, load states, folders and loader settings.
Using assetsAssets<T>, handles and ids, asset events, adding and changing assets at runtime.
Hot reloadingReloading assets when their files change, and reloading by hand.
Custom assets and loadersYour own asset types, the RON loader and writing an AssetLoader.
Asset processingProcessing assets ahead of time with .meta files, transformers and savers.
Asset sourcesExtra folders, embedded assets and how NEO games find their content.
glTFLoading glTF models, their labels, materials and extras.

What's on in NEO's builds#

NEO games build the engine with its default features. A few asset features are off:

FeatureWhat it addsIn NEO's builds
file_watcherHot reloading from the file systemOff
asset_processorProcessing assets ahead of timeOff
jpeg, bmp, tga, webp, ...More image formatsOff. PNG, HDR and KTX2 are on.
http, httpsLoading assets from web addressesOff
mp3, flac, wavMore audio formatsOff. Ogg Vorbis is on.

See Cargo features for turning features on.

Next steps#