Sandustry Pipe Layouts: Fluid Routing Designs for Factories

Every pixel in Sandustry behaves like a tiny particle of matter, which means water flows, steam rises, and sand absorbs moisture in ways that feel almost alive. That same pixel-level simulation is exactly why Sandustry pipe layouts matter so much: a poorly routed pipe network can starve your furnaces, flood your sorting lines, or leave steam venting uselessly into the sky. Getting the routing right from the start saves you hours of rebuilding, and it directly determines whether your factory can scale into true Sandustry mass production or stalls at a few dozen machines.

The good news is that you don't need a degree in fluid dynamics to design reliable networks. By understanding a handful of core principles — branch points, merge junctions, loop backfeeds, and elevation changes — you can build pipe systems that handle thousands of pixels per minute without clogging. This guide breaks down the most effective Sandustry pipe layouts for mid-game and late-game factories, with concrete diagrams, comparison tables, and step-by-step builds you can drop into your own world. Whether you are routing water from a distant reservoir or distributing steam across a sprawling production hall, these designs will keep your fluids moving.

For optimal flow in Sandustry, arranging your pipes in a closed-loop configuration—rather than a single straight line—minimizes pressure drops and ensures even distribution, a principle explored further in our guide on the Pipe System.

According to Sandustry Pipe Layout Guide, optimal pipe layouts prioritize straight runs and minimal bends to reduce pressure drop and ensure consistent fluid flow across the network.

Core Principles Behind Every Sandustry Pipe Layout

Before you place a single pipe segment, it helps to understand how the simulation actually pushes fluid through your network. Sandustry treats each pixel as an independent particle, so water does not behave like a single column of liquid — it spreads, pools, and seeks the lowest available point based on gravity and pressure from surrounding pixels. That means a straight horizontal pipe is not automatically a reliable conveyor; you need to think about flow direction, capacity, and where fluid can escape.

Flow direction is determined by elevation and outlet pressure. Water naturally moves downhill, so a pipe running level across flat ground will only push fluid if there is enough incoming pressure from a pump or a taller reservoir behind it. Steam, on the other hand, rises because it is less dense than the surrounding air, which means you can route it upward without pumps as long as the outlet is above the source. This asymmetry is the single most important reason why Sandustry pipe layouts for water and steam look completely different.

Capacity is another constraint that catches new players off guard. Each pipe segment can only hold a limited number of pixels at once, and when you exceed that limit, the pipe backs up and flow stalls entirely. Community testing suggests that a single straight segment handles roughly 10 to 15 pixels per second under ideal conditions, though this number shifts with pipe length, elevation changes, and the number of branches feeding into it. If you are pulling water from a large lake, you will almost certainly need multiple parallel pipes rather than one oversized trunk line.

Pressure loss accumulates with every bend, junction, and elevation change. A 90-degree turn costs more flow than a gentle diagonal, and each T-junction splits the available pressure between two outlets. This is why the most efficient Sandustry pipe layouts minimize sharp turns and keep branch points as close to the destination as possible. Players who ignore pressure loss often find that their last machine in a chain runs at half speed, even though the first machine is drowning in fluid.

Backflow is the final piece of the puzzle. Because pixels can move in any direction when pressure equalizes, a dead-end pipe can slowly fill with water and then push it backward into the source when the outlet closes. Loop designs solve this by giving fluid a continuous path to circulate, which prevents stagnation and keeps pressure stable across the entire network.

Branch Layouts for Distributing Water Across Multiple Stations

The most common need in any factory is splitting a single water source across several machines — maybe three furnaces, two washing stations, and a cooling loop all draw from the same reservoir. A naive approach would be to run one long pipe and tap into it at each machine, but that creates a classic pressure problem: the first tap steals most of the flow, and the last machine gets a trickle. Instead, you want a branch layout that balances pressure across every outlet.

The simplest reliable design is a star topology, where the main trunk runs from the source to a central distribution hub, and each machine gets its own dedicated branch from that hub. This keeps every branch roughly the same length, which means pressure loss is similar across all outlets. In practice, a star layout works well for up to six or seven machines; beyond that, the hub itself becomes a bottleneck because it has to split the incoming flow into too many directions.

For larger factories, a tree topology with tiered branching works better. The trunk splits into two or three secondary lines, and each secondary line splits again to serve a small cluster of machines. This reduces the number of junctions any single pixel has to pass through, which keeps pressure loss lower than a star with many branches. The tradeoff is that you need to plan your machine placement carefully so that clusters make geographic sense.

Balanced branch spacing is the trick that most players overlook. If you tap the trunk at uneven intervals, the shorter branches will always steal more flow because they offer less resistance. Community reports suggest spacing branch points evenly — every 8 to 12 tiles — to keep pressure distribution predictable. You can also add small buffer tanks at each branch point; these absorb short-term demand spikes and smooth out the flow to each machine.

