How the Web Cryptography API Enables Secure In-Browser Hashing and Encryption

Why Pure JavaScript Crypto Libraries Were Flawed#

JavaScript engines are optimized for dynamic scripting, not cryptographic bitwise math. Pure JavaScript crypto libraries suffered from three fundamental weaknesses:

• Timing Attacks: Variable-time loop execution in JavaScript JIT compilers leaked secret key information through micro-architectural CPU caches.
• Poor Entropy: Standard `Math.random()` is a pseudo-random number generator (PRNG) that is completely predictable and cryptographically insecure.
• Performance Bottlenecks: Computing SHA-256 over a 100MB file in userland JavaScript took seconds and froze the browser UI.

The SubtleCrypto Interface and Native Speed#

The `crypto.subtle` interface delegates operations directly to the underlying operating system’s cryptographic libraries (such as OpenSSL, Apple CommonCrypto, or Windows CNG) and leverages CPU hardware instructions (such as Intel AES-NI and ARMv8 Cryptography Extensions).

This provides constant-time execution resistant to timing attacks and speeds up hashing and encryption by 50x to 100x compared to pure JavaScript.

Hardware-Accelerated SHA-256 Hashing in 5 Lines#

Generating a cryptographic hash with the Web Crypto API is clean, modern, and asynchronous:

async function sha256(message: string): Promise<string> {
  const msgBuffer = new TextEncoder().encode(message);
  const hashBuffer = await crypto.subtle.digest('SHA-256', msgBuffer);
  const hashArray = Array.from(new Uint8Array(hashBuffer));
  return hashArray.map(b => b.toString(16).padStart(2, '0')).join('');
}

Authenticated Symmetric Encryption with AES-GCM#

AES-GCM (Galois/Counter Mode) provides authenticated encryption, guaranteeing both data confidentiality (encryption) and data integrity (tamper-proofing).

If an attacker modifies even a single byte of the encrypted ciphertext, the decryption operation throws an integrity exception and rejects the payload.

Secure Key Generation and Non-Exportable Keys#

The Web Crypto API allows developers to generate cryptographic keys with `extractable: false`. Non-extractable keys live inside browser memory buffers that cannot be accessed by external scripts, protecting them against XSS data exfiltration.