How to Install, Update, and Restore Factorio Mods【Space Age Compatible】

If you want to work with mods in Factorio 2.0 and Space Age environments, it's safer to separate the convenience of the in-game Mod Portal from the strength of manual management by placing files in the mods folder. This article is written for everyone from first-timers installing QoL mods to those who want to manage official add-on mods including quality and Elevated Rails without disruption.

The core approach boils down to: know where your user data is located, back it up, check dependencies and startup logs, then update, disable, or restore with confidence. I personally started by sticking to one small QoL mod at a time, checking the logs before expanding, and that discipline kept me at zero save data accidents while transitioning to larger mods.

Prerequisites to Know Before Installing Factorio Mods

Target Version and Assumptions in This Guide

This guide assumes a Factorio 2.0 or later environment. For mod installation paths, I'll focus on the Mod Portal accessed from the in-game "MOD" screen and the browser version at factorio.com. The community generally uses the Mod Portal, though for Steam Workshop compatibility, I'd recommend checking primary sources (the official recommended path is typically described as Mod Portal).

The reason to clarify this upfront is that Factorio mod management doesn't end with just "where the game is installed." Saves, settings, mods, and script-output are organized on the user data side, and depending on the write-data setting described in the Application directory - Factorio Wiki, the location can vary. In other words, on the same PC, if you're looking at the wrong folder, the mod you thought you installed won't show up in the game—a basic but annoying discrepancy.

After version 2.0, the boundary between vanilla, DLC, and additional mods has become clearer. As a result, if you're not used to the idea that "official add-ons are also managed as mods," you might be momentarily confused when opening the mod list. When I first installed Space Age, I reviewed which DLC-derived mods were activated in the mod screen, then toggled quality individually to get a feel for how it works. This sequence helps you understand the official setup before adding community mods, making it much less confusing.

Note that adding or removing mods breaks replay data. Also, before installing a new version, backing up your saves and configuration directories is recommended. The "preserve first, then modify" workflow mentioned earlier remains valid in this 2.0 environment.

Application directory

wiki.factorio.com

Official Installation Routes

The most natural way to install mods in Factorio is searching and installing through the in-game Mod Portal. Considering ease of installation, dependency handling, and update tracking, this is the most stable entry point. The community widely uses this workflow, with automatic selection of required dependencies when installing from the in-game browser.

The Mod Portal on factorio.com (browser version) is better suited for searching and checking dependencies. Especially when you want to calmly understand "what does this mod depend on?" and "which version series is being updated?", the browser version has better clarity than the in-game interface. On a more technical note, the Mod portal API - Factorio Wiki api/mods/{name}/full endpoint can also retrieve dependency arrays. For people managing large mod configurations, server operations, or considering modpack pinning, knowing this API exists alone changes the outlook.

The strength of this method is version pinning and validation are straightforward. For example, if you want to keep a large mod at an older version, avoid breaking changes from updates, or preserve a reproduction environment, this is more manageable than in-game installation. In exchange, you're responsible for managing dependencies and conflicts yourself. Missing required prerequisites will simply fail at startup, and mixing DLC-required mods will be rejected on the spot. Note that UI labels and setting defaults can change between versions, so check the in-game settings screen for actual labels and defaults.

When you want to record your configuration, being able to write all active mods and versions to script-output/mods.txt is also convenient. When you want to reproduce something later, you won't have to recall "what did I install?" by hand, which is very helpful for validation environments. Factorio's mod management isn't designed around relying on a fancy dedicated launcher; rather, it combines the official Mod Portal, user data placement, logs, and output files—understanding it this way makes it easier to grasp.

Mod portal API

wiki.factorio.com

Clarifying Space Age, quality, and Elevated Rails

Space Age is a paid expansion released on October 21, 2024, and structurally comprises three additional mods. Combining the Japanese and English wiki entries for Space Age, the scope is quite large—4 new planets, 5 science pack types, 22 buildings, 30 intermediate products, 5 weapons, 2 enemy types, and 29 achievements are added. Even starting as an extension of vanilla, the feel partway through becomes an entirely separate phase. This DLC is genuinely closer to "another full Factorio game."

