Following update 3.4 at August 15, 2025. Added around 30 new mods, with now around 200 in total together with the update 3.3 itself.

Following update 3.35 at August 10, 2025. Added around 30 more mods and improved couple of installation instructions to match the changed folder structure of some mods.

Version 3.3 for Cyberpunk 2077 at August 5, 2025. A large update with around 140 new mods and some tweaks related to the game update 2.3. Cyber Samurai module was updated to version 3.0, with additions in form of both new mods related to the named update and some hidden gems.

Version 3.0 for Cyberpunk 2077 at July 5, 2025. A massive update with over 260 new mods and plethora of smaller improvements. Cyber Samurai module was updated to version 2.5 to reflect the modding stage progress and improved synergy with the existing module setup.

Version 2.6 for Cyberpunk 2077 at February 8, 2025. A massive update with over 190 new mods added and fixed/improved some typos/instruction texts + a comprehensive update for Cyber Samurai module, version 2.0, featuring both lots of new mods and a complete UX overhaul.

Version 2.2 for Cyberpunk 2077 at December 24, 2024. Added around 70 new mods (over 1,800 in the guide in total now) and removed a couple of minor mods that became redundant with the 2.2 update.

Version 2.0 for Cyberpunk 2077 at November 16, 2024. Complete remake compared to initial version - fully up-to-date, much bigger and more detailed.

- Guide was completely remade from scratch to provide complete support for modding stage based on game version 2.X further on and Phantom Liberty DLC, growing up way bigger and much more detailed.

- Over 1,500 mods in total in the guide now - nearly x5 times more than in the initial version. If you haven't modded CP 2077 for some time, or never modded it at all before - you'll be absolutely blown up with the modding possibilities it offers today.

- Cyber Samurai, the ultimate module which provides most in-depth modded Cyberpunk 2077 experience and personal modding support from me, is now available.

Future updates:

- More mods and existing mods instruction updates as per future game updates.

- New modules.

- More mod configuration recommendations.

- Corrections of links/typos if needed.

- To report the issue (typos, broken link etc) or to make a suggestion - please drop a message in #suggestions_room in our Discord server.

1) Make sure your game is NOT installed in Program Files and no active overlays are running. Answering possible question - yes, Program Files (x86) is the same. Why so? Most of game clients suggest to istall there by default! True that, but unmodded and modded game are two different things. When game is modded, there are many additional files which didn't exist there in first turn, overlays or script extenders/injectors, etc - and it's needed to be ensured that system has full access to all of them. Program Files is a system folder, and because of this modded games can be often messed up without you even knowing that - so to make sure it won't happen, install your game anywhere - just not in Program Files. If it's same drive that has your Windows installed on it - it's ok too, just once again, not.. well, you got it :) GOG is DRM-free so you can install your game anywehre at all basically - it doesn't require for game to be installed inside GOG directory. With Steam, you may just want to create an another Steam directory out of Program Files, and install Cyberpunk 2077 there.
Similar situation with overlays - disable Steam overlay, GOG overlay, various things like Afterburner etc - most of overlays can mess up things, creating unneeded problems with a modded game. NVIDIA overlay is known to be fine - so you may use that sweet Ansel for panoramic screenshots anytime.

2) How to install CP 2077 mods at all? Is there some kind of mod manager? Quite the contrary to modding in TES/FO series, Cyberpunk 2077 mods, at least at this point, should be installed manually. Why so? In Skyrim, for example, there's a single directory where all mods are being stored - the "Data" folder. So no matter the folder structure of the mod, it still goes in Data folder always (asides from ENB files which you install manually in TES/FO games too). As for Cyberpunk 2077, mods have multiple possible directories where mod files can go. Lastly mods are often packed in most different ways not suitable for mod manager installation, which is leading to issues and confusion. Yes, multiple mod managers (NMM, Vortex, MO2) support CP 2077 "on paper", but on practice, if you want proper work of your modded game, it's important to install them manually, to make sure each mod is installed correctly. Plus, the way CP2077 mods handle their files structure prevents from direct files overwriting each other when placing the mods into game folder. Once again - install CP 2077 mods manually. I won't be able to provide any troubleshooting support otherwise. If/when situation with this will change, I'll make sure to update the guide accordingly.

