VGKAMI
Advertise Get listed

Game Guides

Cyberpunk 2077 Mods: How to Install Them and Handle Updates

Published 20 min read

For most PC players, the simplest way to install Cyberpunk 2077 mods is Vortex, with the Cyberpunk 2077 extension and the game’s required community frameworks installed first. To keep mods working after a game update, pause automatic updates when possible, wait for framework releases made for the new game version, then update and deploy your other mods. That PC workflow is separate from the in-game Mods menu added in Update 2.5: its mod.io catalog is the route for consoles, Mac, and players who want that curated catalog, and it does not convert Nexus mods into console-compatible mods.

This guide covers the PC options, official REDmod, the 2.5 in-game catalog, and a safe update-and-repair routine. The version-specific details reflect Update 2.5, which CD PROJEKT RED released for existing owners on October 22, 2026; the Switch 2 and Apple App Store versions were still to follow later at the time of the cited information.

Which Cyberpunk 2077 mod system should you use?

Choose the installation route that matches the mod and your platform. On Windows PC, Vortex is the beginner-friendly choice for Nexus mods; manual installation offers direct control; and REDmod is needed only for mods packaged for REDmod. On consoles, the supported route is the in-game mod.io menu introduced with Update 2.5. Mac players can use that in-game menu as the straightforward option.

Method Best fit What it does Main caveat
Vortex with Nexus Most Windows PC beginners installing community mods Installs, enables, disables, and deploys mods from a manager Its staging folder must be on the game’s drive and outside the game folder; avoid mixing it with hand-copied files.
Manual unzip A small number of mods, or a setup where a manager is unsuitable Copies mod files into the game’s folders Putting files one folder too deep or in the wrong location can make a mod appear installed but do nothing.
Official REDmod Mods that include an info.json manifest and require REDmod Adds an official loading and deployment path for REDmod-format mods It is not required for every mod; older .archive mods use a different load path.
In-game Mods menu (mod.io) Console players and PC or Mac players using the curated in-game catalog Installs supported catalog mods through the game It is a separate ecosystem, not a way to install Nexus files on consoles.

Keep to one PC installation method where practical. Mixing files copied by hand with Vortex-managed files makes it harder to know which version is active and which files to remove when troubleshooting. CD PROJEKT RED cautions that community mods are not reviewed or maintained by the studio: “Cyberpunk 2077 mods are created by the community and not reviewed by CD PROJEKT RED.”

What do you need before installing PC mods?

You need a PC copy of Cyberpunk 2077 installed through Steam, GOG, or Epic Games Store. Phantom Liberty is not required to mod the base game or receive Update 2.5, although a particular mod may require the expansion if it changes expansion content. Vortex requires Windows 10 or later and a free Nexus Mods account. REDmod is free; Vortex and the community frameworks discussed here are also available without paying for a mod manager subscription.

  • Back up your saves before changing a substantial mod setup. The save folder is %userprofile%Saved GamesCD Projekt RedCyberpunk 2077.
  • Make sure the game itself launches before adding mods. Keep Windows and graphics drivers current, and have the Microsoft Visual C++ Redistributable 2022 installed if a framework requires it.
  • Since Update 2.0, an SSD is a game requirement. Installing under Program Files can also create Windows folder-permission problems for some managers; a library folder such as C:Games can avoid that class of issue.
  • Read the mod’s requirements, supported game version, installation instructions, and recent file dates. A mod page’s old endorsement or a collection’s inclusion does not establish compatibility with the current patch.

CD PROJEKT RED says it does not create or maintain mods and does not take responsibility for their function or resulting issues. Treat mod pages and their authors’ compatibility notes as the relevant source for individual files, and keep an unmodded save or backup available.

How do you install Cyberpunk 2077 mods with Vortex?