What matters here is that Space Age additions aren't "fixed features baked directly into the game engine"—they're also managed on the mod screen. That's why after installation, when you see the mod list, "what's official and what's community mod?" can be unclear at first, but the system keeps it in the same management interface. You can understand it on the regular mod screen.

quality is somewhat special among these: as noted in the Quality - Factorio Wiki, it's an independent mod you can activate separately, but using it requires owning Space Age. This is actually quite important—just because you installed Space Age doesn't mean you always have to play with quality. I initially toggled quality off and played for a few hours, then enabled it to see the difference. This approach made it easier to grasp where recipes, equipment feel, and production line meaning change.

Elevated Rails works similarly to quality conceptually. The official Elevated Rail as a Space Age feature exists, but the Mod Portal also has multiple community mods related to it. In other words, seeing "Elevated Rails-related names" in the mod list doesn't mean everything is the same thing. You need to distinguish between official DLC add-on mods and community mods that extend, accelerate, or adjust those features.

Once you can make this distinction, choosing mods in a Space Age environment becomes much easier. First understand the relationship between the 3 official add-on mods and quality, then layer on QoL and major mods. After Factorio 2.0, approaching mods in this order alone dramatically reduces mishaps.

Two Approaches to Installing Mods: In-Game Mod Portal vs. Manual Installation

Installation Steps via In-Game Mod Portal

The least confusing method is using the Mod Portal directly from the in-game "MOD" screen. Factorio makes this path straightforward, with search, installation, and updates completing in a single interface—that's the strength. Especially for adding a few QoL mods, it's much easier than manually tracking dependencies.

The actual workflow is simple: open "MOD" from the main menu, search for the mod you want in the installation tab, select it, and install. As widely known in the community, required dependencies are automatically selected with this method, benefiting beginners most. For instance, even if a library-type mod requires a standalone prerequisite, the in-game browser often follows along.

After installation, the mod appears in your mod list and is often shown as active. What matters isn't just whether installation succeeded but whether it loaded error-free at startup. The automatic dependency handling is quite convenient, but it doesn't completely ensure compatibility. With large mods or DLC-dependent configurations, installation can succeed while failing during load.

Technically, the Mod portal API - Factorio Wiki also clarifies mod information retrieval and download specs, with api/mods/{name}/full retrieving dependency arrays. You don't need to touch the API directly during normal play, but understanding that the in-game browser can handle dependencies more easily behind the scenes makes it clear why this method suits beginners.

Account Creation and Steam Integration Notes

One thing that can trip you up with the in-Game Mod Portal is sometimes requiring a factorio.com account to download. Even if you play Factorio via Steam, the mod retrieval path isn't directly tied to Steam's features—it involves authentication on the official Mod Portal side.

Because of this, even Steam purchasers benefit from creating a factorio.com account and linking it to their Steam account. Once that's done, the workflow of finding mods in-game and installing them directly becomes stable. Conversely, if this linking is unclear, you can end up in a state like "the game itself launches but I can't get mods," which causes confusion on first installation.

This understanding is especially important in Space Age environments. Official add-ons appear alongside community mods in the mod list context, so both DLC-derived elements and community mods sit on the same screen. If authentication also gets muddied here, it's hard to tell whether something is an installation failure, ownership issue, or dependency error. Personally, when setting up a new environment, I confirm login status in-game before touching mods. This one step makes cause identification much faster.

Manual Installation (mods folder placement) and zip Handling

Manual installation basically means placing a downloaded zip directly in the mods folder. You might imagine extracting it and putting just the inner folder there, but normally placing the zip as-is is sufficient. As mentioned earlier, using the mods folder in Factorio's user data side applies here; if you've changed write-data, that new location becomes the actual placement spot.

The strength of this method is version pinning and validation are straightforward. For scenarios like maintaining a large mod at an older version, avoiding breaking changes, or preserving reproduction environments, this is more manageable than in-game installation. In exchange, you're responsible for managing dependencies and conflicts. Missing required prerequisites will fail at startup, and mixing DLC-required content will be rejected outright.

An easy-to-overlook point: don't have multiple versions of the same mod coexisting. The community knows that parallel versions of the same mod in the mods folder won't launch. Before manual installation of a major mod, I always check that mods direct doesn't have duplicate zips or folders with the same name. Just this check cuts startup failures noticeably. Mundane in practice, but by far the most effective check.

