Skip to content
Antoine Le LouëtIndependent senior developer (Home)

Tools / Configuration anonymiser

Tools · .env & JSON

Share the structure.
Mask the values.

Prepare a configuration file for a README, a support request or a developer joining the project.

Open the anonymiser

Free · No account needed · Processed on your device

Before / after Entirely fictional example
API_TOKEN="fake_source_token"
APP_URL="https://demo.example.com"
PUBLIC_LABEL="Projet fictif"

↓ All values are replaced

API_TOKEN="XXXXXX"
APP_URL="XXXXXX"
PUBLIC_LABEL="XXXXXX"

Two ways to replace values

Masking
Every string is replaced with XXXXXX, including public and empty variables.
Fictional values
Predefined examples such as user@example.com and https://example.com. Only the key name determines the example; original values are never reused.

What you share

Variable names and JSON keys remain visible. They may reveal a client or internal service: review them before sharing.

Copying and downloading deliberately create a local copy of the result. Downloading does not change any source file.

Supported formats and V1 limits

One line per variable in .env files, with single or double quotes; comments are removed by default. An option preserves comments, blank lines and spacing. Assignments, URLs, emails, IPv4 addresses and known values are masked in comments; review free text because an isolated value may go unrecognised. The # and = characters are accepted in quoted values. Multiline values, interpolation and ambiguous syntax are rejected in active variables.

Strict JSON, with objects and arrays nested up to 64 levels. Keys and types are preserved: strings are replaced, numbers become 0, booleans become false and null stays null. These placeholders do not form a working configuration.

Paste only, up to 100 KiB (102,400 UTF-8 bytes). An error blocks export and clears the previous result. Fields are cleared on reload, when leaving and when returning through browser history.