Convert IPv4 to integer or binary
Swap between dotted-quad IPv4, its 32-bit integer form, and binary octets. Useful for DB storage, log analysis, and bit-level filtering.
3232235521
How to convert an IPv4 address
Every IPv4 address is a 32-bit number. Dotted-quad notation just shows four 8-bit octets — the same bits, easier on the eyes.
- 01
Pick a direction
IPv4 → integer, integer → IPv4, or IPv4 → binary octets.
Bytes flow through
TextEncoder/TextDecoderfor predictable UTF-8 semantics — emoji, surrogate pairs, and combining marks all encode losslessly.modeUTF-8TextEncoderlosslesslivemode · raw bytesset · UTF-8IPv4 → integer
loaded · UTF-8MIME · ready - 02
Type the input
Each octet 0–255. Integers go 0 – 4 294 967 295.
Hash and signature operations call
crypto.subtlefrom the Web Crypto API, so output matches OpenSSL / Node bit-for-bit.inputWeb Cryptosubtledeterministicliveinput · optionsipv4 · live192.168.0.1
options applied · livelive - 03
Read the result
Output updates live with the equivalent representation.
Options re-run instantly through
useEffect+useMemo— switching URL-safe mode or padding doesn’t re-encode from scratch.livememoisedoptionsinstantreactiveout · encodedint · ready3232235521
encoded · livelossless - 04
Copy or download
One click to clipboard or save as .txt.
Copy uses the Async Clipboard API; downloads ship via
Blobwith the appropriate MIME (text/plain,image/png, …) so external tools recognise them.exportclipboardblobMIME-correctclient-sideok · copiedready · doneCopied
shipped · ready to shipsuccess
Encoding without surprises
Always UTF-8 first
Use TextEncoder / TextDecoder for bytes ↔ string conversion. btoa alone breaks on non-ASCII.
URL-safe vs standard Base64
Standard uses +, /, =; URL-safe swaps to -, _, no padding. Don’t mix them.
Hashes aren’t passwords
SHA-256 is fast; that’s good for fingerprints, bad for passwords. Use bcrypt / argon2 for credentials.
Watch padding rules
Some decoders are strict about = padding, others auto-pad. If round-trips fail at exactly 1 or 2 bytes, check padding.
Use Web Crypto for keys
Generate cryptographic keys via crypto.subtle, never Math.random. The latter is predictable.
JWT decode ≠ verify
Decoding a JWT just splits and base64-decodes. Verification needs the issuer’s public key / shared secret.
When to convert IP forms
Databases, log analytics, firewalls, scripts.
DB storage
Store IPs as 32-bit INTs for faster range queries. Output round-trips losslessly with the matching decoder — both run client-side, so end-to-end testing happens in a single tab. Encoding flows through TextEncoder for predictable UTF-8 semantics.
RFC-compliantLog filtering
Compare integer IPs with bitmasks in scripts. Web Crypto's subtle.digest produces output that matches OpenSSL, GPG, and Node's crypto module byte-for-byte. That makes the result trustworthy as a content fingerprint, ETag, or integrity check.
OpenSSL-matchedBit math
Use binary view to teach or debug netmasks. Pairs cleanly with HMAC, JWT, and signed-URL workflows where bit-level correctness matters. The browser's crypto stack is FIPS 140-validated in Chrome and Firefox, so it's production-grade.
losslessMigration
Move IPs between systems with different encodings. Output uses canonical RFC 4648 / 7515 alphabets so curl, openssl, and any standards-compliant decoder accept it as input. URL-safe variants drop padding for tokens that travel in query strings.
byte-identicalHot path
Integer comparison beats string parsing at scale. Heavy hashing runs through useMemo so large inputs don't block typing. PBKDF2, bcrypt, and Argon2 expose configurable cost factors — tune for your threat model, not the default.
spec-gradeGeo lookups
Most geo-IP DBs use integer ranges per region. Same input plus same options always yields identical bytes. That's the foundation for content-addressed storage (IPFS, Git, S3 ETags) and means the output is safe to commit to fixtures.
production-readyFrequently asked questions
Something missing?
Tell us what you need. We ship the top requests every two weeks.