3) Defining the game directories where the mods will be installed, and mod types. Remember them, or just refer to this step later if needed. Most of further mod installation instructions in the guide for each certain mod will look like "XXX file goes to archive mods folder, YYY folder goes to CET mods folder, ZZZ file goes to scripts folder", which should be understood as "download the mod archive, unpack it, and look for files/folders XXX, YYY and ZZZ, which you should place into respectively mentioned directories" - to simplify the instructions and save you, my dear reader, from tons of repetitive and plainly excess text to read <3 - Cyberpunk 2077 root folder, aka \Path_To_Your_Cyberpunk2077_Installation\Cyberpunk 2077 - Cyberpunk 2077 archive mods folder, aka \Path_To_Your_Cyberpunk2077_Installation\Cyberpunk 2077\archive\pc\mod - Cyberpunk 2077 CET mods folder, aka \Path_To_Your_Cyberpunk2077_Installation\Cyberpunk 2077\bin\x64\plugins\cyber_engine_tweaks\mods - Cyberpunk 2077 scripts folder, aka \Path_To_Your_Cyberpunk2077_Installation\Cyberpunk 2077\r6\scripts - Cyberpunk 2077 RED4ext mods folder, aka \Path_To_Your_Cyberpunk2077_Installation\Cyberpunk 2077\red4ext\plugins - Cyberpunk 2077 TweakXL mods folder, aka \Path_To_Your_Cyberpunk2077_Installation\Cyberpunk 2077\r6\tweaks - Cyberpunk 2077 ini mods folder, aka \Path_To_Your_Cyberpunk2077_Installation\Cyberpunk 2077\engine\config\platform\pc - Cyberpunk 2077 RedMod mods folder, aka \Path_To_Your_Cyberpunk2077_Installation\Cyberpunk 2077\mods
The archive mods, those in form of a file with .archive file extension, are usually the mods changing the visual appearance of just about anything in the game, from weapons and cars to characters look and menu icons. They do that by changing the default model and/or texture of the object from base game, to a new one using their own files, overriding the default look. That's what these kind of mods do in [most, but not all] cases though, as some gameplay values are also stored in these files.
The Redscript/CET mods are the wide variety working through the scripting which Redscript and CET (Cyber Engine Tweaks) provide. Mod can be based only on CET, only on Redscript, or on the both. The mods can change the most different gameplay mechanics.
The RedMod mods are type of mods made to be compatible with RedMod tool in mind - extension to the game launcher/settings that allows the game to treat these kind of mods as native "addons" in the game. Note that you will need to launch game exactly through launcher (not just the .exe shortcut) once when you have installed some RedMod mods, so the RedMod is able to compile its type of mods - and do it once again when/if you will add new or delete a RedMod mod - but there's not need to use launcher every time.
The ini mods are basically the .ini configuration files which contain game settings with altered values. Stored in the proper folder, values from these .ini files are overriding base game values of the same settings. While this sounds simply, with proper tweaking, such mods can be also incredibly useful and game-changing (driving, for example).
Note: In most of cases, you can easily adjust the Redscript, CET and TweakXL mods yourself by editing their respective .reds, .lua or .yaml/.tweak files with the text editor. So if, let's say, you got yourself some nice mod which rebalances certain perk or weapon (or adds new one), but you think it'd be just perfect if certain value/s would be a bit higher or lower, you can do this yourself by editing values in the code lines (which will be properly highlighted and easy to find if you're using a good text editor like Sublime Text), then just saving changes and closing the file.

4) [Optionally yet strongly recommended] - download and install Sublime Text. It's a simple yet powerful text editor - similar to Windows native Notepad, just many times better. It's very cozy and makes editing various configuration files (which you'll need to do at least few times as many mods provide them for your comfort) as well as script (.reds) files. It's free and reliable, pleasant to the eye (unlike the hideous Notepad - has dark theme and many optional cozy extensions) and serves millions of people for many years.

5) Install Material and Texture Override. Allows to load mod-added materials (models, textures, sounds etc) to be loaded in the game, iow, for the archive mods to work.
Installation: Download the Legacy file. Unzip the archive. Place "###_nim_material_override.archive file to Cyberpunk 2077 archive mods folder.
Note: Make sure to get this one. Despite it's being technically deprecated and most of modern mods that change models, textures and other basic assets, are using newer methods, some older yet still great mods still rely on this one. Even if you won't have mods in your setup that rely on it, nothing bad will happen to your game, as this mod doesn't modify anything in your game on its own.

