IPv4 to hexadecimal converter

Enter an address such as 192.168.1.10 to see every decimal octet beside its two-digit hex and eight-bit binary equivalent, plus joined forms ready to compare with packet captures, logs, access lists, and router configuration files. The clear byte-by-byte result makes low-level notation easier to inspect without doing repeated base conversions manually.

Read the conversion one octet at a time

An IPv4 address is four unsigned eight-bit values written in decimal and separated by dots. The converter validates that structure first, then transforms each octet independently. Decimal 192 becomes hexadecimal C0 and binary 11000000; decimal 1 becomes hexadecimal 01 and binary 00000001. Fixed widths are important here. Without the leading zero, small values can make a packet field look shorter than it really is and make visual comparisons harder. The result therefore shows a record for every position with its decimal, two-character hexadecimal, and eight-character binary value. It also provides dotted hexadecimal, compact hexadecimal, and dotted binary forms. Use the octet records when learning or checking one field, and use the joined representations when matching a value found in a capture, device export, low-level log, or protocol note. The original address is normalized after validation, so the output stays predictable for scripts and golden comparisons.

Why strict IPv4 validation matters

Network tools should reject ambiguous input instead of quietly guessing. This converter requires exactly four decimal octets, each in the inclusive range from 0 through 255. It does not accept signs, hexadecimal prefixes, missing components, extra dots, or leading zeros such as 001. Leading zeros have been interpreted as octal by some historical software, while other systems treat them as ordinary decimal formatting; rejecting them prevents the same text from meaning different addresses in different environments. Surrounding whitespace is harmless and is trimmed, but whitespace inside an address is not accepted. The validation is purely syntactic and numeric: the converter does not claim that an address is publicly routable, assigned, reachable, private, multicast, or safe to use. Values such as 0.0.0.0 and 255.255.255.255 are valid four-octet representations and can be converted, even though their operational meaning depends on context. A rejected value returns a typed input error rather than a partial or misleading conversion.

Use the formats in packet and router work

Hexadecimal is compact and maps cleanly to bytes, which is why packet dumps and debugging tools often show addresses as groups such as C0 A8 01 0A or as one continuous value. Binary makes bit boundaries, masks, and prefixes explicit: the same address becomes four groups of eight bits, allowing you to see which bits belong to a subnet prefix and which belong to the host portion. The dotted output keeps octet boundaries visible, while the compact hexadecimal field is convenient for searching logs that omit separators. Always check the notation expected by the destination system before pasting a result; some configuration formats want 0x prefixes, spaces, colons, or a 32-bit integer rather than the representations returned here. This capability deliberately supplies neutral, fixed-width values and does not rewrite a configuration file. It runs deterministically without network access, random values, clocks, DNS lookups, or external services, making it suitable for repeatable browser checks and automated API workflows at $0.002 per request.