IP to Binary Converter Online - Convert IPv4 Addresses to Binary

Convert IPv4 Addresses to Binary Online

The IP to Binary Converter transforms IPv4 addresses such as 192.168.1.1 into their equivalent 32-bit binary representation, grouped by octet for clarity. Paste a list of addresses, one per line, and the tool returns the corresponding dotted binary value for each.

How an IPv4 address maps to binary

An IPv4 address is composed of four 8-bit octets separated by dots. Each octet is a decimal value between 0 and 255 that converts to an 8-digit binary number. For example, the address 127.0.0.1 becomes:

127      0        0        1
01111111.00000000.00000000.00000001

Common conversions

IPv4	Binary
0.0.0.0	00000000.00000000.00000000.00000000
127.0.0.1	01111111.00000000.00000000.00000001
192.168.1.1	11000000.10101000.00000001.00000001
255.255.255.0	11111111.11111111.11111111.00000000
255.255.255.255	11111111.11111111.11111111.11111111

Why convert IPs to binary?

Networking and subnetting study: visualise the network and host portions of an address.
CIDR notation calculations and prefix-length verification.
Programming exercises that need a bitwise representation of an IPv4 address.
Routing and ACL debugging where bitmasks must align with the address.

How to use

Type or paste IPv4 addresses (one per line) into the input editor.
Optionally upload a .txt file containing addresses.
Read the binary output on the right or copy/download it for later use.
Validation errors are listed below the input editor with the offending line number.

Frequently Asked Questions

Does this support IPv6?

No. This tool focuses on IPv4. IPv6 addresses are 128 bits and follow a different hexadecimal-based notation, so they require a dedicated converter.

Can I convert many addresses at once?

Yes. Enter one IPv4 address per line. The output keeps the same line order so you can map results to the original input.

Why does the binary output use dots between octets?

IPv4 binary representation traditionally separates the four 8-bit octets with dots (e.g. 11000000.10101000). This makes the bit boundaries between octets easier to read.

What happens with invalid input?

Lines that are not valid IPv4 addresses (wrong octet count, non-numeric values, or octets outside the 0-255 range) are reported as errors. Valid lines continue to convert normally.

Is my data sent anywhere?

No. All conversions run inside your browser. No address ever leaves your device.