Megascans & Quixel Assets

Quixel Megascans is a library of thousands of assets captured from the real world by photogrammetry - photographing a real surface or object from many angles and reconstructing it as geometry plus textures. There are three broad kinds: surfaces (tiling materials - concrete, brick, soil, timber, plaster), 3D assets (props and models - rocks, plants, furniture, debris), and decals/imperfections (stains, cracks, grime you layer over other materials). Epic acquired Quixel and now distributes the library through the Fab marketplace, with a Bridge/plugin path that imports assets directly into an Unreal project.

What makes a scan look real is that it arrives as a full PBR material - the same physically based set of maps from Module 3, but captured from reality rather than authored. A single scanned surface typically includes an albedo (true base colour with the lighting removed), a normal map (the fine bumps), a roughness map (where it is matte versus glossy), plus displacement, ambient occlusion and sometimes metallic or specular. Because those channels come from a real object, they carry the subtle, correlated imperfection that hand-painting struggles to fake - the stain sits where the roughness changes, the wear follows the geometry. That coherence is the secret of the realism.

Megascans surfaces come at multiple resolutions (up to 8K), and 3D assets ship with LODs and are increasingly Nanite-ready, so they behave well in a real-time scene when used sensibly.

It is worth being precise about what each resolution costs. A texture is memory: an uncompressed 8K map is four times the pixels of a 4K and sixteen times a 2K, and a scanned surface carries several such maps (colour, normal, roughness and more). Pull a handful of 8K surfaces into a scene and you can consume gigabytes of VRAM before you have placed a single prop. The number that matters is not how detailed the source is but how many pixels of the screen the surface will ever fill - which is why the discipline section below insists on matching resolution to on-screen size rather than always grabbing the biggest download.

The workflow is deliberately quick. From within Unreal you browse Fab (or the Quixel Bridge panel in older setups), find a surface or asset, choose a resolution, and add it to the project; it downloads and appears in your Content Browser as a ready material or Static Mesh. Drag a scanned surface onto your terrain or a wall and it is instantly photoreal; drop in a scanned rock, planter or piece of street furniture and the scene gains lived-in context.

For archviz the highest-value uses are context and imperfection. Photoscanned ground surfaces, gravel, paving and soil make a Landscape read as real earth. Scanned props - rocks, plants, bins, bollards, garden furniture, debris - populate the middle ground that says a place is used, not staged. And scanned decals are a quiet superpower: layer a subtle grime, water-stain or crack decal over your own clean architectural materials and they stop looking computer-perfect. A brand-new concrete wall in reality already has form-tie marks and faint streaking; a decal restores that in seconds.

Combine Megascans with the previous two lessons and the environment comes together fast: a real DEM Landscape (5.1), instanced Megascans plants and your own trees (5.2), scanned ground surfaces and scattered rocks and props (this lesson). What used to be days of texture and prop work becomes an afternoon - which is exactly why asset discipline matters next.

The danger of an enormous, easy library is that you import everything and drown the scene. Every 8K surface you add consumes VRAM; every distinct prop is more memory and potentially more draw calls; a level stuffed with high-resolution assets you barely see will stutter and take an age to load. Discipline is the professional skill here.

A few rules. Import only what the camera actually sees - if a prop never appears in a shot or a walk, it does not belong in the level. Match resolution to on-screen size: a wall filling the frame may justify 4K or 8K, but a distant rock needs 1K or 2K; pulling everything in at maximum resolution is the fastest way to exhaust VRAM. Reuse a handful of well-chosen assets with varied scale and rotation rather than importing dozens of near-duplicates. And lean on Nanite for scanned 3D assets and LODs so heavy geometry stays affordable - the optimisation tools of Module 9 apply directly.

Think of the library as a quarry, not a shopping trolley. The scenes that look best are rarely the ones with the most assets; they are the ones where a disciplined selection is placed with intent and lit well. A restrained set of the right scanned surfaces and props, used at the right resolution, beats a hoard every time.

Megascans is famously generous, but generous is not the same as unconditional, so know the terms. Historically Megascans has been free to use within the Unreal ecosystem, and Epic has extended broad free access through Fab - but the licence around Fab and standard-versus-extended terms has evolved, and it distinguishes what you can do inside Unreal from other uses. Do not rely on memory or on what was true two years ago: check the current Fab and Megascans licence for your specific use, especially anything commercial, redistribution, or use outside Unreal. That is the honest professional answer, and it protects you.

There is also a craft-honesty dimension. Scanned assets are real objects, so use ones that suit the place - Northern-European mossy boulders scattered around a tropical Indian courtyard read as false as the wrong trees do. And keep the line clear between context and design. Scanned furniture, planting and dressing set a mood; they are not the specified design unless you say so. If a client might mistake a library sofa or a scanned tree for a specified item, flag it as placeholder dressing. Realism is persuasive precisely because it is convincing - which is exactly why you owe the viewer clarity about what is designed and what is set-dressing.

It helps to treat the three kinds of Megascans asset as three different jobs, because they behave differently in a scene. Surfaces are tiling materials with no geometry of their own - you assign them to your own walls, floors and terrain, and they repeat across a face. Their strength is coverage; their weakness is tiling, that tell-tale repeat when the same patch marches across a big surface. Break it up with a larger secondary tiling, a subtle macro-variation texture, or by blending two surfaces together, exactly as you would for any material (Module 3's textures-and-scale lesson goes deeper).

3D assets are actual meshes - rocks, plants, furniture, debris - that you place as objects. Here the cost is geometry and memory, which is where Nanite earns its keep: it virtualises the dense scanned mesh so you can use the high-detail version without hand-authoring LODs, on capable desktop hardware. Decals and imperfections are the quiet third category and often the highest value per kilobyte in archviz: a stain, a crack, a patch of grime or a puddle projected onto your own clean surfaces, breaking the computer-perfect uniformity that screams render. A few well-placed decals do more for believability than a dozen extra props.

A useful mental model is layers of realism. Your designed geometry and specified materials are the truth of the scheme; scanned surfaces give those materials real grain; scanned props populate the lived-in middle ground; scanned decals add the final imperfection. Build in that order and you keep control of what is designed while borrowing the real world for everything around it. Reach for a scanned surface when you need a material to read true, a scanned prop when the camera needs something real to look at, and a decal whenever a surface looks too clean to be believed - and always at the resolution its distance from the camera actually justifies.