TOML to JSON Converter

• Converts TOML [tables] to JSON objects, [[arrays of tables]] to JSON arrays, and inline tables to nested structures
• Preserves all TOML data types: strings, integers, floats, booleans, offset datetimes, local datetimes, and local dates
• Supports pyproject.toml, Cargo.toml, Hugo config.toml, Netlify netlify.toml, and all TOML v1.0 files
• JSON output is formatted with 2-space indentation for maximum readability
• 100% client-side processing — configuration data never leaves your browser

Use Cases

Frequently Asked Questions

How do I convert pyproject.toml to JSON for programmatic access?

Paste the contents of your pyproject.toml file into the TOML input panel. The converter transforms all sections — [project], [build-system], [tool.black], [tool.pytest.ini_options], and other tool-specific tables — into a nested JSON object. Copy the JSON output for use in Node.js build scripts, CI/CD pipeline configurations, or any application that consumes JSON configuration data.

Can I convert Cargo.toml Rust package manifests to JSON?

Yes. Paste your Cargo.toml content and the converter maps [package], [dependencies], [dev-dependencies], [features], and [profile] sections into JSON objects. This is useful for dependency auditing tools, cross-language build systems, and migration scripts that need to read Rust package configuration in JSON format.

Does the converter handle TOML arrays of tables ([[double brackets]])?

Yes. TOML arrays of tables (defined with [[double.bracket.headers]]) are correctly converted to JSON arrays of objects. For example, [[tool.poetry.dependencies]] entries become a JSON array where each element is an object representing one dependency entry with all its key-value pairs preserved.

How are TOML datetime values represented in the JSON output?

TOML supports four datetime types: offset datetime (2026-03-06T10:30:00-05:00), local datetime (2026-03-06T10:30:00), local date (2026-03-06), and local time (10:30:00). All datetime values are converted to ISO 8601 string representations in JSON, since JSON has no native datetime type. Your consuming application should parse these strings using appropriate date libraries.

Can I convert JSON configuration files back to TOML format?

Yes. The converter supports bidirectional conversion. Paste JSON in the JSON panel and get clean TOML output with proper [table] headers, key-value formatting, and correct data type representation. This is useful for creating new TOML config files from existing JSON settings or migrating JSON-based configuration to TOML-based tooling.

Is my TOML configuration data sent to a server during conversion?

No. All TOML parsing and JSON serialization happens entirely in your browser using client-side JavaScript. Your configuration data — including dependency versions, API endpoints, database settings, and any sensitive values — never leaves your machine. This makes the tool safe for converting production configuration files.

What TOML features are supported by this converter?

The converter supports the full TOML v1.0 specification: standard tables, inline tables, arrays of tables, dotted keys, bare keys, quoted keys, multi-line basic strings, multi-line literal strings, integers (decimal, hex, octal, binary), floats (including inf and nan), booleans, offset datetimes, local datetimes, local dates, local times, arrays, and comments (stripped during conversion since JSON does not support comments).