Online ChaCha20-Poly1305 Encryption and Decryption Tool

Report a Problem
ChaCha20-Poly1305 AEAD Authenticated Encryption Server-side Processing
This tool performs calculations on the server. Data is sent to the server for processing. Do not enter real production keys or sensitive data.
ChaCha20-Poly1305 requires a 32-byte key, or 64 hexadecimal characters.
No advanced settings are needed for normal use. Developers can specify the key, IV / Nonce, AAD, and output encoding here for API integration and cross-language verification.
Do not reuse a Nonce with the same key. Reuse can compromise the key stream and allow ciphertext forgery.
Decryption requires the key, Nonce, AAD, and Tag to exactly match the encryption parameters.
Privacy Notice：ChaCha20-Poly1305 is processed server-side because browser-native WebCrypto does not provide this algorithm. The ciphertext, key, and AAD are sent to the server for this operation and are not stored. Do not enter real production keys or sensitive plaintext.

AEAD authenticated encryption with 32-byte keys, 12-byte nonce, AAD and 16-byte authentication tag support

Online ChaCha20-Poly1305 Encryption and Decryption Tool

ChaCha20-Poly1305 is an IETF standardized AEAD authenticated encryption algorithm. ChaCha20 provides stream encryption while Poly1305 generates authentication tags. It is widely used in TLS 1.3, mobile applications and modern secure protocols.

Core Features

  • Provides separate encryption and decryption tabs.
  • Generates secure random keys and nonces automatically.
  • Supports Additional Authenticated Data (AAD) for integrity protection.
  • Displays ciphertext, nonce and authentication tag separately for easy copying.
  • Allows one-click filling of encryption results into the decryption form.

Parameters

The key length is fixed at 32 bytes (64 hexadecimal characters). The nonce length is fixed at 12 bytes (24 hexadecimal characters). The authentication tag is 16 bytes and generated automatically during encryption. AAD is authenticated but not encrypted, and both encryption and decryption sides must use identical AAD values.

Nonce Usage Requirements

The same nonce must never be reused with the same key. Reusing a nonce can expose the encryption stream and allow attackers to recover information or forge messages. This tool generates a new random nonce for each encryption operation.

Processing Method

Browser WebCrypto does not currently provide ChaCha20-Poly1305. This tool uses server-side libsodium for calculation. Input data is used only during the current request and is not stored. Do not enter production keys or sensitive plaintext.

Error Handling

  • Invalid key length or nonce length will be reported immediately.
  • Invalid Base64 ciphertext or authentication tags will show format errors.
  • Failed verification indicates incorrect key, nonce, AAD or authentication tag.

Usage Scenarios

  • Testing ChaCha20-Poly1305 implementations across languages.
  • Understanding AEAD encryption parameters.
  • Verifying protocol designs using AAD fields.
  • Learning modern authenticated encryption algorithms.

Security Recommendations

ChaCha20-Poly1305 provides modern authenticated encryption security comparable to AES-GCM. Choose based on your environment and hardware acceleration support.

Privacy Notice

The calculation service does not store submitted data. However, because this algorithm requires server-side processing, avoid entering real production secrets.

Online ChaCha20-Poly1305 authenticated encryption

ChaCha20-Poly1305 combines ChaCha20 encryption with Poly1305 authentication and is widely used in modern secure communication protocols.
  • Supports ChaCha20-Poly1305 AEAD encryption with 32-byte keys and 12-byte nonce
  • Supports AAD additional authenticated data without encrypting it
  • Outputs Base64 ciphertext and 16-byte authentication tag
  • Automatically verifies authentication tag during decryption
  • Displays ciphertext, nonce and tag separately for easy reuse
  • Suitable for TLS 1.3, mobile and modern protocol testing
Nonce values must never be reused with the same key. Calculation requires server-side libsodium processing, so production secrets should not be entered.
Comments 0
No comments yet. Be the first to comment!
Comment content cannot be empty
0/255