Satisfactory Blueprint Guide: Build, Save and Reuse Factory Modules

The quick answer: unlock the Blueprint Designer Mk.1 at Tier 4 through the FICSIT Blueprints milestone, then build small, repeatable modules inside its 32 m × 32 m × 32 m space and save them with clear names. Place blueprints with the Build Gun, keeping inputs and outputs on consistent sides so every stamp connects quickly. Treat a Satisfactory blueprint as a repeatable, clean idea rather than a copy of a messy factory, that is what makes it scale.

Blueprints are the feature that changes how you actually build in Satisfactory. Instead of hand-placing every constructor, belt and power pole, you capture a proven arrangement once and stamp it down wherever you need it. This guide covers unlocking the designer, designing modules that connect without rework, naming and saving them, placing them in the world, and installing shared blueprints on a server.

What you need before you start

• Satisfactory on PC, PlayStation 5 or Xbox Series X/S. The 1.0 version launched on PC on 10 September 2024, with console versions arriving on 4 November 2025.
• Tier 4 reached and the FICSIT Blueprints milestone completed to unlock the Blueprint Designer Mk.1.
• A stable recipe you intend to place several times. Reinforced plates, rotors, screws, steel pipes and encased industrial beams are good first candidates.
• For sharing or server installs: blueprint files (commonly .sbp, sometimes .sbpcfg) matching your game version, plus matching mods on every player and the server if the design uses modded buildings.

Unlock the Blueprint Designer at Tier 4

1. Progress your HUB until you reach Tier 4.
2. Complete the FICSIT Blueprints milestone. This unlocks the Blueprint Designer Mk.1.
3. Build the designer and step inside its 32 m × 32 m × 32 m build space, enough for foundations, constructors, belts, power poles and storage blocks.

Later tiers unlock the Mk.2 and Mk.3 designers, which offer a larger build space for wider modules and large late-game production blocks.

Do not blueprint everything the moment the milestone unlocks. The right moment is when a recipe is stable and you plan to place it repeatedly.

Design your first module to connect cleanly

Your first blueprint should solve a repeated action, not attempt a perfect megabase. One module, one job.

Keep inputs and outputs on consistent sides. If every module you build takes materials in on the left and pushes them out on the right, every placement connects without manual belt fixes. Power connectors should land in the same relative spot each time too, so you can chain modules together without hunting for a free pole.

Start simple: foundations, belts, power poles, constructors and storage blocks. These are the building blocks you will reuse most, and they are the easiest to get right.

Leave room for upgrades. Better belts and machines unlock later, so a module should be easy to swap rather than a sealed box you have to demolish.

Name and save blueprints for long saves

Blueprint categories are save-specific, so organisation matters on long-running worlds. A messy library is worse than no library at all.

Name every blueprint with the recipe, throughput, version and input direction. A name like "Reinforced Plate 5/min v1 L-in" tells you everything you need at a glance when you are scrolling a long list mid-build.

Only save modules you expect to place several times. The save interface rewards a clean naming habit from the very first blueprint, and that habit pays off once your library grows.

Place blueprints with the Build Gun

Blueprints are placed with the Build Gun and have a forward direction based on the control bench. Check orientation before you stamp anything down.

1. Open the Blueprint menu (default key: B).
2. Confirm the module's input and output faces line up with your belts and power lines.
3. Place it, then connect the stubs.

That is the entire point of the system.

Share blueprints or install them on a server

Community hubs such as SatisfactoryTools, Reddit and dedicated Discord servers are where most shared designs live. Most blueprints arrive as .sbp files, and some include a .sbpcfg file alongside.

To install them on a dedicated server:

1. Connect to your server via SFTP using WinSCP or FileZilla.
2. Enable hidden files in your client. In WinSCP, open the settings gear, go to Panels, then enable Show hidden files. Without this, /.config/ stays invisible and you will think the server ate your blueprint.
3. Create the folder path /.config/Epic/FactoryGame/Saved/SaveGames/blueprints/<exact world name>/. The folder name must match your world name character-for-character, or the blueprint will not appear in the Blueprint menu. To find the exact world name, open /.config/Epic/FactoryGame/Saved/SaveGames/server/ and look at the autosaves named like _autosave_0.sav; use the part before _autosave as the folder name. Create the folder if it does not already exist.
4. Upload the .sbp files (and any .sbpcfg files) into that folder with the server stopped, then start or restart the server and check the Blueprint menu (default: B).

If a blueprint does not appear after that, work through this checklist: confirm hidden files are enabled in your SFTP client, confirm the folder name matches the world name exactly and is case-sensitive, confirm the file extension is .sbp, and confirm the blueprint was made for your game version. Blueprints made for a different version may not show up at all, or may behave oddly once placed. If a design uses modded buildings, every player and the server must run the exact same mods.

What goes wrong and how to recover

• Blueprint not appearing: check the world-name folder, the file extension, hidden files and the game version in that order, then restart the server or reload the save.
• Do not rebuild by hand.
• Modded blueprint failing: if the blueprint uses modded parts, players must have the same mods installed and the server must run them too. Every player and the server need the same versions.

Common mistakes to avoid

• Blueprinting a messy factory: you copy the spaghetti instead of a clean, repeatable idea.
• Inconsistent input and output sides, which forces manual belt fixes at every single placement.
• Installing server blueprints into a folder that does not exactly match the world name, so nothing appears in the Blueprint menu.
• Forgetting to enable hidden files in your SFTP client, making /.config/ seem missing.
• Mixing blueprint and server game versions, or running missing mods on one player.

Turning blueprints into a scalable factory plan

Build a small library of named modules before you expand production: an aligned foundation tile, a two-constructor block, a four-constructor block, a storage block with splitter and merger access, and a power module.

Version notes

Keep an eye on official channels for blueprint changes. Coffee Stain's updates page is the authoritative source. Check the official 1.2 update page (satisfactorygame.com/updates/1-2) and the patch notes for your platform before relying on any blueprint behaviour. As of the 1.2 update, the game is live on all platforms, the first Satisfactory update to launch simultaneously on PC, PS5 and Xbox Series S/X.

Looking further ahead, the Core Values expansion was announced as heading underground without belts, which suggests resource movement may change in a big way. Whatever comes next, the habit that matters now is the same: build clean, name clearly, and stamp often.