When to Use a Ring Branch Instead

A ring topology connects the trunk in a loop, so water can flow in both directions around the ring to reach any outlet. This is overkill for most factories, but it shines when you have a critical process that cannot afford to stall. If one side of the ring gets blocked by debris or a build error, water simply flows the other way around the loop, and your machines keep running. According to player testing, a ring layout adds roughly 20 percent more pipe material but provides dramatically better fault tolerance for Sandustry automation builds that run unattended for long sessions.

Merge Layouts for Combining Multiple Sources Into One Line

The opposite problem — combining several sources into a single output line — comes up just as often. Maybe you have three water pumps drawing from different parts of a lake, and you want to feed them all into one high-capacity trunk that supplies your entire factory. Or perhaps you are collecting steam from multiple boilers and routing it to a single turbine bank. Merge layouts solve this by giving each source a dedicated feed line that joins the main trunk at a controlled junction.

The critical rule for merges is never join two sources at the same point. When two pipes meet at a T-junction, the fluid from both sides collides, and the resulting turbulence slows both flows. Instead, stagger your merge points along the trunk, leaving at least 4 to 6 tiles between each junction. This gives the fluid time to re-establish laminar flow before the next source joins in, which keeps the combined throughput much closer to the sum of the individual inputs.

Pressure equalization matters even more for merges than for branches. If one source has higher pressure than the other, it will push fluid backward into the weaker source, effectively stealing its capacity. You can prevent this by adding a check valve — a one-way gate that only allows flow in the desired direction — or by placing a small buffer tank at each merge point. The tank absorbs the pressure difference and lets both sources contribute evenly.

For steam systems, merges have an extra complication: condensation. When steam from two different boilers meets, the temperature difference can cause some of it to condense back into water, which then pools in the pipe and blocks the flow. Players who run multi-boiler setups report that keeping merge points warm — by routing them close to the boilers or insulating them with surrounding structures — reduces condensation losses by as much as 30 percent.

Merging Water and Steam in the Same Network

Some advanced Sandustry automation ideas involve using the same pipe network for both water and steam, relying on the fact that steam rises while water sinks. In theory, you can route steam along the top of a pipe and water along the bottom, but in practice this is extremely finicky because the two fluids interact at the boundary. Community experiments show that this works only in short, straight segments with no junctions; any bend or split causes the fluids to mix and form a sluggish emulsion. Unless you are building a very specific contraption, it is almost always better to keep water and steam in separate networks.

Loop Layouts for Stable Pressure and Continuous Circulation

Loop layouts are the workhorses of large-scale Sandustry factories because they solve the two biggest problems with linear pipes: pressure drop and backflow. A loop is simply a pipe that starts at the source, runs through all your machines, and then returns to the source, creating a continuous circuit. Water circulates around the loop, and each machine taps into the flow as it passes by.

The main advantage of a loop is that pressure stays nearly constant at every tap point. Because fluid is always moving, there is no dead-end where pressure can stagnate, and the difference between the first and last machine is much smaller than in a linear layout. Players who switch from linear to loop designs often report that their entire production line speeds up by 10 to 20 percent, simply because every machine gets consistent flow.

Loop sizing is the key design decision. A loop that is too small — say, a 10-tile square — will have the same fluid circulating over and over, which means it never gets a chance to replenish from the source. A loop that is too large wastes pipe material and can develop slow spots where flow becomes sluggish. Based on community testing, a loop perimeter of 40 to 80 tiles works well for most mid-game factories, with the source pump feeding into one side and a return line bringing excess water back.

Multiple loops are better than one giant loop for very large factories. If you have a production hall with 30 machines, a single loop would need to be enormous, and the far side would still see some pressure drop. Instead, build two or three smaller loops, each serving a cluster of 8 to 12 machines, and connect them to the main trunk with short feeder lines. This keeps every loop within its optimal size range and gives you natural isolation points for maintenance.

Adding Buffer Tanks to Loops

A buffer tank placed at the source side of a loop acts as a reservoir that absorbs demand spikes. When a machine suddenly needs more water — say, a furnace batch completes and the next one starts — the tank provides immediate flow without waiting for the pump to catch up. This smooths out the pulsating demand that is common in batch-based production, and it also gives you a visual indicator of system health: if the tank level stays high, your loop is healthy; if it drops, you have a blockage or a pump that is underpowered.

Elevation and Pump Strategies for Complex Terrain

Sandustry terrain is rarely flat, and your pipe layouts need to handle elevation changes without losing flow. Water naturally flows downhill, so routing it down a slope is easy — but getting it uphill requires pumps, and the placement of those pumps matters more than their quantity.

