Build Notes

Are Fab Assets Made in Unreal Engine? Separating Modeling from Delivery

By Miles Park·November 7, 2026

While browsing Fab, I kept noticing Unreal Engine in product details. My first impression was that most sellers must be making the objects inside Unreal. That was too much to infer from a format label. A product can be modeled in one application, textured in another and prepared or rendered in an engine. Understanding those stages makes a first asset project much easier to plan.

Build Notes · Preparation series 2 of 5 · Checked November 7, 2026. Screenshots show research and an illustrative test workspace; no first product sale or completed pack is claimed.

A product page contains several kinds of information

The image tells me how the seller presented the asset. The description may name the tools used. The included formats tell me what I can download. Those are separate pieces of evidence, and they answer different questions.

I should not treat a polished engine render as proof that a native engine project is included. Likewise, an Unreal package does not identify the software in which every vertex was created.

Figure 1. Retro CRT Television by Mad Interactive Studio, used here as a third-party packaging example. Source page.

Figure 2. The seller names Blender for modeling and supplies texture maps separately. This is the seller's description, not an independent compatibility test. Source page.

Blender can be the authoring workspace

For our planned 3D workflow, Blender is where the object's shape, UV layout and editable construction can be developed. I want to preserve that working file so changes do not have to begin from an exported copy.

Export then becomes a deliberate handoff. Blender's interoperability documentation lists multiple exchange formats. Choosing one means deciding what information needs to survive the journey, not simply selecting the most familiar extension.

Figure 3. Blender's interoperability page lists formats used to exchange work with other applications. Source page.

Figure 4. The Blender manual documents importing and exporting .glb and .gltf. Source page.

Unreal can be the assembly and verification workspace

Epic's FBX pipeline documentation explicitly discusses bringing meshes from 3D applications into Unreal. That is the connection I was missing when I looked only at storefront badges.

In a lighting product, I would use the engine to check placement, appearance and the behavior I intend to advertise. The editable source and the engine package would serve different customers and different stages of the job.

Figure 5. Epic's FBX pipeline imports models from a 3D application into Unreal. Source page.

Figure 6. The installed Unreal Engine project browser with the blank Blueprint template selected. This is a test workspace, not a finished commercial asset. Screenshot from the local test project.

A bright surface and a working light are different deliverables

A lamp-shaped mesh is one part of a product. A visibly glowing bulb is another. A light source that illuminates the room adds behavior in the target scene. Switching or flickering adds further setup and testing.

These are useful scope choices, not a requirement to implement everything. If the first release is a static prop collection, the description should say so. If it promises working lights, the buyer needs a tested way to use them.

The screenshot shows the default scene's DirectionalLight settings as an illustration of engine-side controls. It is not a demonstration of a finished lamp or a custom lighting system.

Figure 7. The default Unreal scene in the separate FabBuildNotesDemo workspace. The template landscape and sky are supplied by the engine, not modeled by me. Screenshot from the local test project.

Figure 8. The default DirectionalLight exposes intensity and color in the Details panel. This illustrates engine-side controls, not a custom lamp asset. Screenshot from the local test project.

Available formats are a support commitment

Fab's format table distinguishes engine packages from exchange and native authoring formats. A seller can support more than one route, but adding a format also adds a file to check and maintain.

My practical rule is to promise only a route I can open and inspect. An export succeeding is an intermediate result. The real question is whether the receiving application shows the intended scale, materials and structure.

Figure 9. The format table separates engine packages, exchange files and authoring formats. Source page.

Figure 10. The required Unreal content project structure is more than a loose model file. Source page.

The workflow I am planning

The intended sequence is Blender authoring, a checked exchange export, then Unreal assembly and verification if an engine version is included. Promotional images come from the delivered content or clearly identify anything used only for presentation.

This does not mean the product is finished or that its compatibility has already been certified. It means I now know what to verify before writing the listing. I can keep the modeling tool and the customer-facing format separate without treating either as less important.

Continue the preparation series