Assetto Corsa EVO is still in Early Access, and its modding support is built around the official Assetto Corsa EVO SDK Editor Tool rather than loose files dropped into a content folder. If you have a packed car mod, it comes as a single .kspkg file, and it goes into a specific mods folder inside your Saved GamesACE directory. Nothing from the original Assetto Corsa carries over, because EVO cars are built and exported with EVO’s own tools.
Below is what actually works right now, where the file goes, and what to check when a car refuses to show up or crashes your garage.
What modding actually means in EVO right now
The SDK Editor Tool started life as a car editor. External liveries got added on top of that afterwards, and Kunos has said track tools are planned for later, not available yet. That order matters, because it tells you what kind of mod you should expect to find and use at any given point. Before you go looking for a track mod or some other content type, check Kunos’s own release notes for the SDK rather than assuming a feature exists just because it worked in the original game.
This is a young toolset built step by step, so treat any claim about “full mod support” with some skepticism until you’ve confirmed it against the current SDK documentation.
Why your old Assetto Corsa mods won’t work here
If you’ve got a folder full of cars from the original Assetto Corsa, none of them will simply drop into EVO. The original game’s mod tools, and the file structure they produce, were built for that engine and that content pipeline. EVO cars are compiled and exported specifically through the EVO SDK, which produces a different package format entirely. There’s no conversion step, no workaround folder trick. A car has to be built for EVO from the start.
Installing a packed car (.kspkg)
A finished, packed car mod for EVO is a single file ending in .kspkg. SDK users quote the documentation as saying this file goes straight into the mods folder, no subfolders, no renaming.
- Open your user profile folder and go to
Saved Games. - Open the
ACEfolder inside it. - Look for a folder called
mods. If it isn’t there, create it yourself. - Copy the
.kspkgfile directly into thatmodsfolder. - The full path looks like
C:Users<username>Saved GamesACEmods<file>.kspkg. - Start the game and check the car list under the brand the mod uses.
Don’t unzip or unpack the file yourself. It’s meant to stay as one packed file sitting directly in that folder.
If the car doesn’t show up: check the log
Once you’ve installed a .kspkg file, the next step is finding it in the car selection screen, usually filed under whatever brand name the mod uses rather than under a generic “mods” category. If it’s missing, don’t assume the game ignored the file silently. SDK discussions point squarely at a badly built or badly packed file as the usual cause.
Open log.txt in Saved GamesACE. The game writes out what it found when scanning the mods folder, including whether it recognized the package at all. That log is the fastest way to tell the difference between “the file is broken” and “the file never loaded.”
No thumbnail or crashes after adding a car
Two problems come up often with packed cars: the car shows up in the list with no thumbnail image, or the game crashes after you’ve added the modded car to your garage. Neither of these is something you can usually fix on your end, since they come from how the mod itself was built.
To rule a specific mod out as the cause of instability, do this:
- Close the game.
- Remove the suspect
.kspkgfile from themodsfolder. - Restart Assetto Corsa EVO and see if the problem is gone.
If the crash stops, you’ve confirmed the mod is the issue, and you should wait for an updated version of that package rather than try to patch it yourself.
Reporting a crash to Kunos
If you want to report a crash rather than just work around it, Kunos’s own support notice asks for two things from your Saved GamesACE folder: the log.txt file and the crashdumps folder. Grab both before you do anything else.
Their general advice for startup problems is to delete that ACE folder entirely, but that wipes out your setups and replays along with whatever was causing the issue. Copy the folder somewhere safe first, then delete the original if you need to. You can pull your setups and replays back out of the copy afterward.
A word on ripped official content
Some car mods floating around are just official EVO cars with a livery or a few tweaked parameters, repacked and redistributed. Kunos staff have stated plainly that modifying and redistributing official game content goes against the EULA. A mod built that way isn’t something you should rely on staying available, and it’s not something you want to be the one distributing either. Stick to mods built from original content through the SDK.
Questions people ask
Can I use mods made for the original Assetto Corsa in EVO?
No. EVO cars are built and exported with EVO's own SDK tools, and the original game's mod format doesn't work with it at all.
Where exactly does the .kspkg file need to go?
Directly into the mods folder inside Saved GamesACE in your user profile, for example C:Users\Saved GamesACEmods.kspkg. Create the mods folder yourself if it isn't there already.
Why is my installed car missing from the car list?
Usually the .kspkg file is badly built or packed. Check log.txt in Saved GamesACE, since the game records what it found when it scanned the mods folder.
Is it safe to delete the ACE folder to fix startup issues?
It can fix the problem, but it also deletes your setups and replays along with log.txt and crashdumps, so copy the folder somewhere safe before you delete anything.
Browse all Assetto Corsa EVO mods on CrashMods
