Why Build an Iron Sand Module?
An iron sand blueprint matters because it turns an awkward conversion step into a reusable factory block. Instead of rebuilding grinders, belts, storage, and output routing whenever excess iron appears, you can place a tested module and immediately put that iron to work.
Iron Sand is useful both as a bridge back into Iron Ingots and as an input for copper powder processing. A compact layout gives you a controlled way to handle surplus iron while leaving room to expand into soap-fed copper production later.
| Process | Input | Output | Device | Craft Time |
|---|---|---|---|---|
| Grind iron | 1 Iron Ingot | 1 Iron Sand | Grinder | 30 seconds |
| Smelt sand | 1 Iron Sand | 1 Iron Ingot | Crucible | 6 seconds |
| Wash sand | 6 Iron Sand + 6 Soap Powder | 1 Copper Powder or 1 Impure Copper Powder | Athanor | 6 seconds |
The basic conversion cycle is deliberately simple: Iron Ingots enter a Grinder, then Iron Sand leaves on a dedicated belt. The Grinder produces one sand every 30 seconds, or 2 per minute, so downstream equipment can easily keep up. One Crucible can process substantially more sand than one Grinder supplies, making it a practical overflow or recovery destination.
Treat the blueprint as a module with a purpose, not merely a row of machines. Its job might be “convert spare iron into copper inputs,” “hold iron sand for later,” or “recycle sand into ingots.” Naming the blueprint around that purpose prevents confusion once your blueprint library grows.
Plan the Iron Sand Layout
Start with the smallest version that solves your current problem. A single Grinder, chest, and belt may be enough if you only occasionally create extra Iron Ingots. Add processing branches only when you have a reliable use for the output.
A useful alchemy factory iron sand blueprint usually has three zones: iron intake, sand production, and one or more output routes. Keeping those zones distinct makes the module easier to inspect, rotate, and connect to another production line.
| Zone | Recommended contents | Reason |
|---|---|---|
| Intake | Iron storage, input belt, Grinder | Keeps ingots supplied without hand-feeding |
| Conversion | Iron Sand belt and buffer chest | Makes the slow Grinder output visible and manageable |
| Recovery | Crucible and ingot output | Returns unused sand to Iron Ingots |
| Copper branch | Athanor, Soap Powder input, output sorting | Converts sand into copper-related materials |
| Overflow | Storage or disposal connection | Prevents a blocked output from stopping the module |
Place the Grinder near the input storage so the iron route stays short. Put a chest after the Grinder if you want the system to continue producing sand while the copper branch is paused. That buffer also lets you stockpile sand before expanding the blueprint.
The Crucible recovery route is especially useful when you want flexibility. Iron Sand placed into a Crucible becomes an Iron Ingot in 6 seconds, so it can consume a sand backlog far faster than the Grinder creates it. This branch is not intended to increase iron; it is a way to recover material when sand is no longer the best use for it.
For a copper-focused version, route Iron Sand toward an Athanor and provide Soap Powder on a separate input. The recipe consumes six of each ingredient and produces either Copper Powder or Impure Copper Powder. Because the two outcomes are split evenly over repeated production, plan separate storage or sorting capacity for both results.
Before saving, make sure the selected area includes every working part:
- Input and output belts
- Machines and their intended orientation
- Storage chests or portals
- Connections carrying Soap Powder, fuel, or recovered ingots
- Any filters or overflow handling
- Adequate open space around the placement footprint
A blueprint captures what is selected, not what you meant to include. Missing a short belt segment can turn a dependable module into a placement that looks finished but does not run.
Build and Test the Blueprint
Build the module in its final operating state before you save it. Feed it enough Iron Ingots to confirm that the Grinder produces Iron Sand, then test each connected output route independently.
| Test | What to check | Successful result |
|---|---|---|
| Iron input | Belt reaches the Grinder | Grinder receives Iron Ingots consistently |
| Sand output | Grinder exit is clear | Iron Sand reaches its chest or branch belt |
| Crucible route | Sand enters the Crucible | Iron Ingots return on the recovery belt |
| Athanor route | Both sand and soap arrive | Copper-related outputs appear without input stalls |
| Overflow | Storage has capacity | Production does not stop when demand changes |
If the blueprint includes both a Crucible and an Athanor, decide which route gets priority. A simple manual or belt-based split is enough if you want both to run. If copper production is the goal, keep the Athanor supplied first and send excess Iron Sand to the recovery path. If Iron Sand is only temporary storage, send it directly to the Crucible when the buffer becomes full.
Do not assume the Athanor output is always the same item. The recipe produces Copper Powder and Impure Copper Powder in an even split over its sequence, rather than behaving like an unpredictable one-time gamble. Still, build as if both outputs will arrive: give each a destination so the line cannot clog when you are away from the factory.
Once the factory operates correctly, create the blueprint with the in-game selection workflow:
- Select the full working structure.
- Press
Fto copy the selection. - Press
Hto open the blueprint-saving interface. - Enter a clear name and a short description.
- Confirm the save after checking the selection one final time.
A name such as Iron Sand Copper Mk1 tells you more than a vague label like Module 4. If you later improve belt routing, buffering, or throughput, save the revision as Mk2 instead of overwriting your only dependable version.
Place, Scale, and Organize Copies
Open the Build menu with Q, choose the Blueprints tab, select the saved layout, and use the placement preview before confirming. The preview is your chance to catch blocked belt exits, poor alignment, or a rotation that makes the module difficult to connect.
| Placement check | Why it matters |
|---|---|
| Output side faces the intended bus | Avoids rebuilding belts after placement |
| Iron intake is near storage or supply | Keeps the module compact |
| Soap route has a practical connection | Prevents an idle copper branch |
| Chest access remains clear | Makes troubleshooting and manual transfers easier |
| Nearby space supports expansion | Lets you add another module cleanly |
Rotation makes a single blueprint more versatile. A copper-processing version may fit neatly along one side of a central belt bus, while a recovery version can sit close to an Iron Ingot line. Use the preview to confirm that machine ports still face usable directions after rotation.
Scale by copying the entire tested module rather than adding random extra Grinders into its middle. Each Grinder produces only 2 Iron Sand per minute, so a larger demand for sand is usually best met with several identical copies. That approach also makes rates and maintenance easier to understand: every copy has the same input, buffer, and output logic.
Keep your blueprint collection organized by production role. The blueprint menu becomes much more valuable when you can quickly distinguish a sand-only module from a copper-processing module or a recovery module.
Good organization habits include:
- Use the product name first:
Iron Sand,Copper Powder, orIron Recovery. - Add a version marker after any meaningful redesign.
- Describe required inputs, especially Soap Powder.
- Keep early, reliable versions instead of deleting them immediately.
- Group related blueprints in folders if your collection becomes large.
Blueprint files can also be organized outside the game’s menu through the blueprint directory. If you move files into folders, refresh the blueprint directory in-game so the updated structure appears. Keep naming readable; an automatically generated filename is much less helpful than a clear label when you return to a build weeks later.
FAQ
What is an alchemy factory iron sand blueprint?
It is a saved factory layout built around producing, storing, recovering, or processing Iron Sand. A useful version includes the Grinder that turns Iron Ingots into Iron Sand, plus belts and optional machines for your intended use.
How do I make Iron Sand?
Put one Iron Ingot into a Grinder. The recipe takes 30 seconds and produces one Iron Sand.
Can Iron Sand become Iron Ingots again?
Yes. Feed Iron Sand into a Crucible. One Iron Sand becomes one Iron Ingot in 6 seconds.
Why include an Athanor in this blueprint?
An Athanor can combine 6 Iron Sand and 6 Soap Powder. It produces either Copper Powder or Impure Copper Powder, making the module a way to turn spare iron into material for copper-related production.
When should I save the blueprint?
Save it only after all belts, connections, machine directions, and output handling have been tested. A working small module is more valuable than a large blueprint that needs repairs every time you place it.