Need to support additional languages? Some languages use accented characters that are uncommon in English. Make sure you include those characters ahead of time to avoid decryption issues.

To encrypt/decrypt text, we need to first transform each character into a number so that we can perform cipher operations on it. The

Character Mapping

⁠

table handles this conversion for us. If a character isn’t available in that table, it will be dropped from your text during encryption.

💡 To import a set, click Add This Block. Please review

Note about Performance

⁠

for important related info

Warning before you update:

Any updates to

Character Mapping

⁠

will likely cause encrypted secrets to decrypt incorrectly. It’s advisable to only use this tool ahead of launch.

⁠

Why is that?

⁠

Performance Notes

⁠

⁠

🔍 Missing Characters?

Character missing when you decrypt your Secret?

Import new characters

👆 Type new characters here

Warning before you update:

Any updates to

Character Mapping

⁠

will likely cause encrypted secrets to decrypt incorrectly. It’s advisable to only use this tool ahead of launch.

I primarily included the Latin-1 Supplement block to help prevent corruption that could happen when users add or remove individual characters or entire character sets to the Character Mapping after items have already been encoded.

During encryption, some characters end up “out of range” because the sum of their index and the corresponding character in the key’s index exceeds the available characters in the table. To map them to a character (in order to generate the ciphertext), we loop back to the beginning of the table. When the Count() of the available characters changes, these out of range characters end up decrypting to the wrong characters and we get corrupted text. This Latin-1 Supplement block therefore serves as a kind of “buffer” to help reduce the likelihood of this happening often when changes are made to the character mapping table.