Choosing Factory Design Patterns in Factorio - 3 Key Criteria

Around the time you reach red to blue science in Factorio, your factory can suddenly feel cramped. I hit the same wall with main bus width limitations and the yellow belt's 15 items/second ceiling, forcing a complete redesign.

This article focuses primarily on Factorio vanilla 2.0, while also considering how Space Age shifts your design assumptions. I'll organize four patterns—spaghetti, main bus, modular, and train-based—for beginners to intermediate players.

What matters most isn't memorizing the "correct" layout, but choosing a design style that fits your factory by evaluating three axes: throughput needs, available space, and future expansion plans. Understanding what to transport via belt long distances versus what to produce locally is the key. I'll walk through the decision process step-by-step, grounded in belt, beacon, rail, and power numbers you can verify on the official wiki.

How to Choose Your Factory Design Pattern

Understanding the Context and How to Read This Guide

This article won't tell you which design is "strongest." Instead, I focus on what problem you're facing right now. Whether you're rushing through early game, experiencing configuration collapse at blue science, or planning late-game resource absorption via trains completely changes which pattern you should choose. This guide aligns each method with specific pain points so you can make informed decisions.

Let me establish terminology first. Main Bus is the practice of consolidating frequently-used materials like iron plates, copper plates, and circuit boards onto a central artery line, then having individual production lines branch off horizontally to draw from it. It's often presented as the beginner-friendly base layout because it brings structure to your factory. The trade-off is that the main bus consumes significant belt width, and poor expansion decisions create a "long but visible" factory rather than a compact one.

Beacons distribute module effects across a 9×9 area at half strength. They're crucial for late-game density, but each one consumes 480 kW, so placement adds serious power overhead. They're not early-game heroes—they matter when you start thinking about end-game space optimization. Stackers (waiting areas in front of train stations) prevent gridlock when multiple trains target the same station. Without them, multi-train designs jam up immediately.

UPS (Updates Per Second) represents late-game processing load. Your design's quality shows not just in production numbers but also in how smoothly the factory runs at scale. Quality is a Space Age addition that lets you strengthen equipment and machinery to higher tiers—a "vertical" enhancement instead of just expanding horizontally. This fundamentally changes design decisions made under vanilla 2.0 assumptions.

I made the classic early mistake myself: dropping assemblers and belts wherever space existed, losing control around blue science. I couldn't tell if iron was the bottleneck, circuits were backed up, or what needed fixing. That's when I switched to keeping a decision table handy and setting clear rules like "main bus through this stage," then "switch to trains beyond this throughput."

The comparison is straightforward: for raw speed, spaghetti still wins; for stable first completion, main bus is most approachable; for expansion and late-game viability, modular and train-based have the edge. Main bus is an excellent low-failure starting point, not that it's universally optimal.

This guide primarily targets vanilla 2.0. The design decisions are grounded in sections on belt transport, rail systems, beacons, and power generation. I stick to verified numbers. For example, yellow belts carry 15 items/second. Red and blue belt throughputs are calculated from relative speeds (red = 2x, blue = 3x), yielding approximately 30 items/s and 45 items/s respectively. I treat these as guidelines; if primary sources exist, they take priority. When deciding main bus width, I use this conversion to determine whether to dual-track a material or segregate it entirely.

This table is simple to interpret: materials that branch multiple times are suited for the bus, while products consumed in large quantities on specific lines are better produced locally. Main bus is a user-friendly method for beginners, but overloading it can slow it down significantly. If stability up to blue science is desired, the main line should remain a passage for primary materials, and heavy intermediates should be closed off in the design. At this stage, maintaining a focus on "keeping the central artery narrow" is sufficient.

One key insight: your three transport modes (belts, rails, logistics robots) split your design's character. Main bus centers on belts; train-based centers on rails; late-game modules often lean toward robots. Comparing designs is really about choosing which logistics mode to anchor on, not just comparing visual layouts.

Tutorials

wiki.factorio.com

Target Version and Data Sources

This guide primarily targets vanilla 2.0. The design decisions are grounded in the official wiki's sections on belt transport, rail systems, beacons, and power generation. I stick to verified numbers. For example, yellow belts carry 15 items/second per the official spec. Red and blue belt throughputs are calculated from relative speeds (red = 2x, blue = 3x), yielding approximately 30 items/s and 45 items/s respectively. I treat these as guidelines; if official primary sources exist, they take priority. When deciding main bus width, I use this conversion to determine whether to dual-track a material or segregate it entirely.

