Try it

Output target

Presets (comma separated)

node, postgres, redis, s3, smtp, web.

Custom keys (one per line)

File: .env.example
Keys: NODE_ENV, PORT, LOG_LEVEL
Secret keys (placeholder values): none
Content: # Generated in the browser — review this file and adapt it to your project before committing. # Secret values below are placeholders. Store real values in a secret manager, # never commit them to version control. NODE_ENV=production PORT=3000 LOG_LEVEL=info

# Generated in the browser — review this file and adapt it to your project before committing.
# Secret values below are placeholders. Store real values in a secret manager,
# never commit them to version control.
NODE_ENV=production
PORT=3000
LOG_LEVEL=info

Supported formats

Input: text
Output: text

Privacy

Runs entirely in your browser. Your input is never uploaded, stored, or sent to a third party.

Processing: In your browser
Privacy level: Browser only

Generated a dotenv environment file with 10 key(s), 2 of them secret placeholders.

How it works

Collected the selected preset(s): node, postgres.
Merged 1 custom key(s).
Serialized the keys for the chosen target with placeholder values.

Secret values are placeholders; store real values in a secret manager.
No key material is sent anywhere; the file is assembled in this page.

Methodology

Collect the keys for each selected preset in a deterministic order and de-duplicate.
Append custom keys and mark secret keys from the preset metadata.
Serialize for the chosen target with placeholder values and a review header.

Usage

Select the environment presets your service needs.
Add any custom key names, one per line.
Choose the output target and copy the generated file.

Examples

These are examples, not current values: they use fixed inputs, while the interactive tool computes live results in your browser.

Node and PostgreSQL .env

{
  "target": "dotenv",
  "presets": [
    "node",
    "postgres"
  ],
  "customKeys": "FEATURE_FLAG"
}

Example result

{ "filename": ".env.example", "content": "# Generated in the browser — review this file and adapt it to your project before committing.\n# Secret values below are placeholders. Store real values in a secret manager,\n# never commit them to version control.\nNODE_ENV=production\nPORT=3000\nLOG_LEVEL=info\nPOSTGRES_HOST=db.internal\nPOSTGRES_PORT=5432\nPOSTGRES_DB=app\nPOSTGRES_USER=app\nPOSTGRES_PASSWORD=change-me\nDATABASE_URL=postgres://user:password@host:5432/db\nFEATURE_FLAG=change-me\n", "lineCount": 14, "sections": [ "dotenv", "node", "postgres" ], "keys": [ "NODE_ENV", "PORT", "LOG_LEVEL", "POSTGRES_HOST", "POSTGRES_PORT", "POSTGRES_DB", "POSTGRES_USER", "POSTGRES_PASSWORD", "DATABASE_URL", "FEATURE_FLAG" ], "secrets": [ "POSTGRES_PASSWORD", "DATABASE_URL" ] }

Kubernetes ConfigMap

{
  "target": "k8s-configmap",
  "presets": [
    "web"
  ],
  "customKeys": ""
}

Limitations

Placeholders, not secrets

Every value the generator writes is a documented placeholder: real host names and ports where they are harmless, and `change-me` for anything secret. The file is safe to commit as an example.

Frequently asked questions

Are real secrets generated?: No. Secret keys always receive the placeholder `change-me`; the file warns you to store real values in a secret manager.
Why are secret keys missing from the ConfigMap?: A Kubernetes ConfigMap is not for secrets, so the ConfigMap target lists only non-secret keys and tells you to generate a Secret for the rest.

Sources

Kubernetes Secrets — CNCF
dotenv — dotenv project

Send feedback

Tell us if this tool helped, report a problem, or suggest a tool. Only the message you type is sent — never the input you used in the tool.

Was this tool useful?

Prefer to write to us directly? See the contact page.