Back to blog

Organising Your 3D Game Asset Library

A game asset library is organised in three layers: folders to tell you where a file came from, tags to tell you what it is, and collections to tell you which project it serves. Everything else, naming, textures, licences, is a set of habits that keep those three layers from falling apart. This guide walks through them in order, from the first inventory to everyday reflexes.

Nobody decides to build an asset library. It forms on its own: a pack bought during a sale, a free kit picked up for a prototype, your own exports from Blender, a folder sent over by a freelancer. One day you find yourself hunting for ‘that low poly wooden barrel I had somewhere’ among thousands of FBX and GLB files. The good news: putting things back in order goes much faster than you would think, because most of the work can be automatic.

In this guide

  1. Why an asset library falls apart
  2. Step 1: take an inventory
  3. Step 2: three layers, folders, tags and collections
  4. Step 3: naming that both an engine and a human can read
  5. Step 4: put the textures back in order
  6. Step 5: record provenance and licence
  7. Step 6: make the library visible
  8. Step 7: habits that last
  9. Folders alone, DAM or viewer: the verdict
  10. Frequently asked questions

Why an asset library falls apart

Three forces work against you, and none of them depends on how disciplined you are.

On top of that comes a problem specific to games: an asset is not a file. It is a mesh, its PBR textures, sometimes a skeleton and animations. All it takes is one moved Textures/ folder for the model to show up grey everywhere.

Step 1: take an inventory

Before you tidy, look at what you really have. The trap is to start reorganising folders blindly, opening files one by one in a content creation tool.

Instead, open the root folder in Eyemesh and switch to the sortable list view. Within a few minutes you can see, for each file, its triangle and vertex counts, its dimensions and its format. Sort by triangles: the assets too heavy for your target platform rise to the top on their own. Filter by type: you know how many FBX, GLB and OBJ files you are really keeping.

Write down three numbers: the total number of assets, the share of third-party packs versus your own creations, and the number of obvious format duplicates. They will tell you where to start.

Step 2: three layers, folders, tags and collections

The classic mistake is to ask the folder tree to say everything at once: the source, the object type, the project, the style. No hierarchy can hold those four axes. Spread them out.

Layer 1: folders say where an asset came from

A file has only one location, so give it the one that will never change: its origin.

Assets/
├── Packs/
│   ├── VendorName - Medieval Village/
│   └── VendorName - Sci-Fi Props/
├── InHouse/
│   ├── Characters/
│   └── Environments/
└── Freelancers/
    └── 2026-03 - Creatures/

Keep packs exactly as they were delivered. Reorganising them by hand breaks the link with the original version, and the vendor's next update will arrive in their structure, not yours.

Layer 2: tags say what an asset is

This is where everything the folder tree cannot carry lives. Four families are enough in most cases:

FamilyExamples
Subjecttree, barrel, knight, door
Stylelow-poly, stylised, realistic, pixel
Technicalrigged, animated, LOD, modular
Statusto-review, in-game, needs-retopo

In Eyemesh, tags, notes and stars are stored in a companion file beside your models, never inside them. A purchased FBX stays identical byte for byte, which matters if you keep your assets under version control or if the vendor releases an update. Eyemesh suggests the tags you have already used as you type, so you do not end up with lowpoly, low-poly and low poly side by side.

Layer 3: collections say what an asset is for

The same rock is used in your current game, in a prototype and in a portfolio. Eyemesh favourites play that role: one collection per project, filled from any folder, without moving anything. Texture fixes, tags and notes follow the model into the collection.

Step 3: naming that both an engine and a human can read

A good name answers three questions without opening the file: what type of asset, what object, which variant. The prefix conventions common in game engines do the job very well:

PrefixMeaningExample
SM_Static meshSM_Barrel_Wood_A.fbx
SK_Skeletal meshSK_Knight.fbx
AS_AnimationAS_Knight_Walk.fbx
T_TextureT_Barrel_Wood_A_BaseColor.png

Three rules complete the table:

Do not rename third-party packs. Your convention applies to your own creations and to what you bring into a project, not to the original archive.

Step 4: put the textures back in order

This is the most common problem with FBX files: the file often keeps the texture path exactly as it was on the artist's machine. On yours, that path does not exist, and the model shows up without its material.

