Where to Put DLC Files for Civ VI Using File Explorer

Civilization VI supports a wide range of downloadable content — from new civilizations and scenario packs to full expansions. Most players grab DLC through Steam, which handles file placement automatically. But if you've acquired DLC files manually (through a backup, a bundle, or another legitimate source), knowing exactly where those files belong in your directory structure is essential. Getting it wrong means Civ VI simply won't recognize the content.

Here's what you need to know about the folder structure, what goes where, and why the right placement matters.

How Civ VI Reads DLC Files

Civilization VI uses a modular content system. Each DLC pack lives in its own named subfolder, and the game scans those folders at launch to determine what content is available. If the folder is in the wrong location — or named incorrectly — the game either ignores it entirely or throws an error.

This is different from how some older games work, where you might drop a single file into a root directory and call it done. Civ VI expects a specific folder hierarchy, and it checks that hierarchy every time you start the game.

The Default DLC Directory Path

The standard installation path for Civ VI DLC on a Windows PC using Steam is:

C:Program Files (x86)SteamsteamappscommonSid Meier's Civilization VIDLC 

If Steam is installed on a different drive or in a custom directory, the path before steamapps will differ — but the steamappscommonSid Meier's Civilization VIDLC portion remains consistent.

To find your exact path using File Explorer:

1. Open File Explorer
2. Navigate to your Steam installation folder (commonly C:Program Files (x86)Steam or D:Steam)
3. Go to steamapps → common → Sid Meier's Civilization VI
4. Open the DLC folder

Inside, you'll see subfolders with names like Aztec, Poland, Vikings, Nubia, etc. Each folder represents a distinct DLC pack and contains its own internal file structure.

What a Properly Structured DLC Folder Looks Like 🗂️

Each DLC subfolder typically contains:

The .modinfo file is especially critical. Without it, the game cannot identify or load the DLC, even if all other assets are present. When placing files manually, confirm this file is present at the root level of each DLC subfolder.

Manually Placing DLC Files: Step by Step

If you have DLC files extracted from a legitimate archive or backup:

1. Open File Explorer and navigate to the DLC folder using the path above
2. If the DLC subfolder doesn't already exist, create it — using the exact same folder name as the original DLC pack (names are case-sensitive on some systems and must match what the .modinfo references)
3. Place the contents of the DLC pack into that subfolder, preserving the internal folder structure
4. Launch Civ VI and check Additional Content in the main menu to confirm the DLC appears

Do not flatten the folder structure. Dropping all files into the root DLC folder without subfolders will not work.

Steam vs. Manual Installs: Key Differences

Steam-managed DLC is handled entirely by the Steam client. When you own DLC through Steam, it downloads and places files automatically — you don't need to touch File Explorer at all. Steam also verifies file integrity, so if something gets corrupted or goes missing, you can use the Verify Integrity of Game Files option to restore it.

Manually placed DLC bypasses Steam's verification system entirely. The game may load it, but Steam won't "know" it's there — meaning if you verify file integrity later, Steam might not touch those files, or in some cases could flag inconsistencies. This distinction matters depending on how you manage your install long-term.

What Can Go Wrong

A few common issues when placing DLC files manually:

• Wrong folder name — the subfolder name doesn't match what the .modinfo expects
• Missing .modinfo file — the DLC won't appear in-game at all
• Nested incorrectly — content is one level too deep or too shallow in the directory
• Permissions issue — the Program Files directory sometimes requires administrator access to modify; running File Explorer as admin or moving the Steam library to a non-system drive resolves this
• Expansion conflict — some DLC packs have dependencies on the base Expansions (Rise & Fall, Gathering Storm). Content tied to those expansions won't function without the expansion itself installed, regardless of file placement

The Variable That Changes Everything 🔍

Where things get more nuanced is in non-standard setups. If you're running Civ VI through a non-Steam launcher, through an Epic Games Store install, or via a custom Steam library path on a secondary drive, the directory structure is similar but the root path changes significantly. Epic's version, for example, uses a completely different base directory.

Users running mods alongside DLC also need to understand that mods go in a different location entirely — typically in the user's DocumentsMy GamesSid Meier's Civilization VIMods folder — and the two should never be mixed.

Your Steam library location, whether you're using Steam or another platform, and whether you're working with true DLC or mod content all determine which path applies to your situation and what the right placement looks like for your specific install.