Convertidor TOML
Convertir entre formatos TOML, JSON y YAML
Siguientes pasos sugeridos
Herramientas Relacionadas
JSON ↔ YAML
Convertir entre formatos JSON y YAML
Convertidor de JSON a CSV
Convertir arreglos JSON a formato CSV y descargar
Formateador JSON
Embellece, minimiza y valida datos JSON
Formateador SQL
Formatear y embellecer consultas SQL
Minificador CSS/JS
Minificar y embellecer código CSS y JavaScript
Formateador XML
Formatear, embellecer y minificar datos XML
Cómo Usar
Pega o Escribe
Ingresa tu texto, código o datos en el área de entrada.
Elige las Opciones
Selecciona la transformación o formato que deseas aplicar.
Copia el Resultado
Copia la salida a tu portapapeles con un solo clic.
Por Qué Usar Esta Herramienta
100% Gratis
Sin costos ocultos, sin niveles premium — todas las funciones son gratuitas.
Sin Instalación
Se ejecuta completamente en tu navegador. No necesitas descargar ni instalar nada.
Privado y Seguro
Tus datos nunca salen de tu dispositivo. Nada se sube a ningún servidor.
Funciona en Móvil
Totalmente responsivo — úsalo en tu teléfono, tableta o escritorio.
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
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.
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.
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.
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.