Pump spacing is the first thing to get right. Each pump can lift water a limited height, and community testing suggests that a single pump raises water about 6 to 8 tiles before it needs another pump to continue. If you space pumps too far apart, the water column between them becomes unstable and flow stalls. If you space them too close, you waste power and create turbulence at each pump outlet.

Steam elevation is the opposite problem. Steam rises naturally, so routing it upward is free — but getting it down into a machine that sits below the boiler requires either a long vertical drop or a pump that forces it downward. Many players avoid this by placing steam consumers above the boilers, which is an elegant solution that costs nothing in pumps.

Terrain shortcuts can save you a lot of pipe. Instead of routing water around a hill, consider tunneling through it — a straight tunnel is almost always shorter than a winding surface path, and the pressure loss from a straight run is lower than from multiple bends. Players who plan their pipe routes before placing machines often find that a few minutes of terrain survey saves them hundreds of pipe segments later.

Dealing with Sand Absorption

One quirk of Sandustry is that sand absorbs surrounding water, which means buried pipes can slowly lose their contents to the surrounding terrain. If you route a pipe through a sandy area, you will notice the flow rate dropping over time as the sand drinks up the water. The fix is to line your pipe trench with non-absorbent material — stone, metal, or any solid block — before laying the pipe. This creates a barrier that keeps the water in the pipe and the sand dry. According to player reports, unlined pipes through sand lose up to 15 percent of their flow per 10 tiles, which adds up quickly on long runs.

Advanced Automation Builds Using Integrated Pipe Networks

Once you have mastered the basic layouts, you can start combining them into integrated networks that handle multiple fluids across your entire factory. The most effective Sandustry automation builds treat water and steam as part of a single closed-loop system, where water boils into steam, steam drives turbines, and the condensed steam returns as water to be reused.

The closed-loop power cycle is the classic example. Water from a reservoir feeds into a boiler, which produces steam that rises to a turbine bank. The turbine consumes the steam and outputs water, which then flows back to the boiler through a return pipe. This cycle runs indefinitely with minimal water loss — the only losses are from steam that escapes during pressure spikes and water that gets absorbed by nearby sand. A well-built closed loop can run for hours without needing a top-up, which makes it ideal for unattended Sandustry mass production runs.

Multi-fluid sorting is another advanced application. By using the fact that different fluids have different densities and behaviors, you can build a pipe network that automatically separates water, steam, and other liquids. For example, a vertical chamber with an outlet at the top and bottom will naturally route steam out the top and water out the bottom, since steam rises and water sinks. This is a simple but powerful separator that requires no moving parts.

Cascading pressure systems use the output of one process to power the input of another. For instance, the steam exhaust from a high-pressure turbine can be routed to a low-pressure boiler, where it provides pre-heating that reduces the fuel needed to reach boiling temperature. This kind of cascading design is where Sandustry automation ideas really shine, because it squeezes extra efficiency out of every pixel of fluid.

Scaling From Mid-Game to Late-Game

The jump from a mid-game factory to a late-game megafactory is where most pipe layouts break down. What worked for 10 machines will not work for 50, and you need to plan for scale from the beginning. The most successful approach is to build in modular blocks — each block is a self-contained loop with its own pump, buffer tank, and set of machines, and blocks connect to a central trunk line. This way, adding capacity means adding another block, not redesigning your entire network.

Frequently Asked Questions

What is the best pipe layout for a beginner factory?

Start with a simple linear layout from your water source to your first few machines, then upgrade to a loop layout once you have 5 or more machines. A loop gives you stable pressure and prevents backflow, which are the two most common problems beginners face. Keep your loop perimeter under 80 tiles for best results.

How many pumps do I need for a large water network?

A single pump can typically feed a loop serving 8 to 12 machines, assuming the terrain is flat. For every additional 8 to 10 machines, add another pump feeding into the loop at a different point. Space pumps at least 6 tiles apart to avoid turbulence, and always place a buffer tank at the primary pump outlet.

Can I use the same pipe for water and steam?

Technically yes, but it is almost always a bad idea. Water and steam mix at junctions and form a sluggish emulsion that blocks flow. Keep separate networks for water and steam unless you are building a very specific contraption like a gravity separator. The extra pipe cost is worth the reliability.

Why is my last machine getting almost no water?

This is a classic pressure loss problem. The last machine in a long linear chain gets the least pressure because every bend and junction before it steals flow. Switch to a loop layout or add a buffer tank near the last machine. You can also check for sand absorption if your pipe runs through sandy terrain.

How do I prevent backflow in my pipe network?

Backflow happens when pressure equalizes and fluid pushes backward from a dead-end branch. The best fix is to use a loop layout so fluid always has a path to circulate. You can also add one-way check valves at branch points, or place small buffer tanks that absorb pressure spikes before they can push fluid backward.