Sandustry Sand Types and Uses – Sort Materials Without Guessing
Learn Sandustry sand identification, safe sampling, labeling, and routing so mixed materials do not silently contaminate production chains.
Published 2026-08-21 · Updated 2026-08-21 · Early Access guidance
Start from properties, not color alone
The official description says individual grains, flakes, seeds, spores, and ice chips are simulated physical entities with their own properties. That makes visual similarity an unsafe basis for a large automated route. Identify a material by where it came from, how it moves, whether it absorbs or reacts, and what a controlled process produces. Early Access can alter names or recipes, so this guide deliberately avoids presenting a frozen encyclopedia of every material. Its goal is a repeatable method you can use with the current build.
Create a sample bay
Build a small isolated bay beside the main factory. Carry in a tiny sample, label its source in your notes, and observe it without other materials present. Check how it settles, whether water changes it, and whether normal transport captures it. Keep heat and ignition away unless the sample test explicitly requires them. A failed experiment should cost a handful of pixels, not a reservoir or an hour of production. Restore the bay to a known clean state between samples so residue from one test cannot affect the next.
Separate raw, conditioned, and output states
Treat dry sand, wet sand, processed output, and residue as four routing identities even when two look similar at a glance. Give each its own lane or chamber. Crossovers should be visible and intentional. Never send a return stream directly into a raw input without a filter or inspection pocket. The store description explicitly connects sand absorbing water, wet sand, and gold sifting; it does not justify assuming that every byproduct can share the same route. Separation makes later upgrades safer and makes blockages legible.
Label by task
Use practical labels such as RAW-SAND, WET-FEED, GOLD-OUT, and RESIDUE-HOLD rather than relying only on game terminology. Task labels survive balance and naming changes. In the blueprint notebook, record the source, destination, last verified date, and any required condition such as water, heat, or height. If a community blueprint names a material differently, compare the observable property and process before joining it to your factory.
Prevent mixed-feed failures
Mixed materials often create intermittent failures: one pixel passes, another bridges an opening, and a third reaches a chamber that cannot process it. Install an inspection pocket before a narrow or expensive stage. Add an overflow that leads to quarantine, not back to the primary feed. Run a short mixed test while watching the lowest and narrowest points. If a contaminant enters, stop input first, preserve the scene, and trace backward rather than digging through the output side.
Maintain a current material ledger
Keep one table per save with columns for material, source, observed behavior, accepted destination, rejected destination, and build/date tested. Link each row to a screenshot or blueprint note stored locally if useful, but never treat an image from an older demo as proof of current retail behavior. This ledger becomes the data source for calculator rates and automation decisions. It also tells you which uncertainty is worth testing next instead of encouraging random factory changes.
Sources and evidence notes
- Sandustry on Steam
Tier 1. Developer/publisher description, Early Access status, features, and requirements; checked 2026-08-21.
- Sandustry by Lantto
Tier 1. Developer overview of falling sand, automation, exploration, bosses, puzzles, and tech; demo-era mechanics are not treated as retail balance facts.
- r/SandustryGame community
Tier 4. Used for demand signals and candidate failure modes; ratios and workarounds require in-game verification.