How to Remove All Mods from BG3
Created in collaboration with ResplendentArrow, Maze, DefinitiveToast, Norbyte, Surōand, SatanModding, and with a very special thanks to LaughingLeader and NellsRelo!
C:\Users\YourName\AppData\Local\Larian Studios\Baldur’s Gate 3\Mods
Example image of Mod folder located in the AppData of a users computer
%localAppData%/Larian Studios/Baldur’s Gate 3/Mods
Example image of run command window using the copy and pasted text from above
Example image of mod files to delete or move to another location
Some mods may have files in your BG3 Installation folder, such as UniqueTav or other replacer mods. These files and folders must be deleted.
D:\SteamLibrary\steamapps\common\Baldurs Gate 3\Data
Example image of the Data folder in the BG3 installation folder
If you are using the Steam version of BG3, you can access your Bin folder by right clicking the game in your game list, clicking Manage, then Browse Local Files.
Example GIF of how to access Data folder through Steam
DO NOT DELETE .PAK FILES OR THE LOCALIZATION FOLDER, DOING SO MAY RESULT IN NEEDING A FULL REINSTALL OF BG3. ONLY DELETE THE FOLDERS HIGHLIGHTED IN THE SCREENSHOTS BELOW
Example image of the specific files in the Data folder to delete or move to another location
It is possible you may have two folders for the toolkit in your data folder even if you never downloaded the toolkit. See below for what extra folders you may need to delete. MODDERS, if you want to keep the tools and your mod projects, do NOT delete these folders.
Example image of the toolkit folders in the Data folder to delete
Use this step if you are using NativeMods/WASD/NativeCameraTweaks
This folder is inside your game installation folder, refer to the steps taken in 2.1 Navigate to your Installation folder at
Example image of the Bin folder in the game installation folder
Example image showing what to delete in the Bin folder
The file “bink2w64_original.dll” was created when NativeMods was installed.
Example image showing the file to rename
Use these steps if you have Script Extender installed.
Script Extender is installed in the Bin folder. Refer to the steps taken in 2.1 Navigate to your Installation folder at to get to your Bin folder.
Example image showing the file to delete
Example image showing the file to delete if you have them
Navigate to your local folder, as done in step 1.1 Navigate to your Mods folder and delete the BG3ScriptExtender folder.
Example image showing the file to delete
Navigate to your Baldur’s Gate 3 folder in the your AppData. You can use the same “run” method as earlier but use the following text instead:
%localAppData%/Larian Studios/Baldur’s Gate 3
Example image of run window with the copy and pasted line of text
If you use the .pak version of this mod, skip this step.
If you had Party Limit Begone Legacy, then you need to delete your .exe files in your bin folder and the .exe backup.
The .exes do not get altered/reinstalled when you verify the game so this is a MUST!
If you are using a translation/dialogue mod, the following must be done:
Navigate to C:\Users\YourName\AppData\Local\Larian Studios\Baldur’s Gate 3\PlayerProfiles\Public
You can use the same “run” method as earlier but use the following text instead:
%localAppData%/Larian Studios/Baldur’s Gate 3/PlayerProfiles/Public
You can navigate to this folder using the same “run” command as done in step 2.2.4 Delete the folder ”Script Extender”
Example image of run window with the copy and pasted line of text
In the Public folder, delete the modsetting.lsx file
Example image showing the file to delete
Example GIF of how to verify files through Steam
Example GIF of how to verify files through Steam
This process may take some time. Verifying game files replaces missing files and files that have been overwritten by mods. It does not delete mod files, which is why all the above steps must be done.
For GOG users, you can verify files in a similar way as Steam
If you have made it here, then congratulations, you have successfully returned your modded BG3 to a vanilla state! You can choose to continue without mods or use this as an opportunity to test mods.