Dotted Decimal to CIDR Calculator

August 11, 2026

HomeServerBlog IPv4 mask converter

Dotted Decimal to CIDR Calculator

Convert subnet masks such as 255.255.255.0 into CIDR prefixes, wildcard masks, usable host counts, network ranges, ACL notes, and VLAN planning capacity.

▶Real network presets
⚙Subnet mask, host, and routing inputs
Choose whether the dotted value is a normal mask or an inverse ACL-style mask.
Enter four IPv4 octets. Valid subnet masks must have contiguous one bits.
Used to calculate the aligned network, broadcast, and usable host range.
Clients, servers, containers, APs, cameras, or VPN peers needing addresses.
Gateway, DHCP, DNS, VIPs, controller addresses, static servers, and monitoring.
Extra demand added before judging whether the mask has enough host capacity.
Adds realistic address, DHCP, ACL, and route-planning context.
Treat /31 and /32 differently for links, summaries, or ordinary LAN planning.
CIDR prefix
/24
24 network bits
Equivalent prefix for the entered dotted decimal mask.
Usable hosts
254
normal IPv4 LAN
Excludes network and broadcast addresses unless link mode applies.
Subnet mask
255.255.255.0
dotted decimal
Contiguous mask accepted for IPv4 route and VLAN planning.
Wildcard mask
0.0.0.255
ACL inverse mask
Useful for Cisco-style ACLs, route maps, and match statements.

Full breakdown

This /24 mask fits the requested hosts with normal home-lab growth space.
▦Live conversion details
192.168.10.0Aligned network address for the sample IP and mask.
192.168.10.255Broadcast or final address in the block.
192.168.10.1 - 192.168.10.254Usable range under the selected range mode.
119 neededRequired hosts plus reserved IPs and selected growth buffer.
🛠Equipment and networking spec comparison

Home router LAN

/24

Typical 254 usable addresses, one gateway, DHCP pool, static reservations, and a simple default route.

Managed switch VLAN

/25 - /26

Good for segmented clients, lab services, printer VLANs, or access switch ports with ACL boundaries.

Wi-Fi SSID subnet

/24 - /23

Client-heavy networks benefit from extra DHCP space, short lease checks, and clean guest isolation.

PoE camera network

/27 - /26

Camera VLANs often need static or reserved addresses plus NVR, gateway, and management headroom.

Hypervisor management

/28 - /26

Fits hosts, IPMI, storage interfaces, cluster VIPs, DNS, monitoring, and migration services.

VPN peer pool

/28 - /24

WireGuard and remote-access pools should leave addresses for users, phones, travel routers, and tests.

Container bridge

/16 - /20

Docker, Kubernetes, and lab overlay ranges need large private blocks that do not overlap LAN routes.

Routed transit link

/31 - /30

Point-to-point links use compact masks, usually no DHCP, and clear route statements on both ends.

▤Mask to CIDR reference table
Dotted decimal maskCIDRAddressesUsable LAN hostsCommon home lab use
255.255.0.0/1665,53665,534Container bridge, large lab overlay, non-overlapping private block
255.255.252.0/221,0241,022Site summary, lab supernet, multiple VLAN allocation pool
255.255.254.0/23512510High-client Wi-Fi or larger household device network
255.255.255.0/24256254Default LAN, normal VLAN, small office subnet
255.255.255.128/25128126Guest Wi-Fi, split LAN, medium client group
255.255.255.192/266462IoT VLAN, camera VLAN, access switch segment
255.255.255.224/273230Small PoE camera group or server management block
255.255.255.240/281614VPN peer pool, DMZ, storage network, lab services
255.255.255.248/2986AP management, firewall HA, public IP handoff block
255.255.255.252/3042Traditional router-to-router or firewall transit link
255.255.255.254/3122 link IPsRFC 3021 point-to-point transit links
255.255.255.255/3211 host routeLoopback, single host route, static firewall object
📊Capacity by configuration table
ConfigurationRecommended maskUsable capacityMetric equivalentPlanning note
Default home LAN255.255.255.0 /24254 hosts1 class-C sized blockEasy DHCP scope and static reservation planning
Guest and family split255.255.255.128 /25126 hostsHalf of a /24Works well when splitting a /24 into two equal zones
IoT or camera VLAN255.255.255.192 /2662 hostsQuarter of a /24Enough for cameras, sensors, controllers, and NVR services
Hypervisor management255.255.255.240 /2814 hostsSixteenth of a /24Compact but leaves only modest growth room
Firewall transit255.255.255.252 /302 hostsOne router pairClassic link mask when both endpoints need one address
Route summary block255.255.252.0 /221,022 hostsFour /24 blocksUseful parent block for several nearby VLANs
🔗Standards and conversion table
ReferenceValueWhere it mattersCalculator handling
IPv4 mask bits32 total bitsEvery subnet mask, wildcard, hostmask, and route prefixCounts leading one bits and rejects non-contiguous masks
Normal LAN host formula2^(32-prefix)-2Ethernet VLANs, Wi-Fi, DHCP pools, and server subnetsSubtracts network and broadcast for /30 and larger blocks
RFC 3021 link mode/31 has 2 usable IPsPoint-to-point router, firewall, or lab transit linksDisplays both addresses as usable when link mode is selected
Host route/32 is one IPLoopbacks, firewall objects, static host routesReports one address with no broadcast range
Wildcard mask255-mask octetACLs, route maps, policy match statementsCalculates inverse dotted mask from the subnet mask
Private IPv4 planningRFC 1918 blocksHome labs, VPNs, container networks, VLAN route summariesWarns through breakdown when capacity is tight or excessive
🏢Common project sizes table
ProjectTypical equipment countMask to enterPrimary resultSecondary result
Small managed home LAN40 to 90 clients255.255.255.0/24254 usable hosts
Guest Wi-Fi subnet25 to 80 clients255.255.255.128/25126 usable hosts
PoE camera VLAN8 to 30 devices255.255.255.224/2730 usable hosts
WireGuard peer pool4 to 14 peers255.255.255.240/2814 usable hosts
Firewall transit link2 endpoints255.255.255.252/302 usable hosts
Container overlay lab500+ containers255.255.0.0/1665,534 usable hosts
★Subnet planning tips
Check mask contiguity first. A valid subnet mask changes from one bits to zero bits once. Values like 255.0.255.0 are not routable subnet masks even though they look dotted-decimal.
Plan DHCP after reserves. Reserve gateway, DNS, controllers, static servers, VIPs, and monitoring before judging capacity. A /27 looks roomy until infrastructure addresses consume part of it.

