What is the .env file format?

A .env file is a plain text file of KEY=value lines, one per line, with UPPER_SNAKE_CASE keys by convention. Lines starting with # are comments, and values containing spaces are typically wrapped in double quotes. This tool follows those rules.

Are the secret values real?

No. Every secret, API key, and password is randomly generated fake data with no connection to any real service. They are safe to commit to documentation, but you should never use generated secrets in production.

When should I use placeholder style?

Use placeholder style to produce an .env.example file for a repository. It keeps the variable names but replaces values with markers like your-api-key-here, so contributors know what to fill in without leaking real credentials.

Why are some values quoted?

Values that contain spaces or special characters are wrapped in double quotes so dotenv parsers read them as a single value. Simple values without spaces are left unquoted, matching common dotenv conventions and keeping the file readable.

Mock .env File Generator

Almost every project needs a .env file, and almost every onboarding guide includes an example one. Writing realistic environment variables by hand is repetitive, and accidentally pasting a real secret into documentation is a security risk. This tool generates a .env file full of correctly formatted, plausibly named variables with safe fake values.

How it works

The generator assembles lines in the standard dotenv format: KEY=value, one per line, with UPPER_SNAKE_CASE keys and # comment headers grouping related variables. You choose which groups to include (database, auth and secrets, third-party APIs, app settings) and a value style.

In realistic mode, each variable gets a fake-but-plausible value: DATABASE_URL is a well-formed Postgres connection string, secrets are random hex or base64-like tokens generated in your browser, ports are numeric, and feature flags are true/false. Values containing spaces are wrapped in double quotes so dotenv parsers read them correctly. In placeholder mode, values become markers like your-api-key-here, producing an .env.example template suitable for committing to a repository.

Tips and notes

Use placeholder mode for .env.example files you check into version control; never commit real secrets.
The generated secrets are random fake values, fine for tests and docs but never for production.
Quoting is applied only to values with spaces or special characters, matching common dotenv behaviour.
Pair this with a .gitignore entry for .env so filled-in local files stay out of your repository.