File Checksum Verifier
Calculate a local file checksum and compare it with an expected SHA-256, SHA-384 or SHA-512 value.
Verify FileDeveloper Tools
AES Text Encryption & Decryption
Encrypt or decrypt text locally with AES-GCM and a password-derived key. The interface provides a focused workflow, clear output and export or copy controls…
Input and options
Encrypt or decrypt text locally with AES-GCM and a password-derived key.
Privacy: Your input is processed in the browser where supported and is not intentionally stored by this tool.
Result
Your output
Add the required input and run the tool.
Simple controlsEverything you need for the task.
Clear resultsReview your output before using it.
No signupGet started without an account.
How it works
1. Add the Required Input
The code, structured data, expression, token, or sample value requested by the interface.
2. Review AES Text Encryption & Decryption Options
Choose only the settings that apply to the result you need; leave optional controls unchanged when you are unsure.
3. Run AES Text Encryption & Decryption
Start the task and wait for the interface to return its result or a clear setup message.
4. Verify Before You Use It
Test the result in a non-production environment. Never paste passwords, private keys, live access tokens or confidential production data.
Related Developer Tools
View All Developer Tools →Code Secret Scanner
Scan pasted code for patterns resembling exposed API keys, tokens, private keys and credentials.
Scan CodeMIME & File Type Inspector
Inspect local file signature bytes, browser MIME type, extension, size and modification date.
Inspect FileSSH Public Key Fingerprint Viewer
Calculate SHA-256 and legacy MD5 fingerprints from an OpenSSH public key.
View FingerprintJSON Schema Validator
Validate JSON against common schema rules including types, properties, required fields, arrays and patterns.
Validate JSONFrequently Asked Questions
The code, structured data, expression, token, or sample value requested by the interface. Start with a representative input and use only the options needed for your intended result.
A transformed, generated, or diagnostic result for the submitted technical input. Check the result against the original input before using it in a live or important workflow.
Test the result in a non-production environment. Never paste passwords, private keys, live access tokens or confidential production data.
Processing stays in the browser where the individual feature supports it. Live public checks use a protected, rate-limited site endpoint; avoid unnecessary sensitive data.
The page can be used without creating a visitor account. Your browser or device may limit unusually large files or demanding media jobs.
About AES Text Encryption & Decryption
Use AES Text Encryption & Decryption when you need a focused result without installing a separate desktop application. Encrypt or decrypt text locally with AES-GCM and a password-derived key. The result changes when the source data or selected options change, so it is easy to run a second comparison.
What to prepare
The code, structured data, expression, token, or sample value requested by the interface.
What the result represents
A transformed, generated, or diagnostic result for the submitted technical input.
A practical example
For a typical workflow, use it to inspect a small representative sample before applying the same change in a production workflow. Start with a representative input, inspect the first result, then adjust one setting at a time if you need a different outcome.
- Checking data during development with AES Text Encryption & Decryption.
- Preparing a value for testing with AES Text Encryption & Decryption.
- Spotting formatting or validation problems before release with AES Text Encryption & Decryption.
Before you use the result
- Test the result in a non-production environment. Never paste passwords, private keys, live access tokens or confidential production data.
- Check the result against the original input before using it in a live or important workflow.
Privacy and processing
Processing stays in the browser where the individual feature supports it. Live public checks use a protected, rate-limited site endpoint; avoid unnecessary sensitive data.