If you're manually composing your configuration, load order and halt points become clear through logs, and writing all active mods and versions to script-output/mods.txt makes later configuration comparison easier. In the troubleshooting stage, this list proves surprisingly valuable. For combinations that tend to conflict, understanding the configuration organization approach discussed next makes handling easier.

Choosing Between Installation Methods

Installation method choice is less about superiority and more about choosing based on what you want to accomplish. For first-time QoL additions or regular play, the in-game Mod Portal is clearly easier. Search, install, and it even picks up some dependencies, so the pace of expansion is very light initially.

Conversely, for version pinning, validation reproduction, or prioritizing specific configuration preservation, manual installation suits better. The zip management approach is understated but offers significant value in staying stable without being pushed by updates. When working with configurations like Krastorio 2 or Space Exploration, this stability's worth becomes quite apparent.

The short difference is: in-game Mod Portal provides "installation ease," manual installation provides "configuration pinning ease." Manual management assumes you'll pick up missing dependencies and conflicts yourself, so jumping straight to large-scale installations when inexperienced often leads to trouble. In that sense, starting small in-game then shifting manual when needed feels natural.

Detailed understanding becomes clearer by separating "dependencies," "engine compatibility," and "load order" from a compatibility-checking perspective.

mods Folder and User Data Directory Location

OS-Specific User Data and mods Folder

In Factorio, user data directory is where mods, saves, and configuration files are managed. The mods folder you touch for manual installation sits here too, and understanding it as part of the same system as saves and settings makes organization clearer. The path varies by OS; exact structure is in the Application directory - Factorio Wiki.

Keeping the most common default paths in mind: Windows uses %APPDATA%\Factorio\mods, Linux uses ~/.factorio/mods, and macOS uses ~/Library/Application Support/factorio/mods as the baseline. The saves folder and configuration files sit alongside here, so thinking of "all of Factorio's user data as one" rather than isolating mods makes practical sense.

I've used Windows and Linux setups, and managing just mods separately was much harder than viewing mods, saves, and config as a single parent directory unit. Backup and sync units align, so accidents like "this environment has only new saves" or "that one has old settings" decrease. Juggling major mod configurations really reveals how much this difference matters.

Impact of write-data Option

An easy-to-miss point: the actual save location isn't fixed at the default path. Factorio lets you change the user data directory location via the write-data setting in config/config.ini. When you change this, mods folder location and all user data move with it.

That means if you think "Windows defaults to %APPDATA%\Factorio\mods," you'll come up empty on environments using write-data. Mods, saves, settings, and script-output all move together, making this setting foundational for manual installation, backup, and restoration. The zip placement work mentioned earlier happens in the directory write-data actually points to.

Understanding this setup makes multi-environment management much cleaner. I started explicitly setting write-data across my dual setup to align user data placement, and backup/sync suddenly became much easier. Rather than tracking just mods, the idea of pinning the parent directory that holds everything raises configuration reproducibility.

Relationship Between Saves, Settings, and player-data.json

The user data directory contains not just mods and saves but also settings and account-related info. Among these, player-data.json deserves mention. It's not just appearance settings; it's treated as a file containing Mod Portal tokens. Understanding this file's role when organizing mod retrieval and API usage prevents misreading situations.

To clarify: mods holds installed mod files, saves holds factory data mid-play, various settings files hold operation and display environment, and player-data.json holds player info and Mod Portal authentication helper data. They're all in the same user data directory, so backup and migration work better when you handle related groups together rather than isolating pieces.

Knowing this structure makes environment migration and restoration clearer—situations like "mods are back but login state differs" or "saves exist but settings didn't restore" suddenly make sense. Factorio's file operations are somewhat blunt, but understanding that saves, settings, and auth info live on the same foundation makes it much clearer what to touch to change what.

Safe Update, Disable, and Backup Workflows

Pre-Update Checklist and Backup

Engine updates and new mod installations see accident rates shift dramatically based on what you preserve before touching anything. Factorio consolidates mods, saves, and settings in the same user data directory, so pre-update backups work best when you ZIP the parent directory rather than chasing individual files. The Application directory - Factorio Wiki organizes by this location.

