Satisfactory Splitter Calculator
Calculate equal belt output rates, exact splitter and merger counts for a balanced layout, and the belt capacity needed for loopback.
Method: tree 2×2
The common input segment fits Mk.5 at this rate.
- Target per output
- 195 items/min
- Splitters
- 3
- Mergers
- 0
- Fresh input belt (minimum)
- Mk.5 (780/min)
- Output belt (minimum)
- Mk.3 (270/min)
- Common input segment
- 780 items/min
Build steps
- Stage 1: 1 splitter, 2 connected outputs each.Each incoming belt: 780 items/min — minimum Mk.5.Each outgoing belt: 390 items/min — minimum Mk.4. Feed every outgoing belt into one splitter in the next stage.
- Stage 2: 2 splitters, 2 connected outputs each.Each incoming belt: 390 items/min — minimum Mk.4.Each outgoing belt: 195 items/min — minimum Mk.3. These are the equal tree outputs.
Rates are steady-state averages with all outputs accepting their share and every belt sized for its flow. Fractional rates are valid averages; displayed rates are rounded to 2 decimals. A manifold distributes unevenly until upstream buffers fill; its final distribution depends on machine demand and supply.
Enter the fresh supply rate and number of outputs, then choose the belt used on the common input segment. The Mk. buttons fill the input to that tier's capacity. For loopback, the common segment is the belt after the return flow rejoins the fresh supply.
1→N balanced splits
Use 2-way stages before 3-way stages: 1→6 is a 2×3 tree with one splitter feeding two more. Each stage splits every incoming line. For other counts, build the smallest tree with 2- and 3-way stages that has enough leaves, then return the spare outputs through mergers. Counts describe this construction.
Per-output values are steady-state targets in items/min, rounded to 2 decimals. All outputs must accept their share. Every loopback row at full Mk.5 input needs a Mk.6 common segment; every loopback row at full Mk.6 input exceeds the fastest belt. Reduce fresh input or use separate parallel balancers in that case.
| Split & method | Per output Mk.5 input 780/min | Per output Mk.6 input 1200/min |
|---|---|---|
| 1→2tree 21 splitter · 0 mergers | 390 | 600 |
| 1→3tree 31 splitter · 0 mergers | 260 | 400 |
| 1→4tree 2×23 splitters · 0 mergers | 195 | 300 |
| 1→5loopback 6→53 splitters · 1 mergerTree: 2×3; return 1. Merged segment: Mk.5 input: 936/min (needs Mk.6)Mk.6 input: 1,440/min (exceeds Mk.6) | 156 | 240 |
| 1→6tree 2×33 splitters · 0 mergers | 130 | 200 |
| 1→7loopback 8→77 splitters · 1 mergerTree: 2×2×2; return 1. Merged segment: Mk.5 input: 891.43/min (needs Mk.6)Mk.6 input: 1,371.43/min (exceeds Mk.6) | 111.43 | 171.43 |
| 1→8tree 2×2×27 splitters · 0 mergers | 97.5 | 150 |
| 1→9tree 3×34 splitters · 0 mergers | 86.67 | 133.33 |
| 1→10loopback 12→107 splitters · 1 mergerTree: 2×2×3; return 2. Merged segment: Mk.5 input: 936/min (needs Mk.6)Mk.6 input: 1,440/min (exceeds Mk.6) | 78 | 120 |
| 1→11loopback 12→117 splitters · 1 mergerTree: 2×2×3; return 1. Merged segment: Mk.5 input: 850.91/min (needs Mk.6)Mk.6 input: 1,309.09/min (exceeds Mk.6) | 70.91 | 109.09 |
| 1→12tree 2×2×37 splitters · 0 mergers | 65 | 100 |
| 1→16tree 2×2×2×215 splitters · 0 mergers | 48.75 | 75 |
Download the balanced split table (JSON) with full-precision rates and belt limits.
Why a loopback needs a faster input segment
With N delivered outputs from a tree of M leaves, the common segment carries fresh input × M/N. Each leaf carries fresh input/N. The M−N spare leaves return to the input, so delivered flow still totals the fresh supply.
For 1→5 at 780/min, the return is 156/min and the merged segment carries 936/min. A Mk.5 common segment supports at most 650/min fresh supply in that layout. For 1→10 (also written 1:10), use the table's 12-leaf tree and return two leaves through one 3-input merger together with fresh supply.
780/min · Mk.5
390/min · Mk.4
2 outputs
- Output 1
195/min · Mk.3 - Output 2
195/min · Mk.3
390/min · Mk.4
2 outputs
- Output 3
195/min · Mk.3 - Output 4
195/min · Mk.3
Every listed output is a separate belt. Tiers shown are minimums; all delivered outputs must accept their share.
780/min · Mk.5
936/min · Mk.6
468/min · Mk.4
3 outputs
- Output 1
156/min · Mk.3 - Output 2
156/min · Mk.3 - Output 3
156/min · Mk.3
468/min · Mk.4
3 outputs
- Output 4
156/min · Mk.3 - Output 5
156/min · Mk.3 - Return ↑
156/min · Mk.3
↑ Route the sixth belt back to the merger above: 156/min · Mk.3.
Every listed output is a separate belt. Tiers shown are minimums; all delivered outputs must accept their share.
Conveyor belt speeds
Belt capacities come from the game-data export distributed by SCIM. Layouts, stage rates and loopback limits are calculated by this site's model. See the method and sources.
Manifold vs. load balancer
Choose a manifold for a compact, easily extended row of machines. Splitters along one belt initially send more items to earlier machines. Once their buffers fill, later machines receive more supply; all machines can run continuously if total supply meets their demand and each belt segment has enough capacity. This does not guarantee equal rates when machine demands differ.
Choose a load balancer when you want equal shares across accepting outputs without relying on upstream machine buffers filling first. This tool calculates steady-state averages for a single item type. Travel, item-by-item splitter cycling and loopback circulation still affect startup; blocked outputs can change the split.
Pair this with the production calculator to know each machine's input rate, and the miner calculator to size the belt coming off your nodes.
Manifold supply & demand check
Total demand: 8 × 30 = 240 items/min.
Supply and main-belt capacity can sustain all machines after buffers settle, provided each branch belt carries its machine’s demand.
Available through the selected belt: 240 items/min; usable for this demand: 240 items/min.
Full-rate machine equivalent: 8 of 8. This is a supply ratio, not a prediction of which machines run first.
At full demand, the belt before machine 1 must carry 240 items/min (minimum Mk.3). Each machine removes 30 items/min; the last feed and each machine branch need 30 items/min (minimum Mk.1).
One item type and identical machine demand at your chosen clock speed. No overflow outlet. Checks steady-state supply and belt capacity only; buffer sizes, travel distances and startup time are not calculated.
For recipe demand and machine counts, follow the production ratios guide.
2→3 and 3→4 belt ratios
Merge the inputs, then use the corresponding 1→N tree. The common segment must carry the combined supply; this approach works when that total fits one belt. It does not combine several full Mk.6 belts into one.
- 2→3: 2 inputs at 270/min each total 540/min. Use 1 input merger, then tree 3 with 1 splitter. Each output receives 180/min; the common segment fits Mk.5.
- 3→4: 3 inputs at 240/min each total 720/min. Use 1 input merger, then tree 2×2 with 3 splitters. Each output receives 180/min; the common segment fits Mk.5.
Combined supply: 540 items/min. 270 + 270 = 540.
Target per output: 180 items/min (minimum Mk.3), using tree 3.
1 splitter; 1 merger total (1 for input combining + 0 for loopback).
Combine the fresh inputs through 1 merger (up to 3 inputs each). Use minimum Mk.5 for the combined fresh belt; that tier also suffices for earlier merger outputs in the input cascade.
Common segment: 540 items/min, minimum Mk.5.
The combined flow, including any loopback, fits the selected Mk.5.
Build steps
- Stage 1: 1 splitter, 3 connected outputs each.Each incoming belt: 540 items/min — minimum Mk.5.Each outgoing belt: 180 items/min — minimum Mk.3. These are the equal tree outputs.
Single item type, steady-state targets, all outputs accepting their share. This merges supply onto one common belt; it is not a full-throughput multi-belt network.
Sources, method & maintenance
SatisfactoryCalculator.net maintains this calculator and its computed tables. Read about the site and dataset or send a correction with your input rates, output count and belt tiers.
The belt parameters use the Satisfactory 1.2.3.1 game-data export distributed by SCIM, captured 2026-06-25. The table was computed 2026-10-29. Splitter and merger counts come from the staged-tree construction described above; loopback rates solve conservation of flow at steady state. Counts describe this construction, not a proof of the fewest possible devices.
Mechanics references: Conveyor Splitter, Conveyor Merger and Manifold on the Satisfactory Wiki. These are mathematical planning results; startup time is not measured or predicted.
Splitter calculator FAQ
How do splitters work in Satisfactory?
A splitter divides one input belt evenly across its two or three connected outputs while those outputs can accept items. To supply more lines evenly, use staged splitter trees or a tree with loopback. Blocked or undersized output belts change the distribution.
What are the belt speeds in Satisfactory?
Conveyor belts carry Mk.1 60, Mk.2 120, Mk.3 270, Mk.4 480, Mk.5 780, Mk.6 1200 items per minute.
How do I split a belt into 5 in Satisfactory?
Use 3 splitters in a 2×3 tree to make 6 equal outputs. Keep 5 outputs and return the extra output through 1 merger together with the fresh input. At 780 items/min fresh input, each output targets 156 items/min and the merged input segment needs 936 items/min. Use Mk.6 on that segment; Mk.5 is too slow. All five outputs must accept their share.
How many splitters for 1 to 4?
Use 3 splitters in a 2×2 tree: one splitter feeds two more splitters, each with two connected outputs. No mergers are needed. Each output receives one quarter of the fresh input, or 195 items/min from a 780 items/min belt, provided all outputs accept their share.
What is a load balancer?
A load balancer is a belt network that distributes supply across outputs. This calculator plans equal steady-state rates using splitter trees and, where needed, merger loopbacks. Unlike a manifold, it does not depend on filling upstream machine buffers to distribute an equal share. Belt capacity and blocked outputs still matter.