Sandustry Demo Guide

Get the official demo

Open Sandustry's official Steam store page and use the demo action shown there. This ties the download to the correct application and current platform requirements. No third-party archive is needed for the verified PC demo described on this page.

Confirm that the demo action belongs to the official Sandustry app page before downloading. The listing identifies Lantto Games as developer and Hooded Horse as publisher. That route provides the current platform requirements and avoids third-party archives whose version, contents, and save paths cannot be verified.

Let Steam finish installation and start with default settings. Record the version shown by the demo if available. A guide or video can demonstrate a different demo hotfix or the paid Early Access build, so attach every observation to the build actually running on your machine.

What to learn first

Focus on the systems that define Sandustry: mine Dirt into Sand, wet it with Water, process Wet Sand through a Shaker, move Gold into a Collector, and use research plus logistics to reduce manual handling. Those tasks reveal whether the physical factory model suits you.

Use the first session to test the complete early loop rather than only digging. Mine Dirt into Sand, control Water contact, produce Wet Sand, feed a Shaker, separate the guaranteed Residue from chance Gold, and move Gold into collection. This sequence reveals how physics, chance output, machine geometry, and progression interact.

Build each step as a small visible module with input, output, overflow, and a player path. Practice selecting and removing buildings and clearing one jam. If the Filter or another later tool is available in the demo version, use the live control prompt and test with labeled material instead of memorizing a key from another build.

Measure whether the interface gives enough information for your preferred factory style. Try tracing one material backward from Collector to source, pause the feed, clear a full output, and restart. These small recovery tasks reveal as much about the game loop as reaching the next research unlock.

Explore far enough to see how excavation and production compete for space, but do not treat a demo boundary as proof that the full game ends there. Write down the systems you enjoyed and the constraints you want to verify in the current Early Access build, such as later fluids, thermal work, energy, Aura, or mods.

When sharing a demo result, include its version and call it a demo observation. Do not publish machine rates, controls, or save guarantees as current Early Access facts without checking the paid build or official documentation. Version labels keep otherwise useful beginner experiments from becoming stale advice.

Finish the evaluation with a written decision: which factory loop worked, which control or performance question remains, and which official page will answer it. This keeps the demo useful even if its progression ends before the systems that appear in the current paid build. Preserve those notes with the exact installed demo version and target platform so the comparison remains useful after later Early Access patches.

Version and save caveats

A demo may lag behind the current Early Access version, limit progression, or use different balance. Do not assume a demo save transfers unless the official store or developer explicitly says so for the current build; preserve the save before uninstalling or moving versions.

Treat the demo as a product sample with its own scope. The paid build entered Early Access on August 13, 2026 and has already received multiple updates, including v0.5.6. Mechanics, balance, map generation, performance, and available research may differ even when the same material or building name appears.

Do not promise save transfer unless the current official page or developer post explicitly confirms it. Before installing the paid build or removing the demo, copy the save if the platform exposes it and keep a note with the demo version. Steam Cloud status alone does not prove that two editions use compatible save data.

When comparing performance, reproduce the same scale and settings. A small demo factory cannot predict every late-game Aura, Lava, thermal, fluid, or modded workload. Use the demo to decide whether the core pixel-physics automation is enjoyable, then consult current Early Access guides for systems introduced after its branch.

Field facts