Practically, ZIPing just mods and saves separately before updates is less stable than ZIPing the entire user data directory—restoration is faster. I do this unit before major updates, and even when inconsistencies appear, rollback takes minimal time. Especially for updates like Space Age where official add-ons change significantly, this small step's value is quite high.

For pre-update checks, keeping three points wins over endless checklists:

1. Back up the entire user data directory
2. Duplicate the save you're actively playing
3. Be mindful whether this update breaks your current configuration before applying

The save duplication point is especially critical. Adding or removing mods affects not just load success but replay compatibility. As Replay system - Factorio Wiki notes, replay data breaks when mod configuration changes. Hardly noticeable during regular play, but invaluable when later wanting to reproduce or validate—pre-update save duplication is insurance bordering on standard procedure.

Disabling and Restoration (Rollback) Basics

Post-update issues are faster to solve by first asking can I revert to the stable state just before? rather than immediately troubleshooting. Factorio mod troubles usually stem from "game + mod + save combinations" rather than one broken file, so rollback also works on combinations.

The first step toward disabling is separating added or updated mods. But unchecking doesn't always restore everything. Saves load but content transforms, or the save was saved expecting that mod. Production-chain-adding mods especially have wide impact—removing them changes the factory entirely.

Restoration priority should favor reverting both the pre-update save copy and the pre-update mods state as a pair over just removing the problematic mod. This avoids "old save, new mods" inconsistency. As mentioned, treating user data as a parent-directory unit helps here too.

Easy-to-miss: auto-enabling of new mods on next launch. With zip-based mods folder configs, next startup often has the mod pre-enabled. Even thinking you've restored, leftover zips can re-cause issues. Restoring correctly means synchronizing "what files are placed" with "which mods activate."

Avoiding Multi-Version Coexistence Risk

Wanting to preserve older versions does happen—validation configs, save prolongation, compatibility waits, many reasons exist. The trap here is multiple versions in the same space. Keeping new and old zips in mods, plus updating the engine, makes which combination's active unclear. Troubleshooting becomes harder when mixing occurs, typically the worst-case scenario.

Preserving old versions is workable; management works best when you manually narrow to one. Running your active set and testing set from the same location is less stable than "place only the mods for this save right now." Manual installation especially locks in versions but leaves residue easily, growing into accident kindling if left unorganized.

Space Age areas are trickier—official additions and regular mods sit close together, so configuration boundaries blur. DLC-premised mods and non-premised mods coexist, making similar names mean different things. I avoid this mixing by keeping mods slender when validating. Heavy quantity for convenience loses to single-recipe-focused environment work—results stay faster.

Maintaining multi-version in parallel requires dividing engine, saves, and mods as unified units. Maintaining only one piece breaks consistency, and later reproduction falters. Factorio mod maintenance's actual difference lies in upkeep, not installation—avoiding mixing and clearly selecting one active config is itself strong safety.

Reading Dependencies, Compatibility, and Conflicts

Reading Dependencies

Most non-launching mods initially fail on dependency interpretation. Factorio's Mod Portal pages often show dependencies, and distribution files contain dependency info in info.json. In-game Mod Portal installation auto-picks required dependencies sometimes, but manual or version-pinned work needs you reading this yourself.

The key is asking what does this mod presume? not "does it work standalone?" Library-type, translation-helper, and overhauled-content-extension mods hide dependency weight. Mod Portal explanations matter less than dependency lists for real launch success—overlooking the latter is common.

To check mechanically, Mod portal API exposes api/mods/{name}/full with dependencies arrays. Retrieving this is very helpful when in-game displays feel incomplete. For team reproduction or tracking what depends on what, API tends toward internal accuracy; separation becomes faster.

I check dependency columns before reading descriptions when adding big mods. Grasping this first avoids "I added convenience; turns it needs platform X and DLC Y" accidents.

Confirming Factorio Engine Version Compatibility

Dependencies present doesn't guarantee launch—engine version matching is critical. Which engine version a mod targets is absolutely essential in Factorio. Major-update post-release especially sees popular mods stuck waiting, and here breakage shows more than installation itself.

Space Age released October 21, 2024; post-date, 2.0 migration and DLC support went full throttle. Big turning points like this turn yesterday's stable setup into overnight incompatibility. Space Age looks like additions while truly being DLC-essential, so "name visible means usable" judgment slips easily.

