For those who don’t know the tool: Cargo is a desktop asset browser that connects to Blender, Unreal Engine, Cinema 4D, and more, so you can browse, download, and send models and materials straight into scenes without spreadsheet cosplay.
One app, two libraries, fewer tabs
KitBash3D made the app as the “front door” for discovering and importing its kits, with the bundled library concept now expanded to cover both catalogs.
Two previously separate collections now live side by side inside the same interface, with one sign-in and one search. The combined catalogue includes kits and models alongside scan-based materials, textures, and surface imperfections, all presented as a single system meant to keep structure and surface close together.
That unification also shows up in how content gets packaged. The app emphasizes a consistent pipeline based on OpenUUSDSD and MaterialX, aiming to keep hierarchies and instances intact while translating materials into native shader setups for the target renderer. This is a foundation-level rebuild rather than a cosmetic refresh.
The free starter pack is not tiny
A free account includes a curated set of assets you can browse and download without a credit card. That free set is described as 100 plus assets, and an independent count lists 483 total free items. Its a start :)
245 models, largely building and vehicle parts from two free kits plus a set of semi-abstract biomorphic forms. There are also 189 materials, including fabric, brick, and tile options, plus 44 textures of mostly geometric grids with additional bokeh and dirt textures.
If your day job involves pitching lookdev choices at 9am and shipping frames at 6pm, the free selection matters because it lets you test the pipeline end-to-end. You can confirm how the importer behaves, how instances land, how shader graphs translate, and how your render engine reacts to the material schema before you commit budget.
Search got smarter, and also weirder in a good way
The browsing experience leans hard on discovery features designed to reduce the number of times you type a noun and get punished for it. Smart Search supports natural-language descriptions like “dark industrial”, interpreting intent rather than matching exact keywords. Image Search lets you drop in a reference image and find assets that match its visual style. Show Similar pulls results that share visual DNA with the currently selected asset, encouraging variation hunting without restarting the search. Random Roll reshuffles results within your active filters to push controlled surprise when your brain has gone full beige.
On the surface, these read like creature comforts as they target the most annoying part of asset libraries: you know what you want, but you do not know what the library decided to call it. Natural language and visual matching try to bridge that gap, and the similar and random tools try to keep you moving when the first pick is close but not quite it.
This is also where the unified catalog changes behavior. Similarity searches and random rolls can traverse the combined library rather than staying fenced within a single vendor silo, so discovery sessions can jump between hard-surface set dressing and material detail work without switching apps or accounts.
One click import, persistent connections, and fewer ritual steps
The workflow pitch is straightforward: select an asset, then send it to your scene. The importer is organizing geometry into clean hierarchies and instances, reusing existing assets automatically, and translating materials directly into the native format of the chosen renderer based on render settings. The goal is predictable structure on arrival, so your outliner does not turn into a haunted attic.
The connection model matters as much as the importer. The app supports connecting to installed DCCs and then sending assets through a targeted connector, rather than relying on manual export and import steps for each move. A desktop-based app is available on Windows and macOS including Apple Silicon machines.
Supported host applications and versions are listed in current documentation. The app supports Autodesk 3ds Max versions 2021 through 2024 using a non-USD legacy plugin workflow. It supports Autodesk Maya versions 2024 through 2026. It supports SideFX Houdini versions 20 through 21, including render paths that reference MaterialX. It supports Unreal Engine versions 5.2 through 5.7 using official Epic Games Launcher builds, and it supports Blender versions 4.2 through 5.0 when downloaded from blender.org.
Render engine support is Redshift, OctaneRender, V-Ray, and Arnold. Blender is listed with Cycles and Eevee. Maya is listed with Arnold and Redshift. Houdini is listed with Karma, Mantra, Arnold, and V-Ray.
The practical takeaway is that the connectors and supported versions are specific, not vibes-based. If you live on a source-built Unreal branch or a newer 3ds Max version outside the supported range, you should expect friction and plan your testing accordingly. Also: USD is king here – it might be time to get on the train.
Pricing and membership tiers
Cargo 3.0 is free to download. Subscriptions are three main individual plans and a teams option.
Greyscalegorilla Library plan at $39 per month or $468 billed yearly, which includes 3,500 plus scanned and procedural materials, 1,000 plus models, 650 plus textures, and 600 plus HDRIs.
The KitBash3D Library plan at $59 per month or $708 billed yearly, and includes 20,000 plus textured models, 2,000 plus game ready assets, 300 plus hero props and vehicles, and 200 plus Substance Source materials.
And an Everything Bundle at $79 per month or $948 billed yearly. The Everything Bundle includes full access to every new release from both libraries under one subscription.
There are also Team plans at $99 per user per month billed annually with a four-seat minimum.
What to actually do with this on a deadline
Start with the free assets and run a full pipeline pass in a throwaway project. Test search with a mood phrase, then test Image Search with a real reference frame from your show bible. Send a small cluster of assets into your primary DCC, then verify the resulting hierarchy, instances, and material graphs. Render a quick turntable in your production renderer, then repeat the same asset in a second host app if your studio straddles multiple tools.
If you rely on 3ds Max, treat the legacy plugin note as a sign to double-check compatibility before you promise anything to your producer. If you rely on Unity, the end-of-life date for the older integration means you should map out alternatives now, not when the build breaks the night before a milestone.
Cargo 3.0 sells itself on momentum. The real win is not that it can download assets, every library can do that. The win is whether it reudces the number of tiny interruptions that burn your attention budget. Install, connect, search, send, render, repeat. Then decide if the time saved is real enough to justify the subscription tier you need.
https://kitbash3d.com/pages/cargo
https://kitbash3d.com/pages/pricing
// Quoted info
https://help.kitbash3d.com/en/articles/7833635-cargo-3-0-supported-3d-software-and-render-engines