Install Vortex, its Cyberpunk 2077 extension, and the core frameworks before adding content mods. This order matters: many popular clothing, vehicle, gameplay, and interface mods depend on frameworks such as RED4ext, redscript, or ArchiveXL.

  1. Create or sign in to a Nexus Mods account. Download Vortex from Nexus. A free account can use the Slow Download option, which includes a five-second wait; Premium is not required to install mods.
  2. Install Vortex and connect your account. Install it in a normal application location, then sign in to Nexus from the manager.
  3. Manage Cyberpunk 2077. In Vortex, open Games, search for Cyberpunk, and choose Manage. If a “Game support not installed” message appears, install the Cyberpunk 2077 Vortex extension and restart Vortex. The extension version documented by the REDmodding wiki on September 5, 2026, was 0.13.0; check Nexus for the latest version rather than treating that number as permanent.
  4. Point Vortex to the game if detection fails. Select the folder containing the game executable. For a typical Windows install, that may be C:GamesCyberpunk 2077binx64. The root game folder is the parent containing folders such as archive, bin, engine, and r6.
  5. Set a safe staging folder and deployment method. The staging folder must be on the same drive as the game, but not inside the game directory. A typical default is C:Users<you>AppDataRoamingVortexcyberpunk2077mods. Set deployment to Hardlink Deployment. If the folder is on another drive, deployment can fail.
  6. Choose how Vortex handles installs. The REDmodding wiki recommends enabling Deploy mods when Enabled and Enable Mods when installed, while disabling Install Mods when downloaded so installation errors do not disappear into background automation. Leave Automatically convert legacy-style mods off.
  7. Install frameworks, then test. On each framework’s Nexus page, open Files and use Mod manager download. Install required dependencies in order, launch the game once, and confirm it reaches the main menu. Cyber Engine Tweaks (CET) asks for an overlay key on first launch; seeing its overlay is an additional check that CET loaded.
  8. Add content mods one at a time. Read each mod’s requirements and game-version notes, install it, enable it, and confirm Vortex deploys it. This makes it easier to spot the file that causes a conflict.

The core files have different jobs, so a mod may need several of them:

  • RED4ext is a native plugin loader for files in red4ext/plugins. It checks the game version and is required by ArchiveXL, TweakXL, and Codeware; the community wiki also lists CET as a dependent.
  • Cyber Engine Tweaks (CET) supports Lua mods, an overlay, hotkeys, and runtime TweakDB changes. It requires RED4ext.
  • redscript compiles .reds scripts into the game’s modded script cache.
  • ArchiveXL lets mods add items such as clothing, hair, vehicles, and apartments rather than only replacing existing records.
  • TweakXL handles YAML and tweak-file changes to TweakDB.
  • Codeware is a shared library for some script and CET mods, including event, spawning, and UI features.

For reference, the Nexus pages listed in the framework guides are CET, redscript, RED4ext, ArchiveXL, TweakXL, and Codeware. These links identify the projects, not a guarantee that any particular uploaded file is compatible with the latest game patch. Check the file date and the author’s current notes.

Collections can be convenient, but they need ongoing maintenance and may be abandoned or outdated. Use one as a list of mods to consider; download and verify the individual files so you can select versions that match your game and framework versions.

How do you install mods manually?

Manual installation means extracting a mod’s files into the game’s actual folder structure. It works across operating systems that can write to the game folder, but it requires careful extraction and tracking because it does not provide a manager’s enable/disable record.

  1. Open the game’s install folder. In Steam, use Manage → Browse local files. In GOG Galaxy, open the settings beside Play, then Manage installation → Show folder. In Epic Games Store, open the three-dot menu, select Manage, then use the folder icon.
  2. Inspect the archive before extracting. Many properly packaged mods already contain folders such as archive, bin, or r6. Merge those folders with the matching folders in the game root.
  3. Check that there is no extra wrapper directory. A common mistake is ending up with a path such as Cyberpunk 2077MyModarchivepcmod, when the game expects Cyberpunk 2077archivepcmod.
  4. Use the destination that matches the file type. The mod author’s instructions take precedence if the package has a special layout.
