Convert .env environment files to JSON, YAML, or Docker Compose env format and vice versa.
Environment settings often need to move between tools that expect different representations. This converter turns .env assignments into a JSON object, YAML mapping, or Docker Compose environment form, and can turn supported structured input back into .env lines. It changes the representation, not the configuration's scope or runtime behavior. The main source of surprises is type ambiguity: .env has no universal scalar type system, while JSON and YAML distinguish strings from numbers, booleans, and null values.
A concrete input and expected output from the current implementation.
Input
APP_NAME=demo REGION=us-east
Expected output
{
"APP_NAME": "demo",
"REGION": "us-east"
} In the .env-to-JSON direction, the two assignments become two JSON object members. Both example values are ordinary text, avoiding ambiguity about numeric, boolean, or null-like values.
For straightforward input, each .env variable name corresponds to a target key, and the material assigned after the equals sign corresponds to its value. JSON expresses the result as object members, YAML as mapping entries, and .env as NAME=value lines. The conversion changes delimiters and quoting conventions while retaining the flat key/value relationship.
The Docker Compose target expresses the pairs as environment configuration intended for a Compose service. Reverse conversion reduces a supported JSON, YAML, or Compose mapping to flat .env assignments. Nested objects and arrays have no single equivalent in .env syntax, so a flat mapping of variable names to scalar values is the dependable shape for conversion.
No type guarantee should be inferred from the resulting .env syntax. An assignment records a name and textual value, and the program reading that variable decides whether to interpret it as a number, boolean, or something else. If you convert the result back to JSON or YAML, inspect the displayed quoting and scalar types.
No. The converted result represents environment settings, not a complete Compose project with services, images, networks, volumes, and other required context. Place the environment configuration under the intended service and verify its indentation and surrounding structure. A Compose interpolation .env file, an env_file entry, and a service environment section also serve different roles.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.