❔Users: Modding Cyberpunk 2077
Modding your game, for users
How to install mods
TL;DR:
The first thing you will be told on Discord is to read this guide.
When installing a mod, make sure to install all of its dependencies. You will find a list on the Nexus description tab under "Requirements".
If you do not do this, your mod will not work.
You need to enable REDmod. Without it, most of your mods will not work.
You mod Cyberpunk 2077 by adding files to your game directory. There is no need to overwrite base game files, since the game natively supports modding.
The game directory is the toplevel folder of your game install.
Unless you changed the default settings, it will be installed to:
STEAM
C:\Program Files (x86)\Steam\steamapps\common\Cyberpunk 2077\
GOG
C:\Program Files (x86)\GOG Galaxy\Games\Cyberpunk 2077\
You can install mods by hand or by using Vortex.
Dependencies / Requiremends
Although Cyberpunk natively supports modding, this out-of-the-box support is extremely limited. To allow modders greater freedom, a number of frameworks have been created to allow e.g. adding items, influencing the weather, or add flying cars.
Since this kind of mod interacts with the game's code on such a fundamental level, they are prone to breaking whenever CDPR changes their API. This is the reason why game updates break mods — we recommend to turn off auto-update and manually upgrading once the frameworks you need have been brought up-to-date.
Unless they are marked as optional, you have to install the dependencies, and their dependencies as well.
If you don't, then your mod will not work.

Overview of mod folders
This list is supposed to give you an overview of which files go where. It is not a bucket list of things you have to install.
- archive
- pc
- mod << .archive files from non-REDmods go here
- bin
- x64
- plugins << Cyber Engine Tweaks goes here
- mods << REDmods go here
- r6 << redscript folder
- tools
Installing and activating REDmod
If REDmod is not installed and activated, your mods will not load.
For instructions on how to install, see here.
For instructions on how to activate it, see here for GOG and here for Steam and Epic.
REDmods are installed in Cyberpunk 2077\mods
, where every mod has a subfolder with an info.json
.
Depending on your other mods, you might require cybercmd.
Installing Mods
You can install mods via Vortex or manually. There are upsides and downsides to each — however, for beginners, we recommend using Vortex.
Vortex
What does Vortex do and should I use it?
If you had terrible experiences with Vortex for other games, be assured: Cyberpunk integration is working extremely well. Maybe give it another chance?
Vortex is a mod manager which will automate almost everything that you can fuck up when installing by hand. You will be able to see at first glance if a mod has been updated, and you can uninstall/delete your mods without losing data.
Once Vortex is installed, you can add mods directly from Nexus. The downloaded files will be kept inside the staging directory rather than in the game directory itself; you need to install, enable and deploy them if you want them to become active. Fortunately, this process is extremely simple.
0. Download and login
Download the mod manager from Nexus, then log in to your Nexus account.
Set a Mod Staging folder (if it doesn't ask you, open Settings/Mods). This is where Vortex stores its files, so do not put it into the game directory.
Add Cyberpunk 2077: the executable is in the game directory under
/bin/x64/Cyberpunk2077.exe
1. Install a mod
On the mod's page, click the "Vortex" button under "Download":

If there isn't one, browse to the "Files" tab and look for the "Mod Manager Download" button.

If neither of these options are available, the mod author has chosen not to support Vortex. You can still try to download the archive, then drag and drop it on the running Vortex client.
If that doesn't work, you have to install it by hand.
2. Enabling
By default, mods you install via Vortex will be disabled. To add them to Cyberpunk, you need to enable them.

3. Deploying
Instead of cluttering your game directory, Vortex keeps everything in its staging folder until you're good to go. Here's how you give it the go:
launch the game via Vortex
hit the deploy button.

Vortex will give you an error message if any of your mods couldn't be deployed successfully.
4. (optional) Deactivate REDmod conversion
You should only do this if you run into problems with your mods. By default, this setting works fine.

5. Troubleshooting
For problems that are related directly to Vortex, you can use Nexus support or join our Discord and find (volunteer) help in the #vortex-support channel.
anual install
"Manual install" is a rather glorified term for "extracting the downloaded archive into your game directory". However, you have to make sure that the right files end up in the right folders.
You can inspect the file structure by simply opening the downloaded file, or by using this feature on Nexus (unless a mod author has disabled it):

The file structure is different for REDmods and non-REDmods. Mod authors usually tell you which file is which, though.
REDmod:
Extract the entire folder into /mods/
. You should have /mods/ModName
afterwards.

Non-REDmod
In your archive, find the folders corresponding to this overview and extract them directly to your game directory. Their content will be added to the already existing files, overwriting anything that needs to be replaced.

Anything else
Some mods are just a loose collection of files and it's up to you and the mod's install instructions to put them in the right place.

As a rule of thumb: usually, but not always…
.archive
files go into/archive/pc/mod/
.xl
files go into/archive/pc/mod/
.reds
files go into/r6/scripts/
.
lua
files go into a subfolder of/bin/x64/plugins/cyber_engine_tweaks/
Troubleshooting
If you have problems with Vortex, check the corresponding section of the guide.
For everything else, this wiki has a dedicated troubleshooting page that has solutions to many common problems. If that doesn't cut it, you're welcome to find us on Discord in the #mod-troubleshooting channel (but your first answer will be a link to that guide).
Last updated