Subnet Splitter (/x to /y)

The Subnet Splitter (/x to /y) divides a larger subnet into smaller subnets of a specified prefix length. Enter a source CIDR like 192.168.1.0/24 and a target prefix like /26 to instantly generate all 4 resulting subnets with their network addresses, broadcast addresses, and usable host ranges -- a fundamental operation in network design and IP address planning.

Understanding Subnet Splitting

Subnet splitting is how you take a block of IP addresses you have been allocated and carve it into smaller pieces for different purposes. If your organization receives a /16 from your ISP or allocates one from RFC 1918 private space, you do not assign all 65,534 usable addresses to a single flat network. Instead, you split it into /24 blocks for individual VLANs, /28 blocks for DMZ segments, and /30 blocks for point-to-point router links. Each split creates subnets that are self-contained, with their own network address, broadcast address, and usable host range.

The math behind splitting is binary and therefore always involves powers of two. When you add one bit to the prefix length, you double the number of subnets and halve the number of addresses in each. A /24 (256 addresses) split into /25s gives you 2 subnets of 128 addresses. Split it into /26s and you get 4 subnets of 64. Into /27s, 8 subnets of 32. The pattern is predictable and consistent, which is what makes CIDR-based addressing so powerful for hierarchical network design.

This tool handles the arithmetic for you and lists every resulting subnet with full details. Whether you are splitting a campus /16 into department-sized /24s, carving a data center allocation into availability-zone subnets for AWS, or dividing a small /24 into point-to-point /30s for a WAN topology, the output gives you the exact addressing details you need for your configurations.

How to Split a Subnet by Prefix Length

1. Enter the source CIDR block (e.g., 10.0.0.0/24).
2. Enter the target prefix length (e.g., /26).
3. The tool calculates and lists all resulting subnets with complete addressing details.

The target prefix must be a larger number (more specific) than the source prefix. Each additional bit in the prefix length doubles the number of subnets while halving the addresses per subnet.

Subnet Splitting Examples

Splitting a /24 into /26 subnets

Source: 192.168.1.0/24 (256 addresses) split into /26 subnets (64 addresses each):

Result: 4 subnets with 62 usable hosts each (248 usable hosts total).

Common prefix-to-prefix splits

Splitting for point-to-point links

Router-to-router links need only 2 usable addresses. Splitting a /24 into /30 subnets:

192.168.1.0/24 -> 64 point-to-point links (/30)

192.168.1.0/30   -> usable: .1 and .2
192.168.1.4/30   -> usable: .5 and .6
192.168.1.8/30   -> usable: .9 and .10
...
192.168.1.252/30 -> usable: .253 and .254

When to Use Prefix-to-Prefix Splitting

• Department subnet allocation -- split a campus /16 into /24 subnets, one per department or floor.
• VLAN segmentation -- divide a data center block into equal subnets for different VLANs.
• Cloud VPC subnet design -- split an AWS VPC CIDR (e.g., 10.0.0.0/16) into subnet CIDRs for each availability zone.
• Point-to-point WAN links -- split a block into /30 or /31 subnets for router interconnects.
• Wireless AP group allocation -- create per-AP-group subnets from a wireless controller's address block.
• Lab/test environments -- subdivide a test network into isolated segments for different test scenarios.

How Prefix-to-Prefix Splitting Works

The number of resulting subnets is always a power of two, calculated by the formula:

Number of subnets = 2^(target_prefix - source_prefix)

For a /24 split into /26:

2^(26 - 24) = 2^2 = 4 subnets

Each resulting subnet has this many total addresses:

Addresses per subnet = 2^(32 - target_prefix)

For /26:

2^(32 - 26) = 2^6 = 64 total addresses (62 usable)

Network address calculation

The network address of each resulting subnet increments by the subnet size. For the example above, each /26 contains 64 addresses, so network addresses are 192.168.1.0, 192.168.1.64, 192.168.1.128, and 192.168.1.192.

IPv6 splitting

The same logic applies to IPv6 with 128-bit addresses. A common operation is splitting a /48 allocation into /64 subnets:

2001:db8:abcd::/48 -> 65,536 /64 subnets
  2001:db8:abcd:0000::/64
  2001:db8:abcd:0001::/64
  ...
  2001:db8:abcd:ffff::/64

Practical Splitting Advice

When deciding on a target prefix length, resist the temptation to make every subnet the same size. While this tool creates uniform splits (which is appropriate for many scenarios), real-world networks often have segments of very different sizes. A server VLAN might need 200 addresses, while a management VLAN only needs 10. If you split your /16 entirely into /24s, the management VLAN wastes 244 addresses. Consider using the VLSM Calculator for networks with mixed requirements, and reserve this tool for cases where uniform sizing is genuinely appropriate -- department allocations, availability zone splits, or point-to-point link pools.

Another practical consideration is leaving room for growth. If you split a /22 into four /24s today and later need a fifth /24, you have no room within the original block. A better approach might be to split the /22 into /23s (giving you 2 subnets of 510 hosts each) or to keep one /24 in reserve from the start. The cost of over-provisioning a little today is far lower than the cost of renumbering a production subnet later.

For cloud environments, pay attention to the minimum and maximum subnet sizes enforced by your provider. AWS requires VPC subnets to be between /16 and /28, and Azure VNets must be at least /29. Splitting a VPC CIDR into subnets smaller than the provider allows will produce valid CIDR math but fail at deployment time. Always check your provider's documentation before finalizing your splitting plan.

Frequently Asked Questions

What is the maximum number of subnets I can create? The maximum depends on the difference between source and target prefix. A /8 split into /32 produces 2^24 = 16,777,216 individual host routes. For practical display purposes, very large splits may be truncated with the option to export the full list.

Can I split into subnets of different sizes? This tool creates equal-sized subnets only. For variable-sized splits (e.g., one /25 and two /26 subnets from a /24), use the VLSM Calculator or the Subnet Splitter (Target Host Count).

What happens if I enter a target prefix smaller than the source? The tool rejects this as invalid. You cannot split a /24 into /16 subnets -- that would require creating larger blocks from a smaller one, which is aggregation, not splitting. Use the CIDR Aggregator for that operation.

Should I use /30 or /31 for point-to-point links? Traditionally, /30 provides 2 usable hosts (network and broadcast addresses are reserved). RFC 3021 defines /31 subnets for point-to-point links, eliminating the broadcast address and giving exactly 2 usable addresses with no waste. Most modern routers support /31.

How do I know which prefix length to choose? Start with the number of hosts you need per subnet and work backward. If you need 50 hosts, a /26 (62 usable) is the smallest that works. If you need 200 hosts, a /24 (254 usable) is required. The Subnet Splitter (Target Host Count) automates this calculation.

Does splitting change the total address space? No. Splitting redistributes the same total addresses into smaller blocks. A /24 with 256 addresses split into four /26s still has 256 total addresses (4 x 64), but 8 of those are now consumed by network and broadcast addresses (2 per subnet) instead of 2, reducing the total usable hosts from 254 to 248.

Related Tools

• Subnet Splitter (N Equal Subnets) - Split a subnet into a specific number of equal subnets
• Subnet Splitter (Target Host Count) - Split a subnet based on required hosts per subnet
• VLSM Calculator - Calculate variable-length subnet masks from host requirements
• IPv4 Subnet Calculator - Calculate network, broadcast, and host range from CIDR notation
• Subnet Allocation Planner - Plan subnet allocations to fit requested blocks