Mod file or folder Typical destination under the game folder
.archive or .xl assets, including many clothes, cars, and textures archive/pc/mod (create mod if it does not exist)
REDmod package containing info.json mods/<ModName>
CET Lua file such as init.lua bin/x64/plugins/cyber_engine_tweaks/mods
.reds script r6/scripts
.yaml or .tweak file for TweakXL r6/tweaks
Native .dll plugin red4ext/plugins

Older archive mods load from archive/pc/mod. They are loaded alphabetically unless a modlist.txt in that folder sets an order; if two files change the same item, load order can determine which change takes effect. Keep a note of every manually installed mod and its files so you can reverse the installation later.

What is REDmod, and when do you need to enable it?

REDmod is a free DLC and official mod-loading tool, but it is not a prerequisite for every Cyberpunk 2077 mod. Install it when the mod is specifically packaged for REDmod or says it requires REDmod; many ordinary clothing and vehicle archive mods do not need it.

CD PROJEKT RED describes it this way: “REDmod is a free DLC for Cyberpunk 2077. It adds integrated support for installing and loading mods into the game, as well as provides new modding tools which you can use to create mods specifically for Cyberpunk 2077.” REDmod was released on September 6, 2022, alongside the Edgerunners Update (Patch 1.6), as free Windows DLC. Steam lists it for Windows; no CD PROJEKT RED statement that it runs on Mac or Steam Deck was published.

To use a REDmod-compatible package, install the DLC through Steam or GOG. Epic Games Store installs REDmod automatically with Cyberpunk 2077 version 1.6 or later. Put packages with an info.json manifest in Cyberpunk 2077mods, then deploy them through the REDlauncher’s Enable mods control, GOG Galaxy, Vortex, or WolvenKit. REDmod’s tools are under tools/redmod/bin/redMod.exe. Deploy again after adding or removing a package; the first launch after a change may take longer.

CD PROJEKT RED’s FAQ says: “New, REDmod compatible mods should be placed in the \Cyberpunk 2077\mods folder. You can recognize REDmod compatible mods by checking whether a JSON manifest (info.json) is included.” It also clarifies: “The game still supports loading old mods from the archive folder, but please keep in mind that they will not appear in the REDmod menu.” In other words, absence from that menu does not by itself mean an older archive mod failed to install.

If a mod author offers both a regular archive package and a REDmod package, follow the mod page’s recommendation. Do not install both variants unless the author explicitly instructs you to: duplicate content can create conflicts or confusing load-order results.

How do you install mods from the in-game menu on consoles, Mac, or PC?

Update 2.5 added the in-game Mods menu using mod.io. It is separate from Nexus and Vortex: the catalog is the route for supported console mods, and a Nexus mod does not become available on a console simply because you installed it on a PC.

  1. Update the game to 2.5 or later. Confirm the version on the main menu. CD PROJEKT RED said Update 2.5 automatically downloaded on October 22, 2026, for existing owners on Xbox Series X|S, PlayStation 5, PC, and Mac through Steam, GOG, or Epic, if connected to the internet. Switch 2 and the Apple App Store build were listed as coming later.
  2. Open the main-menu Mods panel. Sign in with a CD PROJEKT RED account and connect it to mod.io. The menu can create a mod.io account from that login. Using the menu means accepting the displayed CD PROJEKT RED and mod.io terms.
  3. Read each listing before installing. Check the description for supported platforms, game version, and requirements. “Available on consoles” is a useful compatibility label, but it does not mean every listed mod works on every device or save.
  4. Install or subscribe using the displayed action. The flow may show an install action or a subscribe action followed by a restart. Follow what the game presents, then restart if requested.
  5. Verify that it is enabled on this device. In the Installed list, check that the box next to the mod’s title is selected. A subscription synchronized to an account is not proof that the mod is installed and enabled on another device.

