Using and Sharing Blueprints in Satisfactory

Blueprints are files on your machine, which means they can be copied, backed up and shared. It also means importing someone else’s carries a few conditions that are not obvious until one fails to place.

Blueprints are files

Each blueprint you save produces up to two files:

• .sbp — the layout itself. This is the blueprint.
• .sbpcfg — description, icon and icon colour. Optional. A blueprint works without it; you just lose the description and get a randomised icon.

They live under %LOCALAPPDATA%\FactoryGame\Saved\SaveGames\blueprints\ on Windows, in a subfolder named after the world.

That per-world folder is the detail that matters. Blueprints are organised by save, not by installation. A blueprint sitting in the wrong world’s folder simply will not appear in game, which is the most common reason an import seems to have failed.

To use a design in a second world, copy the files into that world’s folder as well.

Back the folder up. Copying it somewhere safe costs nothing and it is the only protection your designs have — see the warning about deletion below.

Importing someone else’s

The mechanic is file placement: put the .sbp into the folder for the world you want to use it in. The .sbpcfg is optional but worth taking if it is offered, since it carries the creator’s description of what the module expects and produces.

Then reload the save. Downloaded blueprints do not appear in the build menu until the game save has been reloaded. This catches almost everyone the first time, and it looks identical to the blueprint not working.

Four things commonly go wrong.

You do not have the recipes unlocked. A blueprint containing Manufacturers will not place if you have not unlocked them. The blueprint is not broken — you are not far enough along. This is the most common cause of a downloaded blueprint refusing to appear usable.

It was made in a larger designer. A blueprint built in a Mk.2 or Mk.3 designer exceeds what a Mk.1 can hold, and you cannot open it for editing in a smaller one.

It assumes alternate recipes you do not have. A layout built around Coated Iron Plate is a layout that needs Coated Iron Plate. The machines will place; the ratios will not work.

You put it in the wrong world’s folder. Covered above, and it is the single most common cause of a blueprint that never shows up.

That third point is worth checking before you build ten copies of something. Read what a shared blueprint assumes, not just what it looks like.

Editing across designer tiers

A restriction that catches people upgrading their designer: a blueprint made in one tier cannot have its parts edited individually in a different tier.

What you can do is nest it — a Mk.1 blueprint can be placed inside a Mk.3 designer as a component of something larger. Blueprints compose upward but do not become editable when they move.

The practical rule: if you expect to revise a design, keep it in the tier you made it.

What travels with a blueprint

Colours and materials do. A module you painted carefully stamps out already painted, which is a good reason to finish the visual work before saving.

Vehicle paths do, since 1.2. A standard road segment with its path is one repeatable unit.

Belt connections to neighbours do not. Anything you attach after stamping is outside the blueprint, which also means blueprint dismantle mode will not remove it.

Costs are paid at stamping

Placing a blueprint costs the full materials for everything inside, drawn from your inventory or the Dimensional Depot.

That pairing matters more than it sounds. Without the Depot, a blueprint containing 200 concrete means carrying 200 concrete to every site you want to stamp it. With it, you walk over and place.

If you are planning to lean on blueprints, uploading their common ingredients to the Depot multiplies the benefit of both systems.

Sharing your own

If you are publishing a design, three things make it usable by someone else:

State the designer tier it was made in. Otherwise the first thing a downloader discovers is that they cannot open it.

List the alternate recipes it assumes. A layout built for Solid Steel Ingot is not a layout for the base recipe, and the ratios will be wrong rather than obviously broken.

State the input and output rates. A module that wants 120 iron ore per minute and produces 60 plates is immediately useful. One described only as “steel setup” is not.

The community sites that host blueprints are a legitimate way to distribute them, and several are well established. We do not host blueprints ourselves.

Should you use other people’s designs?

An honest answer, because opinions run strong.

They save real time, particularly for the fiddly standard modules everyone builds eventually — a balanced smelter row, a rail junction, a stairwell.

They cost you the understanding. Working out why a layout is arranged that way is most of what makes the next one easier to design. Stamping a downloaded module teaches you nothing about ratios.

The middle position most people land on: build your own production modules, download the structural and decorative pieces. The production logic is the game; the eighth identical stairwell is not.

Blueprints in multiplayer

Worth knowing because it differs from most shared systems in the game.

Milestones, MAM research and Space Elevator progress are all properties of the save. Blueprints are not — they are files on each player’s own machine, so a design one person made does not appear in anyone else’s build menu.

Sharing within a group therefore works the same way as sharing with strangers: copy the files. That is a mild annoyance for a co-op group who all want the same module, and it is worth doing once rather than each person rebuilding the design separately.

Versioning your own library

Once you have more than a handful, a design you superseded becomes clutter in a menu you use constantly.

Three habits that keep the library workable:

Name by function and size. “Smelter cell 4x” tells you when to reach for it; “blueprint 7” does not.

Be careful deleting. Removing a blueprint deletes the file from your computer, and it cannot be undone — not even by loading an older save. The design does not live in the save file, so rolling back the world does not bring it back. Move things you are unsure about out of the folder rather than deleting them in game.

Keep one backup copy outside the game directory before a large revision. Between overwriting a working design and the irreversible in-game delete, this folder is the only thing standing between you and losing an hour’s work permanently.

Common mistakes

Downloading a blueprint you cannot yet place. Check the unlocks before assuming it is broken.

Ignoring what alternate recipes a design assumes. The machines place, the ratios fail.

Expecting to edit a Mk.3 blueprint in a Mk.1 designer. Tiers do not edit each other’s work, though they nest.

Deleting a blueprint to tidy up. It is permanent and a save rollback will not recover it. Move the file out of the folder instead.

Forgetting to reload the save after importing. The blueprint is there; the menu has not noticed yet.

Never backing up the folder. Your designs are files and nothing else protects them.

Publishing a design without stating its rates. It is not usable without them.