Using Mods

Modding your game, for users


Published: ?? by manavortex Last documented update: Jan 23 2024 by manavortex
This page will teach you how to manually install mods.
We strongly recommend using a mod manager. You have the following options:
Vortex Mod Manager (Nexus Mod Manager)
MO2 (Mod Organizer 2) (known from e.g. Skyrim and Fallout)
It is possible to mod your game fully manually (and in fact, many modders do exactly that), but you have to understand the stuff on this page. Mod managers will save you from that effort.

How to install mods

TL;DR: Your mods will not work unless you
  • make sure all files end up in the right folders
  • make sure to install all requirements (and their requirements)
When you fuck things up, hit up Troubleshooting or run mod remover and start over.
To see an Overview of mod folders, scroll down.

How do I mod?

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, by using Vortex, or by using Mod Organizer 2 with additional steps detailed here.
Regardless of your past experiences, the Nexus Mod Manager Vortex works reliably and well for modding Cyberpunk.

What are dependencies / requirements?

For more detailed information, see Users: troubleshooting requirements.
Unless a requirement is marked as optional, your mod will not work until you install all of them.
Some requirements have requirements of their own. Make sure to check.
Although Cyberpunk natively supports modding, this out-of-the-box support is limited in what it lets modders do. To allow 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 executable (.exe), they will break every time CDPR updates. 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. To learn more about this, check Core Mods explained.

Overview of mod folders

TL;DR: you can ignore this unless you want to understand how things work.
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.
To learn more about the individual frameworks, check Core Mods explained
REDmod directory: contains .archive mods (in subfolders)
Legacy directory: contains .archive mods and .xl files
Plugins like Cyber Engine Tweaks
Redscript mods (not the same as REDmod)
red4ext tweaks
- 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 << Folder for modders. Also, REDmod DLC lives here.

Installing and activating REDmod

If REDmod is not installed and activated, your mods in /mods will not load.
Loading a mod as REDmod means that Cyberpunk will precompile it to optimize load times — integrating it into the game's other files by adding it to the files under r6/cache.
By contrast, vanilla mods (from /archive/pc/mod) will be loaded individually and might add to your load times.
  • For instructions on how to install, see here.
  • For documentation on the Vortex installation toggle, 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.
If the mod contains only files inside the folder archives, you can un-REDmod-ify it by moving all of those files to archive/pc/mod.

Installing Mods

You can install mods via Vortex or manually. There are upsides and downsides to each — however, for beginners, we recommend using Vortex.
If you had terrible experiences with Vortex for other games, be assured: Cyberpunk integration is working extremely well. Maybe give it another chance?

Manual 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. To find out what that means, read on.

Mod format: REDmod or vanilla?

As a rule of thumb, a REDmod is a different way of packaging the files, which will cause it to be loaded into the games by a different mechanism. Here is how you can tell the two apart:
Vanilla mod (packed correctly)
is in a folder named after the mod
might be inside an extra folder
has an info.json
has a subfolder archives or tweaks at the top level
contains any of the folders - archive - bin - r6 with files nested under them
Is packed with one level of nesting (info.json is in top level folder)
Has multiple levels of nesting
Manual install instructions: Extract the folder ModName into Cyberpunk 2077/mods
Manual install instructions: Merge the folders archive, bin, r6 into the folders with the same names directly in Cyberpunk 2077

Mod format: a collection of loose files

Some mods (especially older ones) are just a loose collection of files without any folder structure:
In this case, it's up to you and the mod's install instructions to put the files into the right game folders.
As a rule of thumb: unless specified otherwise,
  • archive files go into /archive/pc/mod/
  • .xl files go into /archive/pc/mod/
  • .reds files go into /r6/scripts/
  • .tweak or .yaml files go into /r6/tweaks/
  • .lua files go into a subfolder of /bin/x64/plugins/cyber_engine_tweaks/


If you have problems with Vortex, check the corresponding section of the guide.
For everything else, this wiki has a dedicated troubleshooting page with step-by-step instructions for pretty much every common problem. 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).