$ip-convert --binary 10.0.1.100

IP Binary Converter

IP Binary Converter. Enter an IP address and click Convert to Binary in this IP binary converter, or paste binary and convert it back to decimal.

Decimal → Binary

Binary Result
00001010.00000000.00000001.01100100

Binary → Decimal

Decimal Result
10.0.1.100

Octet Breakdown

OctetDecimalBinaryCalculation (128+64+32+16+8+4+2+1)
32-bit Integer
-
Hexadecimal
-

Enter an IP address in dotted-decimal format or binary to instantly convert between the two representations. View the binary equivalent of each octet, understand bit-level subnetting, and analyze network vs host bits — a must-have tool for learning IP addressing and troubleshooting subnet boundaries.

Every device on a computer network gets an address, but routers and switches don't read dotted numbers the way you do — they read bits. The IP Binary Converter above takes any IPv4 or IPv6 address and instantly shows you the raw binary pattern a machine actually sees, broken down by octet or hextet. Whether you're studying for a certification exam, debugging a subnet mask, or just curious how 192.168.1.1 looks in binary, this page walks through exactly how the conversion works, why the Internet Protocol relies on it, and where it matters in practice.

Understanding the IP Binary Converter and IPv4 Address Structure

An IPv4 address is a 32-bit number, but writing out thirty-two 1s and 0s isn't practical for humans, so we split it into four 8-bit sections called octets and separate them with dots — the familiar dotted decimal format, sometimes called the dotted-decimal format. Every IP binary converter follows the same underlying logic: split the address into its component parts, convert each part to its binary representation using base-2 math, then reassemble the result. Computers, switches, and routers work exclusively in the binary number system because a transistor only recognizes two states — on and off — which is why every device on the network ultimately makes its routing and filtering decisions in binary, not decimal.

The base-10 decimal system you use every day has ten unique digits (0-9), while binary has only two. An IP address written as 192.168.1.1 is really just a human-friendly shorthand for a much longer string of bits — the decimal representation exists purely for our convenience, and converting back and forth between the two is a core networking skill for anyone managing a modern computer network.

How to Convert IP to Binary Manually

You don't need this tool to convert IP to binary by hand — the process is mechanical once you understand positional notation. Each of the eight bit positions inside an octet represents a power of two, and you simply check whether that power "fits" into the number you're converting.

Octet-by-Octet Positional Notation

Convert each octet (a number from 0-255) independently using this formula:

$$ \text{Octet} = \sum_{i=0}^{7} b_i \times 2^{i} $$

where each \(b_i\) is either 1 or 0. Working left to right through the bit position table below, compare the remaining value against each powers of 2 column: if the value is greater than or equal to that power, write a 1 and subtract it; otherwise write a 0 and move on.

Worked Example: 192 to Binary

  • 192 ≥ 128? Yes — write 1, remainder 64
  • 64 ≥ 64? Yes — write 1, remainder 0
  • 32, 16, 8, 4, 2, 1 — all No, write 0
  • Result: 11000000

Repeat this for all four sections of 192.168.1.1 and you get 11000000.10101000.00000001.00000001 — the same 32-bit string an IP address to binary converter would generate instantly.

Second Example: 55 to Binary

  • 55 ≥ 128? No, write 0. 55 ≥ 64? No, write 0.
  • 55 ≥ 32? Yes — write 1, remainder 23
  • 23 ≥ 16? Yes — write 1, remainder 7
  • 7 ≥ 8? No, write 0. 7 ≥ 4? Yes — write 1, remainder 3
  • 3 ≥ 2? Yes — write 1, remainder 1. 1 ≥ 1? Yes — write 1
  • Result: 00110111

Powers of Two Reference Table

Bit Position76543210
Power of 21286432168421

Memorizing this table is the fastest way to work these conversions by hand, exactly what's tested on the CCNA and CompTIA Network+ exams, where you're expected to work out a subnet id under time pressure without a calculator.

IPv4 Network Classes, Subnet Masks, and Subnetting

Once you can read an ipv4 address in binary, network classes start to make sense — each network class is really just a pattern in the leading bits of the first octet. Every class carries its own default mask and, by extension, its own network mask behavior when you're calculating a mask for a given block.

ClassFirst Octet RangeDefault MaskPurpose
A1-126/8 (255.0.0.0)Large networks
B128-191/16 (255.255.0.0)Medium networks
C192-223/24 (255.255.255.0)Small networks
D224-239N/AMulticast groups
E240-255N/AExperimental / reserved

Class A, Class B, and Class C ranges cover ordinary host addressing, Class D is reserved for multicast traffic, and Class E is set aside for experimental use and rarely seen in production. Subnetting — dividing a Class A, B, or C block into smaller networks — is really just binary arithmetic applied to a mask, which is why every subnetting exercise eventually comes back to the same reference table above.

Private IP Address vs Public IP Address Ranges

  • A private ip address range (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) is reserved for internal networks and never routed on the public internet.
  • A public ip address is globally unique and reachable directly from the internet.
  • Network address translation (NAT) is what lets an entire private network share one externally routable address.
  • A loopback address (127.0.0.1) and a link-local address (169.254.x.x) never leave the local machine or segment.

IPv6 Binary Conversion

IPv6 addresses use 128 bits instead of 32, grouped into eight 16-bit sections called hextets rather than 8-bit octets. Each hextet is written in hexadecimal, and every hex digit expands to exactly four binary digits, so a full IPv6 address always converts to 128 raw bits even though it looks much shorter on screen. Take 2001:0db8::1: the first hextet 2001 expands to 0010000000000001, and each of the remaining hextets expands the same way before you concatenate all eight groups into one continuous binary string.

