What the IP Address Base Converter helps you do
Use this page to inspect one IPv4 address as canonical dotted decimal, four binary octets, four octal octets, four hexadecimal octets, and one unsigned 32-bit integer. The workspace keeps the source, settings, and result together so you can understand what changed instead of receiving an unexplained clipboard value. Start with a small known example before using unfamiliar data.
192.0.2.42 becomes C0.00.02.2A in hexadecimal and 11000000.00000000.00000010.00101010 in binary. The canonical decimal result remains 192.0.2.42. The visible result remains available for selection, copying, and download. Nothing is copied or saved automatically, so you can stop and compare it with the source before taking the next step.
How the conversion works
The selected source form is parsed into exactly four bytes. Decimal validation uses canonical four-part IPv4 rules; the other modes require fixed-width octets. Every displayed representation is generated from the same four validated byte values.
Auto accepts canonical dotted decimal only, avoiding ambiguous legacy forms such as shortened addresses or decimal strings with leading zeros. Choose Binary, Octal, or Hex for fixed-width octets, or Unsigned 32-bit integer for one canonical decimal value from 0 through 4294967295. Inputs and outputs stay in the current browser tab during ordinary use. NexaCurrent does not upload the working value to perform this operation. Reset clears the entered value, settings, result, messages, and generated download from the workspace.
How to use IP Address Base Converter
Enter or paste the smallest complete source value that represents your task. Choose the source format, direction, byte order, output family, or fixture type shown on this page. Run the primary action, read the summary, and inspect the complete visible result before using Copy or Download.
Confirm all five outputs correspond to the same four bytes. When copying into a configuration, prefer canonical dotted decimal unless that configuration explicitly documents another notation. If the receiving application has its own specification, sample, or validator, use that as a second check. A successful result here confirms this page’s stated rules; it cannot promise that another system has selected the same convention.
Errors, boundaries, and recovery
Fewer or more than four octets, an octet outside 0–255, wrong token width, invalid base digits, shortened IPv4 notation, integers outside the unsigned 32-bit range, leading-zero integers, and ambiguous automatic input are rejected. An error clears an earlier result so an obsolete success cannot be mistaken for the corrected answer. Fix the first message, then run the operation again. Changing the input or a setting also removes stale copy feedback.
Text input is limited to 200,000 characters, generated quantity to 100 items, and pattern or schema expansion to the smaller limits shown beside those controls. These bounds keep one browser tab responsive. For a large file or batch, use a streaming command-line tool and preserve an original copy.
Limits and responsible use
Different text does not create a different network address when the underlying 32 bits are the same. This tool does not perform DNS, geolocation, ownership, reachability, subnet, firewall, or security checks.
Do not paste a real password, private key, access token, personal record, or production customer dataset when a harmless sample can prove the same behavior. Treat downloaded output as a new file, keep the source until the target system accepts it, and document the selected format whenever another person must reproduce the result.