Now with secret detection

Your .env
finally explained

Drop in your .env file. Get descriptions, formats, and sources for every variable. No more asking the guy who left.

Free to use • No signup required

1# PostgreSQL connection string
2# Source: Supabase Dashboard → Settings → Database
3# required
4DATABASE_URL=postgresql://...
5# Stripe API secret key for server-side operations
6# Source: Stripe Dashboard → Developers → API keys
7# required secret
8STRIPE_SECRET_KEY=sk_live_...
9# Public API base URL (exposed to browser)
10# Source: Your API deployment URL
11# required
12NEXT_PUBLIC_API_URL=https://api.example.com
13# SendGrid API key for transactional emails
14# Source: SendGrid → Settings → API Keys
15#optional secret
16SENDGRID_API_KEY=SG...
17# AWS IAM access key ID
18# Source: AWS Console → IAM → Security credentials
19# required secret
20AWS_ACCESS_KEY_ID=AKIA...
21# AWS IAM secret access key
22# Source: AWS Console → IAM → Security credentials
23# required secret
24AWS_SECRET_ACCESS_KEY=wJalr...
25# Redis connection URL for caching
26# Source: Upstash Dashboard → Database → Details
27#optional
28REDIS_URL=redis://...
29# Secret key for signing JWT tokens (min 32 chars)
30# Source: Generate with: openssl rand -base64 32
31# required secret
32JWT_SECRET=your-secret

// features

Everything you need to document .env files

Smart Inference

Automatically detects variable purpose from naming conventions and common patterns.

Secret Detection

Flags API keys, tokens, and credentials so you never accidentally commit them.

CLI & Web

Use the web app for quick checks or integrate the CLI into your workflow.

Markdown Export

Generate a README-ready table documenting all your environment variables.

Instant Results

No account needed. Paste, process, copy. Your .env never leaves your browser.

Privacy First

All processing happens client-side. We never see or store your secrets.

// how it works

Three steps to documented env files

Drop your .env

Paste your .env or .env.example contents, or drag and drop the file directly.

DATABASE_URL=
STRIPE_SECRET_KEY=
NEXT_PUBLIC_API_URL=

We analyze it

Our parser identifies each variable, infers its purpose, and detects secrets.

analyzing...
→ DATABASE_URL: connection string
→ STRIPE_SECRET_KEY: 🔴 secret
→ NEXT_PUBLIC_API_URL: public

Get documentation

Copy the documented version or export as markdown for your README.

# PostgreSQL connection string
# Source: Supabase Dashboard
DATABASE_URL=postgresql://...

// cli

Works where you work

Integrate into your CI/CD pipeline or run locally. Zero config.

terminal

Document your .env

$ npx dotscribe@latest

Analyze .env in current directory

Output to file

$ npx dotscribe@latest -o .env.documented

Save documented version to a file

Generate README table

$ npx dotscribe@latest --markdown

Output as markdown table for docs

Strict mode

$ npx dotscribe@latest --strict

Fail if secrets detected without .gitignore

Stop explaining .env files

Your new contributors will thank you. Your future self will thank you.

> It's free. It's fast. It works offline.

Your .envfinally explained