toString of that value. Encode/decode uses the browser’s Base64, URL and HTML-entity helpers on the text you paste. SHA-256 / SHA-1 / MD5 are hashed locally in the page — nothing is sent to a server.
Number base conversion works from one shared integer value: type a number in decimal, hexadecimal, binary, or octal, and the other three bases are calculated as that same integer's toString representation in each base — so all four fields always describe exactly the same number.
Encoding and decoding for Base64, URL encoding, and HTML entities each use the browser's own built-in conversion functions on the text you paste, rather than a custom re-implementation — keeping the results consistent with what your browser or a web server would actually produce.
SHA-256, SHA-1, and MD5 hashes are all computed locally inside the page using your browser's own cryptographic functions — nothing you type is ever sent to a server, which matters if you're hashing anything sensitive during testing or development.
The hashing itself runs entirely in your browser using local cryptographic functions — nothing is transmitted to a server. That said, MD5 and SHA-1 are considered cryptographically broken for security purposes; use SHA-256 or a stronger algorithm for anything security-sensitive.
Every base shares one underlying integer value. Typing in any one base updates that integer, and the other three fields are recalculated as that same integer's string representation in their respective base.
Base64 encodes binary data as printable text using a 64-character alphabet, commonly used for embedding data in text formats. URL encoding (percent-encoding) escapes characters that aren't safe in a URL, like spaces and special symbols. They solve different problems and aren't interchangeable.
No — number base conversion, encoding/decoding, and hashing all run locally in your browser using built-in JavaScript functions, so none of it requires a network request.