Skip to tool

MIYAIP TOOLS

YAML Validator

Find syntax errors and duplicate mapping keys before a configuration file reaches your application. Paste YAML or open a UTF-8 file, then inspect the document number, line and column for each error.

YAML input and validation result

Your input is processed locally in this browser.

YAML 1.2 core · UTF-8 files · 200,000 characters

Results

Enter input or load an example.

Find duplicate keys instead of losing a setting

This configuration assigns region twice:

service: catalog-collector
region: us
retries: 3
region: de

The report points to line 4, column 1: “Map keys must be unique.” Remove the unwanted key or give the two values different names. Do not rely on one parser keeping the first value and another keeping the last.

A missing closing bracket, an invalid indentation level or a malformed mapping can produce a different location. Start at the first reported error, fix it and validate again; later messages may depend on the same mistake.

YAML validator showing a duplicate region mapping key at line 4, column 1.
A duplicate region key is reported at line 4, column 1. The input is fictional example data.

Understand a valid result

Valid YAML means the text can be parsed with the selected YAML rules. It does not establish that a deployment, proxy client or scraping application accepts its settings.

Check Included here
YAML syntax and duplicate mapping keys Yes
Multiple YAML documents Yes, with document numbers
Parser warnings Shown separately from syntax errors
Required application fields and allowed values Use the application's own schema or checker
Proxy connectivity, credentials and exit IP Use the client and network tools

For example, follow_redirects: false contains a boolean. A syntactically valid follow_redirects: maybe contains a string and may be rejected by the consuming application. YAML 1.2 also treats plain yes as a string; applications using another schema may behave differently.

Keep comments when you only need a syntax check

Validation does not rewrite your input. Comments and formatting stay in the editor. The downloaded report contains the findings, rather than a reformatted configuration file.

If you convert YAML to JSON, comments, anchors and presentation choices cannot all survive the conversion. Keep the original configuration as the editable source, and use the converted data for a consumer that actually requires JSON.

FAQ

Frequently asked questions

Is this a schema validator?

It checks YAML syntax, not Kubernetes, Docker Compose, Clash or another application's schema. Run the corresponding application check after fixing YAML errors.

Can valid YAML contain custom tags?

Some tags can produce warnings under the core schema. Review the warning and confirm how the target application handles the tag. A valid syntax result is not proof that the tag has the intended meaning.

Does validation test a proxy connection?

No network request is made from this workbench. After loading the configuration into your client, use What Is My IP or the proxy documentation to check the actual connection.

Continue with MIYAIP

Use the resulting data with the intended client or check the connection from the environment where it will run.

Verify the configured proxy connection