# Using Mods

{% content-ref url="user-guide-troubleshooting" %}
[user-guide-troubleshooting](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/user-guide-troubleshooting)
{% endcontent-ref %}

## Summary

**Published:** Jun 15, 2023 by [mana vortex](https://app.gitbook.com/u/NfZBoxGegfUqB33J9HXuCs6PVaC3 "mention")\
**Last documented update:** January 18, 2026 by [minnierylands](https://app.gitbook.com/u/VSIYzNHUyRPaBCk2ExHhQzpPfo82 "mention") 

This page will give you a brief introduction of **how** mods work and how to install them.

***

### Wait, this is not what I want!

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td>I need help installing Cyberpunk!</td><td><a href="users-modding-cyberpunk-2077/getting-started">getting-started</a></td><td><a href="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2FOXtgOQyMEnSLBe58cglz%2Finstalling_cyberpunk.png?alt=media&#x26;token=580541c2-e919-4abc-ba1d-2a239128e20a">installing_cyberpunk.png</a></td></tr><tr><td>I need to troubleshoot my mods!</td><td><a href="user-guide-troubleshooting">user-guide-troubleshooting</a></td><td><a href="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2FCOMLdi3vWsg4QVacquWX%2Ftroubleshoot_mods.png?alt=media&#x26;token=dd99d9b9-9c24-45dd-8909-4d51e63149b3">troubleshoot_mods.png</a></td></tr><tr><td>I want to create mods!</td><td><a href="../modding-guides/getting-started-making-mods">getting-started-making-mods</a></td><td><a href="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2FVY1mKEN9adlq0ql07MdF%2Fcreating_mods.png?alt=media&#x26;token=67e9692a-dc19-4b0f-842c-defea01a2433">creating_mods.png</a></td></tr></tbody></table>

***

## Installing Mods

{% hint style="danger" %}
We **strongly recommend** using a mod manager. Manual modding is only recommended for **advanced users**.
{% endhint %}

You mod **Cyberpunk 2077** by adding files to your [**game directory**](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/users-modding-cyberpunk-2077/the-cyberpunk-2077-game-directory). The game doesn't need any complicated workarounds to mod, and the core mods will do all the heavy lifting.

You can install mods via [mod manager](#mod-manager-options) or [manually](#manual-install). There are upsides and downsides to each — however, **for beginners,** [**we recommend using Vortex**](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/users-modding-cyberpunk-2077/getting-started/vortex-mod-manager).

Overall, your mods will not work unless you

* Put all the files **exactly** into the [correct place](#mod-folders-by-file-extension)
* Make sure to install **all** [requirements](#what-are-dependencies-requirements) <sub>*(and*</sub><sub>*&#x20;*</sub><sub>***their***</sub><sub>*&#x20;*</sub><sub>*requirements, too)*</sub>
* Have REDmod **enabled** <sub>*(*</sub>[<sub>*REDmod*</sub>](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/users-modding-cyberpunk-2077/redmod) <sub>*exclusive)*</sub>

{% hint style="warning" %}
If you're on Linux/Steam Deck, you need to follow [this guide](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/users-modding-cyberpunk-2077/modding-on-linux) to the letter
{% endhint %}

## Mod Manager Options

Below you can find links to guides for all three supported mod managers for Cyberpunk 2077.&#x20;

{% hint style="success" %}
If you had terrible experiences with Vortex for other games, be assured: Cyberpunk integration is working extremely well. Maybe give it another chance?
{% endhint %}

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><h4><strong>Vortex</strong></h4></td><td align="center">Recommended for most mod users. Easy to use.</td><td data-object-fit="contain"><a href="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2FmB1FyJx4AUGHceEszzYp%2Fvortex-logomark.png?alt=media&#x26;token=bf7348c2-bed3-440f-8489-16ee3bca3b6c">vortex-logomark.png</a></td><td><a href="users-modding-cyberpunk-2077/getting-started/vortex-mod-manager">vortex-mod-manager</a></td></tr><tr><td align="center"><h4><strong>Mod Organizer 2</strong></h4></td><td align="center">Recommended for anyone already used to MO2. More complicated to use.</td><td data-object-fit="cover"><a href="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2F49p7x4c6SrpcwwRiVuCn%2F37225415.png?alt=media&#x26;token=52387763-e10c-4fba-9edd-99803bf0f60c">37225415.png</a></td><td><a href="users-modding-cyberpunk-2077/getting-started/mo2-mod-organizer-2">mo2-mod-organizer-2</a></td></tr></tbody></table>

***

### Manual Install

"Manual install" is a glorified term for "extracting the downloaded archive into your game directory".

{% hint style="danger" %}
**You have to make sure that the right files end up in the correct folders.** \
This method is very error prone, which is why we recommend using a mod manager.&#x20;
{% endhint %}

You can check the file structure by opening the downloaded file, or by using this feature on Nexus:

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-25a41c8a1a0c9c2b142cc253bc6adb9c0417c095%2Finstalling-nexus-preview-file-structure.png?alt=media" alt=""><figcaption><p>Some mod authors have this disabled, meaning you won't see this option on the mod page.</p></figcaption></figure>

{% hint style="warning" %}
The file structure is different for REDmods and non-REDmods (often referred to as "`legacy`" mods). Mod authors usually tell you which type their mod is. To lean what the difference is, [read here](#whats-the-difference).
{% endhint %}

***

### What Are Requirements?

A requirement (sometimes called "dependencies"), are mods that other mods rely on.&#x20;

This means the mod you want to download **will not work** if you don't **download the listed requirements first**.&#x20;

For more detailed information, see [requirements-explained](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/user-guide-troubleshooting/requirements-explained "mention").

{% hint style="danger" %}
TL;DR:

Unless a requirement is marked as optional, **your mod will not work** if it is not installed.

Some requirements have requirements of their own. Make sure to check.
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-da89e3ec099b5f6e1470fa31ee4bdad574b4249a%2Fmod-requirements.png?alt=media" alt=""><figcaption><p>You should be checking for the requirements of the requirements, too. You gotta catch 'em all!</p></figcaption></figure>

***

## The Core Mods

{% hint style="info" %}
To learn more about this, check [core-mods-explained](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/core-mods-explained "mention").
{% endhint %}

Cyberpunk 2077 offers limited out-of-the-box support via REDmod. To allow greater freedom, a number of **core mods** have been created — without them, we couldn't add items, influence the weather, or have flying cars.

{% hint style="warning" %}
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 — although you can [**turn off auto-update**](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/users-modding-cyberpunk-2077/users-downgrading-preventing-auto-updates) and only update your game once mods have updated.&#x20;

\
After each patch, you can find a post on our [Discord](https://discord.gg/redmodding) that is kept up-to-date as the modders update their tools.&#x20;

Be aware that **once all the core mods have updated**, you will *not* recieve support until you have **updated your game and all your core mods**.
{% endhint %}

### Overview of Mod Folders

{% hint style="info" %}
TL;DR: you can ignore this unless you want to understand how things work, or want to install mods manually.
{% endhint %}

This is supposed to give you an overview of which files go where. It is **not** a bucket list of things you have to install.

{% tabs %}
{% tab title="Mod folders explained" %}

<table><thead><tr><th width="256">Directory</th><th>explanation</th></tr></thead><tbody><tr><td>\<code>mods</code></td><td><a data-mention href="users-modding-cyberpunk-2077/redmod">redmod</a> directory: contains .archive mods (in subfolders).<br>Contains only a .stub file if empty.</td></tr><tr><td>\<code>archive\pc\mod</code></td><td>Default mod directory: contains .archive mods and .xl files in <code>legacy</code> (non-REDmod) format. Most of your mods should be here.</td></tr><tr><td>\<code>bin\x64\plugins</code></td><td>Plugins like <a href="https://app.gitbook.com/o/-MP5ijqI11FeeX7c8-N8/s/-MP5jWcLZLbbbzO-_ua1-887967055/"><strong>Cyber Engine Tweaks</strong></a> and RadioExt</td></tr><tr><td><code>\r6\scripts</code></td><td>Redscript mods (<strong>not</strong> the same as REDmod)</td></tr><tr><td><code>\r6\tweaks</code></td><td>red4ext tweaks</td></tr><tr><td>\<code>archive\pc\patch</code></td><td>Mod directory from before 1.3. Use <code>\archive\pc\mod</code> instead.</td></tr></tbody></table>
{% endtab %}

{% tab title="Mod folders by file extension" %}
As a rule of thumb, here's which files go where (unless the mod's instructions tell you otherwise):

<table><thead><tr><th width="200">File type</th><th>Folder path</th></tr></thead><tbody><tr><td><code>.archive</code></td><td><code>/archive/pc/mod/</code></td></tr><tr><td><code>.xl</code><br><code>.archive.xl</code></td><td><code>/archive/pc/mod/</code></td></tr><tr><td><code>.reds</code></td><td><code>/r6/scripts/</code></td></tr><tr><td><code>.tweak</code><br><code>.yaml</code></td><td><code>/r6/tweaks/</code></td></tr><tr><td><code>.lua</code></td><td>a subfolder of <code>/bin/x64/plugins/cyber_engine_tweaks/</code></td></tr><tr><td><code>.ini</code></td><td><code>engine/config/platform/pc</code></td></tr><tr><td><code>.script</code></td><td>part of a REDmod, can't be installed standalone</td></tr></tbody></table>
{% endtab %}

{% tab title="Mod folder structures" %}

```markup
- 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
  - scripts        << redscript mods (not the same as REDmod)
  - tweaks         << RED4ext tweaks (TweakXL / ArchiveXL)
- tools            << REDmod DLC lives here — only needed for making mods.
```

{% endtab %}
{% endtabs %}

***

## REDmod

{% hint style="danger" %}

#### Generally, you'll be told to avoid REDmod when possible. But why?

**Compatibility issues**\
REDmod was CDPR's attempt to standardize mod loading, but there were various compatibility issues with it, and it never quite took off. Most mod authors stick to "`legacy`" versions of mods.

**Load order**\
REDmods are loaded after everything else, so that format is simply not an option for mods that rely on being loaded at a certain point, like body mods.

**Vortex autoconvert**\
In theory, Vortex can automatically convert legacy mods to REDmod. In practice, that didn't help with any of the compatibility issues mentioned before, and even caused some of them.

#### **If you'd still like to know the difference, or there's a mod that only offers REDmod format and you cannot live without it, read on.**

{% endhint %}

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`.

{% hint style="info" %}
If your `/mods` folder is empty, you don't need this. For more information, see [#whats-the-difference](#whats-the-difference "mention") below.
{% endhint %}

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](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/users-modding-cyberpunk-2077/getting-started).
* For documentation on the Vortex installation toggle, see [here](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/getting-started/vortex-mod-manager#v2077-settings).
* For instructions on how to activate it, see [here for GOG](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/users-modding-cyberpunk-2077/getting-started) and here for [Steam and Epic](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/redmod/usage#steam-and-epic).

REDmods are installed in `Cyberpunk 2077\mods`, where every mod has a subfolder with an `info.json`.

{% hint style="warning" %}
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`.&#x20;

For a guide on the correct folder structure, [click here](#fixing-broken-mod-file-paths).&#x20;
{% endhint %}

***

### Mod format: REDmod or Legacy?

{% hint style="danger" %}

#### If in doubt, install the non-REDmod (`"legacy"`) format. To learn why, read below.

{% endhint %}

#### What's the difference?

All REDmods mods will be **preloaded** by `redMod.exe` before the game starts up. After a short delay, the mods will then be loaded as if they were part of the game itself — you're saving the startup delay on every savegame load.

<details>

<summary>REDmod when using Vortex</summary>

{% hint style="danger" %}

#### As of 2026, the Vortex "autoconvert" option **will break your mods**.&#x20;

In the 0.12.0 version of the Cyberpunk 2077 Vortex Extension, a bug was introduced that would **enable this toggle without warning**.&#x20;

Thankfully, version 0.12.1 of the extension has squashed that bug, but Vortex will not automatically acknowledge the new version. [You can get version 0.12.1 here](https://www.nexusmods.com/site/mods/196).

#### **How can I check my extension version?**

In Vortex, there's an "`Extensions`" tab on the left hand side. Click it.

Check what it says under "`Version`" for the "`Cyberpunk2077`" extension.

<p align="center"><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2FNkLg4pTgVT1qK2nIbXN8%2Fvortex_ex_2.png?alt=media&#x26;token=51885c9f-a62c-485e-acdb-8837cc820e69" alt="" data-size="original"></p>

If it says `0.12.1`, you're good to go!

If not, you'll need to click "`Remove`" on the extension.

[Click "Manual Download" on the top file from the extension's download page.](https://www.nexusmods.com/site/mods/196?tab=files)

Go back to your Vortex "`Extensions`" page

Drop the zip you just downloaded into the box that says "`Drop File(s)`"

<p align="center"><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2FBs8v9IgND47u2VFIlda3%2Fvortex_extension_page.png?alt=media&#x26;token=c6f92d86-9555-4b42-a7a7-b6414d15c285" alt="" data-size="original"></p>

You need to go back into your "`V2077`" settings and **turn the toggle off**!

Go to your "`Mods`" page in Vortex, press `CTRL + A` on your keyboard (you may need to click on one of your enabled mods first)

A bar should pop up at the bottom. Click "`Reinstall`". It shouldn't take too long!

<p align="center"><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2FwxLSHMvblsdt3g3KbAwj%2Fvortex_reinstall.png?alt=media&#x26;token=8cdb51bb-c1c4-4954-b89d-a8aec7b86ff8" alt="" data-size="original"></p>

You should now be free of the autoconvert bug.
{% endhint %}

Vortex will let you define load order for REDmods. To support compatibility, it offers you automatic conversion.

</details>

Here is how you can tell the two apart:

| REDmod                                                                                                                                                                                                                                                      | Legacy mod (packed correctly)                                                                                                                                                                                                                                                                                                                                          |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-3ac5770562e2d46db0d9040afc6cd6326a961a4a%2Finstalling-redmod-preview.png?alt=media" alt="" data-size="original"> | <img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-1e2587a4b5ee563625fc55e7c3b63e79bcb9be2d%2Finstalling-gift-wrapping.png?alt=media" alt="" data-size="original">                                                                                                             |
| is in a folder named after the mod                                                                                                                                                                                                                          | may be in an extra folder if packed incorrectly                                                                                                                                                                                                                                                                                                                        |
| has an `info.json`                                                                                                                                                                                                                                          | does **not** have an `info.json`                                                                                                                                                                                                                                                                                                                                       |
| <p>contains a folder with any of</p><p>- <code>archives</code></p><p>- <code>tweaks</code></p>                                                                                                                                                              | <p>contains any of the folders<br>- <code>archive</code><br>- <code>bin</code><br>- <code>r6</code><br>with files nested under them</p>                                                                                                                                                                                                                                |
| Is packed with **one** level of nesting (`info.json` is in top level folder)                                                                                                                                                                                | Has **multiple** levels of nesting                                                                                                                                                                                                                                                                                                                                     |
| <p><strong>Manual install instructions:</strong><br>Extract the folder <code>ModName</code> into <code>Cyberpunk 2077/mods</code></p>                                                                                                                       | <p><strong>Manual install instructions:</strong><br><strong>T</strong>he folders <code>archive</code>, <code>bin</code>, <code>r6</code> from the download must <strong>merge</strong> with the same folders in your <a href="users-modding-cyberpunk-2077/the-cyberpunk-2077-game-directory">game directory</a> (do <strong>not</strong> put the bin in the bin).</p> |

***

## Fixing broken mod file paths

{% hint style="info" %}
TL;DR:

Mod makers sometimes pack files incorrectly, causing mods to end up in the wrong places, which makes them not work

To fix it, you need to correctly path the contents of the zip file:

* `.archive` and `.xl` files go to `archive/pc/mod` folder structure.
  * For other files see [#mod-folders-by-file-extension](#mod-folders-by-file-extension "mention").

For detailed instructions on how to create the new zip, see below.

* You can drop the fixed zip you made into your mod manager to have it install properly.
  {% endhint %}

Sometimes, mod makers create strange paths for their mods. Sometimes, they delete the paths altogether *(even when Wolvenkit creates those paths for them)*. This can cause issues, especially when installing mods with a mod manager as the manager doesn't know where this mod is supposed to go.

{% hint style="warning" %}
Don't know which method you need to follow?

[I'm manually installing mods!](#manually-fixing-folder-paths-1)

[I'm installing mods through Vortex!](#fixing-folder-paths-in-vortex-1)

[I'm installing mods through MO2!](#fixing-folder-paths-in-mo2-1)
{% endhint %}

<p align="center"><strong>Always check the file contents before downloading a mod!</strong></p>

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-71e33083ea292720e07f5bce19c035a950905469%2FPreview%20File%20Contents.png?alt=media" alt=""><figcaption><p>Go to a mod's "FILES" tab on Nexus, then click "Preview File Contents".</p></figcaption></figure>

<div><figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-6f157e2c54943b4776840f3218b2545807ef7c17%2FPreview%20File%20Contents%20Popup%20Correct.png?alt=media" alt=""><figcaption><p>This is how mods <em>should</em> be packaged</p></figcaption></figure> <figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-e206ff52ce1f72216b2d2882be369f639253ea82%2FPreview%20File%20Contents%20Popup%20Incorrect.png?alt=media" alt=""><figcaption><p>This mod is badly packaged, and needs our help!</p></figcaption></figure></div>

{% hint style="success" %}
If the mod you've downloaded looks like the picture on the left. Great! You don't need to do anything. Enjoy your game!\
\
If not, keep reading... we've got work to do!
{% endhint %}

**You'll usually see a few types of mismatches of pathing:**

<div><figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-2521375744a483a33c3cb2e3cf0436478d620044%2Finstalling-other.png?alt=media" alt=""><figcaption><p>Scenario 1: Files without any folders</p></figcaption></figure> <figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-b5089c74dd82d3e247a6d5e552fadbb8b6dc0e44%2Fbadfilepaths2.png?alt=media" alt=""><figcaption><p>Scenario 2: Files inside non-game sub folders</p></figcaption></figure> <figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-46394abcf90bfb098b7789e4e6b2d74b6b71262d%2Fbadfilepaths1.png?alt=media" alt=""><figcaption><p>Scenario 3: Unnecessary first subfolder</p></figcaption></figure></div>

{% hint style="info" %}
To find out how to install the mod properly, you have to read the **mod's install instructions**. If that isn't clear enough, the following might help you.
{% endhint %}

All of these can cause a mod manager to get mixed up, or for you to manually install it wrong, so let's go through fixing these!

You can do these fixes in the file explorer or through Vortex/MO2 if you're using them.

{% hint style="warning" %}
If you get stuck at all along the way, come ask us in [#mod-troubleshooting on the discord](https://discord.com/channels/717692382849663036/788213273530335233). We wrote these guides, so we can help, I promise!
{% endhint %}

{% tabs %}
{% tab title="Manually Fixing Folder Paths" %}

<h4 align="center">Manually Fixing Folder Paths</h4>

1. Extract the `.zip`/`.rar`/`.7z` to your `Downloads` folder (or whichever folder you're working in).&#x20;

{% hint style="warning" %}
You might get an extra unnecessary folder depending on where you extracted the folder to. If you want it to extract straight into the Downloads folder, remove the extra folder at the end of the path so it looks something like this:
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-843b145c29b413a5f76c0296cf901c119cc25720%2Fextractbrokenfilepaths.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
In the case of Scenario 3 (pictured above), you can just move the folders out of the first unnecessary folder and continue from step 8 or 9.
{% endhint %}

***

2. You should now have the mod files inside your Downloads folder. \
   Locate the files you want to move and check their file extensions.

{% hint style="warning" %}
If you don't have file extensions turned on, you can check this part of the file to know what file it is:
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-e06e56f31aaf8653f816e0fbe998a64acfebb071%2Ffiletypecheckguidance.png?alt=media" alt=""><figcaption></figcaption></figure>

***

3. We need to create the correct file path. This is an `.archive` file, so it needs to go into `archive/pc/mod`&#x20;

{% hint style="info" %}
If you aren't sure where your file should go, check out [#mod-folders-by-file-extension](#mod-folders-by-file-extension "mention").
{% endhint %}

***

4. Create a folder by right clicking. Name it `archive`&#x20;

***

5. Double click the `archive` folder to open it.

***

6. Right click to create a new folder. Name it `pc`

***

7. Double click the `pc` folder to open it.

***

8. Right click to create a new folder. Name it `mod`

{% hint style="info" %}
For our .archive you should have a folder path like this now:
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-5301f27daef9a4c69bb4cb916236c1d00dc5bdf0%2Ffilepathforfixingbrokenfilepaths.png?alt=media" alt=""><figcaption></figcaption></figure>

***

10. Repeat this process for the [correct folder paths](#mod-folders-by-file-extension) for other file types if you have any.

***

11. Go back to the Downloads folder (or any subfolder that holds the files we need to move)

***

12. Select the files you want to move, then press CTRL + X (this cuts the files)

***

13. Navigate back to the mod folder we created in step 8, then press CTRL + V (this pastes the files)

{% hint style="info" %}
Your file and folder structure should now look like this:&#x20;
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-4b2ad2123d3cc11b270ef5c27a1e677afe656a44%2Ffixedmodfolderpath_endresult.png?alt=media" alt=""><figcaption></figcaption></figure>

***

{% hint style="warning" %}
If you're using a mod manager, skip this step and continue from the next one!
{% endhint %}

14. If you're manually installing, you can now copy paste the archive folder into the `Cyberpunk 2077` folder of your game installation. It will automatically merge with the existing folders.

***

15. If you're using a mod manager, right click the archive folder and turn it into a `.zip`/`.rar`/`.7z`. If you're just using Windows' own zipping system, the option might be hidden under `Send to -> Compressed (zipped) folder`.

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-e13b28b8779840b1ea5869bdd796c9d3d7cbf47e%2Fhowtomakezip.png?alt=media" alt=""><figcaption><p>Send to -> Compressed (zipped) folder, a visual guide.</p></figcaption></figure>

{% hint style="info" %}
You can name the newly created .zip to whatever you want, but it is **recommended** you name it something identifying, like the **original mod name**, so you can easily find the mod on Nexus. \
\
\&#xNAN;*Adding the mod to your mod manager this way means it won't be able to locate the mod on Nexus by itself, so naming it the same makes it easier for you in the future.*
{% endhint %}

***

16. You can now add it to your mod manager!

{% hint style="info" %}
For Vortex, drag the `.zip` to the bottom of the `downloads` page and drop it there.
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2FRV8xK2tNy21gWAZLG46x%2Fvortex_downloads_page.png?alt=media&#x26;token=d53cb7ac-45eb-4ff0-a9c5-5169b0567094" alt=""><figcaption><p>The section of the Vortex Downloads page where you can drop .zip files!</p></figcaption></figure>
{% endtab %}

{% tab title="Fixing Folder Paths in Vortex" %}

<h4 align="center">Fixing Folder Paths in Vortex</h4>

1. Press *"Mod Manager Download"* as you normally would.

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-9e14cb22c769bda3cbbf6746d25c85faaca5e104%2FVortex%20Step%200.png?alt=media" alt=""><figcaption></figcaption></figure>

***

2. Navigate to "Never Installed" in Vortex (on the "Mods" tab). You should see the mod you just downloaded here.

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-236d1ef21a48c30b4ed026c3472a4f9eaeb2b329%2FVortex%20Step%201.png?alt=media" alt=""><figcaption></figcaption></figure>

***

3. Click "Install"

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-d9cd17a02fb9e96dc30ca0346b3a48d664d21ff0%2FVortex%20Step%202.png?alt=media" alt=""><figcaption><p>We don't want to enable this mod yet! It will make it more difficult in the future if we do!</p></figcaption></figure>

***

4. You should get a popup that says "You have reached the fallback installer!". \
   Click "Yes, Install to staging anyway".

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-06809f435030f5fa9802ce6c15f44c001bf24baa%2FVortex%20Step%203.png?alt=media" alt=""><figcaption></figcaption></figure>

***

5. Right click on the mod name

***

6. You should then get another pop-up that says "Mod installed but may need manual adjustment!". Click "Understood!"

{% hint style="warning" %}
**You should read this pop-up!** It explains **where** the files are expected to go and **why**!
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-39df05ba276255b8835e8c6712d8efa8b908093b%2FVortex%20Step%204.png?alt=media" alt=""><figcaption><p>Just read the dang pop-up, I promise!</p></figcaption></figure>

***

7. The mod should now be under "Disabled." \
   Right click the mod name again to bring up the menu.

***

8. Click "Open in File Manager".

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-c88b59acb9e97d630c72158fbfdcf0e2f47219cd%2FVortex%20Step%205.png?alt=media" alt=""><figcaption></figcaption></figure>

***

9. To make life easier, we'll set up our folder structure **the first folder it takes us to**.\
   Right click to create a new folder. Name it `archive`

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-95ed9d1fe33a7ebcd671b7feb345fe787d7eb792%2FVortex%20Step%207.png?alt=media" alt=""><figcaption></figcaption></figure>

***

10. Double click the `archive` folder to open it

***

11. Right click to create a new folder. Name it `pc`

***

12. Double click the `pc` folder to open it.

***

13. Right click to create a new folder. Name it `mod`

{% hint style="info" %}
You should now have a structure that looks like this in the top bar:
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-3ae03626b7a7fba4397e7b0d4f058b81f49b8c63%2FVortex%20Step%208.png?alt=media" alt=""><figcaption></figcaption></figure>

***

14. Click back through the folders until we find the exact files you want.

{% hint style="info" %}
In this example, I want to use the "COOL VERSION", so I would click through the folders until I find the "COOL VERSION" files.
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-ece084b61995dcae0fd88e29a15005edfb55dc32%2FVortex%20Step%206.png?alt=media" alt=""><figcaption></figcaption></figure>

***

15. Select the files you need and cut them!

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-c33f4b3980fa4bffd7d24c28d0e250ac6a651db9%2FVortex%20Step%209.png?alt=media" alt=""><figcaption></figcaption></figure>

***

16. Go to the `mod` folder we made in step 13 and paste the files (CTRL + V)

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-1aaea0a5f7ebf5a4e33ba9576f40bc62ef351779%2FVortex%20Step%2010.png?alt=media" alt=""><figcaption></figcaption></figure>

***

17. Repeat this process for any other folders that contains files you **need** to make sure your mod works.&#x20;

{% hint style="info" %}
Don't worry, there's a table on this page <sub>(</sub>[<sub>here!</sub>](#mod-folders-by-file-extension)<sub>)</sub> which shows the paths you need to create for each file type!
{% endhint %}

***

18. Now to deal with the folders that ***you did not make***. Select them and press delete!

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-e880959c012aabe01520787ef7d16d4d7d33789b%2FVortex%20Step%2011.png?alt=media" alt=""><figcaption></figcaption></figure>

***

19. Go back into Vortex and enable that mod!

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-baab461db303f05c8816248d9bf36a0300a32eb3%2FVortex%20Step%2012.png?alt=media" alt=""><figcaption><p>Yippee!!! You did it!</p></figcaption></figure>

***

20. Now you can get back to your regularly scheduled mod downloading session. Hooray!
    {% endtab %}

{% tab title="Fixing Folder Paths in MO2" %}

<h4 align="center">Fixing Folder Paths in MO2</h4>

It's recommend to set up your MO2 Installer to default to the **manual installer** instead of using the Simple Installer plugin.\
MO2 already checks for a correct path and will warn you if the mod you are trying to install deviates from the expected structure, but removing the Simple Installer plugin helpful for both new users as well as MO2 veterans regardless. \
It might seem like overkill, but it's a valuable tool to make sure the user checks for a working file structure - so the mod ends up where it's supposed to be!

{% hint style="info" %}
If you are unsure where files should go, refer back to the "[Overview of mod folders](#overview-of-mod-folders)" section of this page.
{% endhint %}

***

<h4 align="center">Setting up your MO2 installer</h4>

1. Open your MO2 settings and click the `plugins` tab.

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-c03cadc2963371691f8e7914cd679d0458102541%2FScreenshot%201.png?alt=media" alt=""><figcaption></figcaption></figure>

2. In the left pane scroll down to the Installer section.\
   Make sure Simple Installer is `disabled`.

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-589445a45224f25eec5103d418f64444014dcae7%2FScreenshot%202.png?alt=media" alt=""><figcaption></figcaption></figure>

Now you can go to Nexus and download mods using the `Download with Manager` button as per usual! \
\
Often times mod authors set a correct file structure, but due to how packaging works they end up with an additional folder that MO2 doesn't know how to handle. \
\
In these instances, you have to manually change the Cyberpunk 2077 directory in the installer. \
This is explained in [Example #1](#example-1-adjusting-the-cyberpunk-2077-directory) (below). \
\
To see how to create new folders from scratch, for mods that have no folder structure or are only partially correct, see [Example #2](#example-2-creating-your-own-folders) (further down).

{% hint style="info" %}
If you make a mistake you can cancel out of the installation process during any given step and start again! Even if you somehow falsely install something you can right click your mod in MO2 and select the "reinstall" option to restart the manual adjustment.
{% endhint %}

***

<h4 align="center">Example #1: Adjusting the Cyberpunk 2077 directory</h4>

1. MO2 is unhappy because it doesn't recognize a correct file path, due to an additional folder inside the mod.

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-806151d67acff44be78d1abdafa0c3b1663c16df%2FScreenshot%203.png?alt=media" alt=""><figcaption></figcaption></figure>

***

2. This is easily fixed by making MO2 recognise the additional folder as the Cyberpunk 2077 directory itself. \
   \
   Right click the folder and select "`Set as <cyberpunk 2077> directory`"

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-3aaf781427a65160899cacdd2b988160c08bd427%2FScreenshot%204.png?alt=media" alt=""><figcaption></figcaption></figure>

***

3. Now we are left with the `.archive` file going into `Cyberpunk 2077/archive/pc/mod/` \
   \
   MO2 gives us the green light for the installation.\
   \
   You can finalise the process by clicking `OK`

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-11e29d895b050e6b8d89649044141df5194ddd49%2FScreenshot%205.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
You should now be good to go! If MO2 isn't giving you the green light, or the folder structure looks different to this, check the below example for how to fix!
{% endhint %}

***

<h4 align="center">Example #2: Creating your own folders</h4>

1. MO2 doesn't recognize the file path due to the `.archive` having the incorrect folder structure.

{% hint style="warning" %}
All `.archive` files should be inside `archive/pc/mod/`. \
For more info on where each file type should go, [you can check here](#mod-folders-by-file-extension).
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-ca2cee343f1ee56761404ec5938229e033503ed7%2FScreenshot%206.png?alt=media" alt=""><figcaption></figcaption></figure>

***

2. Right click the `Cyberpunk 2077` directory. \
   Select "`Create directory`".&#x20;

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-0502f8ade4c78718ac501b577e508c6366c7a3be%2FScreenshot%207.png?alt=media" alt=""><figcaption></figcaption></figure>

***

3. Name the new folder "`archive`" \
   Press `OK`

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-498584f44709b9a3fa44a2bbc32c2561ee2069ce%2FScreenshot%208.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="success" %}
You should now see something that looks like this:
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-0184f6c54c7a6159256853226f863292f418275c%2FScreenshot%209.png?alt=media" alt=""><figcaption></figcaption></figure>

***

4. Right click the `archive` directory. \
   Select "`Create directory`"

***

5. Name the new folder "`pc`" \
   Press `OK`

***

6. Right click the `pc` directory. \
   Select "`Create directory`"

***

7. Name the new folder "`mod`" \
   Press `OK`

{% hint style="success" %}
Your screen should now look like this:
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-d868ae7197ce96a597e91a2c51e39b1e85a128ed%2FScreenshot%2010.png?alt=media" alt=""><figcaption></figcaption></figure>

***

8. Drag the .archive file into the mod folder.&#x20;

{% hint style="success" %}
MO2 should then give you the green light for installation.

You can finalise the process by clicking `OK` to install your mod!
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-989676e75ceaaa0b46721bb74613592fc8de8ab4%2FScreenshot%2011.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
For bigger and more complicated mods - like those that come with multiple `.archive` files to choose between - you can use the checkmarks to enable/disable files and folders.

You can also drag multiple files to the correct location.\
Create your own structure (pictured above) and drag the files you need into the correct places while disabling unnecessary files.&#x20;

MO2 will ignore and ultimately not install them.
{% endhint %}

***

9. You can now enable your mods like any other. Happy gaming!

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-857ff42c53b33b468dcbc8de989540b2dc1ad7be%2FScreenshot%2012.png?alt=media" alt=""><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

## Troubleshooting

If you have problems with Vortex, check the [corresponding section](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/users-modding-cyberpunk-2077/getting-started/vortex-mod-manager) of the guide.

For everything else, this wiki has a dedicated [troubleshooting page](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-users/user-guide-troubleshooting) 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](https://discord.gg/redmodding) in the **#mod-troubleshooting** channel (but your first answer will be a link to that guide).