Quick answer: Satisfactory blueprints live in their own directory on the server, per world. Upload the .sbp and .sbpcfg files to /SaveGames/blueprints/<world_name>/ over SFTP and they become available to everyone playing that world. They do not travel with the save and they do not sync between players on their own, which is why one engineer's beautiful design stays stubbornly stuck on one engineer's machine.
Why your teammate cannot see your blueprint
Blueprints are stored separately from the save file. That is the whole confusion in one sentence.
When you design something in the Blueprint Designer, the result is written as a pair of files on your machine. Joining a dedicated server does not upload them, and a teammate loading the same world does not receive them. The world is shared. The blueprint library is not.
So a blueprint that exists on your PC exists nowhere else until somebody copies the files.
The two files, and why you need both
Every blueprint is a pair:
.sbpis the blueprint itself, the actual building data.sbpcfgis its configuration, including the name and icon you gave it
Copy only the .sbp and the blueprint may appear without its identity, or not appear cleanly at all. Move them together, always. This is the most common mistake and it produces confusing results rather than an obvious error.
Where to put them
On the server, the path is:
/SaveGames/blueprints/<world_name>/
Note the <world_name> part, because it is where people go wrong. Blueprints are stored per world, not per server. If you run two worlds on one server, a blueprint dropped into one world's folder does not appear in the other. Copy them into each world you want them available in.
Upload over SFTP, restart or reload, and the designs appear in your teammates' blueprint menus.
A workflow that actually holds up
For a group building a factory together, the pattern that works is treating blueprints like shared assets rather than personal files.
Nominate one person to maintain the library. Not because others cannot, but because a folder that four people write to independently becomes a mess of near duplicate names within a week.
Name them so the name survives without you. smelter-4x tells the next person what it is. bp_final_v3_REAL does not.
Copy the pair into the world folder when a design is finished, not while it is still being iterated on. Half finished blueprints in the shared library are worse than no blueprints, because someone will build one.
While we are in the file system: watch your disk
Two things about a Satisfactory server that surprise people, and they compound.
Saves get large. An endgame factory save can reach several gigabytes. That is not a bug, it is a consequence of tracking a very large number of placed objects.
You want multiple backup generations. One backup is not a backup strategy for a factory representing a hundred hours of work.
Together, plan for roughly 20GB of free disk to hold the server binaries, your saves, and a few generations of backups comfortably. It is the resource people forget to check because RAM gets all the attention.
Update 1.2 is on stable
For anyone still on 1.1: Update 1.2 hit Experimental on 17 March 2026 and was promoted to the Stable branch on 2 June 2026. If you are running a server that has not been touched since spring, that is worth knowing before you troubleshoot something that was fixed months ago.
The two ports, since it comes up in the same breath
A Satisfactory server needs two ports open, and this trips up nearly everyone setting one up for the first time.
Port 7777 is the standard game port. It does not support redirection: the internal and external port numbers must match. If you are used to remapping ports freely, this one will not let you.
Port 8888 is the Reliable Messaging Port, required since patch 1.1.0.0. Unlike 7777, this one can be remapped using the -ExternalReliablePort launch parameter.
The classic symptom of getting this wrong is a server that appears in the list but cannot actually be joined. If that is what you are seeing, it is the second port.
Sizing a Satisfactory server
Memory follows factory size, not player count. That is the single most useful thing to know when picking a plan.
| Stage | Realistic RAM |
|---|---|
| Early game, small factory | 6GB |
| Mid game, a few production chains | 8 to 12GB |
| Late game megabase, trains, thousands of machines | 12GB+ and climbing |
Our Satisfactory hosting starts at EUR 8 a month, and the honest advice is to start where your factory is now rather than where you hope it will be. Moving up later is easy. Paying for a megabase you have not built yet is just paying.
FAQ
Where do Satisfactory blueprints go on a dedicated server?
/SaveGames/blueprints/<world_name>/. Upload over SFTP. They are stored per world, not per server.
Do blueprints sync between players automatically? No. They are stored separately from the save and do not travel with it. Somebody has to copy the files.
Which files do I need to copy?
Both the .sbp and the matching .sbpcfg. Copying only one produces confusing partial results rather than a clear error.
Why does my blueprint not appear in my other world? Because blueprints are per world. Copy the pair into each world folder where you want them available.
How much disk does a Satisfactory server need? Around 20GB to hold binaries, saves and a few backup generations. Endgame saves alone can reach several gigabytes.
Why can players see my server but not join it? Usually the second port. Satisfactory needs both 7777 and the Reliable Messaging Port, default 8888, and 7777 cannot be remapped.
Related reading: Satisfactory dedicated server network and CPU requirements, or Satisfactory hosting plans across four regions.