What Foxel Adds Beyond Basic Color-Only Workflows

This tutorial explains one of the clearest differences MagicaVoxel users will notice in Foxel.

Foxel does not stop at assigning visible color to voxels. It separates color and material more explicitly, adds reuse systems, and places everything inside a broader project structure.

Why This Matters

If you expect Foxel to work mainly as a color-driven voxel editor, some of its structure can feel unnecessary at first.

It makes more sense once you see that Foxel adds several workflow layers beyond visible color alone.

The main differences are:

• Color and material are separate.
• The same color can use different material properties.
• Reuse is built into the workflow.
• Projects and assets provide broader structure.

Color Is Only One Part Of The Result

Foxel still supports color-based voxel work.

But color is only one part of the final look.

In Foxel, Material is separate from Color.

That means two voxels can share the same visible color but still react differently to light because their materials are different.

For example:

• A green matte voxel and a green shiny voxel can use the same green color.
• A gray stone voxel and a gray metal voxel can use the same gray color.
• A red painted voxel and a red emissive voxel can use the same red color.

The visible color can stay the same while the lighting behavior changes.

The Separation Is Practical

This is not just a technical distinction.

In MagicaVoxel, material is tied to the palette color.

That means if you want the same green with two different material setups, you effectively spend another color slot.

In Foxel, the same color can be reused with different material properties without that limitation.

This makes material variation easier to manage, especially in larger assets where color slots should stay meaningful.

Reuse Is Built Into The Workflow

Foxel also adds reuse-oriented systems such as:

• Prefabs
• Minis
• References

These systems let you build reusable content instead of treating every edit as a one-off result.

Prefabs

Prefabs are reusable 3D voxel content.

Use them when you want to place prepared voxel building blocks again later.

Minis

Minis are reusable mini heightmaps.

Use them for repeated 2D-plus-height details, surface variation, and small relief elements.

References

References let you reuse source assets inside a scene.

Use them when another asset should contribute generated voxel content without being rebuilt manually.

Project Structure Matters Too

Foxel places all of this inside a broader Project and Asset structure.

That means the workflow is not only about coloring a single model.

It is also about organizing, reusing, and scaling content more effectively.

A project can contain multiple related assets, such as:

• Voxel Scenes
• Voxel Movies
• Heightmaps
• Mesh Assets

This structure makes more sense as the amount of content grows.

How To Think About The Difference

A basic color-only workflow focuses mainly on assigning visible colors to voxels.

Foxel adds more layers:

Color + Material + Reuse + Project Structure

That is why Foxel can feel broader than a palette-bound voxel workflow.

The added structure is there to support larger, more reusable, and more material-aware work.

What To Remember

• Foxel goes beyond visible color alone.
• Color and Material are separate.
• The same color can use different material properties.
• Material variation does not require duplicating color slots in the same way.
• Reuse is built into the workflow.
• Prefabs, Minis, and References solve different reuse problems.
• Project structure supports broader workflows.