Beacons are equally important for late-game math. The 9×9 range with 50% effect transfer and 480 kW per unit makes their trade-off crystal clear: high density comes at the cost of pre-paid power and footprint overhead, not "free bonus optimization."

Power examples also teach design thinking. Solar panels and accumulators have a 21:25 optimal ratio, and 23.8 solar panels sustain 1 MW continuously. While this guide focuses on layouts, late-game beacon and logistics network expansions make power planning an integral part of design. Factory and power designs are separate conceptually but deeply intertwined in practice.

Rails introduce signals and stackers as the foundation for multi-train viability. Train-based designs work well at scale precisely because station design, signals, and waiting areas can be templated and repeated. The opposite is also true: jumping to train-based layouts too early without understanding signals makes debugging harder than belt networks.

I'll also clearly mark established facts (like "beacons work in 9×9 ranges" or "multiple trains need signals") versus practical design interpretation (like "modular templates are easier to expand than single-point scaling"). The four patterns don't have an official "correct" form; this article distills how each addresses specific expansion challenges in vanilla 2.0 and beyond.

Old Steam guides and community posts may contain outdated version info. They're useful for design philosophy but don't anchor this article's numbers or mechanics. The comparison tables here exist to help you identify which pattern solves your current bottleneck, not to rank them universally.

The Four Core Design Patterns Explained

Pattern Definitions and Intended Scale

Factory design discussion gets messy because visual appearance and logistics are conflated. Here I'll separate the four patterns by what drives your expansion. This mental model helped me decide whether a problem needed a local patch or a full redesign.

Spaghetti means dropping machines wherever space exists, then connecting them ad hoc. It's the fastest early setup—you're strong through red-green science while you're racing for initial resources on your starting patch. Belt runs are short, research moves quickly. But once you want to expand an iron line or circuit line, existing belts start crossing and visibility collapses. You can't easily trace supply chains or identify bottlenecks, making it weak for planned expansion. Think of it as early game through red-green science.

Main Bus consolidates high-use materials (iron plates, copper plates, circuit boards) into parallel trunk lines, with production flowing horizontally off the main. The tutorial explains this as a structure-giving philosophy. Beginners gravitate to it because item flow is nearly one-directional and visible. You can count belt lanes and spot shortages. The downside is horizontal sprawl—you end up with a "clear but very wide" factory. Best for mid-game through blue science and the midgame phase overall.

Modular splits production into independent functional blocks: one for circuits, one for smelting, one for science packs. The advantage is replication—standardize inputs and outputs, then duplicate the same block to scale up. It's scalable but requires upfront planning on block boundaries and internal routing. Suited from blue science onward through end-game.

Train-Based (Distributed) scatters smelting, circuits, oil, and science production across remote outposts, connected by rail. Long-distance and large-scale dispersal are its strengths—you're not constantly rebuilding as ore patches run out. However, train networks require signals and stackers to work reliably. Multi-train operation depends on proper blocking and waiting area design. Best for late-game scaling.

In practice, progression often looks like: spaghetti until red-green, switch to main bus for blue, gradually introduce modular blocks, finally transition to trains when you need massive dispersal. Building a late-game pattern too early means wasted setup; matching your current bottleneck to the right pattern minimizes restart costs.

User:Fried biter/workspace2

wiki.factorio.com

Comparison Matrix

A table makes the distinctions concrete. The goal isn't "which is strongest" but which pattern handles your current growth without strain.

The key trade-off is expansion capability versus planning burden. Spaghetti favors today's research over tomorrow's growth. Trains favor tomorrow's scaling over today's setup. Main bus sits in the middle, giving beginners a structured entry point. Modular and train-based look similar in the table but differ fundamentally: modular is about block-level replication, trains are about distance-enabling transport. Whether you want to duplicate production units or link far-flung facilities shapes your choice.

Decision Flowchart

If the matrix feels indecisive, filter by progress stage and current pain. Patterns are chosen by what's hurting now, not by preference.

1. Red-green science: maximize research and early resource grab

Spaghetti dominates here. Raw output and defense matter more than architectural beauty. This is your opportunity window.

1. Blue science hits, iron/circuit/oil routing becomes invisible

