Why EnvSift stays in your browser
A private, client-side toolkit for comparing, inspecting, formatting, merging, and converting environment files.
Environment files are useful, messy, and often full of values that should not travel any farther than necessary. EnvSift processes pasted values and local files in the browser instead of sending them to a server.
That choice is not a privacy slogan pasted onto the product later. It is the starting constraint.
Six tools, one local workflow
EnvSift currently brings six jobs into one client-side toolkit:
- ENV Compare finds missing or changed variables across two or more files.
- .env.example Generator removes values and creates a safe template.
- ENV Inspector detects invalid lines, duplicate keys, empty values, missing references, and risky whitespace.
- Merge & Clean merges two files with automatic or manual conflict resolution.
- ENV Formatter normalizes quotes and ordering, with optional comment preservation.
- Format Converter converts ENV or flat JSON to ENV, JSON, shell exports, or Docker Compose syntax.
The app uses TanStack Start with statically prerendered routes, React, TypeScript, Tailwind CSS, and shadcn/ui components built on Base UI.
What it is not
EnvSift is released as open-source software under the Apache License 2.0 and is free to use. It is not a hosted secret vault, and we are not pretending future ideas have shipped.
The longer-term question is whether local tooling can help developers understand configuration
contracts and environment health without becoming another service that stores their secrets. For
now, the useful thing comes first: make everyday .env work less error-prone while keeping the
contents on the client.