Quick Answer
The Sandustry demo is currently available through the official Steam store page. Use the “Download PC Demo” control on that page or find the demo from the Sandustry entry inside the Steam client. No crack, torrent, mirror, or standalone archive is needed.
The demo is the safest way to test the falling-pixel factory concept and your hardware before buying the Early Access game. The current official page confirms the demo's availability but does not, in the reviewed text, guarantee save transfer or define an exact content boundary. Those details are Pending confirmation and should be checked in the client or current official announcement before planning a long save.
How to Install the Official Demo
Sign in to Steam through the official client or website, open Sandustry's product page, and choose the demo download. Steam handles the package, updates, and launch entry, which keeps the source verifiable. If a page asks you to disable security software or run an unrelated installer, it is not the official route described here.
Use these steps:
- Open Sandustry on Steam.
- Confirm the developer is Lantto Games and the publisher is Hooded Horse.
- Select “Download PC Demo” and allow Steam to install it.
- Launch from your Steam Library rather than an external executable.
- Keep Steam updates enabled while the game remains in active development.
What the Demo Can Tell You
The official store describes Sandustry as factory automation in a fully destructible world where every pixel is a physical resource. A demo session can therefore answer whether you enjoy the interaction model: digging, mixing materials, routing physical particles, and iterating on a factory that may be orderly or chaotic. It can also reveal whether the interface and performance feel comfortable on your system.
Use the session to test basic responsiveness rather than to infer the full game's total depth. Early Access includes the content described on the store page and is expected to change, while a demo can remain a smaller or differently updated branch. An exact comparison of current demo and paid content is Pending confirmation unless the store or an official patch note provides it.
| Check | Why it matters | What not to assume |
|---|---|---|
| Launch and frame pacing | Confirms basic compatibility | That every late-game factory performs identically |
| Digging and movement | Tests the core tactile loop | That all tools are included in the demo |
| Material interaction | Shows the pixel simulation style | That every full-game reaction is accessible |
| Save creation | Confirms local persistence | That the save transfers to the paid build |
| Language selection | Tests readable interface text | That community mods support the same languages |
Demo Saves, Updates, and Mods
Do not promise yourself that a demo save will migrate. The reviewed official store text confirms a demo but does not state a save-transfer contract, so copy any important save only as a personal backup and expect that the paid version may require a fresh world. Save location and compatibility are version-sensitive and therefore Pending confirmation.
Avoid testing unofficial loaders as part of your first demo evaluation. If the vanilla demo fails, official support can reason about a clean installation; if several external tools are present, the cause becomes harder to isolate. Steam Workshop is listed for the full product, but exact Workshop availability and compatibility for the demo are Pending confirmation.
When to Move to Early Access
Buy only if the current Early Access state is valuable to you now. Steam explicitly warns that Early Access games are unfinished and can change, while the developer describes the current version as playable with the features on the store page. Waiting for more updates is a valid choice if you need a final content scope or stable long-term mod compatibility.
The store's current price and any discount are region- and time-sensitive. Check the live store while signed into your region rather than relying on a screenshot or this guide. The demo remains a separate try-before-buy route as long as the official Steam page continues to show it.
A Focused Demo Evaluation Plan
Start with a clean launch and confirm the selected language, display mode, input response, and save creation before building anything elaborate. Then follow the core loop shown by the official description: excavate material, observe how individual pixels move, create a small production route, and see whether a blockage is understandable. The purpose is to learn whether the physical automation model is enjoyable and readable, not to rush toward a feature that may belong only to the paid build.
Use a short checklist after the session instead of relying on first impressions. Note whether movement and digging felt predictable, whether the material state was visible, whether a simple factory could be corrected after a mistake, and whether performance remained acceptable as activity increased. These observations are specific to your hardware and demo build, so they should not be published as universal requirements or late-game guarantees.
| Evaluation area | Useful question |
|---|---|
| Controls | Can you place, inspect, and correct structures comfortably? |
| Pixel simulation | Can you understand why a material moved or reacted? |
| Factory iteration | Is finding and clearing a small blockage satisfying? |
| Performance | Does the demo remain responsive during your test setup? |
| Presentation | Is the chosen language and interface readable for you? |
What to Verify Before Continuing a Demo Save
Check the live store and official news for any statement about demo updates or save migration. If no explicit statement exists, treat transfer to the paid edition as Pending confirmation and avoid making the demo world your only record of an important design. Screenshots or written layout notes can preserve an idea without assuming binary save compatibility.
Also verify that advice you follow refers to the demo branch you are actually running. A guide using late Early Access tools may describe valid full-game mechanics while remaining unusable in the demo. When an item, research option, or Workshop function is absent, do not download a replacement file; first consider that the feature may simply fall outside the current demo scope.
Sources
Sandustry is developed by Lantto Games and published by Hooded Horse. This independent guide is not affiliated with or endorsed by the developer, publisher, Valve, or Microsoft.