Foxel Is Not Just a Single Model Editor

This tutorial explains one of the biggest mindset shifts for MagicaVoxel users.

Foxel is not centered around working on one isolated model alone. It is structured around projects, assets, scenes, objects, and reusable workflows.

Why This Matters

A lot of early friction comes from the wrong expectation.

If you expect Foxel to be mainly about one isolated model, the structure can feel heavier than necessary.

Once you understand the broader model, the interface makes more sense.

Foxel is built around this structure:

Project > Asset > Scene > Object

Foxel Starts With A Project

In Foxel, your work lives inside a Project.

A Project is the main container that organizes the content you are working on.

Instead of treating each model as a completely isolated file, Foxel lets related content live together in one project.

Projects Contain Assets

Inside a Project, you can have multiple Assets.

That means a Project is not just one file with one model. It can hold a larger set of related content.

Assets can include:

• Voxel Scenes
• Voxel Movies
• Heightmaps
• Mesh Assets

This makes it easier to keep related work together instead of managing everything as separate standalone files.

Scenes Contain Objects

When you open a Voxel Scene, you are working inside a scene structure.

A scene can contain multiple objects.

For example, a Voxel Scene can contain:

• Voxel Layers
• References
• Lights
• Cameras
• Helper objects

This adds another layer of organization and control.

Instead of only editing one fixed voxel model, you can build, arrange, transform, and manage several objects inside the same scene.

Why This Changes The Mindset

This structure means Foxel is not only about editing one static voxel object in isolation.

It is built for:

• Organized project content
• Scene-based workflows
• Multiple related assets
• Reusable content
• Broader workflow structure
• More complex production setups

The added structure is intentional.

It supports workflows where one project may contain several assets that need to work together.

How To Think About The Difference

A simple way to compare the mindset is:

• A single-model workflow focuses on one isolated object.
• Foxel’s workflow focuses on related assets inside a project.

That does not mean every project needs to be complex.

A Project can still contain one simple asset. The difference is that Foxel gives you room to grow beyond that when needed.

What To Remember

• Foxel starts with a Project.
• Projects contain Assets.
• Voxel Scenes contain objects.
• A scene can contain multiple objects.
• The workflow is broader than one isolated model.
• Reusable content is part of the structure.
• The added structure is intentional.