Number of Subnets from Borrowed Bits Calculator

August 4, 2026

HomeServerBlog subnet planning tool

Number of Subnets from Borrowed Bits Calculator

Calculate how many subnets borrowed bits create, the resulting CIDR prefix, usable hosts per subnet after reserves, and whether the plan fits host, subnet, and VLAN requirements.

▶Borrowed bits presets
⚙Subnet borrowed bits inputs
The starting CIDR prefix before borrowing, such as /24, /16, /20, or IPv6 /56.
Bits moved from the host portion into the subnet portion. Subnets equal 2 raised to this value.
IPv4 uses 32 total bits. IPv6 uses 128 total bits and normally keeps LANs at /64.
Host bits held back inside each new subnet for growth, static pools, infrastructure, or policy reserves.
Minimum usable hosts needed in each generated subnet after network, broadcast, and reserved host-bit rules.
How many separate routed, VLAN, tenant, lab, or point-to-point networks the plan must produce.
Classic mode subtracts network and broadcast for IPv4 subnets with enough host bits. IPv6 has no broadcast.
Optional VLAN target. The calculator checks the borrowed subnet count against this value too.
Number of subnets
4
2^borrowed bits
Borrowing 2 bits creates 4 equal subnets.
New prefix length
/26
original plus borrowed
The original /24 becomes /26 after borrowing.
Usable hosts/subnet
62
after reserves
Classic IPv4 endpoint reserve is applied.
Requirement check
PASS
hosts, subnets, VLANs
Current inputs meet the selected requirements.

Borrowed bits breakdown

Address familyIPv4, 32 bits
Formula2^2 = 4 subnets
Remaining host bits6 bits
Working host bits6 bits after reserve
Total addresses per subnet64
Held by host-bit reserve0 addresses
Endpoint reserve2 addresses
Required target4 subnets, 50 hosts, 4 VLANs
This plan passes because it creates enough subnets and each subnet has enough usable host capacity.
📊Subnet math comparison grid

One fewer bit

2 subnets

Lower subnet count, larger host pools.

Current plan

4 subnets

Balanced against the active requirements.

One more bit

8 subnets

More segments, smaller host pools.

Minimum bits

2 bits

Smallest borrow that meets subnet and VLAN count.

🗂Current plan table
CheckCalculated valueRequirementStatus

The host-bit reserve is applied after the new prefix is calculated. It models capacity intentionally held back inside each subnet rather than extra subnets held back outside the split.

🧮Borrowed bit reference table
Borrowed bitsSubnet countNew prefix from current originalUsable hosts/subnetFit note
📘IPv4 and IPv6 planning table
ScenarioCommon originalBorrowed bitsResultPlanning note
Small home VLAN split/2424 x /26Good when each VLAN needs about 60 classic IPv4 hosts.
Department addressing/168256 x /24Easy to document, route, and delegate by department or site.
Tenant carve-out/20416 x /24Clean split for labs, customers, or building floors.
IPv6 site allocation/568256 x /64Common residential or small-site plan where each VLAN receives a /64.
🛠Use case fit table
Use caseSubnet pressureHost pressureBorrowing guidance
Guest, IoT, camera, and lab VLANsModerateModerate to highBorrow enough bits for VLAN count, then verify each VLAN still has hosts left.
Point-to-point routed linksHighLow/30 is classic for IPv4 links; /31 may be acceptable when endpoint reserve is disabled.
Branch office plansModerateVariableKeep spare subnets for voice, printers, cameras, wireless, and future security zones.
IPv6 LAN segmentationUsually highVery low relative to /64Prefer assigning full /64s to LANs unless you have a very specific routing reason.
💡Borrowed bits tips
Borrow for the count, then test the hosts. Each borrowed bit doubles the subnet count and halves the address count inside each subnet. A plan can pass the VLAN count while failing the host requirement.
Keep endpoint rules explicit. IPv4 LANs commonly reserve network and broadcast addresses, but point-to-point /31 links and IPv6 plans are different. Set the reserve mode to match the network you will actually deploy.

As your house gets larger with networks beyond capacity of one router, there’s a certain sort of panic that sets in: How do you set up a separate network for the backyard cameras? How about guest network for visitors? What about different one for smart appliances that shouldn’t be chatting to your primary computer? That means stealing some of the host part of your IP address and making new subnets.

It sounds abstract…until you’re trying to figure out how many subnets you’ll get on a napkin, time to break out a calculator. Essentially, borrowing bits mean trading host capacity for network segments. For example, if you borrow one bit, you get twice as many subnets… But half as many addresses within each subnet.

How to Plan Your Home Network Subnets

That’s where the basic conflict lies with any kind of IP planning: On the one hand, you need sufficient networks so that devices can be logically segregated for traffic management/security reasons. But on the other hand, you’d like each network segment to have sufficient addresses to accommodate real-world device instead of running out. Define your initial prefix and number of bits you’re prepared to part with, and the calculator above will do the math for you.

As it turns out, however, the inputs are more important than initially thought. The original prefix length determines how large a playground you’re creating. A typical home block is a /24, which give you 256 addresses total. An enterprise space could easy be a /16. Grab two bits from a /24 and now you’ve got four subnets each containing sixty-four addresses. Reserve one for the network address and one for the broadcast, and now you’ve got sixty-two host addresses on each subnet. This is enough for most home or small office VLAN plans.

Go up and borrow three bits and now you’ve got eight subnets but only thirty-two addresses each. This may be all you need for an isolated pool like IoT devices, but if you want to fit in a full department’s worth of workstations, not so much. This all completely changes the flow of discussion with IPv6.

With IPv4, the address space is small and we hoard bits. With IPv6, it’s so large that default action is to give each link a /64 even if there are only two or three machines on it. Borrowing bits from your IPv6 allocation, such as a /56, is almost always targeting that same goal: getting down to that /64 number. And the table at the bottom of the page make it clear why, eight borrowed bits produce 256 unique /64s. It’s not about packing more hosts onto a subnet. It’s about carving sufficient lanes for routing based off how you use them.

The second thing to avoid when picking your CIDR is getting overly hung up on how many subnets you get at the cost of hosts per subnet. Borrowing four-bits will let you generate all sorts of networks but if they’re going to have too few addresses for your devices, it won’t help you much. That’s where this tool comes in… it balances out not just how many subnets you end up with but whether any of them fall below some reasonable threshold of hosts. So if you try to borrow four bits and discover halfway into the build-out that you don’t have enough room for twenty phones on your new guest network, that doesn’t happens.

Additionally, pay close attention to endpoint reserves. In classic IPv4 addressing, you reserve the first and last address of each subnet as a broadcast and network identifier. Sometimes people omit this on point-to-point links to conserve space; they use /31 subnets with both IPs available. Your calculation needs to reflect how you’ll actualy deploy your hardware, which means selecting the appropriate reserve mode.

Finally, don’t overengineer. Plan for growth, but do so with some flexibility. Only borrow enough bits to support your current grouping needs and a little more to support your next project or two. Otherwise, you either run out of networks (too few bits) or you starve every subnet of addresses (too many).

There’s not really much complex algebra involved; it’s all about knowing what you want to connect to and protect. With those numbers, the actual configuration is simply typing them into the boxes. Figuring out how to divide up the space was the difficult part, and you should of planned it well.

Number of Subnets from Borrowed Bits Calculator

Related posts

Leave a Comment