Drop any file to identify it
No upload. No signup. No sending your file halfway across the internet.
We tell you what it is, right here in your browser.
Drop it!
Let go to identify this file.
Couldn't identify this file
Need to convert it? fwip it →
You found a .env file in a project directory. It contains environment variables — key-value pairs like `DATABASE_URL=postgres://localhost:5432/myapp` and `API_KEY=sk-abc123`. These are the configuration values that change between development, staging, and production environments, kept separate from code so they can be managed independently.
The .env convention was popularised by the twelve-factor app methodology and tools like dotenv. Most web frameworks (Node.js, Python, Ruby, PHP) have libraries that load .env files automatically on startup. The critical rule: never commit .env files to version control. They contain secrets — API keys, database passwords, OAuth tokens — that should not exist in your git history. Add `.env` to your .gitignore immediately if it's not already there.
Any text editor opens .env files. VS Code with the DotENV extension provides syntax highlighting. If you need to share environment variables with a teammate, use a secrets manager (1Password, Doppler, AWS Secrets Manager) or a secure channel — not email, not Slack, and definitely not a git commit.