Cross-Platform Mod Support became available alongside Update 2.5 on October 22, 2026, according to the mod.io FAQ. The listed platforms are PC, Mac, PlayStation 5, PlayStation 5 Pro, Xbox Series X|S, and Switch 2. PS4 and Xbox One are not listed as supported. The later release dates for Switch 2 or the Apple App Store build were not established in the information cited for this guide, so check the game’s own update information for those versions.

Console uploads and validation have size limits: the uncompressed mod-folder limit is 900 MB on PS5 and Xbox, and 250 MB on Switch 2; an individual Switch 2 file cannot exceed 64 MB. These are publishing limits for the catalog, not a promise that any specific mod will run on a particular save. CD PROJEKT RED and mod.io do not guarantee individual mods or modded saves.

Offline play has a useful distinction: you can use a modded save offline if every required mod is already installed on that device, but you cannot install a new mod while offline. Keep an unmodded save. CD PROJEKT RED advises against adding mods that change quest structure partway through a playthrough. Report a problem with a mod’s content to its creator or mod.io; report a bug in the Mods menu itself to CD PROJEKT RED.

Why do Cyberpunk 2077 mods stop working after an update?

Game updates can change the interfaces that community frameworks depend on. Mods that hook into the executable, load native plugins, or compile scripts may stop matching the new game version, so the framework can fail before the game reaches the menu. A launch crash after a patch is more often a sign to check core frameworks such as RED4ext, redscript, or CET than to assume a simple clothing archive is the cause.

As the REDmodding wiki puts it: “as long as you’re living on earth, things fall down when you let go of them, and game updates break mods.” Its practical explanation is that core mods interact with the game at a fundamental level and can break when CD PROJEKT RED changes APIs. Hotfixes can affect mods even when the main-menu version number does not change, so check recent patch notes and framework files rather than relying only on the displayed version number.

There is no reliable universal list of “mods broken by 2.5.” CD PROJEKT RED has not published a list of specific mods that broke with that update. Compatibility is file-specific and can change as authors publish fixes. An older mod can work unchanged, while a framework required by many mods can block a large portion of a setup.

For Update 2.5, a few late-October community guides described temporary compatibility forks for RED4ext, ArchiveXL, and TweakXL, while later compatibility tracking listed releases marked safe for 2.5. Those are time-sensitive reports, not a permanent recommendation to replace official project files. Check each project’s Nexus Files tab and sticky posts for a release dated after your game patch, and use a fork only if its maintainers currently recommend it. As of the cited ModSafe check on October 29, 2026, the versions it labeled safe for 2.5 were CET 1.38.1, RED4ext 1.31.0, redscript 0.5.32, ArchiveXL 1.28.5, TweakXL 1.12.0, and Codeware 1.21.2. These numbers can become obsolete; prefer current post-patch files over a version number preserved in an article.

How do you keep mods working when Cyberpunk 2077 updates?

Use a repeatable maintenance loop: delay the game patch if you need a stable modded save, update the frameworks first after a patch, and only then update dependent content mods. If the essential frameworks have not been updated yet, the safer options are to play without mods or roll back the game version where the store permits it.

Before a patch: prevent an avoidable break

  • Turn off automatic game updates where your platform allows it. The REDmodding wiki recommends waiting to upgrade until required core mods have been brought up to date. On Steam, manage when updates are applied; the game may still update when launched. GOG Galaxy has an automatic-update setting. Store controls and labels can vary by client version.
  • Keep a list of installed mods and their framework requirements, and back up saves before changing a working setup.
  • Do not assume a small hotfix is harmless. Framework compatibility can change without an obvious change to the game’s main-menu version.
  • Before updating, check whether the mods your save depends on have current files and whether the mod authors recommend waiting.

