YAML/JSON5 Config Validator
Format Comparison
YAML
- • Human-readable, minimal syntax
- • Comments with #
- • No quotes needed for most strings
- • Indentation-based structure
- • Best for: Config files, CI/CD
JSON5
- • JSON with comments (// and /* */)
- • Trailing commas allowed
- • Unquoted object keys
- • Single or double quotes
- • Best for: OpenClaw configs
JSON
- • Strict, standardized format
- • No comments
- • All keys must be quoted
- • No trailing commas
- • Best for: APIs, data exchange
Related tools: YAML ↔ JSON Converter • TOML Editor
What This Tool Does
YAML/JSON5 Config Validator is built for deterministic developer and agent workflows.
Validate YAML, JSON5, and JSON configs with instant error detection, line-by-line feedback, and format conversion. Perfect for OpenClaw, skills, and config files.
Use How to Use for execution steps and FAQ for constraints, policies, and edge cases.
Last updated:
This tool is provided as-is for convenience. Output should be verified before use in any production or critical context.
Agent Invocation
Best Path For Builders
Browser workflow
Runs instantly in the browser with private local processing and copy/export-ready output.
Browser Workflow
This tool is optimized for instant in-browser execution with local data handling. Run it here and copy/export the output directly.
/config-validator/
For automation planning, fetch the canonical contract at /api/tool/config-validator.json.
How to Use YAML/JSON5 Config Validator
- 1
Choose config format
Select YAML, JSON, or JSON5 format. The tool auto-detects format when you paste, or you manually choose from dropdown.
- 2
Paste your config file
Copy your config (docker-compose.yml, app.json, .eslintrc, tsconfig.json, etc.) into the textarea. Syntax highlighting shows structure instantly.
- 3
Validate syntax
Click 'Validate' to check for parse errors, duplicate keys, and format-specific rules. Shows line numbers for quick fixing.
- 4
Check against schema
Optionally paste a JSON Schema to validate values (e.g., port must be 1-65535, loglevel must be 'info' or 'debug').
- 5
Export clean config
Download the validated config, optionally minified or expanded. Convert between YAML and JSON if needed.