Organize Prefabs With Metadata

Prefab libraries become much more useful when they are organized well.

In Foxel, both Prefab Packages and individual Prefabs can store metadata such as names, categories, scale information, and descriptive text.

Why This Matters

Reusable content becomes harder to manage as the library grows.

Metadata helps turn Prefabs into a more structured and searchable system.

This is especially useful when a package contains many reusable pieces or when the same library is used across multiple projects.

Why Prefab Metadata Exists

Prefab Packages and Prefabs can store descriptive metadata such as:

• Names
• Categories
• Scale information
• Descriptive text
• Keywords
• Copyright information

This metadata helps organize, identify, and search Prefab content more easily.

Good metadata makes a reusable library easier to browse and easier to maintain.

Editing Prefab Package Properties

To edit the properties of a Prefab Package:

1. Open the Prefabs page.
2. Locate the package on the left side.
3. Double-click the package to open its properties.

Package metadata describes the library as a whole.

Use it for information that applies to the complete package, not only to one individual Prefab.

Package Attribute Fields

A Prefab Package can contain these attribute fields:

• Name
• Main Category
• Subcategory
• Unit Scale

Name

Name identifies the package.

Use a clear name that describes the package content.

Main Category And Subcategory

Main Category and Subcategory help group the package in a larger library.

Use them to separate different kinds of reusable content, such as environment pieces, props, architecture, vegetation, or mechanical parts.

Unit Scale

Unit Scale describes the intended scale of the package content.

Use consistent scale information when Prefabs should fit together across packages or projects.

Package Description Fields

A Prefab Package can also contain:

• Title
• Headline
• Description
• Keywords

These fields help explain what the package contains and how it should be used.

Title And Headline

Title and Headline provide readable labels for the package.

Use them when the package needs a more descriptive presentation than the internal name alone.

Description

Description explains the package contents in more detail.

Use it to describe the theme, intended use, or important notes about the package.

Keywords

Keywords help with searching and filtering.

Use short terms that describe the package content, style, use case, or theme.

Package Copyright Fields

A Prefab Package can also store:

• Creator
• Copyright Status
• Copyright Notice
• Copyright Info URL

Use these fields when authorship, licensing, or attribution information matters.

This is useful for shared libraries, marketplace-style packages, studio content, or any package that may be reused outside the original project.

Editing Prefab Properties

To edit the properties of an individual Prefab:

1. Open the Prefabs page.
2. Make sure the correct package is open.
3. Locate the Prefab on the right side.
4. Double-click the Prefab to open its properties.

Prefab metadata describes one reusable piece inside the package.

Use it for information specific to that individual Prefab.

Prefab Attribute Fields

An individual Prefab can contain:

• Name
• Size at LOD0
• Main Category
• Subcategory
• Unit Scale

Name

Name identifies the individual Prefab.

Use a name that makes the piece easy to recognize later.

Size At LOD0

Size at LOD0 describes the Prefab’s highest-detail dimensions.

This helps you understand how large the Prefab is before placing or reusing it.

Main Category And Subcategory

Main Category and Subcategory help organize individual Prefabs inside a package.

Use them when one package contains several kinds of content.

Unit Scale

Unit Scale describes the intended scale of the individual Prefab.

Use it when scale matters for placement, modularity, or consistency with other assets.

Prefab Description Fields

A Prefab can also contain:

• Title
• Headline
• Description
• Keywords

These fields help identify and search individual Prefabs.

Use them when a name alone is not enough to explain what the Prefab is for.

Practical Use

In daily use, the most valuable metadata is usually:

• Clear names
• Useful categories
• Keywords
• Consistent unit scale
• Short descriptions where needed

These make libraries easier to browse and easier to reuse correctly.

You do not need to fill out every field for every Prefab. Focus on the metadata that helps you find and use the content later.

Good Metadata Habits

As a Prefab library grows, these habits help:

• Use consistent naming.
• Keep categories broad enough to stay useful.
• Use subcategories for more specific grouping.
• Add keywords for common search terms.
• Keep descriptions short but meaningful.
• Use consistent unit scale information for modular content.
• Add copyright information when content may be shared.

Metadata is most useful when it stays consistent across the library.

What To Remember

• Both Prefab Packages and individual Prefabs can store metadata.
• Package metadata helps organize the library at a broader level.
• Prefab metadata helps identify individual reusable pieces.
• Categories, keywords, and scale information are especially useful.
• Copyright fields help track creator and licensing information.
• Metadata makes large reusable libraries easier to manage.
• You only need to fill out the fields that are useful for the library.