Free tool · No account needed

.env.example changed.Don't rebuild your .env.

A release or an AI coding session changed the example again. Stop hunting through two files and copying every key by hand: keep what already works, surface only what is new and export an updated .env.

Free to use. No account. No file uploads.

Your secrets stay with you

  • Your file contents are never uploaded
  • No saved inputs or tracking
  • Offline-ready after the first load

See it in action

Keep 8 values. Fill just 2.

Paste your current .env and the new example. Your configured values carry over together — not the example's placeholders. Only the new, empty fields need your keys.

env-matcher / walkthroughWalkthrough
existing values carried over
2new fields to complete

Keep your whole setup. Focus on what is new.

Only these two still need your keys.

In the real tool, add the missing values during Review before you export. Your eight existing settings are already taken care of.

SEARCH_API_KEYPAYMENT_WEBHOOK
  1. 01Paste your .env
  2. 02Paste the example
  3. 03Review & export

Illustration only. Every credential shown is fictional and cannot authenticate. Your real files stay in the tool below.

Eight existing values, including seven fictional credentials, are preserved unchanged. STRIPE_KEY is on line 3 of the current file, matches line 5 of the example by name, and stays on line 3 of the output. Example placeholders never overwrite configured values. Only two new fields, SEARCH_API_KEY and PAYMENT_WEBHOOK, need values. The saving is manual work, not deleted configuration lines.

✓

Your whole configuration comes along

API keys, passwords and settings: all eight configured values stay. You do not copy each secret into a fresh example by hand.

↔

Matched by name, not by line

Watch STRIPE_KEY travel from line 3 to its match on line 5, then into the updated file. Reordered examples and placeholders do not overwrite your values.

+

Only the new fields need attention

SEARCH_API_KEY and PAYMENT_WEBHOOK stand out in amber. Review the additions, enter the missing keys and export. Less manual work — no configuration thrown away.

Your turn

Bring your own files.

Paste, review, export. You choose which new keys to include; nothing is written back to your project automatically.

  1. 1PasteAdd your files
  2. 2ReviewCheck the changes
  3. 3ExportCopy or download

Step 1 of 3

Add your files

Paste text, drop a file or choose one from your device. Starting fresh? You can leave the current file empty.

Current .env

Your existing non-empty values take priority

New .env.example

The new keys and default values

File contents stay in this tab. Cleared after 15 minutes without activity.

Made for everyday development

A small tool. One less manual check.

On your device

Files are compared in your browser. Their contents never reach our server.

A fresh start every time

Nothing to sign in to. No saved inputs or session history.

Your values come first

Filled current values stay. Empty on both sides stays empty. Example defaults fill empty current entries.

Quick guide

How Env-Matcher works

  1. 1
    Add both files

    Paste or choose your current .env and the new .env.example. You can leave the current file empty to create one from the example. UTF-8 files up to 2 MiB and 10,000 lines are supported.

  2. 2
    Review the result

    Non-empty current values always take priority. If both values are empty, the entry stays empty. If only the example has a value, that value is used. New keys are selected by default; you can skip them or enter a raw value.

    Duplicate example keys must be fixed in the example. For current duplicates, choose the line to keep active; other occurrences are preserved as comments. Values and variable references are never executed or expanded.

  3. 3
    Copy or download

    Choose a layout, generate the result and copy it or download it as .env. Values are hidden until you reveal them. Clear everything when you are done.

To use the tool offline, open it once while connected. You can also install it from your browser's app menu where supported. Updates take effect after all tabs of the app have been closed. Legal documents and cookie settings are available online.

Privacy details

What happens to your secrets?

Env-Matcher by Lilly Systems processes .env contents on your device. Pasting text or choosing a file does not upload its contents. The server only delivers the app and its security headers.

The app has no accounts, tracking, analytics or crash reporting. It does not save your inputs in cookies, browser storage or the offline cache. The offline cache contains only the app itself and its English interface text.

Inputs and generated output are cleared when you leave or reload the page, use Clear everything, or return after 15 minutes without activity. Browser memory management and suspended tabs can delay physical removal from memory.

Loading the app sends ordinary web requests to the hosting provider. Depending on that provider's settings, access logs may contain your IP address, request time and browser information. These requests do not contain your .env contents.

Copying puts the result on your clipboard; downloading saves a file on your device. Clipboard history, downloaded files, browser extensions and other system-level features are outside the app's control.

In addition to serving the comparison tool, the server now retrieves legal documents and consent configuration centrally. Those requests do not include your .env contents or visitor details. Saving cookie settings stores your consent choices on your device for up to 365 days; consent logging is disabled and no random identifier is created. The information above remains available until the full central privacy policy is published.

Read the full privacy policy (opens in a new tab)