YAML Unflattener

Paste a JSON object of flattened paths and values, reconstruct the nested data structure, and serialize YAML locally.

Flattened path/value JSON

Rebuilt YAML

ReadyInput must be a JSON object whose keys use this tool's reversible bracket-style flattened path syntax.

Before using the YAML

Parse first, then choose a target format whose data model matches the job. Conversion success does not prove that an application will accept the resulting config.

Format / validateConfirm the YAML parses before migration.

Inspect structureCheck mappings, arrays, paths and scalar types.

Choose target modelTOML has tables; Properties and ENV are fundamentally string-key/value formats.

ConvertUse explicit flattening/type rules rather than hidden guesses.

Verify in contextReview application-specific schema and semantics before replacing production config.

Format Validate Tree Find path YAML → JSON JSON → YAML YAML → XML XML → YAML YAML → TOML TOML → YAML YAML → Properties Properties → YAML YAML → ENV

conversions run in the browser. The new TOML path targets common configuration syntax rather than claiming a complete TOML conformance suite; Properties nesting is an explicit WebToolArc convention, not part of Java Properties itself.

Common dot/bracket path bridge

The original reversible bracket syntax remains available above. This bridge accepts common path=value lines such as app.name=WebToolArc and app.ports[0]=8080, detects path collisions, and converts them into the core reversible flat-object format before rebuilding YAML.

Input path syntaxScalar parsingPath/value lines

—Paths

—Array indexes

—Collisions

—Bridge status

Ready.

Use one path=value pair per line. Colliding scalar/container paths are rejected instead of silently overwriting data.

Before converting YAML

Format and validate first, inspect the parsed structure, then convert only after deciding how the target format should represent arrays, nested mappings and scalar types.

Syntax is not application validity

A YAML document can parse successfully and still be invalid for Kubernetes, Docker Compose, GitHub Actions, CI/CD, OpenAPI or another application schema.