Mod Portal pages show compatible versions; distribution metadata tracks too. The sight line is straightforward: does your engine version match the mod's compatible versions? For extending old-save play, chasing new mods less serves; old-engine plus old-mod pinning stabilizes better. Back to parent-directory handling showing its value.

Error Messages, Logs, and Conflict Reading

Conflicts surface faster through error text and log sequence than guesswork. Factorio outputs very straightforwardly at launch, so the issue matters less than which load stage halts. Error screens first catch the failing mod's internal name.

Error-screen first-grab: the internal name. Display names help but errors use internal names, so mistaking this means searching for wrong mods on Mod Portal. More detailed look goes to Log file for load sequence and failure point. Logs show "how far did normal loading go," making A-caused-B-missing scenarios apparent.

Log-reading worth: skip the flashy full error text in favor of lines just before. Missing dependencies, version mismatch, competing definitions from other mods show context before the knockout punch. Heavy-mod environments especially benefit from following load sequence over final error alone. Systematic compatibility checking via mod-compatibility-check splitting "dependencies," "engine compatibility," "load order" prevents noise.

Internal Name (name) vs. Display Name (title) Difference

Factorio mod management's understated strength is internal name (name) and display name (title) being separate. Display names show human-readable in Portal and in-game; internal names live in info.json as identifiers. Logs, dependencies, APIs, save data use internal names, so troubleshooting without reading these keeps things disconnected.

Display names with decoration or similar-titled derivative mods look related visually but may be entirely different internally. Conversely, updated-prettier titles don't change old internal names. This gap means hunting by display looks alone on Mod Portal can miss the target mod.

API use also expects {name} in api/mods/{name}/full to be internal. That means dependency solving, log analysis, API use work with internal names; browsing lists uses display names—split this mentally to avoid confusion. I started habit-checking internal names after early log chasing left display-searched mods unresolved. Bigger mod collections really reward this split.

Common Errors and Fixes

Login and Account Issues

In-game Mod Portal surprisingly often hits Steam account assumed = factorio.com account confusion. Steam ownership doesn't flow to mod downloads—factorio.com authentication handles that separately. Realizing they're separate prevents the "Steam logged in but can't download mods" state.

Common: mixing Steam email with factorio.com username/password. In-game login fields demand one or the other; confusion causes "credentials right but denied" frustration. I blended them early, thinking Steam ownership just worked—came up empty.

Separation trick: Steam handles purchase and launch; factorio.com handles mod distribution auth. Splitting these prevents cross-wiring. Login-status review with factorio.com-info-in-mind runs faster than retry-password cycling. Aligning account sources before troubleshooting wins.

Multi-Version Coexistence / Dependency Missing Errors

Manual installation often sees same mod with multiple versions remaining in mods folder. Forgetting to remove pre-update zips while adding new ones leaves both, and launch stops even though latest seemed installed. Old validation files or backups staying put easily become conflict sources—"saving safe" often births conflict.

This error often resolves just consolidating mod folder to single versions. Pinning old versions means separate folders, leaving game-facing space with current-use-only files—simple segregation fixes. Old seveswith new-engine usually mismatch somewhere anyway; body-and-engine-and-saves staying together beats piecemeal surviving.

Another classic: missing dependency mods. In-game browser picks some required dependencies automatically; manual installs need you filling those. Checking Mod Portal dependency columns against the error name usually reveals "engine matches, base mods just absent." Space Age-adjacent mods especially trip on typical QoL-level dependency reading.

My sense: once touching several major mods, mindset shifts from "single mod installs" to "configuration installations." Solo seems handled; really prerequisite-plus-dependent bundles are singles. Missing isn't usually the main installed mod but its ecosystem.

Load Order / Startup Failure Checklist

Startup failures get closer faster through what was last added + what last loaded in logs than random culling. Log file preserves load sequence, so skipping the error summary to trace flow from slightly prior shows reality. A-halted seems true; really B-absence caught A in crossfire—common pattern.

Troubleshooting separates via "disable suspect, launch, re-enable piecewise"—slower seeming, actually quicker. Heavy-mod configs multiply frustration; cutting direct-addition and tracing log-end narrows better. Load-order issues show: solo-launches but combos fail. Discovering which pair breaks is the real troubleshooting content.