6) Install RedMod. RedMod is a special DLC for the game, that practically acts like an extension that adds integrated support for loading mods into the game. Many of the mods released since game version 2 and introduction of Phantom Liberty DLC, were made specifically with RedMod support, and so, RedMod is required for these mods to work properly.
Installation: Make sure your game launcher (GOG/Steam) is launched. At the RedMod official page, click on your corresponding client image link, like shown here, and simply add this free DLC to your library. Your game will be quickly updated and that's it - you now have RedMod installed.

7) Install Cyber Engine Tweaks. Or just CET in short is a scripting framework required for most of the mods. It also introduces some performance and QOL (quality of life) fixes by default. We should have it for many mods to work properly.
Installation: Download the latest release (usually the "cet_x_xx_x.zip") archive somewhere. Unpack it. Place "bin" folder to Cyberpunk 2077 root folder. That's it! Launch the game once now - a window will appear prompting you to choose a keybind to bring up the overlay (CET ingame menu when you can configure it and some mods based on it). Pick any key (or keys combination, up to 4 keys) and save it. Now this menu will open with that key from now on to use CET itself and control CET-based mods. Now, go inside \bin\x64\plugins\cyber_engine_tweaks\ folder and create "mods" (named exactly mods) folder there so it looks like this.
Note: If using latest CET version causes issues to you like game crashing, CET menu not appearing and CET-based mods not working, try to remove the current latest version and install previous version (latest one before it) and see how it goes.

8) Install Native Settings UI. This mod allows CET mods to easily add settings menus using only native UI, thus looking like the games settings menu.
Installation: Download the main file. Unpack the archive. Place "nativeSettings" folder into Cyberpunk 2077 CET mods folder. You will now have "Mods" setting in the main menu, looking like this, where you can configure CET mods that are made with Native Settings UI in mind.
Note #1: If you're sure you've installed the mod correctly, but after you click "Mods" there's nothing there - check (at their mod pages) if any of your CET mods actually have Native Settings UI configuration option - just the fact mod is CET-based doesn't automatically mean it has this.
Note #2: Optionally, if you have many mods with Native Settings UI configuration, install this improved navigation addon for it (place the "nativeSettings_side_menu_add_on" folder into Cyberpunk 2077 CET mods folder.)

9) Install Redscript. This one is a compiler for the game scripts, which is also required for many great gameplay mods - they would not exist without it, basically. The great benefit of the mods based on Redscript is that their script files are editable via text editors (like the Sublime Text recommended above), and while not always guaranteed, yet pretty often, with just a minimal understanding of what the mod does and without need of any programming skills, you can adjust the mod parameters to your likings by editing the .reds files.
Installation: Download the latest release (usually the "redscript-mod-vXXX.zip") archive somewhere. Unpack it. Place "engine" and "r6" folders to Cyberpunk 2077 root folder. Done :)
If you'll have Redscript compilation issues at the game launch and you're sure you've installed every Redscript mod correctly, you can also try to install a (sometimes) newer Redscript version available on its Github. Default (nexusmods) version is what you should use normally, but in case of what, you can try one of the newer versions from the Github.

10) Install RED4ext. A script extender for REDengine 4, on which CP2077 is made. You can see it as an analogue of SKSE/NVSE and such script extenders for Bethesda games.
Installation: Download the latest release (usually the "red4ext_x.y.z.zip") archive somewhere. Unpack it. Place "bin" and "red4ext" folders to Cyberpunk 2077 root folder. That's it.
To make sure it runs properly, go to \red4ext\logs\ and open "red4ext.log" file. If in it you see "RED4ext has been successfully initialized" and "RED4ext has been started", then it runs just fine.
Note: At some mod pages, you may sometimes see a framework mod named "Cybercmd" as requirement, either at the mod frontpage or somewhere in the comments section. RED4ext fully supersedes Cybercmd - for whatever mod existing with such a requirement, you don't need to install Cybercmd, only RED4ext.