Switch to main bus. A single trunk instantly makes item flow and shortage locations visible. Most new players report understanding factory design here.

1. Main bus running fine, but you want to duplicate specific production blocks independently

Modular is your answer. Carve out circuit, refining, or science as self-contained units. You fix the problem area without touching the whole plant.

1. Resources spread far, running multiple large blocks at once

Train-based time. Standardizing loading stations, unloading stations, and main lines scales better than endless belt runs. Multi-train operation requires solid signal knowledge, though.

1. Space Age in mind—multi-planet logistics and quality upgrades

Block and distribution multiplicity beat centralized scaling. Quality adds vertical strengthening, so modular and train systems mesh better with new expansion axes.

Compressed: speed favors spaghetti, visibility favors main bus, replicability favors modular, distance favors trains.

Three Pillars for Choosing Your Design

Narrowing to three evaluation axes helps you pick among spaghetti, main bus, modular, and train-based with confidence. I prioritize how easily you can expand later, how clearly you can read the flow, and how much planning you need upfront. Factories see far more expansions than initial construction, so these three factors predict long-term stability better than opening-day efficiency.

Criterion 1: Expansion Capacity (Measurable)

Expandability isn't "feels easy to add to"—it's do you have unused buffer lanes, can you duplicate blocks independently, or can you reroute transport later. Spaghetti struggles because empty space exists but wiring prevents use. Main bus, by contrast, branches horizontally on a fixed axis, so spare lanes enable straightforward expansion. Modular goes further: you can wholesale duplicate circuit blocks, refinery clusters, or science packs.

Train-based achieves expansion via geographic dispersal. You're not fighting for land; you spin up new ore processing, a new circuit factory, or a new science plant at a distant station. This "expansion into new territory" scales farther than packing the original plot.

The yellow belt's 15 items/second ceiling is your math. If you run a heavy mid-tier item on one lane indefinitely, you hit that wall fast. I learned this around blue science when copper cable traffic choked a single belt—the moment I switched to local cable production, the whole flow opened up. Sustainable expansion asks: can I avoid running this item long-distance altogether, rather than adding more belts? That mindset shift unlocks real growth.

Criterion 2: Flow Visibility

Visibility determines how quickly you pinpoint and fix bottlenecks. Main bus shines here because you can count lanes: 4 iron, 4 copper, 2 circuits, etc. Shortage instantly reveals whether it's production, transport, or distribution. Spaghetti hides the problem because multiple lines are entangled; each expansion makes the tangle worse. By contrast, a visible design lets you spot insufficient throughput as a design signal, not just a reason to add more belts.

The yellow belt again: 15 items/second is your limit per lane. Designs that toss random mid-tier items down a "temporary" belt get clogged. Good designs ask upfront: "Can I produce this locally instead of transporting it?" That's especially true for high-volume, low-density items like cable.

Trains also benefit from clear flow. Trains hide bottlenecks more easily than belts, so role separation—main line, branches, station approach, unload zone—must be visually distinct. Rails are placed in 2-tile units, so sloppy spacing undermines later station or signal tweaks. Like counting belt lanes, knowing "here's the trunk, here's the platform" determines whether you can debug gridlock.

Belt transport system

wiki.factorio.com

Criterion 3: Upfront Planning Burden

This is the most overlooked switching factor. Spaghetti lets you start instantly but mortgages your future. Main bus requires only deciding trunk width and growth direction, then you're off. Modular and train-based demand stations, signals, power reserves, and land reservations figured out beforehand—they fail if you wing it.

Trains make this stark. Multiple trains using the same unload or load station need stackers (waiting bays) in front of the station so they don't idle on the main line. The signal tutorial explains this: keep idle trains off main lines. Station shortage isn't your problem; absent waiting zones are. That distinction shapes your entire approach: 1 station is never enough; a station plus multiple waiting bays is a complete unit.

Power planning mirrors this. Early designs sidestep planning and patch as needed. Late designs need advance capacity reservation. If you're going solar, the 21:25 ratio and 23.8 panels per MW targets let you pre-allocate land. Beacons consume 480 kW each; heavy beacon usage demands calculated power expansion, not post-hoc scrambling.

This lens clarifies the trade-offs: minimal planning = spaghetti or main bus; heavy planning up front = modular or trains, rewarded by easier later scaling. Design quality is measured by whether expansions go as planned, not by opening-day aesthetics.

