Mod Folder Anatomy in Assetto Corsa Cars Tracks Skins and Apps

Content Manager hides a lot of complexity, but the filesystem underneath Assetto Corsa is still the source of truth. When you understand the mod folder anatomy, you can spot a bad archive in seconds, fix nested zip mistakes, and explain problems clearly in Discord threads.

This complements our install car mods and install track mods guides.

The content directory is the hub

Most player-added material lives under content/ with subfolders such as cars, tracks, skins, and often apps for extensions that integrate with CM or the game UI. Think of each immediate child folder under content/cars as one car package with its own internal layout.

When a download page says “extract into content,” it should merge into those folders—not create a random new root called mods unless the author explicitly designed that structure.

Cars: what “complete” usually means

A typical car folder contains 3D and physics data (often data.acd or loose data files), UI metadata (ui_car.json or legacy ini files), textures, and audio references. Missing UI metadata might mean the car never appears in selection lists. Missing audio banks might mean silent engines.

If you see two car folders that look like duplicates with _v2 suffixes, you probably installed an update without removing the old package. That invites conflicts.

Tracks: LOD and data folders

Tracks are larger and more varied. Some ship with multiple layouts as sub-layouts inside one package. Others incorrectly pack layout folders in ways that confuse first-time installers. If CM lists the track but loading hangs, suspect folder naming, missing collision meshes, or incompatible CSP features tied to that venue.

Skins: where liveries belong

Skins generally live under the car’s skin directory, not as a separate global folder you invent. A skin that shows in CM but renders wrong in-game may have wrong texture naming or dds format issues. Keep skin packs from trusted sources on AC Supply skins to reduce broken archives.

Apps: read the readme

Apps vary wildly—some add HUD elements, others extend CM. Always read the author readme because install paths differ. Blind drag-and-drop into apps without reading is how people duplicate plugins.

Nested zip failure mode

The classic broken archive contains content/cars/mycar inside another folder named after the download site. When extracted naively, you end up with content/cars/somefolder/mycar. Fix by moving mycar up one level so it sits directly under cars.

Permissions and read-only flags

On Windows, occasionally folders copied from external drives arrive read-only or blocked by inherited permissions. If CM cannot update thumbnails or unpack temp files, clear read-only on the content subtree and ensure your user owns the folder. This is rare but real on hand-migrated libraries from old PCs.

FAQ

Should I manually merge mods?
Only if you know exactly why. Otherwise prefer clean install of one version.

Does antivirus matter?
Yes—quarantined partial extracts create “half cars.” See our false positives article.

Why does CM show a mod grayed out?
Often disabled, conflicting, or structurally incomplete—inspect details.

Folders are boring until they save your evening. Learn the anatomy once, and every future install gets faster.