Eyemesh automatically detects missing textures and suggests the ones found in the folder. When automatic matching is not enough, you assign each image to its slot (base colour, normal, roughness, metallic, occlusion, emission, opacity) by hand, once. The fix is remembered, and it follows the model into your favourites.

Use this step to spot assets with an incomplete PBR set: a missing normal or roughness map stands out straight away in MatCap or untextured mode, far more clearly than with the textures displayed.

Step 5: record provenance and licence

This is the quickest step, and the one that will save you the most time when you ship a game. An asset under a CC-BY licence requires attribution in the credits. A store-bought asset can go into your games, but it cannot be redistributed as is, in a public repository for instance. Some licences also depend on the number of seats or on your studio's revenue. Two years after the purchase, nobody remembers.

The rule is simple: every incoming pack gets a note. Source, author, licence type, purchase date. In Eyemesh, a file's note is a free-text field that saves as you type. A cc-by or attribution tag then lets you list, in a single search, every asset that needs crediting before a release.

Step 6: make the library visible

A folder of generic icons cannot be browsed, only dug through. Two settings change everything:

For version duplicates, side-by-side comparison with linked cameras quickly settles the choice between Rock_v02 and Rock_v03.

Step 7: habits that last

Once the foundation is in place, keeping it clean takes almost nothing. Four reflexes are enough:

  1. A single inbox folder. Every new pack lands in Inbox/, never directly in the folder tree.
  2. A short sorting pass every week. Open Inbox/, tag, note the licence, move to Packs/ or InHouse/. A few minutes are enough.
  3. One working format per use. Keep the original, and convert when needed rather than piling up copies: Eyemesh converts to GLB, glTF, USDZ, OBJ, STL or 3MF on demand.
  4. Move files from the app rather than from the Finder. A file renamed or moved from Eyemesh keeps its tags and notes. Moved on its own in the Finder, it gets separated from its companion file. Moving the whole folder, on the other hand, takes everything along.

Folders alone, DAM or viewer: the verdict

Folders and FinderDAMViewer with metadata (Eyemesh)
SetupNoneMigration, configurationOpen a folder
See the asset without opening itUSDZ onlyDepends on the tool 17 formats, thumbnails and QuickLook
Animations and skeletonNoRarelyYes
Missing texturesNoNo Detection and remapping
Tags, notes, starsFinder tags (no notes)YesYes without modifying the files
Files stay in placeYesNo the DAM becomes the custodianYes
CostFreeUsually a subscription$14.99, one-time purchase

The honest verdict: working alone on a Mac, or in a small team sharing folders, a viewer with metadata covers the essentials without imposing anything on you. As soon as several people need to reach the same catalogue with different permissions, a DAM becomes justified, and this article does not claim to replace one. That trade-off is covered in detail in managing a 3D asset library without a DAM.

Organising 3D game assets: frequently asked questions

Should assets be organised by project or by source?

By source in the folders, by project in the collections. An asset often serves several projects, whereas its source never changes. Organising by project in the folder tree forces you to duplicate files.

Should I extract every ZIP pack?

To browse them as thumbnails and tag them, yes: a file has to exist on disk to be previewed. Keep the original archive aside if the vendor releases updates, as it will serve as a reference.

How do I find an asset when I do not know its name?

Through tags and through numbers. Eyemesh search covers names, tags and notes, in the open folder and its subfolders. The list view then sorts by triangles or dimensions to isolate the right candidate.

Does tagging my FBX files modify them?

No. Tags, notes and stars live in a companion file beside the models. A tagged file gives the same checksum as before.

Which format should I keep in the library?

The original, always. A pack's FBX or source file often holds more information than its conversions. Exchange formats can be generated on demand.

Do I have to organise everything at once?

No. Start with the folder of your current project: it is the one you open every day, and the benefit is immediate. Thumbnails, triangle counts and texture detection are automatic as soon as the folder is open, so all that is left for you is adding tags and notes as you go. The rest of the library will follow naturally through the inbox folder.

See your assets before you open them

Open your asset folder in Eyemesh: thumbnails, animations, textures and tags, with no import and no migration. 7-day free trial, then $14.99 as a one-time purchase.

Download on the Mac App Store · See all features

All articles