Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Godlike.Host offers hosted Valheim servers with its own game panel, SFTP access and free DDoS protection, if you would rather not host it yourself.
On a Steam installation of Valheim, the dependable path is to install the community-maintained BepInExPack Valheim loader, add mods through one profile manager such as Gale, Thunderstore Mod Manager, or r2modman, and start the game from that manager. For a manual Windows install, copy the pack contents beside valheim.exe, then put plugin files in BepInEx/plugins.
Use the Steam PC build for this guide. Microsoft Store and Game Pass files are protected and substantially harder to modify, Xbox clients cannot load these mods, and crossplay does not make an Xbox client a modded client. Multiplayer support depends on each mod: some are client-only, while world, progression, and content mods can require the dedicated server and every participating player to use compatible files.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What you need before installing
Prepare the game and your mod plan before copying anything. A clean starting point prevents most loader and dependency problems.
- Steam PC edition: This guide targets the Windows Steam build first. A Microsoft Store or Game Pass installation uses protected files and is considerably more difficult to modify. Xbox clients cannot load Valheim mods; crossplay does not change that limitation.
- A save backup: Back up characters and worlds before adding content or progression mods. If a mod adds items, recipes, or world objects, removing it can leave unknown data in a save.
- One installation route: Decide whether you will use a profile manager, Vortex, or manual files. Do not let two managers control the same
BepInEx/pluginsdirectory. - A current game copy: Game updates can invalidate the loader payload, unstripped assemblies, or individual plugins. Check compatibility before adding a large collection.
- A small first test: Install the loader and one mod, launch, and read the BepInEx output before you add more. This makes the first failing component identifiable.
Choose an installation route
Profile managers are the easiest choice when you want isolated mod sets and automatic dependency handling. Manual installation gives you direct control over every file. Vortex is a separate route that uses the Nexus Mods catalogue and must not be mixed with a Thunderstore-style profile on the same game directory.
| Route | Catalogue or source | Operating-system coverage stated in the guidance | Profile isolation | Dependency handling | How the game starts | Directory considerations |
|---|---|---|---|---|---|---|
| Gale | Gale package catalogue | Windows and Linux | Yes; create separate Valheim profiles | Installs declared dependencies through the profile | Use Gale’s modded start command | Profile-managed files are attached when launched from Gale |
| Thunderstore Mod Manager | Thunderstore catalogue | Windows | Yes | Installs declared dependencies | Use the manager’s Start modded command | Launch attachment is bypassed by a direct Steam launch |
| r2modman | Thunderstore-compatible catalogue | Windows, Linux, and macOS | Yes | Installs declared dependencies | Start from the selected profile | Keep each profile separate and launch through r2modman |
| Vortex | Nexus Mods catalogue | Not stated in the Valheim extension notes | Uses Vortex’s deployment model rather than a Thunderstore profile | Installs the tested BepInEx payload and mod files; follow each mod’s requirements | Manage Valheim in Vortex, then install and enable the mods | Do not run it alongside another manager that also controls BepInEx/plugins |
| Manual files | Mod archive and its readme | Windows procedure documented here | No automatic profile isolation | You locate and install every required library yourself | Start Valheim normally after the loader is in the game root | You are responsible for the exact folder layout and cleanup |
Install with Gale, Thunderstore Mod Manager, or r2modman
These managers use the same basic sequence: select Valheim, create a clean profile, install the Valheim-specific loader, add a mod with its dependencies, and launch from the manager. The names of buttons can vary slightly between releases.
- Install one manager. Choose Gale, Thunderstore Mod Manager, or r2modman. Pick according to your operating system and the catalogue you intend to use: Gale supports Windows and Linux in the documented guide; Thunderstore Mod Manager is documented for Windows; r2modman is documented for Windows, Linux, and macOS.
- Select Valheim. In the manager’s game list, choose Valheim and let it locate your Steam installation. If it asks for a game directory, select the folder that contains
valheim.exe. - Create a fresh profile. Give the profile a meaningful name, such as
Vanilla-testorEpicLoot-coop. A profile lets you disable a complete mod set without deleting your files and gives you a clean baseline for troubleshooting. - Install BepInExPack Valheim first. Search for the package by that exact name and install it before any gameplay mod. This is the Valheim community package, not a generic upstream BepInEx download; it contains preconfigured settings, Valheim launch support, and compatibility changes used by most Valheim mods.
- Install the target mod. Open its package page, review the game version and readme, and select Install. Accept every declared dependency. Shared libraries such as Jötunn or JsonDotNET may be required even when they are not visible as gameplay features.
- Check the profile list. Confirm that the loader, the mod, and all required libraries are enabled in the same profile. Do not install the same plugin manually into the game directory as well; duplicate copies can load twice or leave an old version behind.
- Launch from the manager. Use Start modded, Launch modded, or the equivalent command shown by your manager. A direct Steam launch can skip the profile manager’s launch attachment and produce an apparently vanilla game.
- Read the first launch output. The BepInEx console or log should show the loader starting and list the plugins it loads. Stop here if there is an error; adding ten more mods makes the original failure much harder to isolate.
- Add additional mods gradually. Close the game, add one small group with compatible dependencies, launch again, and keep the profile that last worked. This creates a usable rollback point.
When a profile manager is the best choice
- Use profiles when you play different worlds with different mod sets.
- Use automatic dependency installation when a mod has several shared libraries or frequent updates.
- Use the manager’s disable or remove controls instead of deleting random files from the game folder.
Manual installation on Windows
Manual setup is a file-copy operation. It is transparent and gives you complete control, but you must read every mod’s instructions, install dependencies yourself, and repeat compatibility checks after updates.
- Open the Steam game directory. In Steam, open your Library, right-click Valheim, choose Manage, then Browse local files. Leave the window open; this is the folder that contains
valheim.exe. - Download BepInExPack Valheim. On the package page, choose Manual Download. Use the Valheim-specific community pack rather than a generic BepInEx archive.
- Extract outside the game folder. Unpack the downloaded archive to a temporary location such as your Downloads folder. Do not extract directly into Valheim, because it is easy to create an extra nested directory.
- Open the pack’s inner folder. Locate the directory named
BepInExPack_Valheim. Select the contents inside it, not the outer folder itself. - Move the contents to the game root. Copy the contents of
BepInExPack_Valheiminto the folder containingvalheim.exe. Approve a merge if Windows asks to combine folders. - Check the root layout. At minimum, the following entries should be beside
valheim.exe:
Valheim/
BepInEx/
doorstop_config.ini
winhttp.dll
valheim.exeIf you instead see a path such as Valheim/BepInExPack_Valheim/BepInEx, the contents are one level too deep. Move the inner contents up so that BepInEx, winhttp.dll, and doorstop_config.ini are directly in the game root.
- Read the mod’s installation notes. Download one mod, inspect its readme for dependencies and any special folders, and do not assume every archive has the same structure.
- Place the plugin. A plugin DLL normally belongs in
Valheim/BepInEx/plugins. For example, the documented Jötunn example placesJotunn.dllin that folder. If the archive contains a packaged plugin folder, preserve the folder structure described by its author. - Install shared libraries before dependent mods. Add libraries such as Jötunn or JsonDotNET when the mod requires them. The loader alone does not supply every library that a large mod may need.
- Start Valheim and inspect BepInEx output. Confirm that the loader starts and that the plugin appears without an exception before copying another mod.
What the manual layout tells you
winhttp.dllanddoorstop_config.inibelong in the same root folder asvalheim.exe; they are not plugin files.- Individual plugin DLLs belong below
BepInEx/plugins, not beside the game executable. - Putting a DLL in an arbitrary
Modsfolder will not make BepInEx load it unless that mod’s own documentation explicitly requires a different path.
Using Vortex with the Nexus Mods catalogue
Vortex is a separate workflow from Thunderstore-based managers. The Valheim extension documentation says the game has no official mod support, requires the BepInEx injector for most mods, and supplies a tested BepInEx payload together with unstripped assemblies for compatibility.
Rank #2
- Viking Game laminated laptop stickers All approx 3"-4" in length
- Laminated, Not UV Proof. Will fade in sun. Best used indoors.
- Great for Laptops, Phones, Computers, Tablets and more!
- Handmade by a Stay at Home Small Business Mama!
- Install and open Vortex. Add Valheim to your managed games and confirm that Vortex points to the Steam installation containing
valheim.exe. - Install or update the tested BepInEx payload. Use the Valheim extension’s current payload rather than copying an unrelated BepInEx build over it. The unstripped assemblies supplied by the extension are part of its compatibility setup.
- Download a Nexus mod. Read its requirements, game-version notes, and installation instructions before enabling it.
- Install and enable the mod in Vortex. Resolve any dependency prompts, deploy the files when Vortex requests it, and verify that the mod is enabled.
- Launch through the workflow Vortex provides. If the extension displays a modded launch action, use it rather than switching to a different manager.
Do not operate Vortex and Thunderstore Mod Manager or r2modman on the same Valheim installation. Both can manage BepInEx/plugins; mixing them can overwrite files, leave conflicting versions, and make a profile appear broken when the real problem is duplicated deployment.
Install dependencies in the right order
BepInExPack Valheim is the loader, not a complete library for every mod. A large mod can require shared frameworks, configuration libraries, or content packages in addition to the loader.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →| Component | Role | How to handle it |
|---|---|---|
| BepInExPack Valheim | Valheim-specific injector and preconfigured loader environment | Install it first through your manager or copy its contents to the game root manually |
| Jötunn | Shared library used by some content and gameplay mods | Install the version declared by the mod; the documented manual example places Jotunn.dll in BepInEx/plugins |
| JsonDotNET | Shared JSON library required by some larger mods | Install the declared dependency before launching the dependent mod |
| EpicLoot | Example of a mod with real dependencies and multiplayer requirements | Follow its package notes and install the required files on the server and clients when its labels require both |
Managers normally read a package’s declared dependency list and install those files for the selected profile. Manual users must perform the same check by reading the mod page and archive readme. If a dependency is missing, the BepInEx output commonly identifies the plugin that failed to load; fix that dependency before changing unrelated files.
Make multiplayer and dedicated servers work
Never infer multiplayer behavior from the mod’s name. Read the package’s client-side and server-side labels and its installation notes.
Rank #3
- Gaming Inspired Design
- Geek Culture
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
| Mod classification | Typical placement | What every player should do |
|---|---|---|
| Client-side quality-of-life | Player’s client only | The player who wants the feature installs it; other clients may be able to remain unmodded if the package says so |
| Server-side | Dedicated server, sometimes with a client component | Install the server files exactly as documented and check whether clients also need the same package |
| Server and client | Dedicated server plus every participating client | Use compatible versions and matching dependencies on all sides before joining |
| Content or progression mod | Often affects world data, inventories, recipes, or progression | Assume the server and all clients may need it until the package explicitly says otherwise; make a save backup first |
For a hosted or dedicated server
- Read the mod’s server instructions separately from its client instructions.
- Check whether the package is marked client-side, server-side, or both in the Thunderstore Valheim directory or on its package page.
- Install the required loader, libraries, and server plugins in the locations specified for that server build.
- Give every participant the exact compatible client profile when the mod requires client files.
- Start the server and check its BepInEx output before players connect.
- Join with a test character or a backed-up world first, especially for progression and content changes.
A client-only interface or quality-of-life plugin may affect only the person running it. A world-generation, progression, or content plugin can change the save and usually needs coordinated installation. If the package notes conflict with a general label, follow the package author’s detailed instructions for that version.
Verify a successful installation
Use a short verification pass before building a large profile.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Close Valheim completely.
- Confirm that you are launching the intended Steam installation, not another copy of the game.
- Start from the selected manager profile, or start normally after a correct manual root installation.
- Watch the BepInEx console or log for the loader initialization message and the names of enabled plugins.
- Check for exceptions, missing dependency messages, or duplicate assembly warnings.
- Enter a test world and verify one feature from the mod. Do not test a new content mod on your only production save.
- Exit cleanly, keep the working profile, and record the mod versions if you plan to share the setup with friends.
Troubleshooting common failures
The game starts normally, but no mod appears
First check the launch method. A profile manager’s files and launch attachment are applied when you use its modded start command; starting directly from Steam can bypass that setup. For a manual install, inspect the root layout and make sure winhttp.dll, doorstop_config.ini, and BepInEx are beside valheim.exe, not inside an extra BepInExPack_Valheim folder.
BepInEx does not initialize
Confirm that you installed BepInExPack Valheim rather than generic upstream BepInEx. Re-copy the pack contents from inside BepInExPack_Valheim to the game root, then launch again. If you are using a manager, verify that the profile is selected and that the manager has located the same Steam folder you opened through Manage → Browse local files.
Rank #4
- Valheim Boar Loves You quote. A perfect design for fans of the best selling Viking game.
- An amazing and unique design which is also perfect as a gift.
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
A plugin reports a missing dependency
Read the error in the BepInEx console or log and return to the mod’s requirements. Install the named shared library, such as Jötunn or JsonDotNET, in the same profile or in BepInEx/plugins for a manual setup. Check the required version; installing a library with a similar name is not enough.
The game crashes after adding one mod
Disable the newest mod and launch the last known-good profile. If the crash disappears, check that mod’s supported Valheim version, dependency versions, and client/server classification. Add the mod back only after those checks. Avoid changing several packages at once, because you will lose the ability to identify the incompatible file.
Two copies of a plugin are loading
This usually indicates that a manager and a manual copy, or two managers, are controlling the same directory. Choose one workflow, remove the duplicate deployment through that workflow, and keep only the version declared by the active profile. Do not delete files blindly if you are unsure which manager owns them; disable the profile first and inspect its installed-file list.
Friends cannot join or see the same content
Compare the package’s client-side and server-side labels, then compare versions and dependencies on the server and every client that needs the mod. A client-only quality-of-life plugin may not need to be installed for everyone, but a world or progression mod commonly does. Restore the save backup if a removed content mod leaves unknown items or objects in the character or world.
Best Value
- Gaming Inspired Design
- Gaming and Geek Inspired
- Lightweight, Classic fit, Double-needle sleeve and bottom hem
The setup broke after a Valheim update
Pause mod additions and update the loader payload and affected plugins. A game update can make BepInEx files, unstripped assemblies, or an individual mod outdated. The Vortex extension documentation specifically warns that its payload and assemblies can become stale, so check for an updated tested payload before troubleshooting individual plugins. Launch a loader-only profile first, then add dependencies and mods one at a time.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteUpdating without losing a working setup
- Back up saves before updating the game or removing a content or progression mod.
- Record the profile’s mod list and versions, or preserve the manager profile so you can revert.
- After a major Valheim update, check for a current BepInExPack Valheim release or a current tested payload in your chosen manager.
- Update shared libraries before the mods that depend on them.
- Launch with only the loader and essential libraries enabled.
- Add gameplay and content mods in small groups, testing after each group.
- For a dedicated server, update the server and clients in a coordinated window and keep versions compatible.
- If a save behaves incorrectly after removing a mod, stop experimenting on the original and restore the backup.
Manual versus managed installation: the practical trade-off
Manual files are best when you need to see and control every DLL, want to follow an author’s exact folder instructions, or are maintaining a small, stable set. The cost is that you must track dependencies, remove old versions, and repair the layout after updates yourself.
A profile manager is better for experimenting, switching between mod collections, and sharing a repeatable setup. Its automatic dependency handling reduces routine work, but it only works when you launch through the manager and keep one manager in charge. Vortex is appropriate when the mods you need are distributed through its Nexus catalogue; Thunderstore Mod Manager and r2modman are appropriate for packages in the Thunderstore ecosystem, while Gale provides a profile workflow on Windows and Linux.
Safe removal and rollback
- Disable the mod in the active profile, or remove its files using the manager that installed them.
- Do not remove a library while another enabled mod still declares it as a dependency.
- For manual installs, move the plugin to a temporary backup folder instead of permanently deleting it on the first attempt.
- Test the game with the affected world only after confirming that the mod did not add required items or structures.
- Restore the save backup if the world or character contains missing content after removal.
The safest long-term pattern is a vanilla profile, a small test profile, and a separate multiplayer profile. Keep the multiplayer profile unchanged once the server and clients are working, and experiment in the test profile instead.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
