The 30-second version. Automotive’s asset problem is a clock meeting a network you don’t control. Every model year the range is re-shot — increasingly rendered rather than photographed — and the outgoing year has to stop being marketed, except it lives on across hundreds of independent dealer sites and listings. Underneath sits a combinatorial explosion: model × trim × colourway × wheel × angle means one vehicle is thousands of images, which is why so much of it is now 3D and CGI. On top sit two constraints most industries never meet: a trim or claim legal in one market isn’t in another, and launch imagery is embargoed until reveal. The payoff is one approved, current, market-correct set that dealers self-serve — and a clean way to retire the year that just ended.
This page is the automotive asset problem, not a ranking. Because the imagery is published mostly by dealers, the tools that feed them are the ones we test in our brand portal software ranking; because so much of the range now exists as renders, our 3D asset management ranking covers whether a library can actually hold and preview those files; and because a trim or claim has to be gated by market and by reveal date, our granular permissions ranking is the third leg.
The asset problem in automotive
Start with the clock. A model range is re-shot on a cycle, and when the new model year lands the previous one has to come out of circulation — not be archived quietly, but genuinely stop appearing in market. That is where the trouble starts, because the imagery isn’t on your channels. It is on hundreds of dealer sites, third-party listings, local press ads and forecourt screens, each maintained by a business you do not employ. The failure mode is specific and it is expensive: last year’s car marketed as this year’s. That isn’t only an aesthetic problem — when the outgoing car’s wheels, lights or interior are the ones a buyer sees, the spec shown may not be the spec sold, and that is a compliance conversation rather than a tidiness one.
Now the network. It behaves like franchising: dealers and distributors are independent businesses with their own sites, their own agencies and their own deadlines. They are not going to wait on an email, and they are certainly not going to hunt through a shared drive. If the approved, current, market-correct set isn’t genuinely self-serve, the predictable thing happens — they keep using the zip they already have, or they photograph the car on their own forecourt in bad light. You cannot instruct your way out of this. You can only make the right asset the easiest one to reach.
Then the volume. One vehicle is not one shoot. Model × trim × colourway × wheel × angle, plus interior and exterior, plus detail crops, multiplies into thousands of images per nameplate — a combinatorial explosion no photography budget survives. That arithmetic is exactly why the industry moved to CGI and 3D configurators: it is cheaper to build the car once as a model and render the combinations than to physically shoot them. The consequence for the library is that it now holds 3D source models and rendered stills alongside photography — and a DAM that treats a .glb or a .stp as an opaque blob behind a generic icon is storing half your range blind. The buyer’s test we apply in the 3D ranking is exactly that: can the tool preview the formats in the browser, or not?
Finally, two gates. Market variance: a trim, an engine or a claim available in one market isn’t available in another, so the assets themselves have to be permissioned by market rather than published globally and hoped over. And embargo: launch imagery exists, is finished, is loaded, and must not be visible until the reveal — a release-date problem that most industries simply do not have. Together they make automotive a permissions story as much as a distribution one.
Where a DAM saves money here
- Retire the outgoing model year cleanly. The asset lifecycle — ingest, approve, distribute, retire — is the whole job here, and automotive runs it on a schedule. One approved current set, with the superseded year pulled back rather than left to drift, so the network stops selling a car you no longer make. Fewer mis-sold specs, fewer corrections.
- Dealers self-serve instead of reusing last year’s zip. A brand portal gives every dealer, distributor and their agency the approved, current, correctly sized set on demand — ending the cycle of packaging and re-sending imagery to a network that will otherwise improvise.
- One master per combination, not a folder per dealer. Generating renditions from one approved master keeps the dealer site, the listing feed and the social cut the same car — without storing a dozen copies of every trim-and-colour permutation, which is where a combinatorial library becomes unmanageable.
- Gate by market and by release date. Granular permissions mean a market only sees the trims and claims it can actually sell, and embargoed launch imagery can sit loaded and ready without being reachable until reveal — instead of living in a separate secret folder that someone eventually shares.
How it plays out
An illustrative composite. The scenario below is not one named manufacturer — it is a composite of the patterns we see, built entirely from capabilities we have tested and published. No invented benchmarks.
Picture a brand with a handful of nameplates, sold in several markets, through a network of independent dealers. Each nameplate exists as a set of CGI source models plus rendered stills for every trim, colour and wheel, topped up with a small amount of location photography for campaigns.
The model year turns. New renders are approved and pushed out as a download link. Some dealers take it; many don’t, because their site is run by a local agency with its own backlog. Months later the outgoing car is still the hero image on a good share of the network, in a colour that was discontinued, on a wheel that is no longer offered — and the brand finds out from a complaint, not from a report. Meanwhile a market-specific trim leaks into a neighbouring country’s listing because the zip contained everything; and the next launch’s embargoed set is sitting in a folder called DO_NOT_SHARE, which is exactly the sort of folder that gets shared.
In a DAM, the new year’s set becomes the approved current version and the previous one is retired in a single move; because dealers pull from a portal rather than hoard a zip, the next thing they publish is the current car. Each market’s portal shows only what that market sells. The launch set is loaded ahead of reveal and simply isn’t reachable until its release date. The saving isn’t a percentage we can invent — it is the end of the outgoing model year selling under this year’s badge, the end of hand-delivering imagery to a network that never all takes it, and the end of a secret folder standing in for a permission. To weigh that against tool cost, our business-case guide counts search time, rework and the cost of waiting.
The capabilities that matter most here
1. A dealer portal you don’t have to staff
The decisive one. Dealers, distributors and their agencies self-serve the approved, current, market-correct set from a brand portal — correctly sized, on-brand — rather than waiting on a link. For a brand whose imagery is published almost entirely by other businesses, this is make-or-break; the tools built for it are in the brand portal ranking.
2. Model-year versioning and retirement
The clock needs a mechanism. You want one current approved version per combination, the ability to supersede the whole set at once, and a real restore path rather than a download-and-re-upload dance — the distinction we test in the version control ranking. Paired with a clean retire step from the asset lifecycle, that is how last year’s car actually leaves the market.
3. 3D and rendered-still handling
Because the range is increasingly CGI, the library holds 3D assets as well as images. The test is whether the tool previews the formats in the browser or files them as anonymous blobs — see the 3D asset management ranking and our guide to previewing 3D in the browser. Be clear about the boundary: we test DAM tools, including 3D preview and metadata fidelity — we do not test configurator platforms. The DAM holds and governs the assets; the configurator is a delivery surface that consumes them.
4. Permissions that gate by market and by date
Two gates, one mechanism. Access scoped per market so a trim or claim doesn’t travel where it can’t be sold, and release-date control so embargoed launch imagery can be staged in advance without being reachable — the fine-grained access control we test in the granular permissions ranking. Keeping the whole network on one look, meanwhile, is the same job a marketing-team DAM does for brand consistency, stretched across businesses you don’t own.
Buyer’s test: during a trial, turn the model year on paper. Load a new set for one nameplate, supersede the old one, and confirm that a dealer logging into the portal now sees only the current car, in the size their site needs, with no email from you — and that the retired set is genuinely gone from their view, not just re-sorted. Then load an embargoed launch set and a market-only trim, and check a dealer in the wrong market and the wrong week sees neither. Finally, drop in a .glb or a .stp and see whether it previews in the browser or turns into a grey icon. A tool that can’t retire a year, can’t gate by market and date, or can’t see your 3D is solving a fraction of the automotive problem.
FAQ
Why does an automotive brand need a DAM and not just a shared drive?
Because the imagery has to change on a clock and then stop being used by people you don't employ. Every model year the range is re-shot or re-rendered, and the outgoing year has to come out of circulation across hundreds of independent dealer sites, listings and local ads. A shared drive or an FTP drop can hand out files, but it has no way to mark which set is current for which market, no way to pull a superseded set back, and no way to stop a dealer publishing last year's car as this year's. That last one isn't only untidy - the spec shown may not be the spec sold.
What is the biggest DAM payoff for a car maker with a dealer network?
Getting the current, market-correct set to dealers without sending it. Dealers are independent businesses; they will not wait on your email, and if the approved set is hard to reach they will reuse the old zip or shoot the car on their own forecourt. A branded portal that always shows the current model year, in the market's spec, in the size the dealer's site needs, makes the right asset the easiest one to grab. The saving is the end of hand-delivering imagery to every dealer, and the end of last year's car being sold under this year's badge.
How is automotive different from manufacturing, which also has products and distributors?
The shape of the library is different. A manufacturer's problem is heterogeneity - one product carries photos, CAD, a spec sheet, packaging and certification, each for a different audience, over a lifecycle measured in decades. Automotive is closer to the opposite: one asset type, vehicle imagery, exploding combinatorially across model, trim, colourway, wheel and angle, on a short model-year clock, pushed through a network the brand does not employ. One is many kinds of file per product; the other is thousands of variants of one kind of file, with an expiry date on them. We keep the two as separate pages for that reason.
We already have a 3D configurator. Do we still need a DAM?
Usually yes, because they do different jobs. A configurator renders and presents combinations to a shopper; it is not where the source 3D models, the approved rendered stills, the market permissions or the model-year history live. Those are library problems, and a configurator is a delivery surface - in practice the two sit next to each other, with the DAM holding and governing the assets the configurator consumes. Be aware of our limits here: we test DAM tools, including in-browser 3D preview and metadata handling, and we do not test configurator platforms. We can tell you whether a library will hold and serve your 3D models and rendered stills; we cannot tell you which configurator to buy.
Which capability matters most for automotive?
Two, and they are joined: a dealer-facing portal, and permissions that gate by market and by release date. The portal decides whether the network uses your approved current set or something of its own. The permissions decide whether a trim or a claim that exists in one market can leak into another, and whether launch imagery stays down until the reveal. Search, renditions and 3D preview all matter, but for a brand whose imagery is published mostly by independent businesses, under an embargo and against a model-year clock, self-serve distribution plus market and release gating is the pair that decides it.
Sources & references
- Brand portal software ranking and brand portal — the external, self-serve distribution to an independent dealer network that is the core automotive job. July 2026.
- 3D asset management ranking, 3D assets and previewing 3D in the browser — the in-browser preview test for .fbx, .glb/.gltf, .obj and .stp/.step that decides whether a library can hold a CGI range. Scope note: this is DAM testing, not configurator testing. July 2026.
- Granular permissions ranking — folder- and role-level access control, the mechanism behind market gating and embargoed launch imagery. July 2026.
- Version control ranking and asset lifecycle — superseding and genuinely restoring a version, and the retire step that takes an outgoing model year out of circulation. July 2026.
- Rendition and the DAM for marketing teams ranking — per-channel sizes from one master, and holding one look across a network of businesses you don’t own. July 2026.
- DAM business-case guide — sizing search time, rework and the cost of waiting against tool cost.
The portal, permissions, versioning, rendition and 3D-preview capabilities are drawn from our testing and reviews; the composite brand invents no manufacturer and no numbers, and we do not test configurator platforms, per how we source claims. See how we test.