11) Install ArchiveXL. Modding tool that allows you to load custom resources without touching original game files, thus allowing multiple mods to expand same resources without conflicts.
Installation: Download the latest release (usually the "red4ext_x.y.z.zip") archive somewhere. Unpack it. Place "r6" and "red4ext" folders to Cyberpunk 2077 root folder.
To make sure it runs properly, check out the red4ext\logs\red4ext.log file. If in it you see "RED4ext has been successfully initialized" and "RED4ext has been started", then it runs just fine.
Note: Mods that support ArchiveXL also have the files with .xl extension together with the regular .archive file/s in their folders. Further in the guide, when you'll see installation instructions "place the .archive file/s", this by default means also placing the .xl file/s together, if those are present. That's purely to unify and shorten installation instructions, as the .xl files always go to the same directory as the .archive files do.

12) Install Mod Settings. A mod that provides support for ingame configuration menus for Redscript-based mods. What's the difference from Native Settings UI? Yes, you guessed it right. Native Settings UI is for CET mods, Mod Settings is for Redsript mods, that's all - you can use both and need both.
Installation: Download the main file. Unpack the archive. Place "red4ext" folders to Cyberpunk 2077 root folder. You will now have "Mod Setting" setting in the main menu, looking like this, where you can configure Redscript mods that are made with Mod Settings in mind.

13) Install Codeware. Another library that provides script extensions for both CET and Redscript mods. Required by some mods below.
Installation: Download the main file. Unpack the archive. Place "red4ext" folder to Cyberpunk 2077 root folder.

14) Install TweakXL. Framework required by some other mods as well.
Installation: Download the main file. Unpack the archive. Place "red4ext" folders to Cyberpunk 2077 root folder.

15) Install Input Loader. Merges .xml files from various mods that have those files in \r6\input\ folder, and saves results to a single file. Don't think much, soldier - it just works.
Installation: Download the main file. Unpack the archive. Place "engine", "r6" and "red4ext" folders to Cyberpunk 2077 root folder.

16) Launch the game once before intalling mods themselves. Simply launch the game once (not needed to start the walkthrough, just run the game till the main menu is opened, and then exit) to make sure all base game configuration files are generated and CET/Redscript work fine, just in case.

17) Check your game after each few mods installed. Always make at least a basic check (launch the game - load a test save - fast travel somewhere/start a random combat/open character menus and inventory) from time to time in process of modding, after each few mods installed. This is needed to prevent situations like if something goes wrong (improper mod installation or conflict) but you having no idea what and when exactly because you last time checked your game 30 mods ago. So, simply check your game often enough to always keep the hand on pulse.

18) Understanding the compatibility. At the one hand, for Cyberpunk 2077, at this point, there are no tools as sophisticated as xEdit for TES/FO games modding or Script Merger for Witcher 3. But, certain compatibility tips and hints are still available. Some of them:
- Apply common sense. For instance, if you have 2 "archive" type of mods one of which is recoloring ingame UI, and other one is changing the shape of its icons, they most likely will conflict and you'll need to choose one.
- Ask yourself. If a certain game mechanic doesn't work as it should (or doesn't work at all), ask yourself "which of my mods may be affecting it"? The proceed to re-reading respective paragraphs of such mods in the guide and their mod pages.
- Script extenders are amazing! These powerful tools needed for most of mods have compilation log files that can serve you well in finding out about issues and mod conflicts. For instance, for RedScript, after every few mods installed, check out the "redscript_rCURRENT.log" file (and many other log files which are showing chronologically previous logs - open it by text editor like Sublime Text mentioned above) located in \r6\logs\ folder. After you open it, press CTRL+F and and type "WARN" (without qoutes). This is a shortening for "warning", a type of notification which will be present in the log. If there's a conflict between two mods modifying same method, usually at the [WARN] line you'll see something like "\Path_To_Your_Cyberpunk2077_Installation\Cyberpunk 2077\r6\scripts\ModName\ScriptFileName.reds Conflicting method replacement", which means there's a certain conflict between ModName (name of the mod), in ScriptFileName.reds (name of its script file) and some other mod. While this is not a 100% clear answer, it can hint you what exactly conflicts, and so, find other mod which conflicts with this one. This, in turn, will help you to either adjust some mod settings (if possible) to get rid of this conflict, ask for compatibility advice from the community, or (in "worst" case, but still it is the solution which is better than improperly working mods) to remove one of two conflicting mods.
Similar steps appy for other mods based on other script extenders (like RED4ext). This may look "scary" at the first glance, but practically, it will not happen often (or may not happen at all, depending on your mod list), and it's usually absolutely possible to find the culprit and get rid of it in either of ways.
- Load order priority. As for now, there are no sophisticated methods to manipulate with the load order (like LOOT tool for TES/FO games), and in most of cases, you will not need to do so to begin with, but just for sake of knowledge - CP 2077 mods load order is working [binary-alphabetically]. This means if you have mod named "Big Bad Samurai" and "Large Speedy Choomba", the Big Bad Samurai one has the load order priority over the Large Speedy Choomba in case they will conflict somehow - because the first mod name starts with "B" and second mod name starts with "L". Further on, "modX" loads before "modXX" and "modYY".
Another example is you can rename the mods yourself, and if you want a certain mod to take the definitive load order priority, just add a prefix like "a_" to it's name, so the mod with name "Your Cheeky Wakako" will be now named "a_Your Cheeky Wakako" (and "a_Your Cheeky Wakako" will have load order priority over "aa_Your Cheeky Wakako"). Once again, it's not like you'll have to do this often (if at all - it all depends on your setup), but it's better to know than not to know :)

