One rule applies across the whole section: processing runs with no result stored on the server any longer than it takes to answer. For some tools (the image converter) processing happens entirely in the browser – files never leave the device.
Base64 is encoding, not data protection: anyone can decode the string back in a second. It should not be used to hide passwords or personal data.
Browsers and DNS work with domains in ASCII. A domain like "münchen.de" is technically stored as a punycode string, and the converter shows that correspondence.
One that uses a cryptographically random source and allows a length from 12 characters with digits, mixed-case letters and symbols.
This section brings together utilities that turn one kind of data into another: text into a different case or number system, an image into a different format, randomness into a number, a password or a QR code.
Some converters work both ways: Base64 and the binary system can be turned back to the original without loss. Other conversions are irreversible by nature – changing text case erases the original mix of upper- and lowercase letters, a compressed image cannot be restored byte for byte, and an MD5 hash fundamentally cannot be decoded back into the original string. It is worth keeping a separate copy of an important file before converting it if the process is irreversible.
If the task is to shrink an image's weight without losing quality, an image converter is needed, not a generator. If the task is to get an unpredictable value (a password, a number, a code), a generator is needed: unlike a converter, it has no input data beyond its settings.
Some converters from this section are used more by developers – the URL converter, Base64 converter and number system converter are also listed in the Developer Tools section. Preparing text before converting it is covered in Content & SEO Optimization.