AES File Encrypt and Decrypt
AES File Encrypt and Decrypt turns pasted data or a file into converted output and any error positions. Files are read on your device.
- File, image, and document tools run in the browser, but originals may still contain personal or sensitive information. Review both source files and outputs before sharing or submitting them.
AES File Encrypt and Decrypt turns pasted data or a file into converted output and any error positions. Files are read on your device.
Example AES File Encrypt and Decrypt result hello.txt.tb8aes: 53 bytes Container: TB8B Recovered hello.txt: 5 bytes Recovered contents: hello Next step: TB8A output warns that legacy normalization was used. Compare recovered contents or checksums with the original before re-encrypting as TB8B.
How to use AES File Encrypt and Decrypt
Encrypt a whole local file into a .tb8aes copy or recover its original bytes. This is file encryption, not document parsing; text, images, and archives are handled as byte sequences.
TB8B preserves exact password text. It uses PBKDF2-SHA256 at 150,000 iterations and AES-256-GCM; only legacy TB8A decryption applies the old password normalization.
- Keep the original, then select one file to encrypt or one ToolBada .tb8aes file to decrypt.
- Enter your own 8–4,096-character password in the dedicated field and choose Encrypt or Decrypt. Keep it out of public examples, support messages, and screenshots.
- Run, check the version and byte count, and download. Encryption appends .tb8aes to the original name; decryption removes that extension.
- Test a small encrypt/decrypt roundtrip and compare the recovered bytes with the original. Downloading does not automatically overwrite the source.
Useful for
- Protect a local backup copy with a password while retaining the original separately.
- Recover an old TB8A file and migrate it to exact-password TB8B encryption.
- Verify a small roundtrip before preparing a file for transfer.
Limits and checks
- Plaintext is limited to 40 MiB. Encryption adds 48 bytes; decryption accepts 40 MiB + 48 bytes including container overhead.
- TB8B distinguishes digits, semicolons, quotation marks, and surrounding spaces. TB8A uses its original numeric rounding, semicolon splitting, and trimming of spaces or outer quotation marks.
- A lost password cannot be recovered by this tool. Store it separately from the encrypted file; never publish or reuse a demonstration password.
Worked example
Five-byte test file
File: hello.txt Contents: hello (UTF-8, 5 bytes, no newline) Direction: encrypt Password: enter your own value privately
Do not put the password in a shared example. Retain the original file.
TB8B size and recovered bytes
hello.txt.tb8aes: 53 bytes Container: TB8B Recovered hello.txt: 5 bytes Recovered contents: hello
53 = 5 plaintext bytes + 48 container bytes. Random salt/IV means the ciphertext is not a fixed example.
Common issues
Incorrect password or damaged encrypted file.
Check Decrypt mode and the original spaces, semicolons, and digits. TB8B has no legacy fallback. A wrong password and damaged ciphertext produce the same error.
Not a supported ToolBada AES file.
The input needs a TB8A or TB8B container header. Renaming another encrypted format to .tb8aes does not make it compatible.
How to interpret the result
TB8B confirms exact password handling, not password strength or safe storage.
Related workflow
TB8A output warns that legacy normalization was used. Compare recovered contents or checksums with the original before re-encrypting as TB8B.
Privacy and review notes
Web Crypto processes the file in this browser. Do not expose passwords in examples, links, screenshots, or support requests. A lost password may leave the file unrecoverable.
FAQ
Why does the ciphertext change between runs?
Each run creates a new 16-byte salt and 12-byte IV. Compare recovered plaintext with the original instead of expecting identical ciphertext.
Why is no password published in the example?
A public example password should not protect real files. Choose your own password privately and store it separately. Processing uses Web Crypto in the current browser.