Cryptography Workspace
Encoding and encryption are often confused. Encoding changes how data is written so it can travel through text-only channels; anyone can reverse it. Encryption makes data unreadable without a key. This workspace provides both, clearly separated, for text and files.
Encoder / Decoder
Convert text to and from Base64, Base64URL, Base32, hex, URL and HTML encoding.
Full access on every plan
File Encryption
NewEncrypt and decrypt files or text with a password using AES-256-GCM.
From Basic · 100 MB → 512 MB on Plus
Which tool to choose
- Encoder / Decoder
- Data must be written in another format, and secrecy does not matter.
- File Encryption
- Only people who know the password may read the data.
What these tools solve
- Convert text to and from Base64, Base64URL, Base32, hex, URL and HTML encoding.
- Encrypt a file or a piece of text with a password before storing or sending it.
- Decrypt files and text produced by HashlLab File Encryption.
When they are useful
- Reading a Base64 value from a config file, an e-mail header or an API response.
- Sharing a sensitive document through a channel you do not fully trust.
- Preparing data for a URL query string or an HTML attribute.
How it works
Encoding is done in the browser with UTF-8 text handling. File Encryption uses AES-256-GCM, an authenticated cipher: any change to the encrypted data is detected on decryption. The key is derived from your password with PBKDF2-HMAC-SHA-256 (600,000 iterations) and a random 16-byte salt; each encryption uses a fresh 12-byte nonce.
Limits and good practice
- Encoding is not protection: Base64 or hex can be decoded by anyone.
- File Encryption is a premium tool: 100 MB on Basic, 256 MB on Standard, 512 MB on Plus and Ultra. The whole file is processed in memory.
- There is no password recovery. The security of an encrypted file is only as good as its password.
- Encrypted files use the HashlLab .agr format, so they are decrypted with this tool.
Questions about crypto
Help centerIs Base64 a form of encryption?
No. Base64, Base32, hex and URL encoding only change how data is written. Anyone can decode them without a key. Use File Encryption when the content must stay secret.
What is the difference between Base64 and Base64URL?
Base64URL replaces + and / with - and _ and usually omits the = padding, so the result can be used in URLs and file names. JWTs use Base64URL.
How does File Encryption protect my data?
With AES-256-GCM, an authenticated cipher. Your password is turned into a 256-bit key with PBKDF2-HMAC-SHA-256 using 600,000 iterations and a random salt, which slows down password guessing. Any change to the encrypted file is detected when you decrypt it.
My file is rejected as too large.
Each plan has a maximum file size; the hint under the drop area shows yours. Sign in or choose a plan with a higher limit. For File Encryption, 512 MB is the maximum on every plan because the whole file is processed in memory.
Decryption fails with “Wrong password or the file was modified”.
Either the password differs from the one used to encrypt — check the keyboard layout and Caps Lock — or the file was changed or truncated after encryption, for example by an incomplete download. Authenticated encryption cannot tell these two cases apart by design.