19) Download the Archive Conflict Checker Tool. Useful tool to see conflicts between archive mods (in most of cases - texture/model graphics mods). Simply download the archive somewhere on your PC (not in the game folder), unzip it, and launch the "red4-conflicts.exe" file anytime you want - it will show you conflicts between archive mods, if there are any, so you could think how to re-arrange load order, or maybe just ditch something.

20) Develop this good habit when it comes to meeting a bug in modded CP 2077 ↓↓↓↓↓ When experiencing a game issue which you think is related to mods - don't rush to report it as bug to the first mod you think it's coming from. Replicate it a few times, try to remove mods few by few and see when exactly the issue goes away - it often happens that what you have thought of being a bug from a certain mod at first, may be not even related to it to begin with or be not a bug but a feature which you just personally don't like. Mod authors not always can help with every possible issue because they can't surely know about how exactly their mod will work together with all other possible mods on the stage. Tldr, often "bug" reports made without a proper check will only confuse other players and bring yet another report of the issue which has technically nothing to do with the mod itself. Always narrow down the culprit carefully and respect the time of people who make this game better <3

21) Disable Cyberpunk 2077 autoupdates. CDPR is, happily, working on the game to fix its many bugs and polish, releasing updates from time to time. Yet when it comes to the modded game, such update may or may not mess up your mods (or introduce new bugs even). So the general rule is to simply disable autoupdates for the game. When you see the new official game update arrived, wait a bit and check the pages of mods you're using - make sure it's confirmed they are working fine with the latest updated or were properly updated for it. Also, look here regarding the features/changes list of the current update - whether it's actually great or maybe breaks some things on top of fixing others (it can happen). Then, it's ok to update the game.

22) When updating your mods, always check if you need to update Redscript/CET and other groundbase mods and frameworks. It's important as well, because the new stuff introduces in the mod update may be based on the new features added in updates of those as well, so you may need to update them to begin with, for the updated mod to work properly.

23) [Optionally] - download and install WolvenKit. WolvenKit is a powerful tool which mod authors can use to make Cyberpunk 2077 mods. It can access the game files, edit them and pack mods. If you're not planning to make mods yourself, you won't need it.

