Free2BoxFree2Box

TOMLコンバーター

TOML、JSON、YAML形式間の変換

入力 (TOML)
Paste TOML content to convert
出力 (JSON)
変換結果がここに表示されます...

使い方

1

テキストを貼り付けまたは入力

テキスト、コード、またはデータを入力エリアに入力します。

2

オプションを選択

適用する変換やフォーマットを選択します。

3

結果をコピー

ワンクリックで出力をクリップボードにコピーします。

このツールを使う理由

完全無料

隠れたコストもプレミアムプランもありません — すべての機能が無料です。

インストール不要

すべてブラウザで実行されます。ソフトウェアのダウンロードやインストールは不要です。

プライベート&安全

データはデバイスの外に出ることはありません。サーバーにアップロードされることはありません。

モバイル対応

完全レスポンシブ対応 — スマートフォン、タブレット、デスクトップで利用できます。

TOML: Tom's Obvious Minimal Language for Configuration

Key Takeaways

  • TOML is designed to be unambiguous and easy to read, with explicit typing for strings, integers, floats, booleans, dates, arrays, and tables.
  • TOML is the standard configuration format for Rust (Cargo.toml), Python (pyproject.toml), and many modern tools.
  • All conversion between TOML and JSON happens in your browser — your configuration data stays private.

TOML (Tom's Obvious Minimal Language) was created to be a minimal, unambiguous configuration file format that maps clearly to a hash table. Unlike YAML, which has complex features and implicit type coercion pitfalls, TOML aims for simplicity and explicit semantics. It has been adopted as the standard config format by Rust's Cargo, Python's pyproject.toml, and many other modern tools.

TOML is the official configuration format for over 150,000 Rust crates on crates.io.

Ecosystem Adoption

Key Concepts

1

Tables and Nested Tables

TOML uses [table] headers to define sections and [table.subtable] for nesting. This maps directly to JSON objects and makes configuration hierarchy immediately visible.

2

Explicit Type System

Unlike YAML where 'yes' becomes a boolean, TOML has unambiguous types: strings always use quotes, integers never have quotes, and dates follow RFC 3339 format.

3

Array of Tables

The [[array]] syntax creates arrays of tables (equivalent to JSON arrays of objects), enabling lists of structured configuration entries like multiple server definitions.

4

TOML vs. YAML vs. JSON

TOML trades YAML's flexibility for unambiguity and simplicity. It lacks YAML's anchors and aliases but avoids its pitfalls. JSON lacks comments and has more verbose syntax. TOML occupies the sweet spot.

Pro Tips

Use inline tables { key = 'value' } sparingly — they are best for small, single-line groupings.

TOML supports multi-line strings with triple quotes and literal strings with single quotes (no escape processing).

When converting JSON to TOML, deeply nested objects become long dotted table names — consider restructuring for readability.

TOML native date/time types (RFC 3339) are converted to strings in JSON — ensure your application handles the conversion correctly.

All TOML/JSON conversion is performed entirely in your browser. Your configuration data is never transmitted to any external server.

よくある質問