Server Splitter lets you take a portion of one server’s resources and turn it into a brand-new second server, without paying for a second plan. If your Loafbox server has more RAM, disk and CPU than a single game needs, you can peel some of it off into a child server on the same node — run a Minecraft server and a small test server, or a main world and a creative build, side by side. The child is free: it shares your existing plan rather than adding a new subscription to your bill, and whenever you delete it the resources flow straight back to the master. This guide covers exactly what the splitter does, who can use it, how the resource pool stays balanced, and the step-by-step for creating, resizing and deleting a split.
What the Server Splitter Does
The splitter moves resources, it never invents them. When you create a split, a slice of the master server’s memory, disk, CPU and slot allowances is carved off and handed to a new child server that boots on the same node as the master. Everything stays within the resources you already pay for: the master plus all of its children always add up to the same total pool. There is no separate bill for a split — the child runs under the master’s plan, so creating one does not start a new subscription or change what you owe.
Because the child is a real server, it gets its own console, files, backups and databases, just like any server you order. The only difference is where its resources come from: instead of a plan of its own, they are on loan from the master, and deleting the child returns them.
Note: A split moves resources from the master to the child — the master + all its children always equal the same total pool
Note: Splits are free: the child shares the master’s plan and never adds a new subscription to your bill
Note: Deleting a split returns its resources to the master, so the master goes back to full strength
Who Can Use It
Server Splitter is a Loafbox feature. Creating a split requires the master server to be on a Loafbox plan — if it is on a Shared plan, the splitter is disabled and you will be prompted to upgrade. The feature also has to be enabled for your server’s game, which it is on the games where Loafhosts offers it.
If you are the server owner you already have what you need. If you manage someone else’s server as a sub-user, you need the dedicated Split Manage permission granted to your account before the Server Splitter page and its actions become available.
Note: Creating a split requires a Loafbox plan; Shared plans cannot split
Note: Sub-users need the Split Manage permission before they can open or use the splitter
Tip: The Server Splitter page lives in your server’s sidebar in LoafHub at hub.loafhosts.com — open the master server, then open Server Splitter
How the Resource Pool Works
Every split is bound by one rule: the master has to keep a healthy share of its own resources so it does not get starved. By default the master must retain at least 30% of each of its memory, disk and CPU, measured against the full original pool rather than whatever is left after earlier splits — so you cannot grind the master down to nothing across several splits. Memory always has to stay above zero, and the master always keeps at least one network allocation so it stays reachable. Backup and database slots can be given away down to zero, but never below.
There is also a hard limit on how many children one master can have. The absolute ceiling is four splits per master, no exceptions. Within that ceiling your plan sets the practical number — the standard allowance is three, and an operator can raise a specific server up to the four-split maximum. A split cannot itself be split: child servers are final, so to create another sub-server you always go back to the master.
Note: The master must keep at least 30% of its memory, disk and CPU (measured against the original pool), and at least one allocation
Note: A master can have at most four splits; the usual allowance is three
Warning: Child servers cannot be split again — start every new split from the master server
Create a Split
Creating a split asks for four things: a name for the new server, which game it runs, how much of each resource to peel off, and which network allocation (IP and port) it should use. The allocation has to be a free one on the same node as the master, because the child lives alongside it. By default the child runs the same game as the master; cross-game splits are off unless your operator has turned them on, in which case you can pick another supported game for the child instead.
- Sign in to LoafHub at hub.loafhosts.com and open your master (Loafbox) server
- Open Server Splitter from the server’s sidebar
- Choose to create a new split and give the new server a name
- Leave the game as your master’s game, or pick another one if cross-game splits are enabled
- Set how much memory, disk and CPU to peel off, plus any backup, database and allocation slots
- Pick a free allocation on the same node for the new server
- Confirm to create it — the child server starts provisioning right away
The form keeps a sensible reserve in mind when it suggests amounts, so it nudges you toward a split that leaves the master comfortably above its floor. If you ask for more than the pool can spare, the split is refused with a clear message rather than quietly shrinking the master too far.
Tip: You only have to give away what you want — backups, databases and extra allocations can all be left at zero on the child
Tip: The new server appears in your server list and in the master’s split list once provisioning completes
Warning: The child uses a free allocation on the master’s node, so you need at least one spare allocation available there
Resize a Split Child
A split is not locked in once you create it. You can adjust how much each child holds later — rename it and change its memory, disk, CPU or slot amounts — and the difference moves between the master and the child accordingly. Giving the child more pulls from the master; giving it less hands resources back. The same floor applies on every change, so a resize that would push the master below its 30% retention (or below one allocation) is refused.
Note: Resizing rebalances resources between the master and the child in either direction, always within the pool
Note: The minimum-master floor is re-checked on every resize, not just at creation
Delete a Split
Deleting a child is how you reclaim its resources. The action returns everything the child was holding to the master in one atomic step and then tears the child down completely — its Wings runtime, its allocation and its databases are all cleaned up. Once it is gone, the master is back to the resources it had before that split. As with any server deletion, the child’s own files and data go with it, so download anything you want to keep first.
- Open Server Splitter on the master server
- Find the child you want to remove in the split list
- Choose to delete that split
- Confirm — the child is torn down and its resources return to the master
Warning: Deleting a split permanently removes the child server and its data — back up anything you need first
Note: The resources return to the master automatically as part of the delete, so you do not have to rebalance anything by hand
The Rules the Splitter Enforces for You
A few guardrails are built in so a split can never break your master or your billing. The master always keeps at least 30% of its memory, disk and CPU and at least one allocation. There is a hard ceiling of four splits per master. Children live on the same node as the master and cannot be split further. Splits never create or cost extra resources — they only move what you already have — and to keep things sane there is a sensible limit on how quickly you can spin up new splits in a short window. If any action would break one of these rules, the panel stops it and tells you why instead of doing something surprising.
Tip: Because every split is reversible, it is safe to experiment — create one, try it, and delete it to get your resources back
Note: If a split is refused, the message names the exact rule (for example the 30% master floor) so you know what to adjust
Frequently Asked Questions
Does a split cost extra?
No. A split is free — the child server shares your master’s existing plan, so creating one does not start a new subscription or change your bill. It simply borrows resources from the master, and deleting it returns them.
Which plans can split?
Creating a split requires the master to be on a Loafbox plan. Shared plans cannot split. If you are on Shared and want the feature, upgrade the server to a Loafbox plan.
How many sub-servers can I make?
Up to four per master, and no more — that ceiling is absolute. The usual allowance is three, and an operator can raise a specific server up to the four-split maximum.
Can the new server run a different game than the master?
Only if cross-game splits are enabled by the operator. By default a split runs the same game as the master. When cross-game is turned on, you can pick another supported game for the child instead.
Where does the new server run?
On the same node as the master, using a free network allocation (IP and port) there. That is why you choose an allocation when creating the split, and why the master’s node needs a spare allocation available.
Can I split a server that is itself a split?
No. Child servers cannot be split again. To create another sub-server, go back to the master and split from there — a master can hold up to four children.
What happens to my resources when I delete a split?
They return to the master automatically and atomically as part of the deletion, and the child server is fully torn down. Your master goes back to the resources it had before that split.
Can a sub-user manage splits?
Yes, if they have been granted the Split Manage permission. Without it, the Server Splitter page and its create, resize and delete actions are not available to that sub-user.