HTML Formatter
Beautify and indent HTML markup.
OpenFlatten a nested YAML config into KEY=value lines you can drop into a .env file.
Use a settings map of simple values, without lists.
Parent and child keys join with underscores in uppercase.
Add quotes to values with spaces, # or $ characters.
Copy the lines or download them as a .env file.
Your app's settings live in a nested YAML file, but the container platform or CI runner you deploy to wants environment variables. Typing APP_DATABASE_HOST and its siblings by hand is slow and easy to get wrong.
Paste YAML and each scalar setting becomes one line. Keys are uppercased and nested keys are joined to their parents with underscores, so an app map containing name: toolkit and port: 3000 becomes APP_NAME=toolkit and APP_PORT=3000. Booleans and numbers are written as text, quotes around YAML strings are removed, and the output updates live. Download saves it as a file named .env.
Values are written exactly as they are, without quoting or escaping. A value containing spaces, # or $ should be wrapped in quotes before you load the file, or the shell and many dotenv parsers will cut it short. The converter uses a small built-in YAML reader that handles nested maps of simple values: list entries are not read, a comment after a value stays attached to it, and keys with dashes produce variable names with dashes, which most shells reject. If you need arrays, paste the config as JSON instead and each array becomes a comma-joined value. Check the result with the .env validator, and to see how the YAML is structured first, convert it to JSON.
Conversion happens in the page with no library download, which is reassuring when the config holds database passwords or API keys.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
Each level is uppercased and joined with an underscore. A host key under primary under database becomes DATABASE_PRIMARY_HOST.
No. Values are copied as they are. Add quotes yourself for values with spaces, # or $, or anything else your dotenv loader might interpret.
There is no prefix option. Nest your YAML under a top-level key such as myapp: and indent the rest beneath it; every variable will then start with MYAPP_.