Narrow-down order:

1. Grab internal name from error screen
2. Trace prior-loaded mod in logs
3. OFF the directly-added/updated mod
4. Launch, then re-enable sequentially to find reproduction spot
5. Parse whether missing-dependency, duplication, or combination-cause

mods.txt Recording and Restoration Commands

Serious recovery gains from saving active mod configuration as text. Factorio's Console (mods.txt output) feature writes script-output/mods.txt with active mod names and versions. Whether manual or in-game install, having this list cuts "what did I install again?" accidents massively.

Even folder-zips sometimes mismatch active configs—not everything placed activates. mods.txt strength: retains actually-active combos. I've recovered post-failure by saving script-output/mods.txt, later manually recreating that exact setup—separate-meaning backup value. This record matters beyond snapshots.

Commands themselves are simple; value lives in comparing "last-stable-active" versus "broken-right-after" sets. Whether unmet prerequisite, update-version-shift, or just activation-state-change becomes visible in lists. Dependency-hunt-feeling work becomes record-backed precision. Reliable troubleshooting needs mods.txt, worthy of validation-environment standard.

Console

wiki.factorio.com

Advanced: Mod Portal API and Profile-Style Configuration Thinking

API Basics

For normal play, the in-game MOD browser (Mod Portal) search-and-install path feels most natural. Steam users typically launch this way too; Steam Workshop treatment varies by community, so checking official info or your environment's behavior before deciding operations is safest. Official guidance tends toward Mod Portal.

The interesting part: beyond auto-downloading, recording configurations themselves becomes possible. When which mod, which version, which dependencies you use moves into text or scripts, hand-remembered modsets become "reproducible setups." Touching a few major mods reveals this difference's significance. My reproduction iterations showed GUI-only management paled against storing configs—recovery speeds up markedly.

Related-mods searching organizes cleanly when space-age-compatibility becomes frame—pre-DLC QoL, post-DLC expansions, translation packs cluster naturally. Flagging these groups makes compatibility judgment and validation prioritization much smoother.

Token and player-data.json Relationship

API and authenticated downloads pivot on player-data.json token. Factorio lets username and token pairs authenticate API, letting authenticated downloads work. In-game browser usage hides backings, but external tools or custom scripts pulling Mod Portal hit this combination as their real entry.

Foundation: factorio.com account. Steam Factorio play still routes mods through factorio.com. Steam-user login friction often stems from unclear factorio.com + Steam linkage. Feel-sense "Steam means everything flows" causes snags here.

Tokens warrant caution. Sharing config directories wholesale or posting token-visible screenshots means auth-info leaks dressed as mod notes. API touch tempts direct script embedding; public repository or shared files must avoid it. Common use calls for "my-environment-only auth"—safety-first.

Profile-Style Operations (Environment Separation) Tips

Manual install strength: zip placement in mods folder makes configuration explicitly viewable. Windows defaults %APPDATA%\Factorio\mods, Linux ~/.factorio/mods, macOS ~/Library/Application Support/factorio/mods. In-game browser lacks convenience; version-pinning and validation environments strengthen here.

Critical: place zip unextracted. Factorio reads zips natively; hand-extraction over management confuses more. Equally watch: no same-mod multi-versions in single folder. Backup-keeping old-zips remaining turns intended recovery into startup kindling. Earlier overlap warnings apply.

Useful: profile-style operation. Factorio lacks built-in profile UI, but folder-content partitioning by purpose or write-data/--mod-directory switching achieves environment separation—"test," "production," "old-save" setups become practical. Testing new structures while preserving stable sets cut redo friction enormously. Fresh configs fail cleanly; stable ones survive.

In-game browser and manual/API semi-auto workflows aren't opposing—role division fits. Light use favors browser; pinning and reproducibility need manual. Want-code-config leads API deeper. Starting browser, graduation toward manual, then optional API depth feels smooth.

The beginning stays simple: start small, testable, and restorable. Shifting to "small test → document → expand" cut my mod troubles near zero. First, back up current saves and user data directory, add one QoL mod through in-game browser, check startup logs. No issues? Learn log and mods.txt habits before major mods. Space Age installed? Preview quality solo before activation—later choices grow much easier.

Related Articles (suggested)