This section provides you with a core mods to fix some bugs and oversights, or adjust/improve certain gameplay aspects that are not technically a bug, but are practically annoying, and to add certain features that will be useful to and improve joy from playing the game no matter of the gameplay preferences. Mods here do not affect difficulty and do not affect performance (only if they're improving it), being an essential base for any modded setup, and even just a vanilla purist walkthrough.
Note: while some parts of Cyberpunk 2077 interface are just plainly hideous, this exact section doesn't include any of UI mods as still, some players may be not even bothered by UI issues - so all the UI mods (even those I personally consider essential myself) are listed in their own section right after this one.

First of all, must-have bug fixes - either mods fixing some really major/annoying bugs, or those that fix bugs which are not game-breaking neither too notable, but fixing lots of them in a single mod, so you're losing nothing by getting a fix (for instance - a mod that restores dozens of missing database records):

Now, mods that either alter certain game aspects or add new features that will be generally useful to everyone:

Lastly, a mods that are aimed directly on improving performance in the game. These mods may be for some certain hardware (for instance, a performance boost for AMD CPUs only, or an FPS boost when using Ray Tracing, etc) - so mods here are also not obligatory essential, but at the same time, can be so for certain players depending on their PC specs and/or graphics settings:

Now, plenty of other bugfixing mods which are recommended, but practically 100% optional - fixing either some tiny gameplay bugs which are not much notable, or cosmetic bugs/oversights/irrationalities. Get these if you want to correct everything possible down to tiniest, inconsequential bugs or just irrational cosmetic things:

This section is important and almost essential, as it solves huge amount of issues with vanilla user interface (UI), which was one of the most underdeveloped parts of the game and simply wasted you a lot of time during walkthrough. Make interface more intuitive? Fix UI-related bugs? Add more hotkeys to the game? It's all here.

First of all, some massive or/and nearly essential interface mods. You can use them together.

Various other UI mods (some of which are still quite essential if you ask me).

Font mods:

In this section you can find everything related to vehicles. Improve the driving and controls? Change the look of your favourite cars/bikes, or even give them a brand new look at all? Improve city traffic and crowds AI? Read, choose, install - and drift you way through the Night City :)

First of all, a few mods providing minor bugfixes related directly to vehicles and driving:

Various mods needed by some of the other vehicle mods below, as well as driving & car management related mod that systematically affect driving or certain vehicles mechanics:

Now, various mods changing the appearance of the vehicles. If there are few mods altering the look of the same vehicle - choose and use only one mod unless there's a dedicated note provided. Also, something to take into account: Due to certain new approach to how the game works with various materials, Cyberpunk 2077 doesn't have diffuse textures type in general - this means other objects that have the same material as, let's say, the car (of your choice that you're changing appearance to with certain mod) will be affected. For example if you choose the yellow paintjob for the Porsche then other cars that shares the same material will also be yellow. This is not too much of a big deal on practice - just take into account that is not a bug with some mod, but just how the game works in this aspect.

Brand new vehicles added to the game. A note on these kinds of mods: Many of the mods in this section are adding new vehicles to the game that use either real life vehicle models, or models from other titles (movies, videogames etc). It's really difficult to adapt a complex model of the vehicle to the game it never existed in to begin with, so such kinds of vehicles may sometimes have minor cosmetic bugs present due to this. It won't happen to every mod listed here, but keep this in mind. At the same time, all vehicles mods that are actually highly buggy and unstable, are not listed here, so don't worry.

New cars. Note: If you'll install multiple new car mods, you may get (and not once) an overwrite prompt regarding "VehicleManufacturerFix.reds" file. Always approve, it doesn't matter as it's always the same file with a certain same setting that some of car mods use.

New bikes:

Everything related to abilities and combat - V's perks and skills, combat mechanics changes, enemy mods and so on. You may also find this character build calculator provided by CDPR, useful for planning your builds.

Combat-affecting mods:

Abilities-related mods:

Here you will find various gameplay mods which are not directly related to character progression, bur rather to the feeling of a gameplay an world around you in general. Every mod in this section is pretty different from the rest, and in my humble opinion, this almost whole section is pretty essential. There are also mods here which don't quite fit under a single category clearly. Improved factions, smarter and more disctinct enemies, rebalanced loot and various other features, including brand new mechanics (or cut ones being restored).

Various gameplay-affecting mods with most different features (and adding brand new as well):

Immersion mods wich do not directly affect game difficulty or mechanics (aesthetic/cosmetic immersion):

Everything related to weapons, armors and cyberware - rebalance of their stats & mechanics, retextures, improved models and ofc, brand new items added to the game.

Major mods that generally affect weapons, armors and cyberware mechanics:

Mods that affect certain weapons, armors and cyberware themselves, adjusting their stats or abilities:

Mods that change the appearance of weapons. Remember - if there are few mods changing the look of the same itemn - choose only one (scope mods can be used together with weapon apperance mods, as they are technically separate objects):

Mods that add brand new weapons, cyberware and weapon mods:

Let's get to armors and clothing. Mods that change appearance of existing (vanilla) items. Note: There's not much in this section because most of mods that were working only as existing items replacers (there was no other way to change items for CP 2077 modding at some point in past), were sooner or later remade in form of standalone item packs.