This calculator uses IPv4 subnet math for home labs, small offices, and private networks. Provider-specific public allocations and unusual routed designs may need additional policy checks.

If all this sounds confusing. Don’t worry. You’re in good company. That 255.255.255.0 can look like gibberish. In fact, this is the dotted decimal notation that network engineers once relied on. Then they’d type these numbers into their switches and routers by hand. While this system was accurate, it was also time-consummin. And it was easy to make a typo and spend an hour waiting for your connection to come back online.

Enter CIDR, which stands for Classless Inter-Domain Routing. This simplified everything by compressing the mask down to a single prefix length. Instead of typing out 255.255.255.0, you just type a /24. Both mean exactly the same thing, but it saves you half the typing. And it reduces possibility of human error. Plug that into the calculator above and it will instantly translate it for you.

Why You Should Use This Calculator

But more important than simply finding a number to plug in is knowing what the prefix length does. That’s what it defines. That’s what it limits. Plugging in a mask translates to how many hosts you have left on the network, how many can live on the segment. It shows where traffic can flow. And most importantly, where traffic is allowed to flows.

The first and last address in a block are reserved. One is used to identify the network. The other is for sending a message out to everybody else in the segment. The problem is, most folks don’t remember that, so they come up with a raw total and then plug that number in thinking that’s their real count. That’s not accurate though. The calculator does the math and spits out true number instead.

When selecting your prefix length, consider what’s ahead. How many users do you have? How many devices will they bring? Are there any servers involve? A /24 allocates 254 usable addresses. That’s plenty if you’re just building a home LAN or a small office LAN. In fact, this is big enough to cover dozens of devices like servers, phones, laptops, smart home gadgets, etc. All while not wasting address space.

For bigger networks, you may want to consider a /22 or perhaps even a /16. Both of those is handy when you get into more complex stuff like container orchestration. These are also useful for sprawling lab environments where you’re looking for thousands of isolated subnet. The tool visualizes the differences. For example, you can see that a /22 offers over a thousand addresses which could be good for aggregating a supernet of several smaller VLANs.

The other side of the spectrum is your little subnets. They have two usable addresses with a /30 mask. They are perfect for connecting two router via a point-to-point link. When there’s only two endpoints talking, why use anything more? A /24 for your simple modem-to-firewall link is overkill. It wastes space on your routing table.

If you put your expected number of hosts into the calculator it will highlight any mismatches for you. If your desired mask is too big for your requirements. I.e. Absurdly large for a basic connection, then it’ll warn you about that, too. That kind of feedback loop can be very helpful when planning. It can stop you from making one of the most common mistakes; underestimating your own growth.

Sure, maybe you only have ten devices right now. But what about guest Wi-Fi? What about those IoT sensors? How about that smart fridge that you’re going to buy next year? You want to add some breathing room, so it lets you plan for that growth and it keeps you from needing to change your subnets down the line.

Wildcard masks are also important. These are used when you configure access control lists. Or if you use Cisco equipment and set up subnets, you need the inverse of the subnet mask. The calculator produces these for you. It takes all the connected bits in a subnet and turns them around so they’re usable as inverse values needed for ACLs. It saves you from having to do any binary math in your head.

It is handy if you have to secure a network in a hurry. It is a small convenience, sure. But it matters. It matters when you’re trying to accurately block certain types of traffic.

Networking is all about balance. Do you have too little space? It is not convenient. Is it too much? Security blind spots. Too much management overhead? Who wants any of this?

The move from dotted decimal to CIDR wasn’t just a notation change. It was a shift towards efficiency. Once you understand how the prefix relates to the mask and the host count, you gain control over your network design. No more guesswork, it’s time to design! Planning out a guest network or segmenting off your IoT VLAN for security? Same math. You don’t want your guest network interfering with your main LAN. The calculator takes care of the math. You make the decisions and that part will never change.

Dotted Decimal to CIDR Calculator

Related posts

Leave a Comment