IPv6 exists largely because the world ran out of room in the older addressing scheme: a 32-bit address space tops out at roughly 4.3 billion unique values, and phones, laptops, smart TVs, and household sensors chewed through that supply years ago. Moving to a 128-bit space isn't just a bigger number for its own sake — it multiplies the available pool enormously, which is why internet service providers and mobile carriers have been migrating their backbone infrastructure over gradually rather than all at once. Most home networks still run a mix of both versions today, assigning a dual-stack configuration so older devices keep working over the smaller address space while newer hardware negotiates a connection over the larger one whenever it's available.

Expanded and Compressed Notation

An IPv6 address can be written two ways: expanded notation shows all eight hextets with their leading zeros in place, while compressed notation uses a double colon (::) to collapse one run of consecutive zero hextets. A 16-bit hextet like db8 expands to 0000110110111000 in binary, and an 8-bit octet like 192 expands to 11000000 — same underlying math, different group size. This is the full ip address to binary conversion process IPv6 requires: expand every hextet, convert each hex digit to four bits, and concatenate.

Why Binary Matters for Networking and Security

Understanding IP binary isn't just an academic exercise for a certification exam — it's how a router, switch, or firewall on any computer network actually makes decisions, and it underpins network security at every layer:

  • Subnetting and calculating host ranges both rely on binary AND operations between an address and its subnet mask.
  • Access control lists (ACLs) use a wildcard mask — the inverse of a subnet mask — which only makes sense once you can read the underlying bits.
  • Network troubleshooting often comes down to spotting a single flipped bit in a binary IP that's routing traffic somewhere unexpected.
  • Security analysis of IP spoofing, packet analysis, and firewall rules all assume you can translate between decimal and binary on sight.
  • A network administrator preparing for the CCNA or CompTIA Network+ exam will be tested on binary math directly, with no calculator allowed.

Network engineers also lean on a binary IP converter during cross-browser testing, since some browsers normalize a binary-formatted IP address back to its dotted-decimal form automatically — a handy trick for probing how an access list or IP checker behaves. Pair this tool with a full subnet calculator when you need to plan address ranges rather than just convert a single host, and keep it bookmarked alongside your other network security utilities for quick lookups during an incident.

Binary to IP, Decimal, and Hex Converters

An IP-to-binary conversion is one half of a small family of related number base converter tools built on the Internet Protocol. If you're going the opposite direction, a binary to IP converter takes a bit string and reassembles it into dotted decimal. For other bases, you'll want:

  • IP to decimal converter and decimal to IP converter — treats the whole 32-bit address as one large integer rather than four octets.
  • IP to hex converter and hex to IP converter — useful when working with IPv6 hextets or low-level packet dumps.
  • IP to octal converter and octal to IP converter — less common today, but still shows up in legacy Unix networking tools.

Whichever direction you're converting, the underlying logic never changes: split the address, convert each part with positional notation, and reassemble it in the target base. That's the entire IP address to binary conversion process condensed into three steps, and it's precisely the logic running behind every IP address to binary converter — including this one — whenever you paste an address into an IP to binary converter, or, informally, an "IP to bin" tool, instead of working the powers-of-2 table by hand.

Practical Uses You'll Run Into

Outside of exam prep, this kind of converter earns its keep in a handful of everyday networking tasks. Network administrators use it to sanity-check a subnet mask calculation before pushing a configuration to a live router, since a single mistyped bit in a mask can silently merge two subnets or split one in half. Security teams use it while writing firewall rules and access control lists, translating a wildcard mask back into plain octets to confirm exactly which addresses a rule will actually match. Students working through subnetting practice problems use it to check their own by-hand positional notation math against a known-correct answer before an exam.

It's also useful outside strict networking contexts. Developers doing cross-browser testing sometimes feed a binary-formatted address into a form that expects dotted decimal, since some browsers will silently normalize it back — a quick way to test how forgiving an input validator really is. And anyone reverse-engineering a packet capture will eventually need to convert a raw binary or hex field back into a readable IP address, decimal number, or octal value, which is exactly what the related converters above are built for.

Even outside professional networking, plenty of hobbyists end up here. Someone setting up a home lab or a Raspberry Pi cluster on their own local network often needs to hand-pick static addresses that avoid clashing with whatever their router's DHCP pool already hands out, and understanding the binary boundaries of that pool makes it far easier to pick a safe range instead of guessing. Gamers troubleshooting NAT type issues on a console, or anyone setting up port forwarding for a home server, will also run into the same underlying math — a router's forwarding rules are ultimately just binary comparisons between an incoming packet's address and a table of configured ranges, whether or not the admin panel shows you the bits directly.

Related Network Tools

Explore these related tools for subnet calculation and IP address management.

Additional networking calculators for IP address planning and network analysis.

About the author

Subash Geetha Krishnan

Tech Lead for Nimble Storage at HPE Services Storage Support

Subash Geetha Krishnan is a Tech Lead for Nimble Storage at HPE Services Storage Support, based in Singapore, with over 15 years of experience in enterprise storage solutions. He created SubnetCalculate so that accurate networking calculations are free and easy for everyone.

  • Content author: Subash Geetha Krishnan
  • Fact checked by: Subash Geetha Krishnan. Each calculator is built on industry-standard algorithms and tested against known results before it goes live.
  • Published Updated

Comments & Feedback

Share your experience or ask questions about this tool