Power production

wiki.factorio.com

Why Main Bus is the Beginner Recommendation

Main Bus Fundamentals

For beginners, main bus is the safest bet. The central trunk gathers iron plates, copper plates, and similar primary materials, then individual production branches horizontally off it. Troubleshooting becomes far easier: when items jam, look at main bus lane counts to identify which is starved. Spaghetti collapses into cross-routing chaos; main bus separates supply from consumption, instantly clarifying your mind.

Why it works: dividing the main artery from side branches teaches modular thinking. Flow goes down the center; transformation happens on the wings. The wiki's tutorial reflects this philosophy. Early clarity of thought is the real gift.

Valid through blue science. Beyond that, material variety and throughput demand multiply, and the main bus becomes a sprawling liability. At that point, migrating items to local production or train distribution matters more than widening the trunk.

The main pain point is space consumption. Main bus is hard to retrofit, so you must reserve expansion lanes upfront. My first bus ran out of horizontal room by blue science because I over-optimized width. My second featured 4 empty lanes reserved for future use—I filled them perfectly and never hit a wall. Visual density matters less than preserved growth room.

What to Run on the Bus (and What Not To)

Beginners over-load the bus. The rule: run only high-frequency, broad-use materials—iron plates, copper plates, gears, circuits. These feed multiple downstream lines consistently.

Don't run copper cable. It's bulky, heavy downstream, and long-distance transport wastes trunk space. Running copper plates and making cables locally scales far better. This lesson generalizes: plate materials move; voluminous mid-tier products are made on-site. The yellow belt's 15 items/second cap will squeeze you if you're careless about bulk.

My trick: "Move refined ore/plate; make bulky intermediates locally." Iron and copper plates cross the main bus; cable, concrete, and explosives are made where used. This discipline keeps the bus lean and long-lived.

Wide-use base materials move; heavy mid-tier products stay local. This keeps your trunk svelte.

Shifting to Modular and Train Designs in Mid-to-Late Game

When and Why to Transition

Main bus fails visibly: the factory becomes endlessly horizontal. New materials mean new trunk lanes; new lanes mean more width reserved. Eventually, scaling distances grow worse, not better. Simultaneously, the trunk saturates against the 15 items/second-per-lane ceiling, and more lanes don't help if you're still centralizing everything. At this inflection point, separating production into independent, duplicatable blocks beats widening the main bus.

I switch when duplicating a functional block (like circuits or refining) feels easier than forking from the main bus. That's when modular replicability pays off. This also seeds train-based thinking: instead of all-to-center, distribute production and link via rails.

Station Design: Zero Idle Time on Main Line

The cardinal rule for trains: never let a train wait on the main line. Once multiple trains service the same station, gridlock propagates fast. Idle Train A blocks Train B, which blocks Train C, collapsing the entire network. The fix is stackers—holding areas where trains queue before the station, keeping the main line flowing.

I hit this bug in my early rail attempts: main line froze, and I couldn't see why. Adding stackers fixed it instantly. The philosophy: stations are for loading/unloading; main line is for flow. If a train can't immediately dock, it waits in a dedicated siding, not on the trunk.

This scales: each production block gets input and output stations with integrated stackers. The main rail becomes a high-speed inter-block highway, uninterrupted by local congestion.

Space Age Shifts Design Foundations

Multi-Planet Production and Transport Strategy

Space Age (released October 21, 2024) demolishes the "centralize everything on a single main bus" assumption. Four new planets and orbital platforms mean resources aren't uniform, and cloning a single design across worlds breaks the moment supply ratios shift. I started with "scale main bus thinking to planets" and quickly learned: planet-specific modularization beats planet-wide centralizing.

The core issue: supply conditions vary by planet; main bus assumes supply uniformity. Scaling it horizontally works in vanilla; it crumbles in Space Age.

So instead: each planet completes mid-tier production locally; only final or bottleneck items traverse the space network. This inverts the logic—instead of "everything flows to the center," it's now "make what you can locally, ship only what you must."

Each planet gets its own mini-bus or modular blocks; the orbital platform acts as a re-routing hub, not a central megabus. This philosophy extends main bus thinking without copying it wholesale.

Space Age

wiki.factorio.com

Quality and Vertical Strengthening

