.env ↔ Azure Converter

How to convert environment variables to Azure and back

In Azure App Service, application settings can be edited in bulk as a JSON list of objects with name, value and slotSetting. In local development, the same variables live in a .env file with KEY=value lines. This tool converts between the two formats and can also merge a new .env into an existing configuration.

1. Choose the tab: .env → Azure JSON, Azure JSON → .env or Update Azure.
2. Paste the content into the input box. The conversion happens as you type and also through the convert button.
3. When converting to Azure, choose the slotSetting value (false by default). It defines whether the variable is "stuck" to the deployment slot.
4. Check the variable counter, then use Copy or Export. The downloaded files are named azure-app-settings.json, .env and azure-app-settings-updated.json.

What each mode does

• .env → Azure JSON: ignores empty lines and comments (#), splits key and value at the first equals sign and removes single or double quotes wrapping the value.
• Azure JSON → .env: reads the JSON list and generates NAME=value lines. Variables marked as slot settings get a comment saying so.
• Update Azure: takes the current JSON and a new .env. Existing variables get their value updated, new ones are added and those that exist only in Azure are kept. The tool shows how many were new, updated and kept.

Practical examples

• Deploying a new project: convert the local .env to JSON and paste it into the advanced settings editor of the app in the Azure portal, instead of creating each variable by hand.
• Bringing production to your local machine: export the Azure settings as JSON and convert them to .env to reproduce the environment in development.
• Updating without deleting: you changed three variables in the .env and want to send them without losing the other 20 already configured. The "Update Azure" mode preserves the rest.

Precautions

• The converter reads one variable per line; it does not interpret multi-line values or comments at the end of a line. Review the result before applying it in production.
• Environment variables often contain passwords and keys. Prefer using test values or removing secrets before pasting.

Privacy and how it works

The conversion and the merge are done entirely in your browser, with JavaScript: what you type or paste is not sent to or saved on any server. Even so, since .env files and Azure settings often contain secrets, prefer using test values or clear the content when you are done, especially on shared computers. The page loads Bootstrap and Font Awesome from public CDNs, which is normal for loading styles and icons. More information in the Privacy Policy.

Frequently asked questions

Other free tools

• 🏷️ SLP Label EditorVisual editor for creating labels with text, barcodes and QR codes
• 📋 ZPL EditorSpecialized editor for ZPL code (Zebra Programming Language)
• 🌐 Is Up - Website CheckerCheck if a website responds from your browser
• 📡 Is Online - Connection CheckerChecks whether your browser can open a connection to Google and Cloudflare and shows the c
• 🌍 Public IP - Find My IPFind your public IP address and copy it in one click
• 📸 Pageres - Screenshot Capture ToolGet an image of a page’s top at widths from 320 to 1920 px and download the file