After a patch: repair in dependency order

  1. Confirm the actual game version. Check the main menu and note whether the game received a hotfix as well as a major update.
  2. Update core frameworks first. Look for files published after the patch on the relevant project pages. Install compatible RED4ext, redscript, CET, ArchiveXL, TweakXL, and Codeware as needed by your mod list.
  3. Update or disable dependent mods. If a content mod has no post-patch file or compatibility note, disable it instead of assuming it remains safe. Do not leave a dependency stack half-updated.
  4. Update the Vortex extension separately. The Cyberpunk 2077 extension is distinct from the game frameworks. A late-October 2026 community report noted extension 0.13.1 REDmod deployment fixes; check the extension page for current notes, then redeploy.
  5. Deploy and check the game. In Vortex, verify the mods are installed and enabled, resolve deployment errors, and deploy. Launch the game to the main menu before loading a valuable save.
  6. If launch still fails, isolate the offender. Temporarily disable script-heavy mods and test again. If you have many mods, disable half at a time and repeat; this “bisect” approach narrows the failure without guessing at every file.

What should you do if mods are not working or the game crashes?

Start with the least destructive checks: verify the framework versions, confirm deployment and file paths, read the relevant logs, then disable or isolate mods. Do not delete whole folders as the first step; renaming them preserves a route back if the diagnosis is wrong.

Vortex says a mod is installed, but it has no effect

  • Confirm the mod is enabled and deployed, not merely downloaded.
  • Check whether it requires REDmod and, if it does, whether REDmod is installed and Enable mods is active in the launcher.
  • For manual installs, verify that the game folder does not contain an extra wrapper directory and that the files are in the correct destination.
  • For REDmod packages, confirm an info.json is present and the package is under mods/<ModName>. Older archive mods will not appear in the REDmod menu.
  • Check conflicts and load order if another mod changes the same item or setting.

The game crashes on launch after a patch

First disable mods in Vortex and try launching cleanly. If that works, re-enable current frameworks and test, then add dependent mods in small groups. A framework file left over from the old game version is a common culprit. Also deactivate ReShade while troubleshooting, since it can be a crash source, and check whether antivirus software quarantined a CET or RED4ext DLL.

Useful logs can point to the failing component:

  • CET: bin/x64/plugins/cyber_engine_tweaks/cyber_engine_tweaks.log
  • redscript: r6/logs/redscript_rCURRENT.log
  • RED4ext: red4ext/logs/red4ext.log
  • ArchiveXL or TweakXL: logs under red4ext/plugins/

On Linux or Steam Deck, a game update may reset launch options. Reapply the options required by your setup and check that Protontricks has d3dcompiler_47 and vcrun2022 if your guide or framework requires them. One documented launch option is case-sensitive: WINEDLLOVERRIDES="winmm,version=n,b" %command%. Linux and Deck compatibility can depend on the specific setup; official REDmod support for those platforms was not established in the cited documentation.

“Script compilation failed” appears

Read the popup and redscript log for mod names, then check for an outdated or duplicate script mod. Remove duplicate copies, update or disable the named mod, and clear the game’s r6/cache only when following the modding guide’s repair steps. Reinstalling redscript may help if its files are damaged. If an Atelier mod list appears empty, check whether the required Virtual Atelier mod is installed.

REDmod changes are not taking effect

Redeploy after adding or removing REDmod packages. If the game still behaves as though old files are active, one community troubleshooting guide recommends emptying r6/cache/modded and deploying again. Be sure not to confuse this REDmod cache with the archive-mod path or assume that every archive package should appear in the REDmod list.

Last resort: reset the modded files without deleting them

If a clean launch still fails, disable everything in Vortex. Rename rather than delete mod-related folders so you can restore them or inspect them later: mods, plugins, engine, r6, red4ext, archive/pc/mod, and bin/x64/plugins. Then use Steam, GOG, or Epic’s verify/repair game-files function. Once the unmodded game launches, reinstall the required frameworks one at a time, testing after each. This is more reversible than removing files blindly and helps distinguish a damaged game installation from an incompatible mod.

Do mods affect saves, achievements, and cross-progression?

They can. Back up saves before installing or removing substantial mods, particularly mods that add quests, items, apartments, or other persistent content. Cosmetic changes are generally less likely to affect save references, but no modded save is guaranteed safe; removing a mod that a save depends on can leave missing or changed content.

