Other
.env to netlify.toml
Turn `.env` KEY=value lines into a Netlify `[build.environment]` block.
Local `.env` files are easy to edit; Netlify often wants environment variables declared in `netlify.toml` for reproducible builds. Paste your dotenv-style lines and get a snippet you can merge under `[build.environment]`, then deploy with confidence.
Similar tools
Quick links to related utilities—same workflow, different input or output.
- Data formatsYAML to JSONConvert YAML configs and manifests into JSON for tools that only speak JSON.Open
- Data formatsJSON to YAMLConvert JSON into YAML for configs, k8s manifests, and readable diffs.Open
- Data formatsJSON formatterPretty-print or minify JSON for debugging, reviews, and smaller payloads.Open
FAQs
Is this a complete netlify.toml?›
No—it only generates the environment section. Redirects, plugins, and build commands still belong in the rest of your config.
Do you support export and quotes?›
Lines like `export FOO=bar` and common quoting styles are normalized; review output before committing.
Should I commit secrets?›
Prefer Netlify UI or encrypted secrets for production keys; this tool is for shaping text, not securing it.
General
Do these tools send my data to Exemplar’s servers?›
By default, conversion and formatting run entirely in your browser. Nothing is uploaded to Exemplar for normal paste-and-transform workflows. Tools that deliberately open an external service (for example, a third-party speed test) are called out on the page.
Do I need an account or install anything?›
No account is required. Everything runs in the browser—there is nothing to install for these utilities. They complement the Exemplar platform but work standalone.
Are these utilities open-source or the same as other sites?›
These pages are built for Exemplar’s audience (developers working with APIs, config, and ops data). Behavior may differ slightly from other online tools; always verify critical output in your own environment.
Are there size or performance limits?›
Very large inputs can slow down or crash the tab—especially for images, huge JSON, or multi‑MB HAR files. For production-scale data, prefer local CLI tools, streaming parsers, or your own pipelines.
Can I use output in production?›
Yes, when you have validated it. Parsers and formatters here aim to be helpful for everyday tasks but are not a substitute for tests, schema validation, or security review where it matters.
Where can I read more about privacy?›
See our Privacy policy at /privacy for how exemplar.dev handles site analytics and general data practices.