Sandustry Blueprints - Save, Export and Share Designs

Blueprints save a tested layout, not its surroundings

Sandustry has an in-game blueprint system. The practical use is to copy a working factory module, save it in blueprint history, and place that layout again when you need a repeatable section. The saved design carries the selected structures, but the new site still needs matching inputs, outputs, height, and fluid access.

Treat a blueprint as a construction record rather than a guarantee of identical behavior. Terrain is destructible, routes can be blocked, and Early Access updates can change building interactions. Test a small copy before replacing a large working factory.

Select a clean module with the in-game controls

The Beginner's Guide confirms the copy and paste shortcuts used for repeated construction. Select only the module you want to repeat: its feeder, production building, output lane, and the minimum filter or launcher needed to keep it moving. Excluding unrelated walls and temporary piles makes the blueprint easier to inspect later.

Keep one known-good version running while you copy. If the source module is already blocked, the blueprint will reproduce the blockage and make diagnosis harder. Clear the input and output first, then observe at least one complete cycle before saving.

Save the layout to blueprint history

A Steam discussion and the blueprint tutorial describe saving a copied layout through the game's blueprint history. Use the current interface and save control shown by your build. The exact menu labels can change, so this article avoids inventing a keyboard shortcut or a hidden file location.

Name or organize saved designs by purpose instead of by a temporary location. A label such as a water conversion module or a residue clearing module tells you what the inputs and outputs should be when you place it elsewhere. Do not claim a design works for every version without testing it.

Export and import are Early Access-sensitive

The recent blueprint tutorial explicitly covers exporting builds, while community discussion explains the history and save icon. The current sources do not define a universal share-string syntax or promise cross-version compatibility. Follow the export and import controls exposed in the active build and keep a local copy only through the supported workflow.

If an imported design is missing a structure or fails to load, first confirm the game branch and update version. A modded building or a changed recipe can make a previously valid module incomplete. The exact compatibility rules are to be confirmed after future updates.

Audit the placement site before trusting the copy

Check the input material and its matter state, then trace the output route to an empty buffer. For a Kinetic Press, count the required drop height. For Water systems, confirm that Pumps, Pipes, and Liquid Vents can connect without a solid blocker. For a Shaker, preserve the diagonal residue path.

Place the module on a test patch when possible. Watch the first cycle, inspect every filter, and remove temporary scaffolding only after the outputs move correctly. This catches differences between the source terrain and the new location before they become a factory-wide outage.

Blueprint troubleshooting checklist

• Verify that every copied structure is unlocked in the current save.
• Confirm that the input and output lanes are not occupied by terrain or old piles.
• Check height and fluid routes instead of assuming the copied coordinates still fit.
• Disable recently added mods when a blueprint behaves differently.
• Recheck the official update history after a patch.