Drop any file to identify it
No upload. No signup. No sending your file halfway across the internet.
We tell you what it is, right here in your browser.
Drop it!
Let go to identify this file.
Couldn't identify this file
Need to convert it? fwip it →
You're editing a configuration file. It uses indentation instead of curly braces, has no commas, and looks almost like a plain-text outline. That's YAML — the format that won the DevOps world by being easier to read than JSON or XML. At least until a whitespace error breaks your entire deployment.
YAML is the de facto standard for infrastructure configuration: Docker Compose files, Kubernetes manifests, GitHub Actions workflows, Ansible playbooks, and CI/CD pipelines are all YAML. The format is deceptively powerful — it supports references, anchors, multi-line strings, and complex nested structures. It's also deceptively fragile. Indentation is syntactic, and YAML uses spaces only (not tabs). A single misaligned key can cause a silent misconfiguration or a noisy failure.
Any text editor opens YAML. VS Code with the YAML extension provides schema validation, which catches indentation errors before they reach production. For learning the format, the official spec is surprisingly readable. The practical rule: copy a working example, modify it carefully, and never mix tabs and spaces.