IP to Hex Converter

IP to hex conversion maps a dotted-decimal IPv4 address to its hexadecimal (base-16) equivalent. Each of the four decimal octets (0–255) converts independently to a two-digit hex value, then concatenates: 192.168.1.1 becomes C0A80101 (C0 = 192, A8 = 168, 01 = 1, 01 = 1). IPv6 addresses are natively hexadecimal by specification (RFC 4291); this tool also expands compressed notation and strips colon separators, producing a continuous 32-digit hex string. Hexadecimal IP representations appear in firewall ACLs, packet captures, programming environments, and network logging systems that store addresses as integer or hex values.

The tool includes a bulk conversion mode — paste a list of IPv4 or IPv6 addresses, one per line, and convert all of them in a single operation. No file upload is required. All processing runs in the browser: the full list is converted instantly, and no address is transmitted to any server. Bulk mode is useful for processing firewall rule sets, converting network log exports, or preparing address lists for programming test fixtures.

IPv4 addresses (RFC 791) are 32-bit unsigned integers expressed as four decimal octets. Each octet occupies 8 bits and has a range of 0–255. To convert to hexadecimal, each octet is divided by 16: the quotient becomes the first hex digit, the remainder the second. Values 10–15 map to letters A–F. A leading zero is always applied when the value is below 16 (e.g., 1 → 01), ensuring every octet always produces exactly two hex digits. The four hex pairs are then concatenated into an 8-character string.

IPv6 addresses (RFC 4291) are 128-bit values defined in hexadecimal — eight groups of four hex digits separated by colons. Compressed notation (::) represents one or more consecutive groups of all-zero bits. This tool expands compressed notation and pads each group to four digits before stripping colons, producing a continuous 32-character hex string representing the full 128-bit address.

IPv4 Hex Output Formats — Reference

Packet capture analysis. A security analyst reviewing a Wireshark capture sees source address 0xc0a80101 in a raw frame. Entering that value confirms the address is 192.168.1.1 — a private LAN host (RFC 1918), not an external actor. Hexadecimal is the native format of the IPv4 header as defined in RFC 791, making this conversion essential for manual frame inspection.

Firewall and ACL configuration. A network engineer configuring a legacy Cisco ACL or firewall rule set that requires hex IP notation pastes ten addresses into bulk mode. The full output column is copied directly into the configuration — no manual per-address conversion and no conversion script needed.

Network programming and testing. A developer writing a Go network library stores incoming IP addresses as 32-bit integers in a Redis cache, keyed by their hex representation. Bulk mode converts an entire test fixture list in one pass, producing the hex strings needed for unit test assertions without writing a throwaway conversion utility.