Subnet Splitter

What is a subnet splitter?

A subnet splitter divides one IPv4 network into several smaller, equal-size networks. Instead of planning each resulting subnet by hand, you give it a starting network and a target (a new prefix, a required subnet count, or a required host count) and it calculates every child network, its CIDR boundaries, and its usable address range.

How to use this tool

Enter the network you want to split in CIDR form, choose one of the three split methods, and calculate. The tool sorts out how many subnets result, where each one starts and ends, and what address range each provides — then lets you inspect, copy, or export the results.

Split by prefix

The most direct method: choose the prefix every resulting subnet should use. Splitting 192.168.10.0/24 into /27 networks borrows 3 bits from the host portion (27 − 24), producing 2³ = 8 equal subnets of 32 addresses each.

Split into a specific number of subnets

Ask for a number of subnets directly and the tool works out the prefix. Because every CIDR subnet size is a power of two, only power-of-two subnet counts are exact. Asking for 5 subnets doesn't produce exactly 5 — the smallest equal split that provides at least 5 is 8, using one extra borrowed bit. The tool always shows both the number you asked for and the number it actually produced, rather than quietly substituting one for the other.

Split by required hosts

Specify the minimum usable hosts each subnet needs and the tool finds the smallest prefix that satisfies it, then splits the parent into equal subnets of that size. 30 hosts needs a /27 (30 usable); 31 hosts needs a /26 (62 usable), since a /27 falls one host short. This mode always produces equal-size subnets — if your networks need genuinely different sizes, use the VLSM Calculator instead.

How subnet splitting works

Splitting borrows bits from the host portion of the address and hands them to the network portion. Each borrowed bit doubles the number of possible subnets and halves the number of addresses in each one: 1 bit borrowed gives 2 subnets, 2 bits give 4, 3 bits give 8, and so on. Because the boundaries always fall on powers of two, the resulting subnets tile the parent network exactly, with no gaps and no overlap — the Subnet Boundaries panel above shows exactly where each one starts.

Why subnet boundaries matter

Every child subnet begins on an address that's an exact multiple of its own size. That's why, for a /24 split into /27s, the network addresses always end in .0, .32, .64, .96 and so on — never an arbitrary offset. An address like 192.168.1.33 belongs to 192.168.1.32/27 specifically because .33 falls between the .32 boundary and the next one at .64.

How borrowed bits work

"Borrowing" a bit means moving it from the host portion of the address to the network portion, so it helps identify the subnet instead of a host within it. Borrowing n bits always produces exactly 2ⁿ equal subnets, and each one contains 2^{(32 − new prefix)} addresses — the Prefix Transformation panel above walks through both formulas for any result.

Worked example: /24 → /27

Splitting 192.168.1.0/24 into /27 subnets produces exactly 8 networks of 32 addresses (30 usable) each:

Load this example in the calculator above to see it computed live, or work through it by hand: each subnet is 32 addresses apart, and every network address ends in a multiple of 32.

Equal-size subnetting vs. VLSM

A subnet splitter (this tool) always produces same-size subnets from a single prefix, count, or host requirement — simple and predictable when every subnet has similar needs. VLSM (Variable Length Subnet Masking) instead sizes each subnet independently to its own requirement, which uses address space more efficiently when requirements genuinely differ. Use whichever matches your actual requirements; forcing unequal requirements into equal subnets wastes addresses, and forcing equal requirements through VLSM adds needless complexity.

Subnet Splitter vs. Subnet Calculator

The Subnet Calculator analyzes one network you already have: its mask, range, and classification. This tool goes the other direction — it takes one network and divides it into several. Once you've split a network here, you can open any resulting subnet directly in the Subnet Calculator for the same range/binary/classification detail it provides.

/31 point-to-point subnets

A /31 remains a valid network prefix. Under RFC 3021 point-to-point semantics, neither of its two addresses is reserved as the traditional network or broadcast address, so both can be used as link endpoints — useful when splitting a block specifically for router-to-router WAN links.

/32 single-address subnets

A /32 is a single-address IPv4 prefix. Splitting a parent network into /32 blocks produces one individual address prefix per result, with no network, broadcast, or usable-range concept — useful for host routes and loopback address planning.

The number-of-subnets formula

Borrowing n bits from a parent prefix always produces exactly 2ⁿ equal subnets, and each one contains 2^{(32 − new prefix)} addresses. These two formulas are all the arithmetic subnet splitting ever requires; the tool's "Show the math" panel walks through both for any result.

Choosing a prefix

Pick the smallest subnet (largest prefix number) that still comfortably fits your current host count plus reasonable growth. Oversized subnets waste address space; undersized ones force a disruptive re-split later. The Nearby Split Options panel above lets you compare adjacent prefixes without recalculating by hand. If different parts of your network need meaningfully different sizes, plan with VLSM instead of forcing one prefix across all of them.

Plan before you split

Splitting is easy to undo on paper but disruptive to undo on a live network, since it changes every device's subnet mask and usable range. Confirm your host counts and growth expectations before deploying a split in production.

Related tools

Analyze one of the resulting subnets in detail with the Subnet Calculator. Need different subnet sizes across your network instead? Use the VLSM Calculator. Converting a range or aggregating CIDRs instead of splitting? Use the CIDR & IP Range Converter. Checking whether the resulting subnets overlap an existing allocation? Use the Subnet Overlap Checker. Reducing a routing table to the fewest prefixes? Use the Route Summarization Calculator.