What is the Norway problem in YAML?

In legacy YAML 1.1, tokens like 'y', 'yes', 'true', 'on' were coerced to true, and 'n', 'no', 'false', 'off' were coerced to false. Consequently, an unquoted country code 'NO' (Norway) was mistakenly parsed as the boolean 'false'. To avoid this, always wrap country codes and boolean-like strings in double quotes.

What is the difference between '|' and '>' in multiline YAML?

The pipe character (`|`), known as a literal block scalar, preserves all line breaks and indentation exactly as typed. The greater-than symbol (`>`), known as a folded block scalar, replaces line breaks with single spaces, folding multiple lines into a single continuous paragraph.

What happens to YAML comments (#) during JSON conversion?

The RFC 8259 JSON specification does not support comments. Any inline or block comments present in your source YAML are stripped during conversion to standard JSON. If you must retain comments, consider using the JSONC (JSON with Comments) format.

What do the three hyphens (---) mean in a YAML file?

Triple hyphens represent a Document Start Marker in the YAML specification, allowing developers to define multiple distinct documents within a single stream. This is common in Kubernetes, where a Service and a Deployment are defined together in one manifest file.

Is it safe to validate confidential Kubernetes Secret files here?

Yes, completely safe. OrvoKit's validator and converter executes 100% within your local browser runtime. No data is ever transmitted to an external server or logged to disk, ensuring enterprise infrastructure credentials remain private.

YAML to JSON & JSON to YAML Validator

HOT

Bi-directional YAML and JSON parser with syntax error detection for Kubernetes and Docker files.

ADVERTISEMENT · TOP BANNER

Responsive 728x90 / 320x100 Ad Slot

(CLS Prevention Active · Zero Shift)

100% Client-Side Processing (Zero Server Upload, Complete Privacy)

Interactive Client Mode

YAML Input

JSON Output

{
  "apiVersion": "apps/v1",
  "kind": "Deployment",
  "metadata": {
    "name": "nginx-deployment",
    "labels": {
      "app": "nginx"
    }
  },
  "spec": {
    "replicas": 3,
    "template": {
      "spec": {
        "containers": {
          "containers": [
            "name: nginx"
          ],
          "image": "nginx:1.24",
          "ports": {
            "ports": [
              "containerPort: 80"
            ]
          }
        }
      }
    }
  }
}

ADVERTISEMENT · HIGH CTR IN-FEED

Native In-Feed / High Viewability Ad Slot

(CLS Prevention Active · Zero Shift)

Architecture & Interoperability of YAML and JSON Serialization

YAML (YAML Ain't Markup Language) was conceived in 2001 by Clark Evans, Ingy döt Net, and Oren Ben-Kiki with the goal of creating a human-centric data serialization language. Unlike JSON, which relies heavily on brackets and comma delimiters, or XML with its verbose closing tags, YAML mirrors Python's clean aesthetic by using strict whitespace indentation and newlines to represent hierarchical depth.

In the modern cloud-native ecosystem, YAML has achieved undisputed hegemony as the configuration standard for Kubernetes manifests, Docker Compose services, GitHub Actions CI/CD workflows, and Ansible automation playbooks. However, web browsers, Node.js runtimes, and RESTful APIs cannot natively execute YAML; they require strict JSON trees to ingest and manipulate application state.

OrvoKit's YAML to JSON Validator and Converter immediately pinpoints indentation errors, stray tabs, and missing spaces after colons with visual line alerts. Supporting comments (#) and multiline string scalars (|, >), it performs bidirectional conversions between YAML and JSON in sub-millisecond time—executed 100% locally in your browser to keep deployment manifests confidential.

YAML Indentation Semantics & The JSON Superset Hierarchy

How the YAML 1.2 specification models mapping, sequence, and scalar types alongside JSON compatibility.

YAML Structural Equivalents to JSON GrammarMathematical Formulation

Mapping: key: value ↔ { "key": "value" } Sequence: - item ↔ [ "item" ] Block Scalar: | (Literal newlines) vs > (Folded whitespace)

The official YAML 1.2 specification is a structural superset of JSON: every valid RFC 8259 JSON file is inherently a valid YAML document.

Converting a container port configuration into JSON

YAML Inputapp: web ports: - 80 - 4431 scalar, 1 sequence

Key-Value MappingMap 'app' to string property"app": "web"

Sequence TranslationMap hyphenated ports list to array"ports": [ 80, 443 ]

Synthesize JSON{ "app": "web", "ports": [ 80, 443 ] }Standard RFC 8259 JSON

👉 Indentation-bound hierarchical structures are cleanly mapped to strict bracket-enclosed JSON syntax.

Tab Characters Strictly Forbidden: YAML mandates spaces (standard 2 spaces) for indentation; tab characters trigger immediate fatal parser errors.
Mandatory Trailing Space After Colons: Writing `key:value` treats the token as a single scalar. A trailing space (`key: value`) is required to establish key-value mappings.
Multiline String Handling: Literal block scalar `|` retains line breaks; folded block scalar `>` collapses newlines into single spaces.
The Norway Problem: In legacy YAML 1.1, the unquoted country code `NO` was parsed as the boolean `false`. Modern YAML 1.2 parsers prevent this ambiguity.

YAML vs JSON Syntax Specification Matrix

Comparing structural paradigms between YAML 1.2 and JSON RFC 8259.

Structural Feature	YAML (v1.2)	JSON (RFC 8259)	Implementation Details
Object / Mapping	key: value (2-space indent)	{ "key": "value" }	YAML omits braces, relying strictly on whitespace
Array / Sequence	- item1 - item2	["item1", "item2"]	Hyphen must be followed by a whitespace character
Property Key Quoting	key_name: (Optional)	"key_name": (Mandatory)	JSON strictly enforces double-quoted property keys
Comments	# Comment text	Not Supported (Syntax Error)	YAML supports inline comments; omitted upon JSON export
Multiline Text Blocks	desc: \| Line 1 Line 2	"desc": "Line 1\nLine 2"	Pipe operator preserves literal newlines
Boolean / Null	true / false / null (or ~)	true / false / null	YAML accepts tilde (~) as a synonym for null
Multiple Documents	--- (triple hyphen)	Not Supported (Requires Array)	Separates multiple resources in a single stream

* Native support for comments (#) is the primary reason YAML dominates DevOps and infrastructure tooling.

ADVERTISEMENT · IN-ARTICLE CONTENT

High-Engagement In-Article Native Ad Slot

(CLS Prevention Active · Zero Shift)

How to Use

11. Paste YAML Manifest or JSON Payload

Insert raw Kubernetes manifests, docker-compose.yml files, or JSON structures into the input editor.

22. Select Conversion Direction (YAML ↔ JSON)

Toggle between converting YAML into strict JSON or transforming JSON into human-readable YAML.

33. Live Syntax Error Highlighting

Identify indentation mismatches or formatting bugs instantly with clear line numbers and explanatory diagnostics.

44. Copy Result or Download File

One-click copy the validated output or download it directly as a .json or .yaml configuration file.

Cloud Infrastructure & DevOps Production Scenarios

Everyday deployment workflows where automated YAML transformation is essential.

Kubernetes ConfigMap Ingestion

Convert complex YAML application manifests into JSON strings for embedding inside ConfigMap payloads.

Docker Compose Validation

Identify hidden single-space indentation discrepancies that cause container orchestration launch failures.

GitHub Actions Matrix Pipelines

Transform JSON build matrix arrays into clean YAML workflow blocks.

OpenAPI Specification Authoring

Draft comprehensive API contracts in readable YAML before exporting to Swagger UI JSON schemas.

💡 YAML Formatting Best Practices & Production Pitfalls

✓ Enforce 2-Space Indentation

While YAML permits variable indentation widths, mixing 2-space and 4-space blocks within the same file causes silent hierarchy bugs. Standardize on 2 spaces.

✓ Quote Strings with Special Characters

Always enclose strings containing colons (:), braces ({}), or at signs (@) in double quotes to prevent parser misinterpretation.

✓ Configure Editor Tab Traps

Set `editor.insertSpaces: true` in VS Code to ensure pressing Tab always inserts real spaces.

✓ Split Multi-Document Streams

When parsing files delimited by triple hyphens (`---`), use multi-document splitting to output distinct JSON objects.

⚠️ Common Pitfalls & Mistakes to Avoid

❌ Mixing tab characters with spaces

✅ The most common YAML failure. Tabs look identical to spaces visually but break parsers. Use OrvoKit's validator to convert tabs.

❌ Unquoted 'NO' parsed as boolean false

✅ The classic Norway problem. Writing country code NO unquoted maps to false. Always quote reserved tokens ('"NO"').

❌ Omitting space after colon delimiter

✅ Writing `image:nginx:latest` fails. Always include a space: `image: nginx:latest`.

❌ Pasting production secrets to remote servers

✅ Kubernetes secrets contain base64 credentials. Never use remote cloud validators; execute parsing 100% locally.

Frequently Asked Questions (FAQ)

Expert answers to the most frequently asked questions and edge cases.

6 Q&As

The official YAML specification strictly prohibits tabs for indentation. Because different text editors and operating systems render tab stops with varying widths (e.g. 2, 4, or 8 spaces), relying on tabs introduces visual ambiguity that causes silent structural nesting errors. Spaces ensure deterministic indentation everywhere.

ADVERTISEMENT · FOOTER BANNER

Wide Responsive Banner

(CLS Prevention Active · Zero Shift)

Related Tools

Developer & Data View All →

JSON Formatter & Validator

Format, beautify, validate, and minify JSON data with instant syntax error highlighting and tree view.

Open Tool

CSV to JSON & JSON to CSV Converter with Preview

Convert CSV to JSON arrays and JSON to CSV with spreadsheet table preview and delimiter options.

Open Tool

JSON to TypeScript, Zod Schema & Pydantic Converter

Instantly convert JSON objects to TypeScript interfaces, Zod validation schemas, or Pydantic models.

Open Tool

Base64 Encoder & Decoder

Lossless UTF-8 Unicode Base64 encoder and decoder with file upload to Data URL conversion.

Open Tool