Skip to main content

IP Address Converter

Converts an IPv4 address among dotted decimal, binary, hexadecimal, octal, 32-bit integer, and IPv4-mapped IPv6 notation. Auto-detection reads each notation from its shape, and the integer is the first octet x 16,777,216 plus the second x 65,536 plus the third x 256 plus the fourth, so 192.168.1.1 becomes 3232235777.

Runs entirely in your browser

This tool sends nothing over the network. Everything you enter is processed on your device and never reaches our servers.

Networking
IP Address
Binary
Loading the tool
Reference

Documentation

An IP address converter rewrites one IPv4 address in every notation software uses for it. An IPv4 address is a single 32-bit number. The familiar dotted decimal form splits it into four 8-bit octets written in base 10, and the same 32 bits can equally be written in binary, in hexadecimal, in octal, or as one unsigned integer from 0 to 4,294,967,295.

Auto-detection reads the notation from the shape of the input. Four groups of exactly eight 0s and 1s are binary; groups containing the letters a to f, or a value starting with 0x, are hexadecimal; four groups that all start with 0 are octal; a run of digits with no dots is the 32-bit integer; and any other four dot-separated groups are dotted decimal, where each octet must be a whole number from 0 to 255. Naming the input format removes the guesswork for values that fit more than one pattern: 10.10.10.10 is ordinary decimal, while the Binary format reads short groups such as 1.1.1.1 as binary when asked to.

The integer form is the first octet times 16,777,216 (2 to the 24th power), plus the second times 65,536 (2 to the 16th), plus the third times 256, plus the fourth. Hexadecimal writes each octet as two digits, so 192 becomes c0 and 168 becomes a8, and octal writes each octet in base 8 behind a leading 0, so 192 becomes 0300. The IPv4-mapped IPv6 form defined in RFC 4291 places the 32 bits after ::ffff:, and it is shown both as ::ffff:192.168.1.1, the form RFC 5952 recommends, and as two lowercase hexadecimal groups. Settings switches hexadecimal to uppercase, drops the 0x and 0 prefixes, and writes the binary as one unbroken 32-bit string.

Leading zeros are the ambiguity to watch. The classic inet_aton parser behind many command-line tools and the URL parser that browsers follow both read 010 as octal 8, so 192.168.010.001 means 192.168.10.1 to most people and 192.168.8.1 to that software. Auto-detection here reads such an address as decimal unless every octet starts with 0, and a note under the results states which reading was used. The browser URL parser also accepts a single integer or hexadecimal host, so http://3232235777/ and http://0xc0a80101/ reach the same machine as 192.168.1.1.

For 10.0.0.1, 10 x 16,777,216 = 167,772,160, and adding 0 + 0 + 1 gives the integer 167772161. The octets are 0a, 00, 00, and 01 in hexadecimal, so the flat form is 0x0a000001; in octal they are 0012.0000.0000.0001, and the binary is 00001010.00000000.00000000.00000001.

IP addresses appear in many different notations across networking, programming, database storage, and security analysis. Having all representations visible at once eliminates repeated manual calculations and reduces transcription errors when switching between tools or documentation formats.

  • Network Configuration: Translate a dotted decimal address like 10.0.0.1 into its 32-bit integer form (167772161) when configuring firewall rules or access control lists that require numeric IP representations.
  • Subnet Analysis: The binary representation shows the network and host portions directly. Lining up 192.168.1.1 (11000000.10101000.00000001.00000001) against a subnet mask reveals which bits belong to the network prefix.
  • Programming and Database Storage: Store IPv4 addresses as unsigned 32-bit integers in databases for faster indexing and range comparison, and convert between the integer and dotted forms when reading or writing records.
  • Log Analysis: Parse hexadecimal IP representations found in packet captures, memory dumps, or raw network logs. A value such as C0A80101 converts back to 192.168.1.1 for human-readable reporting.
  • Security Research: Phishing links sometimes hide a destination as a decimal integer, a hexadecimal number, or zero-padded octal octets. Converting the host back to dotted decimal reveals the true destination before anyone clicks.
  • Education: Study how IPv4 addressing works by seeing the same address in every base simultaneously. Comparing the dotted decimal, binary, and integer forms side by side shows how the four octets map to a single 32-bit number.
  • IPv6 Migration Planning: The IPv4-mapped form of an address (::ffff:192.168.1.1) is how dual-stack sockets and translation gateways represent IPv4 peers, so it appears in logs and configuration on IPv6-capable systems.
  • Documentation and Technical Writing: Reference IP addresses in multiple notations within network architecture documents, generating every representation from a single input to keep diagrams, tables, and configuration examples consistent.
  • Embedded Systems Development: Work with IP addresses stored as raw 32-bit values in firmware or register maps, converting between the integer in device memory and the dotted decimal form used in diagnostic interfaces.
Inputs, outputs, and what the IP Address Converter computes

What the IP Address Converter asks for and what it returns, as a plain list. Defaults, units, and ranges are the ones the form loads with.

Inputs

  • Input Format · default: Auto-Detect
  • IP Address or Value (text input)
  • Display hexadecimal in uppercase · default: off
  • Include 0x prefix on flat hexadecimal · default: on
  • Include 0 prefix on octal octets · default: on
  • Group binary output by octet (dot-separated) · default: on

Controls

Convert · Reset

Example

For 10.0.0.1, 10 x 16,777,216 = 167,772,160, and adding 0 + 0 + 1 gives the integer 167772161.