What is a .ENV file?
A .env file stores environment variables and secrets for an application.
- Did you know
- .env files grew out of the Twelve-Factor App idea of keeping config in environment variables, via tools like Foreman and dotenv.
- The .env convention took off with Heroku’s Foreman tool and the Ruby dotenv gem by Brandon Keepers, then spread to Node.js and most other languages.
- Each line is a simple KEY=value pair loaded into a process at start-up so secrets stay out of the source code.
- What Analyser reads
- Identify configuration and small text files: TOML, INI, .env, CONF, CFG, Java properties, generic .config, info notes, .lst list/index files, and Windows Setup Information (.inf) driver/install scripts.
- Depth of analysis
- .ENV is an identification-grade format: Analyser recognises it from its bytes and decodes the header metadata it carries, rather than opening it in a full viewer. Formats that do get a full viewer are marked "Full" on the formats page.
- Open a .ENV file
- Drag a .ENV file onto the Analyser home page (or tap to pick one). It is identified entirely in your browser - nothing is uploaded, there is no account, and it works offline once installed.
- Related formats
- .TOML · .INI · .CONF · .CFG · .PROPERTIES · .Config · .Info · .LST · .INF. See all supported file types.