Random Config Generator

What it does

The Random Config Generator produces configuration-shaped test data in five formats: environment variables, complete .env file contents, feature flags, HTTP cookies, and session JSON objects. Each format follows its real-world syntax. Generate up to 10,000 items per run, seeded for stable fixtures.

Common use cases

• Config parser testing — .env and environment-variable input with realistic naming and quoting for loaders and validators.
• Feature flag systems — flag sets for testing evaluation logic, rollout UIs, and flag-cleanup tooling.
• Cookie and session handling — realistic cookie strings and session objects for middleware and serialization tests.
• Environment scaffolding — placeholder .env files for demo projects and onboarding docs.

Settings

• Format — env vars, .env file, feature flags, cookies, or session objects.
• Items — 1 to 10,000 entries, exportable as text, JSON, or CSV.
• Seed — the same seed and settings regenerate the identical config.

Privacy note

Everything is generated locally in your browser and never uploaded. All values are synthetic — the “secrets” in a generated .env are placeholders, not credentials, and nothing here grants access to anything.

FAQ

Are the generated secrets real? No — they’re realistic-looking placeholder values. That makes them ideal for testing secret-scanner tooling (does your CI flag them?) and terrible for actual authentication (use the Secure Token Generator for real secrets).

Does the .env output follow real syntax? Yes — assignment, quoting, and naming conventions match what dotenv-style loaders expect, so the fixtures exercise real parsing paths.

Can I test flag-evaluation edge cases? Generate a large flag set — the mix of states exercises default handling, stale-flag detection, and bulk-evaluation performance.