IPv4 address converter

The IPv4 Address Converter turns a dotted IPv4 address (like 192.168.1.12) into other common representations:

• Decimal (a single 32-bit number) for databases, sorting, and some APIs

• Hexadecimal and binary for debugging packets, masks, and bit operations

• IPv6-mapped form for dual-stack systems and logs

Worked example: 192.168.1.12

Decimal conversion uses a base-256 weighting. If the octets are $a.b.c.d$ then:

The hex form is the same 32-bit value shown in base $16$: C0A8010C. Binary is the same value in base $2$.

• Copy from the results row instead of re-typing (it avoids invisible whitespace and typos).

• If you compare addresses, compare like-for-like: decimal-to-decimal or hex-to-hex.

• IPv6-mapped output is for compatibility/logs; it is not the same as a native IPv6 allocation.

• For subnet planning, convert an IP here, then compute boundaries in the subnet calculator.

• Share the link with results enabled when you want someone to verify the same exact address.

An IPv4 address has 4 octets. Each octet is a number in $[0,255]$. Treat the address as a base-256 number:

Once you have the decimal value, converting to hex or binary is just a base conversion. For example, hex is base $16$, and binary is base $2$.

IPv4-mapped IPv6 form puts the IPv4 bytes into the last 32 bits of an IPv6 address, typically with a ::ffff: prefix.

Octet: Each dotted part of an IPv4 address. It represents $8$ bits.

CIDR: A subnet suffix like /24indicates how many bits are network bits. That’s a subnet topic — use the IPv4 subnet calculator for that.

• This tool converts individual IPv4 addresses (not CIDR blocks, not hostnames).

• IPv6 output here is specifically IPv4-mapped IPv6, meant for compatibility/log reading.

• Always validate security rules (firewalls/ACLs) in your target platform — formats and reserved ranges can differ.

• RFC 791 — Internet Protocol (IPv4)
• RFC 4291 — IPv6 Addressing Architecture (IPv4-mapped IPv6)