How to Save, Import, and Reuse Blueprints Instead of Rebuilding

Separate two jobs in your head. If you only need another copy of something right now, use the regular selection and copy system — press C, drag the selection around the section, then Ctrl+C.

From there you can paste another copy and continue building. That is enough when you are duplicating one working module beside another and connecting both to the same larger line. Do not interrupt the build just to create a permanent Blueprint every time.

Do not save a design because it looks finished. Save it because you have watched material enter one side and get the intended result out the other.

A factory module can look perfect while one Filter is backwards, one machine is missing, a belt points the wrong way, heat never reaches the consumer, an output has nowhere to go, or one block was outside the original selection. If you save that version, you have saved a reusable mistake.

After copying a section, open Building with Q and switch to the Blueprints tab. The current copied selection appears in the Clipboard. From there use Save as Blueprint.

Give the Blueprint a name that tells you what the module actually does — names like Kinetic Press, Gold Washer, or Flower Burner rather than Factory 1 or Good Setup. Once you have several saved modules, the name should tell you why you saved it.

Sandustry lets you save very large selections, but the reusable designs you will like most are smaller modules with a clear job: process one input, separate the outputs, deliver them at predictable locations.

If you save one enormous factory, you inherit all of its assumptions — where the Water is, where the Sand enters, how much vertical room exists, where the next production stage needs to go. A smaller module is easier to fit into a new factory.

After saving a Blueprint, you can export it as a string. That string is the portable version of the design — you can keep it somewhere else or share it with another player.

This is where you distinguish three jobs: copy/paste for immediate building, a saved Blueprint for a design you want available again, and an exported string when that design needs to travel outside the current library.

When you have a Blueprint string you want to use, do not paste it directly into the world. Open the Building menu and go to:

Do not place a new imported Blueprint directly against the most crowded part of your factory. Give yourself room so you can see how it works and have enough space to integrate it.

A working example was a Basic Plinko Shaker design — after importing it, the module was placed and then duplicated to build several copies in a row. It is better to spend a little more room on a module you can inspect than to save a few blocks and make every later connection awkward.

Importing a Blueprint does not make you trust it blindly. Inspect it before you connect a major supply line.

A Blueprint is a shortcut, not a contract. If you import a useful design but one section does not fit your factory, change it. You may move the whole module, widen one side, change where the output leaves, alter the surrounding belt route, or connect it to a different storage area.

Do not throw away a good Blueprint because the final 10% needs adapting. The value of the Blueprint is that you did not have to rebuild the other 90% manually.

One very practical shortcut matters here: Ctrl+Z can undo a bad paste. Use it immediately when you realize the module landed somewhere you did not want.

Cleaning up a large module block by block is exactly the kind of work Blueprints are supposed to save you from. The faster you admit the placement is wrong, the less cleanup you create for yourself.

What you actually want is a tileable module — one Shaker unit, one Kinetic Press section, or one complete burner module. Then you can prove one copy works and repeat it.

That gives you a better scaling decision: if one module keeps up, stop; if input is accumulating faster than it can process, paste another. You are scaling a known working unit instead of designing a larger factory from scratch every time throughput rises.

There are plenty of structures you never save. If you know you will demolish something as soon as the next research unlock arrives, leave it temporary. If a layout only works because of strange terrain in the current world, you are less interested in preserving it. If you are still babysitting the system constantly, fix it before you save it.

The Blueprints you keep are the ones where you can say: I would be happy to build this exact module again.

Once you know a module is good, the routine is: