Assets
How NEO stores your game's files on the content network, how the Studio uploads them, and how to upload files yourself.
On this page
Assets are the files your game is made of: scenes, scripts, images, audio, models and settings. On NEO they live on the content network, where every file is stored once and addressed by its content. This page explains how that works, how files get there, and where you see them.
Content-addressed files#
When a file is uploaded, NEO computes its SHA-256 hash and stores it at an address built from that hash:
/content/<sha256>That has a few useful effects:
- The same file is stored once. Uploading a file that's already there doesn't make a copy.
- An address always means the same bytes. A file's address can't later point at something else, which is why published versions can't change.
- Republishing is fast. The Studio checks whether each file is already on the content network before sending it, so only new or changed files are uploaded.
How files get there#
Publishing from the Studio#
You rarely upload files by hand. When you use Build ▸ Publish to NEO Platform in the Studio, it saves your project and uploads your project's own files, one upload per file, plus a small manifest that lists them. The new version of your game points at that manifest. See Publishing from the Studio.
The starter content that comes with the NEO engine's templates (such as character animation and audio) isn't uploaded with your project: published games read it from the content network directly, as the Studio does.
Your game's key art#
Choosing Upload image on a game's Settings tab uploads the image to the content network and sets it as the game's key art. See Game settings and versions.
Uploading a file yourself#
On the Creator Hub's Development items page, choose Upload a file. The page accepts these types:
| Type | Files |
|---|---|
| Images | PNG, JPEG, WebP |
| Audio | OGG, WAV |
| Models | glTF binary (.glb) |
| Data | JSON, plain text |
Limits#
| Limit | Value |
|---|---|
| Largest single file | 8 MB |
| Upload allowance | 256 MB per account in any 24 hours |
The Development items page shows how much of the allowance you've used, for example "12.4 MB of 256.0 MB uploaded today." When you reach it, uploads stop until older ones fall outside the 24 hours.
The Development items page#
Development items lists everything you've uploaded, newest first: each file's hash (the start of it, linking to the file), its type, its size and when you uploaded it. Files you publish from the Studio show up here too.
Assets in the Studio#
Inside the Studio, the Assets panel lists the content your project can use, in two layers:
- Your project's own files, in the project's
assets/folder. - The template's shared content, which every project made from that template reads.
The panel shows them merged. If your project has a file at the same path as a shared one, your file wins, so you can replace a template file by importing your own with the same name.
To add a file, choose Import in the Assets panel and pick it with your browser's file picker. Imported files go into your project's own assets/ folder. They're part of your project, so the Studio uploads them the next time you publish, and each one has to fit the 8 MB per-file limit. Shared template content is never uploaded with your project.
See Studio and Projects and templates.