Skip to content
Docs navigationBrowse tools →

Tool docs

Secure Secret & Random Generator

Browser-local Web Crypto guidance for generated development secrets: what to generate, which encoding to pick, and what not to do with the result.

Tool

Overview

01

Secure Secret & Random Generator

Generate random values — API keys, passwords, salts, nonces, session IDs — directly in your browser with the Web Crypto API. Results are not sent to Birdor, stored in browser history, or included in a shareable URL.

Guide

Common usage patterns

01

Choosing the right output

  • Use 32 random bytes for common session, JWT, webhook, and application secrets.
  • Base64URL is convenient for environment variables and query-safe strings.
  • Hex is useful where a fixed ASCII alphabet is required, such as some config formats.

Guide

Edge cases & common pitfalls

01

Operational cautions

  • Base64 is an encoding, not encryption — anyone can decode it.
  • Kubernetes Secret YAML containing production values must not be committed to Git.
  • CSP nonces must be newly generated for every HTTP response, never reused.