←

Ultimate Asset Organizer – Models

Documentation and usage guide for Blender 4.5+.

Overview

Ultimate Asset Organizer – Models is a Blender add-on designed to turn messy model packs on your hard drives into a clean, reusable Asset Browser library.

  • Import models from common formats and folder structures
  • Resolve textures and dependencies with an automatic pass plus a manual fallback
  • Build usable PBR materials as a solid starting point
  • Create Asset Browser entries so models can be dragged into any scene
  • Generate preview thumbnails so your library stays visual and easy to browse

The goal is simple:
Spend less time re-importing assets and more time building scenes.

Meet the add-on

If you have a growing collection of downloaded models and you want them to behave like a real library inside Blender, this add-on is made for that.

It helps you go from:

  • “a folder full of packs”
  • “a library file with assets and previews in the Asset Browser”

Typical results:

  • A dedicated library .blend that contains your organized assets
  • Clean preview thumbnails for fast browsing
  • Assets ready for drag and drop into any project

Why you might want it

Using model packs across projects usually means repeating the same chores:

  • Import the same files again and again
  • Reconnect missing textures
  • Fix materials quickly just to get a usable look
  • Dig through folders because previews are inconsistent or missing

UAO – Models is built to reduce that overhead.

You get:

  • A reusable asset library you build once and reuse across projects
  • A faster “find it and place it” workflow through the Asset Browser
  • A consistent preview look so browsing is actually efficient

It’s a good fit if you:

  • Download a lot of props, environments, kit pieces, or scans
  • Work with large packs that include many objects per file
  • Want a personal or team library that stays tidy over time

Key features

Here’s what it can do.

Folder and file import

  • Import common model formats (OBJ, FBX, GLB, GLTF, and .blend sources).
  • Work from single files or larger folder collections.

Texture and dependency resolution

  • Attempts an automatic texture search during import.
  • Provides a manual texture folder selection when automatic resolution is not enough.
  • Rebuilds or reconnects materials so assets are usable before you assetize them.

Automatic material setup

  • Uses the same sophisticated algorithm as Ultimate Asset Organizer – Materials.
  • Builds PBR materials as a strong starting point.
  • Designed for quick look development and dependable library results.

Large pack handling

  • Useful when files import many meshes at once.
  • Can lay out imported objects into a clean grid for review and organization.

Asset Browser integration

  • Marks imported results as Assets.
  • Makes reuse simple: browse in the Asset Browser, then drag and drop into any scene.

Preview generation

  • Generates previews for assets that do not already have a thumbnail.
  • Stores previews inside the library file for consistent browsing.
  • Designed to produce a clean “library look” when scrolling assets.

Logging and diagnostics

  • Writes a running log so you can review what happened during import and processing.
  • Includes an Open Log action for quick access while troubleshooting.

Cleanup tools

  • Optional cleanup actions help keep the library file responsive.
  • Can clear the log when you are done.

How it works

Typical workflow:

  1. Step 1 — Select
    • Choose your model files or folders
    • Import supported formats (OBJ, FBX, GLB, GLTF, and .blend)
    • If a file contains many objects, you can organize them into a clean layout for review
  2. Step 2 — Resolve
    • Let the add-on attempt to locate textures automatically
    • If something is missing, choose the correct texture folder manually
    • Materials are rebuilt or reconnected so the model looks correct before assetizing
  3. Step 3 — Create Assets
    • Mark results as Assets so they appear in the Asset Browser
    • Your library becomes drag and drop ready
  4. Step 4 — Generate Previews
    • Generate preview thumbnails for assets that need them
    • Important: Step 4 does not save automatically
    • Save your library .blend after previews are generated
  5. Clean up (optional)
    • Purge unused data after big import or preview sessions
    • Clear logs when you are finished

After that, you can browse your assets in the Asset Browser and reuse them whenever you need.

Quick start

1. Install the add-on

  • Download the add-on file
  • In Blender, drag and drop the .zip file into the Viewport
  • Click Save Preferences so it stays enabled next time

2. Find the add-on panel

  • Open the 3D Viewport
  • Press N to open the side panel if it is not already open
  • Look for the tab: UAO — Models

3. Recommended: Start a dedicated library file

  • Open a fresh .blend
  • Save it as a dedicated Models Library file
  • This keeps your asset library clean and avoids mixing in unrelated scene data

4. Step 1 — Select your models

  • Choose a file or folder set to import
  • Import your models into the library file

5. Step 2 — Resolve textures when needed

  • If textures are found automatically, continue
  • If textures are missing, select the correct texture folder and rebuild materials

6. Step 3 — Create Asset Browser assets

  • Run Create Assets so models appear in the Asset Browser
  • Confirm assets are visible and named as expected

7. Step 4 — Generate previews

  • Save the library file before generating previews
  • Run Generate Previews to create thumbnails
  • Save again when you are happy with the results

Examples and ideas

Building a personal library from downloaded packs

  • Point the add-on at your downloaded folders
  • Resolve textures and materials once
  • Create assets and previews
  • Save a clean library file you reuse across projects

Working with kit style packs

  • Import a set that includes many objects
  • Use layout tools to keep objects organized while processing
  • Assetize and preview so you can browse quickly later

Environment dressing and set building

  • Build a library of props and modular pieces
  • Drag and drop from the Asset Browser while blocking out scenes
  • Keep previews consistent so you can find what you need fast

Studio or team library

  • Store one shared library .blend in a shared location
  • Everyone points Blender’s Asset Libraries to the same folder
  • Keep naming and preview results consistent across the team

Tips for best results

Start with a dedicated library file

  • Keep your library separate from production scenes
  • Back up the library file occasionally, especially before large preview jobs

Keep packs organized when you can

  • If a pack is extremely messy, consider reorganizing textures into a clear folder
  • Consistent folder structure improves texture resolution results

Resolve before you assetize

  • Make sure materials look correct before Step 3
  • It saves time later and keeps your Asset Browser clean

Save before preview generation

  • Preview generation depends on having a real file location
  • Saving before Step 4 avoids path issues and keeps results consistent

Use cleanup after big sessions

  • After large imports and preview generation, run cleanup to keep files responsive
  • Clear logs once you have confirmed everything looks correct

FAQ

Do I need to build shader nodes myself for this to work?

No. The add-on builds a solid PBR starting point. You can tweak materials later if you want, but you don’t need to build node networks manually to get usable results.

My textures were not found automatically. What should I do?

Use Step 2 and select the correct texture folder manually. Many packs store textures in separate directories or unusual layouts, so a manual folder pick is often the fastest fix.

Can I stop a job if it takes too long?

Yes. If you cancel a long operation, completed work typically stays. You can continue later.

Why are previews missing?

Previews are generated in Step 4 for assets that need them. Make sure you ran Step 3 first so the models are marked as Assets, then run Step 4 and save your library file.

Will this affect my existing projects?

The add-on operates on the file you run it in. For safety and cleanliness, build your library in a dedicated .blend and keep your production scenes separate.

Need help?

If something is not working or you have a question, reach out. It helps if you include:

  • Your Blender version
  • Your operating system (Windows, macOS, or Linux)
  • What you were importing (format and rough library size)
  • Which step you were running (Step 1, Step 2, Step 3, Step 4)
  • Any error messages you saw
  • A screenshot of the add-on panel and the console output when possible