YAML, TOML & .env config tools
Reviewing a config pull request, tracking down why one environment behaves differently from another, or converting a config file into the format a new tool expects — these are the everyday jobs around YAML, TOML and .env files. This page covers formatting, structural diffing, anchor tracing, and conversions between YAML, TOML, JSON, INI, Properties and plist.
YAML formatter and TOML formatter keep your comments and existing structure instead of rewriting the file from scratch, and YAML diff compares documents structurally so reordered keys don't show up as noise. ENV Diff & Missing Keys is built specifically to catch variables present in one .env file but missing from another, and ConfigMap / Secret / ENV turns a plain .env into Kubernetes manifests. All of it runs locally.
15 tools
Format and diff YAML
-
YAML formatter
Reformat YAML while preserving comments, anchors and exact numbers
-
YAML diff
Compare YAML documents by structure while preserving original comments
-
YAML anchor explorer
Trace YAML anchor references and expand aliases with cycle detection
-
JSON to YAML
Transform JSON to YAML preserving exact number types and indentation style
-
YAML to JSON
Convert YAML to JSON preserving root type and controlling anchor expansion
Manage .env files
-
.env editor
Review and edit environment variables in a table with duplicate detection
-
ENV Diff & Missing Keys
Compare .env files by key to find missing variables and changed values
-
.env example generator
Create .env templates by clearing values and selectively preserving keys
-
ENV to JSON
Convert ENV files to JSON with explicit type preservation
-
ConfigMap / Secret / ENV
Convert dotenv and text files into ConfigMap and Secret manifests
YAML / TOML / ENV Config tools FAQ
A naive line-by-line diff flags reordered or re-indented keys as changes even when the data is identical. YAML diff compares documents by structure instead of by text, so it reports only actual value changes and keeps your original comments visible, which makes real changes easier to spot in a review.
Load both files into ENV Diff & Missing Keys. It compares by key rather than by line order, so it lists variables present in one file but not the other along with any values that changed — faster than scanning two files side by side for a typo.
Yes. ConfigMap / Secret / ENV converts dotenv or plain text files directly into ConfigMap and Secret manifests, which saves hand-formatting YAML for each key. For plain format conversion without Kubernetes, Config converter handles INI, Properties and plist instead.