Quality introduces four tiers per item type, shifting optimization from purely horizontal scaling to quality-aware routing. High-quality intermediates are now worth segregating—you don't run them down a general-purpose main bus. Instead, route them to where they deliver maximum value.

This reframes main bus thinking: no longer "push 15 items/sec of identical stuff," but rather "push 15 items/sec split by quality grade, routed by destination." That's more modular, more distributed.

Late-game modular and train setups mesh better with Quality because they already separate production by function. Adding quality branching is natural.

Orbital Platform Roles

The space platform isn't a "second ground layer"—it's a multi-planetary interchange and production hub. Distributing work across planets and re-routing via orbit beats centralizing everything earthside.

Once ground factories self-supply and ship only specialized goods upward, the platform becomes a logistics checkpoint. No megabus in orbit; instead, cleared input/output streams by product.

Space Age's modular potential is its strength, not a weakness of main bus design. Embrace it.

Common Failure Modes and Recovery Strategies

Failure Checklist by Type

Factories collapse for recurring reasons. Ignoring belt throughput caps and skipping expansion buffer space are the biggest culprits. Mid-game breakdowns often look different but stem from the same layers.

Over-saturation on yellow belt: 15 items/second per lane is your ceiling. Don't forget it. Heavy-demand mid-tier items (cable, etc.) should be local, not bussed. Fix: pivot from transporting the item to producing it near consumption.

No expansion margin: Main bus is doomed if no horizontal reserve exists. Spaghetti sprawls without direction. Fix: pre-book expansion zones; name them even if empty.

Train stations without stackers: Multi-train designs jam immediately. Fix: add waiting sidings in front of every busy station.

Beacon overhead underestimated: 480 kW per beacon adds up fast. High-density factories go dark unexpectedly. Fix: estimate beacon load; pre-plan power.

Space Age – neglecting planetary isolation: Treating every planet as part of one supply chain breaks the moment a local shortage cascades globally. Fix: design each planet for internal self-sufficiency first, then decide what it trades.

Recovery-focused design is more practical than perfection-first design. Factories break more often than they launch, so design for quick diagnosis and patchwork, not eternal flawlessness.

Effective recovery means:

• Block boundaries: Split your factory into visibly independent units (smelting, circuits, science, etc.). Faults stay local.
• Fixed growth direction: Whether bus or trains, always expand the same way. Consistency beats optimization.
• Power reserves: Build generation with headroom. Starving for electricity cascades across everything.
• Replicable building blocks: Standardized designs let you scale without re-inventing.
• Planet-by-planet recovery routes (Space Age): Can you rebuild if one planet goes dark?

Recommended Reading Path

This topic spreads across multiple articles. Read this overview first, then branch by problem area.

• guide/main-bus (core main bus theory)
• production/bus-materials (choosing what rides the bus)
• production/ratio-calculation (production math)
• blueprint/city-block-design (modular/city block layout)

Once main bus basics stick, tackle science pack production (all colors at scale) to understand multi-color demand dynamics. This bridges main bus thinking to scaling challenges.

When main bus hits its limit, city blocks and oil refinery design become critical. Crude oil introduces new constraints and teaches production separation.

For late-game, train signaling basics (before stations) prevents multi-train gridlock disasters. Power generation planning (solar/nuclear ratios) keeps beacons viable.

Space Age paths: multi-planet modular and orbital logistics extend the concepts into new territory.

Summary and Next Steps

Choose patterns by current pain, not preference. Start with main bus for structure, shift to modular for replicability, adopt trains for distance, and in Space Age, optimize planet-by-planet. Design isn't a one-time decision; it's iterative diagnosis. Each weekend, observe where it breaks, reference the decision table, and nudge one layer. Factories grow most reliably when you loop: run → bottleneck emerges → adjust that one layer → run again.

Selection Checklist

• Identify which of the four patterns your current factory resembles
• Pick one production item to expand next; decide belt-run vs. local production
• Beginners: confirm main bus spare lanes; mid-players: add stackers to resource outposts; Space Age: verify planet independence

Action Plan

Classify your current factory into one of the four patterns. Pick one production bottleneck. Decide whether that item should be bussed or made locally. Once that's clear, expansion direction locks in. If transitioning to trains, review signal basics first—understanding blocking prevents multi-train chaos. Then build, run, observe, and iterate.