A PBR library dies from inconsistent names, not from a lack of software. Texture management tools help only after the files are predictable. This guide covers a folder standard that works in Blender, Unreal, and Unity, then the tools that sit on top of it. You can apply it to free CC0 downloads from Locker3d and to paid packs in the same tree.
Fix the folder and naming standard first
Put each material in one folder. Keep every map for that material in that folder. Use a single base name:
Library/Wood/Oak_Planks_01/Oak_Planks_01_albedo.pngOak_Planks_01_roughness.pngOak_Planks_01_normal.pngOak_Planks_01_metalness.png
Avoid spaces and mixed language in filenames. Put resolution in the folder or suffix (_2K) only if you keep more than one size. Do not store albedo in one drive and normals in another. Importers in Blender, Unreal, and most painters look for sibling files. If you need a map refresher, see the PBR textures complete guide.
What DCC tools already give you
Blender’s Asset Browser can catalog materials after you build them once. Mark a material as an asset, store the .blend in a library path, and drag it into new files. Unreal’s Content Browser and Unity’s Project window do the same if import settings (sRGB versus linear) are correct on the first import. Adobe Bridge or a plain file manager with thumbnails is enough to browse albedo previews.
Use these before you buy a dedicated manager. A paid tool will not fix a library where half the packs use diff, col, and basecolor for the same map.
When dedicated managers earn their seat
Consider a dedicated texture or asset manager when you have hundreds of packs, multiple artists, or you need 3D sphere previews and tags (warm, dirty, seamless, interior). Features that matter:
- Auto-detect of PBR map suffixes and one-click material create.
- Tags that survive a file move.
- A render preview under a known HDRI so roughness is comparable. Pair that with a consistent HDRI lookdev setup.
- Export presets to 1K/2K/4K. Match choices to the resolution guide instead of keeping 8K copies of every floor.
If the tool cannot write a sidecar or database you can back up, do not let it be the only index. Keep the folder tree readable without the app.
Ingesting Locker3d and other CC0 packs
Download from the texture catalog, then immediately rename into your standard. Sort wood and metal into those category folders even if you also tag them. Locker3d textures are free CC0, so you may convert PNG to your studio format, pack channels, or resize without asking. Confirm the waiver in CC0: what you can and cannot do if legal asks.
On ingest, set color space once: sRGB for albedo, non-color for roughness, normal, metalness, AO, and height. Wrong color space is the most common “the manager preview looks fine but the engine looks wrong” bug.
A weekly maintenance loop
- Delete unused resolutions. Keep 2K as default; archive 4K only for hero materials.
- Re-export any pack that still uses glossiness so the whole library is roughness.
- Add one sentence of notes per hero material (scale in cm per tile, DirectX or OpenGL normal).
- Search for duplicate albedos. If two oaks look identical, keep one and variant the roughness.
Software is optional. A searchable, legal, consistently named shelf is not. More library and lighting notes are on the Locker3d blog.
Frequently asked questions
Do I need paid texture management software?
Not at first. A strict folder layout, consistent filenames, and your DCC’s asset browser cover most indie and small-studio libraries. Add a dedicated manager when search, tags, and 3D previews take more time than modeling.
What is the most important habit?
One folder per material with every map inside, and the same base name for all maps. Tools can then auto-connect albedo, roughness, normal, and metalness. Scattered files break every importer.
Can I manage Locker3d downloads the same way as paid packs?
Yes. Locker3d files are free CC0, so you can rename, convert, and pack them into your library without a license conflict. Treat them like any other metalness/roughness set.