On consoles, a save created with mods enabled is marked with a cog icon, and trophies or achievements are disabled on that modded save. CD PROJEKT RED Technical Support states: “On consoles, Trophies and Achievements are disabled on modded save files. Modded saves are marked by a mod.io (cog) icon displayed next to the save.” The documentation cited here does not say that turning mods off later restores trophies for that same save. On PC and Mac, mod.io’s FAQ says players can still earn achievements with mods.

For Cross-Progression, enable cross-platform saves from the Load menu or through Settings → Gameplay → Enable Cross-Platform Saves, using the same CD PROJEKT RED account. A destination platform needs the same supported mods enabled. CD PROJEKT RED says: “Note that in order to maintain Cross Progression compatibility and be able to transfer your save to another platform, you need to have the same set of mods enabled on both platforms.” The destination also needs matching game content: a save using Phantom Liberty content will not load in a base-game-only installation. Regional-edition restrictions also matter; for example, Japanese restricted consoles cannot load unrestricted PC saves.

Do not assume that an installed PC mod will transfer to a console. The in-game catalog and Nexus are different mod ecosystems, and not every mod is supported on every platform. Mod.io and CD PROJEKT RED do not guarantee modded saves across even supported platforms; a mod can corrupt or permanently change a save.

How should you choose mods safely?

Check compatibility and dependencies before choosing a mod, and make changes in small batches. That approach is more reliable than installing a large collection and trying to diagnose a failure afterward.

  • Prefer an author’s file or compatibility note dated after your game patch. Framework version numbers can change quickly.
  • Read the required-mod list and install dependencies before the mod that needs them.
  • Be cautious with pre-2.0 files unless the author has updated them. CD PROJEKT RED strongly recommended uninstalling pre-2.0 mods in its Update 2.0 guidance, as reported by SenseOS, because outdated mods could disrupt the game and sometimes cause critical errors.
  • Avoid adding quest-structure or major progression changes in the middle of a playthrough unless the author specifically says it is safe.
  • Keep an unmodded save and a separate backup before removing mods that add persistent content.
  • Use the mod.io description’s platform and version labels for in-game catalog mods, but treat them as compatibility guidance rather than a studio guarantee.

Update 2.5 also adds 40 Glamdocs cyberware styles as a game feature. If you are looking for appearance changes, check the game’s own options before adding a mod that overlaps with a built-in feature; fewer overlapping mods can mean fewer conflicts to troubleshoot.

How these options were compared

This guide distinguishes the four supported workflows in the documentation: Vortex-managed Nexus mods, manual PC installation, official REDmod-format packages, and Update 2.5’s mod.io catalog. The recommended order emphasizes dependency frameworks, post-patch file dates, reversible troubleshooting, and platform-specific save and achievement rules. It does not treat a community compatibility label or a temporary post-patch fork as a permanent guarantee.

Frequently Asked Questions

Can I copy a Cyberpunk 2077 mod folder from one PC to another?

You can copy files, but the second PC must have a compatible game version, the same required frameworks, and the mod enabled through its own manager or correct folder structure. For cross-progression, CD PROJEKT RED’s guidance is to have the same supported mods enabled on both platforms; a copied folder alone does not ensure that condition.

Can I install a Nexus mod and its REDmod version at the same time?

Usually you should not install both versions of the same mod, because they may duplicate content or conflict. Use the format and version the author specifies, and keep a note of the files you add so you can remove the right package if troubleshooting is needed.

Do Cyberpunk 2077 mods need to be reinstalled after verifying game files?

A store verification or repair can restore or replace game files, but whether it affects a particular mod depends on where that mod stores its files and how it was installed. After verification, check your manager’s deployment state and test the game before restoring a large set of mods.

Can I use the in-game mod.io catalog and Vortex together on PC?

They are separate installation systems, and using both can make a PC setup harder to track. If you combine them, keep a clear record of which system installed each mod and check for duplicate or conflicting content; a mod.io subscription does not automatically manage a Nexus installation.