Benchmark WebCrypto API encryption and hashing performance in your browser across different algorithms and key sizes.
Encryption Benchmark provides a local performance check for the encryption and digest algorithms and key sizes exposed in its controls. It runs the chosen Web Crypto workload in the active browser and presents timing results for that environment. The result describes this device, browser version, and test configuration, not cryptography in general. The common mistake is treating the fastest result as the best security choice. Speed and suitability are separate questions, and hashing results are not directly comparable with encryption results.
A benchmark run applies the selected Web Crypto operation to test data inside the current browser and records the resulting duration. Algorithm and key-size selections apply only where Web Crypto defines them; digest choices do not have encryption key sizes. Because the work remains local to the page, the test data used for the run is not uploaded.
Read each timing as a measurement of one configured workload on one browser and device. For a useful comparison, keep the operation, input length, run settings, and surrounding conditions unchanged while varying only the algorithm or key size of interest. Repeating the same configuration helps reveal normal timing spread caused by scheduling, warm-up, and other activity.
Browser timing is affected by concurrent work, operating-system scheduling, power management, thermal conditions, and whether related code has already run during the session. Small differences between runs are therefore expected. Repeat an unchanged configuration several times and compare its overall range rather than treating the fastest isolated measurement as the normal result.
No. The result answers a performance question for the measured environment only. Algorithm choice also depends on the protocol being implemented, required security properties, interoperability, key handling, and the distinction between encryption and hashing. Use the benchmark after identifying acceptable configurations, not as a substitute for that security decision.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.