Security guide

What Is the Web Crypto API?

Learn how the Web Crypto API supports browser-local random password generation and why it is different from ordinary JavaScript randomness.

Summary

The Web Crypto API is a browser standard for cryptographic operations. For password generation, the most important feature is crypto.getRandomValues(), which gives web pages access to cryptographically strong random values suitable for selecting password characters.

Why it matters for passwords

Passwords need unpredictability. Ordinary JavaScript randomness was not designed for secrets. Web Crypto exists so browsers can expose safer cryptographic primitives through a standard API. PwdGen uses that API for bounded random selection and avoids Math.random() for password generation.

Operating system boundary

Web Crypto does not mean a page controls the hardware entropy source directly. Browsers typically rely on the operating system and platform cryptographic provider. A careful methodology should say that Web Crypto supplies CSPRNG output, not that every call reads physical noise from the CPU.

How PwdGen uses it

PwdGen requests 32-bit random integers, uses rejection sampling to avoid modulo bias, maps accepted values to character indexes, and shuffles required character classes. This keeps the implementation small and auditable.

Detailed guidance

This guide focuses on understanding Web Crypto API as a browser security primitive. It is written for users and developers who want to know why browser randomness matters, so the practical goal is not to create a dramatic security claim. The goal is to choose a password habit that can survive everyday use: sign-in forms, password managers, mobile keyboards, account recovery, shared devices, and the occasional service with strange validation rules. A secure recommendation is only useful if a real person can follow it consistently.

The safest starting point is randomness plus uniqueness. Randomness means the value is selected from a large space by a cryptographically suitable random source, not invented from a birthday, a pet name, a keyboard pattern, or a favorite quote. Uniqueness means the same password is not used anywhere else. A password that is long but reused can fail quickly after one unrelated breach, while a unique random password limits the damage to the single account where it was used.

For this topic, a practical preset is modern Chrome, Edge, Safari, and Firefox with crypto.getRandomValues available. You can apply that preset with the browser support page and then store the final value in a trusted password manager. PwdGen generates values locally in the browser with Web Crypto; the generated password is not sent to a PwdGen server. That local design reduces server-side exposure, but it does not protect against every threat. A malicious browser extension, a compromised device, a phishing page, or unsafe clipboard handling can still expose a secret after it is generated.

The most common problems to avoid are old browsers, insecure contexts, polyfills that silently use Math.random, and confusing encoding with encryption. These problems matter because attackers rarely need to brute-force every possible password when human habits give them a shortcut. Credential stuffing, phishing, leaked password lists, and account-recovery abuse are often more realistic than a pure mathematical search. That is why the best advice combines password quality with account-level controls such as MFA, passkeys, recovery-code storage, and regular review of recovery email or phone settings.

Use this checklist when applying the recommendation:

• Use a modern browser.
• Avoid tools that implement their own random source.
• Understand that Web Crypto does not fix malware.
• Read methodology before trusting a generator.

If a website rejects the ideal setting, do not force the password into a weaker pattern by hand. Adjust one variable at a time. If symbols are rejected, keep uppercase, lowercase, and numbers enabled and increase length. If a maximum length is low, use the largest accepted length and make sure the value is unique. If a password must be read aloud, printed, or typed on a television or router screen, consider excluding confusing characters and increasing the length to compensate for the smaller alphabet.

Finally, remember the boundary of password advice. A strong password is one layer of defense, not a guarantee. It cannot make a phishing page safe, fix malware, or compensate for a service that stores credentials poorly. The useful habit is boring but durable: generate a unique value, store it safely, protect the recovery path, and replace it quickly if you suspect exposure.

A safe next step

After reading this guide, do one small account audit instead of trying to fix everything at once. Pick the account that would cause the most trouble if it were taken over, confirm that its password is unique, and check the recovery email, recovery phone, MFA method, and backup-code storage. If any part of that chain is weak, improve that part before moving to lower-risk accounts. This order keeps the work manageable and protects the accounts that attackers are most likely to use as a stepping stone. For what is the web crypto api?, the best outcome is a repeatable habit: generate locally, store carefully, and avoid reuse.

Frequently asked questions

What part of Web Crypto does PwdGen use?

PwdGen uses crypto.getRandomValues() to request cryptographically strong random values from the browser.

Does Web Crypto mean every byte comes directly from hardware?

No. Browsers generally use operating-system cryptographic providers seeded by high-quality entropy; the browser and OS choose the implementation.

Is Web Crypto available in all browsers?

It is available in modern browsers. If it is missing, PwdGen disables generation instead of falling back to insecure randomness.