Convert TOML to ENV

Nested TOML sections are flattened using underscores. For example, [database.connection] becomes DATABASE_CONNECTION_ prefix for all variables in that section.

Yes, TOML arrays are converted to comma-separated strings in ENV format. Array items are automatically quoted if they contain spaces or special characters.

Yes, comments from the TOML file are preserved in the ENV output using the # symbol, maintaining your documentation and notes.

Absolutely. This is perfect for Rust projects where you need to extract package metadata, version numbers, or build configuration from Cargo.toml for CI/CD automation.

Booleans become 'true'/'false' strings, numbers are preserved as-is, and strings are properly quoted if needed. All ENV values are strings as per standard.

Yes, the ENV output follows Docker Compose .env file format standards. You can use the converted file directly with docker-compose up.

Yes, this works great for Python projects. Convert pyproject.toml build settings, dependencies, or metadata to ENV format for automated deployment pipelines.

No. All conversion happens locally in your browser using JavaScript. Your TOML configuration files never leave your device.

Special characters are properly escaped and values are quoted when necessary. This ensures the ENV file works correctly across different shells and environments.

Yes, the converted ENV format works perfectly with Kubernetes ConfigMaps and environment variable injection for containerized applications.

Yes, inline tables are converted to flattened ENV variables with appropriate naming. For example, database = {host = 'localhost'} becomes DATABASE_HOST=localhost.

While ENV to TOML conversion is possible, some information may be lost due to ENV's flat structure and string-only values. TOML's data types and hierarchy cannot be perfectly reconstructed.