Is my environment dump uploaded anywhere?
No. It is parsed in this tab, held only in memory, and wiped when you leave. You can confirm it in the Network tab.
Share the shape, not the secrets.
Paste the output of env, printenv, export -p, or docker inspect. Get a copy with every password, token, key, and URL credential redacted, a safe print that lists keys and value types without a single value, and a diff between two environments.
Loading the toolbox.
You do not have to take our word that your environment values stays here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
F12, or Cmd+Option+I on a Mac, and select the Network tab.Only two things can add a line to that log, and neither carries your environment values. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint, so a coding mistake could not quietly send your environment values elsewhere.
When something breaks in a container, a CI job, or a server, the first thing a helper asks for is the environment. Running env or docker inspect and pasting the output into a ticket, a chat, or a forum post is the fastest way to answer, and also one of the most common ways that database passwords, cloud keys, and API tokens leak. Chat logs and tickets are kept for years and read by many people.
Env dump gives you a version you can share. It keeps every key and every harmless value, such as ports, paths, hostnames, feature flags, and log levels, because those are usually what the helper needs, and replaces the secret values with a placeholder. When you only need to show what is set, the safe print leaves out values altogether.
Each value is checked against several kinds of pattern, and the findings list says which one matched, with the line and column, without showing the value.
postgres://app:password@db:5432/app keeps its shape and becomes postgres://app:[REDACTED]@db:5432/app, and query parameters such as token, key, sig, or X-Amz-Signature are redacted the same way.Some names look secret but are not. PWD and OLDPWD are the working directory, SSH_AUTH_SOCK is a socket path, a name ending in _PATH, _FILE, or _TTL describes a secret instead of holding one, and a secret-named key whose value is a file path, such as GOOGLE_APPLICATION_CREDENTIALS, points to a file. Those are shown, and the finding explains why. Two pattern lists let you redact extra keys, such as *_ID, or keep public ones visible, such as NEXT_PUBLIC_*.
KEY=value per line. A line without KEY= is read as part of the multi-line value above it, and the findings say so.'it'\''s' style single quotes and multi-line double-quoted values, and declare -x NAME without a value is kept as declared.docker inspect <container> is searched for Config.Env. When several containers are pasted, the first is used and the page says so."KEY=value" strings, a Kubernetes env: list of name and value pairs, where valueFrom references are listed without a value, or a flat JSON object.Every problem is reported with a line and column, the way .env reports a .env file: invalid JSON, a line without an equals sign, a key with a space or a dash that a shell cannot read, an unclosed quote, and duplicate keys.
Safe print lists every key with the type of its value and nothing else: no values, no lengths, no partial characters. A line looks like DATABASE_URL <URL with credentials> [secret] or PORT <number>. The types are URL, URL with credentials, path, path list, number, boolean, email address, host and port, UUID, hash or commit id, JSON, empty, text, and the secret kinds above.
It answers the most common debugging questions, such as whether a variable is set, whether it is empty, and whether it is a URL or a path, without revealing anything. It is the safest thing to paste into a public issue.
Paste a second dump into Environment B, for example staging next to production, or the environment before and after a deploy. The diff lists keys that were added, keys that were removed, and keys whose value changed. Values are compared in this tab's memory and never displayed. Instead, each changed key shows whether its value type stayed the same or changed, such as REDIS_URL class changed: URL -> empty.
A type change is often the bug itself: a URL that became empty, a number that became text, or a secret that disappeared. The diff is plain text with +, -, and ~ markers, so it can be copied straight into a ticket.
An environment dump is about as sensitive as text gets, so Env dump follows the same rules as TOTP and .env: no analytics events of any kind, input masked on screen by default with a reveal toggle, password managers and spellcheck switched off, everything held only in this tab's memory, and an automatic wipe when you leave the tab, switch tools, or stop interacting for five minutes. Redaction is pattern-based and cannot know every secret, so read the sanitized output before you share it.
Elsewhere in the toolbox: UUID, .gitignore, CSP, .htaccess, and more on the 2toolbox home page. Part of the 2suite.io privacy-first ecosystem.
No. It is parsed in this tab, held only in memory, and wiped when you leave. You can confirm it in the Network tab.
Yes. It catches key names, known token shapes, URL credentials, and random-looking strings, but a secret stored as an ordinary word under a harmless name can slip through. Read the output before sharing.
It shows which keys changed and whether the value type changed, never the values themselves.
In a shell, PWD and OLDPWD hold the current and previous working directory, not a password, so they are shown.