Workflow
You own 4,000 Megascans. You can't find any of them.
Downloaded Megascans land on disk as folders named after asset IDs, each stuffed with a dozen near-identically-named maps and a pile of LODs. What is actually in that folder, why Explorer falls over, and the three ways out — two of which are free.
It is a structure built for a database to read, not a person. One surface is eight files; multiply by a few thousand and you have a library you technically own and practically cannot use.
vlkgcgw/
├─ vlkgcgw_2K_Albedo.jpg ← the only one you can preview
├─ vlkgcgw_2K_AO.jpg
├─ vlkgcgw_2K_Cavity.jpg
├─ vlkgcgw_2K_Displacement.exr ← Explorer shows a blank icon
├─ vlkgcgw_2K_Gloss.jpg
├─ vlkgcgw_2K_Normal.jpg
├─ vlkgcgw_2K_Roughness.jpg
├─ vlkgcgw_Preview.png
└─ vlkgcgw.json ← the readable name is in hereWhy File Explorer cannot save you here
It is tempting to assume this is a discipline problem — that if you just kept the folder tidier it would be fine. It is not. There are four structural mismatches between how Megascans stores data and how a file browser thinks, and no amount of tidying touches any of them.
The name you need is inside a file, not on it
vlkgcgw is the folder name. "Mossy Forest Rock" is a string inside the JSON. Explorer indexes
filenames, so it can never show you the one piece of information you are actually searching by.
Eight files are one thing
A surface is a material, not seven JPGs and an EXR. Any browser that shows you a flat grid of images is showing you the wrong unit of work, and it multiplies your apparent library size by eight for no benefit.
Half the formats have no thumbnail handler
EXR displacement, FBX meshes, sometimes 16-bit PNG — Windows renders these as generic icons. The parts of the asset that are hardest to judge from a filename are exactly the parts you cannot see.
Resolution variants stack up
Download the same surface at 2K and 8K and you get two complete sets side by side. Useful, and also a doubling of visual noise in any tool that cannot group them.
Notice that none of these are complaints about Megascans. The structure is correct for a client that reads the JSON. The problem only appears when that client stops being the thing you browse with.
What each suffix means
Useful whether you wire these by hand or let something do it for you. The colour space column is where most people lose an afternoon: tagging a roughness map as sRGB is the single most common reason a Megascans surface looks subtly wrong in a render.
| Suffix | Channel | Colour space |
|---|---|---|
| _Albedo | Base colour | sRGB |
| _AO | Ambient occlusion | Raw |
| _Cavity | Cavity detail | Raw |
| _Displacement | Height, usually 16-bit or EXR | Raw |
| _Gloss | Glossiness — invert for roughness | Raw |
| _Metalness | Metallic mask | Raw |
| _Normal | Tangent-space normal, OpenGL green | Raw |
| _NormalBump | Bump-derived normal variant | Raw |
| _Opacity | Alpha / cutout mask | Raw |
| _Roughness | Roughness | Raw |
| _Specular | Specular level | Raw |
| _Translucency | Backlight transmission | sRGB |
Older Megascans surfaces ship _Gloss where modern shaders want roughness. They are
inverses, not synonyms. Plug a gloss map into a roughness input unchanged and your material comes out
mirror-polished where it should be matte. Invert it, or use the _Roughness map if the
asset has one.
Every other library uses its own suffixes, of course. There is a cross-library naming cheat sheet covering Poly Haven, ambientCG, Substance, Poliigon and the rest.
Three ways to make it browsable
Rename the folders with a script
Free, an afternoon. You get readable folder names, and it survives any tool you later switch to because it changes the files themselves. But there are no thumbnails, no EXR previews, no 3D previews and no export into a scene — and it breaks Bridge's own library view. If you get the script wrong on 200 GB, there is no undo.
Browse in Explorer or a general image manager
Free to cheap, minutes. Eagle, Adobe Bridge and similar tools will show you JPG previews and let you tag things. Good enough if you mostly need to eyeball surfaces before dragging them somewhere. They do not understand that eight files are one material, there are no EXR or FBX previews worth the name, and nothing lands in your 3D scene wired up.
Index it with a 3D-aware asset manager
Free tier or one-time paid, about ten minutes. Texture sets collapse into single tiles, EXRs and meshes get real previews, and clicking a surface builds the material in your renderer. Non-Megascans folders live in the same library. The cost is a dependency you did not have before, and the good ones are not all cross-platform.
Disclosure. I build one of those third-option tools, so the next section is me describing my own software. The first two options are real answers and plenty of people should stop there — I would rather say that than pretend otherwise.
Doing it with Kiosk
Kiosk indexes folders in place. It does not copy your Megascans into a vault, it does not rename them, and if you uninstall it the folder is exactly as you left it. What it builds is a local database beside your library: one row per asset, thumbnails rendered once, and a record of which loose files belong to the same texture set.
- Add the Downloaded folder as a source. Content Manager, pick a category, point it at the folder. The first pass generates thumbnails, including for the EXRs Explorer refuses to preview.
- Sets resolve automatically. The
<asset>_<res>_<Channel>pattern is exactly what the set detection groups on, so a surface becomes one tile with its channels attached. - Merging rules fold the variants. 2K and 8K downloads of the same surface, or a rock's LOD stack, can sit under one tile instead of cluttering the grid.
- Clicking exports a built material. With a live session open in Blender, Cinema 4D, Maya, Houdini or Unreal, a surface arrives as a wired shader for your active renderer — not as seven files in a project folder.
Questions
Where does Quixel Bridge download Megascans to?
To the library path you picked when you first ran Bridge, with everything under a Downloaded subfolder. On Windows the default sits under your Documents folder, but most people move it to a fast drive. If you cannot find it, open Bridge and check its preferences — the library path is shown there.
Why are the Megascans folder names random letters?
Each Megascans asset has a short alphanumeric ID that is stable across renames and re-releases, and the folder is named after it. That is excellent for a database and hopeless for a human — "vlkgcgw" tells you nothing about whether it is a brick wall or a forest floor. The readable name lives inside the JSON file next to the textures, which is why a tool that reads that JSON can show you something Explorer never will.
Can I just rename the folders to something readable?
You can, and scripts to do it exist. Two cautions. First, Bridge may no longer recognise a renamed asset in its own library, so do it only if you have accepted Bridge is read-only. Second, renaming folders does not give you thumbnails, 3D previews or EXR previews — it fixes the naming problem and leaves the browsing problem untouched.
Do I need an internet connection to browse my downloaded Megascans?
Not with a local index. Once an asset manager has walked the folder and generated thumbnails, everything is served from a local database and the assets are read straight off your drive. This is the main practical advantage of a local library over a marketplace client — it keeps working on a plane, on a locked-down studio network, or when the service is down.
What about the LOD files cluttering everything up?
Megascans 3D assets ship a stack of LODs plus a high-poly source, so a single rock becomes eight FBX files in one folder. In a browser that merges variants under a single tile you see one rock with its LODs attached rather than eight entries. If you are organising by hand instead, the usual approach is to keep LOD0 and the high-poly and move the rest into a subfolder you exclude from indexing.
Does this work for assets that are not from Megascans?
Yes, and that is rather the point. A folder-indexing browser does not care who made the files. The same library can hold Megascans surfaces, Poly Haven HDRIs, your own scans and a decade of bought kitbash packs, which is something no vendor-specific client will ever do for you.
Ten minutes to index, and the first thing you will notice is how much of your library you had forgotten you owned. The Megascans folder is left exactly as it was — nothing is copied, moved or renamed.
Download the free edition