What's in an asset pack

An asset pack is a licensed ZIP of related 3D models for building a consistent scene. Its pack page and README describe the exact contents of the current release. Bundle layouts vary, so treat optional components, catalogs, prebuilds, palettes, and showrooms as pack-specific features rather than universal inclusions.

Common bundle contents#

A low-poly environment pack may contain:

glb/
  individual/          independently placeable models
  <pack>.glb           optional joined catalog for inspection
  prebuilds/           optional composed set-pieces
  configurator/        optional recolourable product models
components/            optional React Three Fiber components
preview/showroom.html  optional browser-based inspector
palettes.json          optional palette reference data
README.md              file list, setup notes, scale, and pivots
MANIFEST.md            optional per-asset detail list
LICENSE.txt            permitted uses and restrictions

• Individual GLBs are the normal choice for composing a scene. Load only the models you need and position each one independently.
• A combined catalog, when included, is a joined inspection model. It is not a ready-made scene and its assets cannot be moved independently after joining.
• Prebuilds, when included, are composed set-pieces. Some expose named decor and placement slots; see decoratable prebuilds & slots.
• React Three Fiber components, when included, wrap matching GLBs for React projects. Their paths and typed surfaces vary by release.
• Configurator models, when included, are the recolourable variants of a pack's products, kept in their own folder because they carry named material zones instead of baked vertex colours; see configurator packs.
• Palette data records colours and scene-lighting values used by applicable low-poly packs. It does not automatically recolour a flattened GLB.
• A showroom, when included, helps inspect the pack. Its browser and network requirements are listed in the pack README; do not assume it works offline.
• A manifest, when included, lists each asset with its own detail line. Use it alongside the README when you need a per-asset inventory.

Editions inside one download#

Some packs ship a free starter alongside the full edition. When that happens, each edition is a self-contained folder with its own README.md, LICENSE.txt, and GLBs, so you can point a project at one folder without pulling in the other. Read the README inside the edition you plan to use, because asset counts and optional extras differ between them.

Most packs ship a single edition. Check your Downloads page and the extracted folder before assuming either shape.

Character packs#

A rigged character pack is laid out differently from an environment pack. Instead of standalone props, it ships skinned meshes — bodies, heads, hair, and wardrobe pieces such as tops, bottoms, and shoes — that share one skeleton, plus a single file of animation clips every body reuses. You assemble a character at runtime by binding the wardrobe pieces you want to the chosen body's skeleton.

Named material zones and attachment sockets vary per pack, so treat the bundled README as the authority for joint order, clip names, and zone names.

What varies by pack#

Current low-poly environment packs commonly use flat-shaded vertex colours and no textures. Configurator packs instead expose named materials for parts such as a body, door, worktop, or handle. Other packs may include textures, animations, editable authoring files, or none of those features.

Check the current pack page and README for:

• asset count and filenames;
• texture and decoder requirements;
• component, prebuild, showroom, and authoring availability;
• scale, pivot, grid, and placement notes; and
• the license included with that release.

What is not included by default#

A pack purchase does not provide a threejsassets-hosted asset URL or CDN. Host the downloaded files in your own application. Procedural generator projects and demo-world source pages are not part of the standard licensed bundle. An editable edition is available only when your Downloads page shows that option.

Choosing a file#

Use an individual GLB for normal scene composition. Use a prebuild when you want an included set-piece. Use a combined catalog only when a compact, one-file inspection model fits your workflow. Decoder requirements differ between those files; see individual GLBs vs the combined catalog.

Next steps#

• Using a pack in React Three Fiber — use an included component or load a GLB directly.
• Using a pack in vanilla three.js — load compressed and uncompressed files correctly.
• Pack pricing & what you get — understand what a pack purchase covers.