Mods that add new armors and clothing:

Armors, suits, pants, clothes, lingerie:

Helmets, hoods and masks:

Footwear and gloves:

Accessories - glasses, piercings, necklaces, cosmetic cyberdecks or body parts, backpacks and so on:

Everything about audio in the game - improved music and sounds, removal of annoying sounds, new radio stations and so on.
Note: When there are both RedMod and non-RedMod versions of the same mod available, it's generally recommended to get the non-RedMod one. This said, when using multiple audio mods of the same type (for instance, mods changing sounds of perks of weapon), if using more than one mod of the same type in classic version, multiple mods may not work together (even though they are not directly changing same sound) - in this case, you can try the RedMod versions of these mods, as they won't conflict in same situation.

Mods which which improve/change the music/sounds and control them:

Radio mods that replace songs on existing stations. Track list is usually written on the mod page, so make sure to read those. Remember - when there are few mods replacing the same radio station, install only one of them.

First of all, a few mods that generally apply to radio as is and change its functionality:

Vexelstorm station replacers:

Morro Rock station replacers:

Samizdat station replacers:

Body Heat station replacers:

Nigh FM station replacers:

Principales station replacers:

Ritual FM station replacers:

Pebcak station replacers:

New radio stations (make sure you have RadioExt installed, it's needed for most of mods in this subsection):

Cyberpunk 2077 is not 10 years old Skyrim - its graphics are insanely good. If not to count some glitches here and there (which are mostly just funny/cringe and not game-breaking), it's one of the best-looking games on the market, and if your PC is capable to utilize Ray Tracing support...oh my! Still, there's no limit to perfection and even while it it's a freshly released game, it could use some visual improvements here and there. Some models/textures replacecement to fit YOUR personal taste more, improved existing textures/fx and also mods to get rid of certain annoying visual effects as well. Take a look!

First of all, a few really large mods. They are 100% optional as they notably (or even drastically) overhaul large number of ingame objects (textures and models) and some can directly change the overall visual aesthetics of the game.

Water mods. Use one:

Rain mods. Use one:

Fire/explosion mods. Use one:

Many other texture/model improvement mods:

Various (often annoying for some players) visuals removals:

Someone may laugh on this, but hey - game icon also deserves some love and assortment. Those are not "mods" technically - just a different icons for the game shortcut which you can change in shortcut properties and use any of those.

Character creation/customization possibilities in Cyberpunk 2077 weren't terrible...but they weren't super great either - similar to many other game aspects, players expected more from an AAA game which was 8 years in development, especially in a cyberpunk settings, where have almost bottomless arsenal of self-expression. Mods in this section help to improve this in many ways, as well as offer some other changes not only to V.

Generally useful character-related mods (not directly essential, but rather a good "base" group of mods in this category):

Mods for V appearance - complexions, skin and body mods. When it comes to body and complexion mods, make sure to use only one of each type. Mod which affect smaller things, like makeup, lips or teeth, can be used on top of those, and often used together (if they are fully standalone or replace different vanilla slots, information about which is usually on the mod page).

A note on body mods: Due to a highly complex nature of what builds up V's resulting look, body mods, especially those that drastically change body shape (such as super curvy fem V or ripped, bodybuilder-like masc V body mods), can (and most likely will) lead to a certain degree of visual glitches in gameplay - from clipping to just really weird looking body parts or items. Ofc, you can try to get only armor/accessory mods that have dedicated versions refitted to your body mod specifically, but even with this, it's still not a 100% guarantee you won't meet some weird things during actual gameplay. Plus, there's not guarantee vanilla items will all look fine on modded bodies. Moreover, as CP 2077 is a first-person game, the only cases where you'll see V's body fully is inventory (where it's body is not taking full screen and has lower level of details), some cutscenes, and photomode. But if you're not planning to use photomode really often to make plenty of screenshots in it, body mods usage is, imo kinda arguable. But ofc, that's just my 2 cents. Wanna have maximum possible results at your screenies? Go wild!

V appearance - eyes, eyelashes and brows.

Hair mods:

Tattoos, scars and various other appearance & cosmetic cyberware appearance mods:

NPCs appearance:

This section title image is from amazing Equipable Glowing Eyes mod.