Last updated: July 4, 2026
shapez 2 Hub Design Guide
Hub design is where shapez 2 transitions from a game about building machines to a game about building systems. Every player eventually reaches a point where individual production lines work fine in isolation, but the moment you try to deliver multiple shape types simultaneously, belts tangle, machines starve, and the factory grinds to a halt. This is called spaghetti — the chaotic belt routing that happens when production lines are added reactively without a coherent plan. This guide teaches you how to design compact, scalable hubs that avoid spaghetti from the start, and how to clean up existing messes without tearing everything down.
What Is a Hub and Why Does Design Matter?
The Hub in shapez 2 is the central delivery point where you submit shapes to complete goals and progress through the technology tree. Every production line in your factory ultimately exists to feed shapes into the Hub. A well-designed hub area — the collection of belt routes, sorters, and delivery points around the Hub — ensures that shapes arrive reliably, that the system can handle multiple simultaneous delivery goals, and that you can scale production without rebuilding from scratch.
The cost of poor hub design compounds over time. A messy hub wastes belt capacity, makes debugging nearly impossible, and creates psychological resistance to expansion — you stop building new production lines because you dread routing new belts through the chaos. A clean hub, by contrast, makes expansion feel effortless: you connect a new production block to the delivery system, shapes flow to the Hub, and you move on to the next goal. The design principles in this guide are drawn from the shapez 2 community's most effective factory layouts and apply whether you are building your second production line or your fiftieth.
The fundamental tradeoff in hub design is between compactness and clarity. A compact hub minimizes belt travel distance, which reduces latency and saves space. A clear hub makes it easy to trace any shape from its origin to the Hub, which makes debugging fast. The best designs achieve both by using structured belt corridors, labeled zones, and modular production blocks that snap together predictably.
Hub Design Patterns: Choosing Your Layout
Different hub layouts suit different playstyles and stages of the game. The table below covers the seven most common hub design patterns, their strengths, and their weaknesses. Choose a pattern based on your current goals — simplicity for early game, scalability for mid game, and optimization for late game.
| Pattern | Description | Pros | Cons |
|---|---|---|---|
| Linear Hub | Single belt line running straight through all processing buildings in sequence. | Simplest to build. Easy to debug — follow the belt from start to finish. | Long footprint. Hard to scale without rebuilding. Belts back up when one stage stalls. |
| Grid Hub | Buildings arranged in a square grid with belts running in parallel rows and columns. | Compact footprint. Scales by extending the grid in any direction. Easy to tile blueprints. | Belt intersections require careful routing. Can become confusing at large scales without labels. |
| Modular Block Hub | Self-contained production blocks, each producing one sub-shape, connected to a central delivery belt. | Highest scalability. Each block is independently blueprinted and replaced. Easy to isolate and debug issues. | Requires more upfront planning. Belt balancers needed between blocks to distribute input evenly. |
| Spoke-and-Wheel Hub | Central hub delivery point with production lines radiating outward like spokes on a wheel. | Short belt paths to the Hub. Visually intuitive. Easy to add new spoke lines for new shape types. | Requires radial belt routing which is harder to blueprint. Wasted space between spokes. |
| Multi-Layer Stack Hub | Production stages stacked vertically using platform layers, with belts moving up/down between layers. | Extremely compact footprint. Separates production stages physically. Clean visual separation. | Requires platform technology unlock. Harder to debug across layers. Belt pathing between floors is complex. |
| Inline Sorter Hub | Sorter buildings placed inline on the main belt to route shapes to side processing branches automatically. | Automated routing without manual splitters. Handles mixed-shape belts efficiently. | Sorter throughput is limited. Requires careful filter configuration. Misconfigured sorters cause silent failures. |
| Buffer Tank Hub | Storage buffers placed between every production stage to absorb throughput fluctuations. | Maximum stability. Factory survives upstream stalls for minutes before downstream stops. Easy to identify which stage is failing. | Large footprint. Buffers mask underlying throughput problems. More buildings to manage. |
Anti-Spaghetti: Causes and Cures
Spaghetti is not a single problem — it is a family of related symptoms that all stem from reactive building without a plan. The table below identifies the six most common causes of spaghetti, the visible symptom you will observe, and the structural fix that eliminates the root cause. Apply these fixes proactively when designing new hubs and reactively when cleaning up existing ones.
| Cause | Symptom | Fix |
|---|---|---|
| Ad-hoc belt placement | Belts crisscross with no clear path, making it impossible to trace a shape from extractor to Hub. | Plan belt lanes before placing buildings. Assign dedicated corridors for input and output belts. |
| No overflow management | When the Hub is full, belts back up through the entire production chain, stopping all machines. | Place Trash buildings or overflow storage at the end of every belt line before it reaches the Hub. |
| Mixed shape types on one belt | Different shapes share a belt, causing machines to receive the wrong input and jam. | Use dedicated belts per shape type. If mixing is necessary, use Sorters to split before processing. |
| Building on top of existing infrastructure | New production lines are squeezed between old ones, creating belt spaghetti over time. | Zone your factory into districts. Reserve expansion space between zones before building. |
| Unplanned scaling | Production lines are copy-pasted in random orientations to meet new goals, creating a tangled mess. | Design tileable blueprints from the start. Always paste in the same orientation along a grid. |
| No belt hierarchy | Fast main belts and slow local belts are mixed together, causing congestion and confusion. | Establish a belt hierarchy: high-throughput trunk belts for long distances, local feeder belts for machine connections. |
Compact Hub Design Principles
Building a compact hub means minimizing the distance shapes travel between production and delivery without sacrificing clarity. The first principle is belt corridor discipline. Assign every belt a dedicated lane — input belts run along one side of the hub, output belts along the other. Never let a belt cross perpendicular to the main flow direction unless it passes through a dedicated underground or bridge crossing. Belt corridors that run parallel and never intersect are the visual hallmark of a well-designed hub.
The second principle is modular production blocks. Instead of placing individual machines ad-hoc, design a self-contained block that takes raw shapes on one side and outputs a finished sub-shape on the other. A typical block is five to seven tiles wide and produces one painted half-shape or one stacked shape. Blueprint the block, then tile copies side by side. Each block connects its output to the main delivery belt independently, so you can add or remove blocks without disrupting the others. This modular approach is what allows compact hubs to scale — you are not redesigning the hub, you are adding identical blocks.
The third principle is input balancing. When multiple production blocks share a raw resource supply, use Balancers to distribute shapes evenly across all blocks. Without Balancers, the first block in the line consumes all available resources and downstream blocks starve. A properly balanced hub ensures that every block receives an equal share of input, which means every block produces at the same rate and the output belt runs at consistent throughput. Place Balancers at every split point in the belt network — they are cheap to build and prevent the most common cause of uneven production.
Optimization: Beyond the Basics
Once your hub is clean and modular, optimization means squeezing more throughput out of the same footprint. The most impactful optimization is parallelization of bottleneck buildings. The Stacker and Painter both operate at 0.5 shapes per second — half the rate of Extractors and Cutters. If your hub has one Stacker per production line, that Stacker is the bottleneck. Adding a second Stacker in parallel doubles the throughput of that stage without adding any belt length. Identify which building type is the bottleneck in each production block and add a second instance in parallel.
The second optimization is belt tier upgrades. Higher tier belts move shapes faster, which increases throughput per lane. Before upgrading belts, measure your actual throughput — if your belts are not running at full capacity, upgrading them provides no benefit. Full-capacity belts indicate that the bottleneck is elsewhere in the system. Upgrade the bottleneck building first, then upgrade belts once they become the limiting factor. This prevents wasted resources on belt upgrades that do not improve overall throughput.
The third optimization is overflow recycling. Instead of sending excess shapes to Trash, route them back into the input side of the production block via a feedback belt. This is especially useful for paint and color production, where excess mixed paint can be reprocessed rather than wasted. Overflow recycling requires a dedicated return belt and a Merger at the input, but it eliminates waste entirely and ensures that every shape produced eventually reaches the Hub or is consumed by another production line.
Frequently Asked Questions
Q: How do I fix spaghetti without tearing down my whole factory?
Fix spaghetti incrementally, one belt corridor at a time. Start by identifying the main input and output belt paths — these are your trunk lines. Reroute any belt that crosses a trunk line to go under or over it using bridges or tunnels. Then, group machines by function: all cutters in one row, all stackers in another. Connect the rows with short feeder belts. You do not need to tear down everything — relocate machines one at a time while keeping the old belts running until the new layout is functional. Once the new corridor is working, delete the old belt path.
Q: What is the most space-efficient hub layout for late game?
The Multi-Layer Stack Hub is the most space-efficient layout for late game, because it uses vertical space that linear and grid layouts waste. Build each production stage on a separate platform layer, connected by vertical belt lifts. The ground floor holds extractors and raw shape storage, the second layer holds cutters and rotators, the third holds stackers and painters, and the top layer is the Hub delivery area. This layout requires platform technology but reduces the hub footprint to roughly one-quarter of an equivalent linear layout while maintaining full throughput.
Q: Should I use one mega-hub or multiple smaller hubs?
For most of the game, one well-designed mega-hub is better than multiple small hubs. A single hub centralizes delivery, makes debugging easier, and allows you to share infrastructure like paint production and overflow management across all production lines. The exception is when your factory spans a very large map area and belt travel time becomes a significant latency factor. In that case, build secondary delivery outposts that collect finished shapes from remote production lines and transport them to the main Hub via trains or long-distance belts. Keep one primary Hub as the main delivery point — the game only counts shapes delivered to the main Hub for goal completion.