Towalles Towalles

Env Diff

Paste two .env bodies to list added, removed, and changed keys. Great for deploy checks and multi-environment config reviews.

Privacy: processed locally, never uploaded.

↓ Paste in the input area below to see results instantly

Compare two env files and list added, removed, and changed keys.

.env A (left)

.env B (right)

Diff output

Diff output

~ API_URL: http://localhost -> https://api.example.com
~ DEBUG: true -> false
+ NEW=1

Notes

Symbols

+ only in B; - only in A; ~ same key, different value; leading space means unchanged. Lines starting with # are ignored.

Paste two .env bodies to list added, removed, and changed keys. Great for deploy checks and multi-environment config reviews.

Quick start

  1. Paste A and B

    KEY=VALUE format; # comment lines are skipped.

  2. Read diff

    + / - / ~ mark added, removed, and changed keys.

Features and use cases

Diff two .env or KEY=VALUE lists with added/removed/changed highlights and optional comment ignore.

Use when comparing staging vs prod, pre-deploy reviews, and Compose env migrations.

vs JSON Diff

Parses env lines; ideal for .env and compose environment blocks.

Typical Workflow

When migrating configurations between environments (e.g., development, testing, production), .env files often change. To use this tool, paste the old environment content on the left and the new environment content on the right. The tool instantly highlights added variables (green), deleted variables (red), and modified variables (yellow).

Quickly check sensitive variable changes before deployment. For example, database password changes from local development values to production values will be flagged immediately. When collaborating, sharing difference screenshots is safer than sending .env files directly, preventing accidental exposure of unencrypted sensitive data.

Examples

Example

Input

DEBUG=true vs DEBUG=false

FAQ

export KEY= support?

Parses bare KEY=VALUE; strip export prefix manually if needed.

Can it compare non-.env key-value files?

Yes. The tool fundamentally parses key-value structures, so similar config files like config.ini also work. However, comment syntax may vary—lines starting with # are comments in .env but could be valid content in other formats.