Quixel Bridge is winding down. Your Megascans are still on your drive.

Nothing you downloaded has been taken away. Bridge still exports its local cache, but it is no longer where new Megascans come from — that is Fab now. Fab covers Unreal Engine well and the rest of the industry thinly, with no Houdini or Marmoset path and no offline browsing. If you work outside Unreal, the gap you are feeling is a local browser gap, not a content gap, and it is filled by a folder-indexing asset manager rather than by another storefront.

What actually changed

Quixel Bridge was two products wearing one coat. It was a storefront for a single vendor's scan library, and it was a local browser that knew how to push those files into fifteen different applications with the material already assembled. Most people only noticed the first half. The second half is the half they miss.

When Epic folded Megascans into Fab, the storefront moved and the browser did not come with it. Fab is a marketplace with an excellent Unreal Engine integration; it was never designed to be the thing you alt-tab to while lighting a shot in Houdini. The export plugins that made Bridge quietly indispensable across the rest of the industry were not rebuilt, and the community threads asking for them have not turned into releases.

So the honest framing is not "Bridge died, find a new Bridge." It is: the acquisition half has a clear successor, the browsing half has none, and those two halves now need two different tools.

Where each tool stops

Fab and a local browser are not competing products, and the table below is not a scorecard. Fab acquires assets; a local manager browses them. The only reason to put them side by side is that Bridge used to do both. I have used Kiosk as the example in the right-hand column because it is the one whose behaviour I can state precisely.

compiled 20 September 2026 from public documentation and community reports — verify anything load-bearing before you act on it

The last two rows matter most. No local browser can get you a single new Megascans asset — that is Fab's job and it will stay Fab's job. What a local browser does instead is treat Megascans as just another folder, alongside your Poly Haven downloads, your studio's scanned props and the kitbash packs you bought in 2019 and never opened again.

Four realistic ways forward

Ranked by effort, not by preference. Two cost nothing and one is genuinely the right answer for a lot of people.

1. Keep Bridge installed and treat it as read-only

Costs nothing and changes nothing. Bridge still exports what it has cached. This is the right answer if Megascans is the only library you use and Unreal is not your target application — right up until an OS or DCC update breaks a plugin nobody is maintaining any more. Fine for now; not a plan.

2. Move to Fab and accept the narrower surface

The correct answer for Unreal-first work, and the only route to new Megascans content. Outside Unreal you are back to downloading a ZIP and wiring textures by hand, and there is no offline browsing of what you already have. Necessary for acquisition, incomplete for browsing.

3. Organise the folder yourself

Rename the asset-ID folders to readable names with a script, then browse them in Explorer with a preview handler, or in a general image manager such as Eagle or Adobe Bridge. Free, transparent, and genuinely enough for some people. You still get no 3D preview, no EXR thumbnails and no export into a scene — and if you get the script wrong on 200 GB there is no undo.

4. Index the folder with a local asset manager

Point a dedicated browser at the Megascans folder and let it generate thumbnails, detect the texture sets and push them into your scene with the material already built. Kiosk and Connecter both do this; they differ in platform support, price and which renderers they wire up. Connecter runs on Windows and macOS and reaches more applications; Kiosk runs on Windows and goes deeper into renderer-specific material graphs. Most setup, closest to what Bridge felt like.

Pointing a local browser at your Megascans folder

Written for Kiosk because that is what I can describe exactly, but steps one and three apply to any indexing asset manager. Nothing here modifies the Megascans folder.

1. Find the Downloaded folder. Bridge stores assets in a library root you chose at install time, with everything under a Downloaded subfolder split into 3d, 3dplant, surface and atlas. If you cannot remember where you put it, Bridge shows the path in its own preferences.
2. Add it as a source. Open the Content Manager, pick a category and add that folder. The app walks it, records what it finds and starts generating thumbnails. Nothing is copied, moved or renamed — the index points at the files where they already are.
3. Let the texture sets resolve. Megascans files are named <asset>_<resolution>_<Channel>, which is exactly the pattern set detection groups on. An eight-file surface collapses into one tile with its channels attached rather than eight loose images.
4. Connect the application you actually work in. Install the plugin from the Plugin Manager and launch from inside Blender, Cinema 4D, Maya, Houdini or Unreal. Clicking a surface now builds the material for your active renderer instead of dropping loose textures in your project.

There is a longer, more folder-level version of this in how to browse a downloaded Megascans library offline, including what the download folder looks like inside and why Explorer handles it so badly.

Questions