Favorite places of your favorite city
Home
Add to preferred sources on Google

YAML to JSON

Paste YAML or choose a UTF-8 file, then convert its supported data to JSON in your browser. Review the result and its conversion limits before using it elsewhere.

YAML input

Paste one YAML document or open a UTF-8 file, then convert it.

Choose one UTF-8 file up to 2 MiB. Opening it replaces the editable draft.

Limits: 2 MiB input, 8 MiB output and 10 seconds, with additional structure and alias limits.

JSON output

Convert YAML to see the result here.

YAML is processed locally in a worker; this tool does not upload or save the document.

Convert YAML in three steps

  1. Paste one document or open a UTF-8 YAML file up to 2 MiB. The converter uses a documented YAML 1.2 Core-based data profile, not application-specific configuration rules.
  2. Choose two spaces, four spaces or Compact, then select Convert to JSON. Correct any reported syntax, unsupported-type, key, alias or limit error in the original input.
  3. Review the complete result status, then copy the JSON or download converted.json. The visible preview can be clipped; current Copy and download still include the whole output.

How values become JSON

Under the selected Core profile, true is a boolean, while yes, on and an ordinary date such as 2026-11-08 are strings. Quoted and block strings keep their parsed content, including YAML folding and chomping rules.

Integer, decimal and exponent tokens are emitted without binary64 rounding. YAML-only plus signs, leading zeros and base prefixes are normalized into valid JSON numbers. Large or precise numeric text can still be rounded by another JSON reader.

Ordinary aliases expand into JSON copies within strict limits. Shared identity is lost, cycles and forward aliases are rejected, and an unquoted merge-like << key is not treated as inheritance. Quote it or explicitly tag it as a string when it is literal data.

JSON property keys must be strings. Non-string or duplicate decoded keys are rejected instead of being coerced or overwritten. Comments, anchors, directives, YAML styles and formatting cannot be preserved as JSON metadata.

Examples worth checking

The input enabled: true, mode: on and id: 9007199254740993 becomes a JSON object with a boolean, a string and that exact integer token. The large identifier is not silently rounded or quoted.

The numeric values 012, 0o12 and 0x10 become 12, 10 and 16. The decimal 1.0000000000000001 remains that precise numeric text, and 1e-400 is not replaced with zero.

A reusable anchored mapping can be referenced several times and becomes repeated JSON data. A self-referencing alias has no finite JSON-tree equivalent and is rejected rather than emitted partially.

Important compatibility limits

Only one document is converted. YAML 1.1, custom or non-core tags, unsupported explicit tagged forms, merge behavior, non-string keys, duplicate keys and cyclic or unresolved aliases are rejected. This is not validation of a deployment, template, schema or business rule.

Blank or comment-only input is incomplete. An explicit empty document beginning with --- and explicit null values have null meaning. NaN and infinity literals cannot be JSON numbers; finite exponent values are kept as text even when common floating-point readers cannot represent them.

Input is limited to 2 MiB, output to 8 MiB and processing to 10 seconds. Object, depth, scalar, numeric-token and expanded-alias limits also apply. Cancellation, timeout or any failed check leaves no downloadable partial result.

Output is UTF-8 without a BOM and ends with one LF. It preserves supported data under the stated rules, not YAML comments, graph identity, original bytes, presentation or a semantic round-trip back to the source. JSON consumers can reorder properties or round numbers.

Local conversion without saved history

The tool processes YAML in a local worker without uploading or saving the document. Copy and download happen only when requested. Its privacy notice does not certify every browser extension, site service or copy you keep.

YAML conversion questions

This converter uses its documented YAML 1.2 Core-based data profile, not YAML 1.1 or application-specific tags. Plain true and false resolve as booleans; yes, on and ordinary date text remain strings. Explicit unsupported versions or tags are not silently reinterpreted.

The converter emits validated numeric source values without binary64 rounding, including exact large integers and decimal or exponent text. YAML-only syntax is normalized to JSON grammar. Another JSON reader can still round those numbers or overflow its own numeric range.

Ordinary aliases expand into bounded JSON copies, including supported scalar-string keys. Cycles and forward or undefined aliases are rejected. Merge inheritance is not supported: an untagged plain << key is rejected, while a quoted or explicitly string-tagged << key is literal data.

JSON properties need string keys. Numeric, boolean, null or collection keys are not coerced, and duplicate decoded strings are not overwritten. Quoting a numeric-looking key can make it a string, but does not resolve an actual duplicate.

No. JSON retains the supported data, not comments, anchor names, tags as metadata, quoting styles or shared graph identity. Parsed block-string contents are preserved; the result is not a lossless YAML representation or a promise of semantic round-trip reconstruction.

No. The preview is bounded and labelled when clipped. Current Copy JSON, the complete readonly clipboard fallback and converted.json use the whole accepted UTF-8 output with one final LF. No partial result is available after a conversion failure.

No tool-added document upload, remote tag resolution, URL import, saved history or input-bearing share link is used. YAML is data here, not an instruction to execute or fetch something. This is not a universal security certificate for the browser or original configuration.

Sources and references

JSON to YAML

Convert JSON to YAML locally while preserving number text and quoted strings; copy or download the complete result.

Open tool — JSON to YAML

HTML to Markdown

Convert pasted or local HTML into Markdown, review conversion notes, and copy or download the result.

Open tool — HTML to Markdown

JavaScript Regex Tester

Test a JavaScript pattern locally and inspect matches, captures, and UTF-16 positions.

Open tool — JavaScript Regex Tester

Markdown to HTML

Convert a Markdown draft to an HTML fragment, inspect the source and inert preview, then copy or download it.

Open tool — Markdown to HTML

Text Sorter

Sort lines alphabetically by a chosen language or by Unicode code point, keeping duplicates, blank rows and complete line contents.

Open tool — Text Sorter

Remove Duplicate Lines

Keep the first copy of each exact text line, preserving order, significant spaces and blank rows, then copy or download the result.

Open tool — Remove Duplicate Lines

Text Diff Checker

Compare two drafts locally, with exact whole-line changes, visible whitespace rules and clear final-newline handling.

Open tool — Text Diff Checker

Case Converter

Convert text to uppercase, lowercase, capitalized words or sentence case with explicit letter rules.

Open tool — Case Converter

HTML Entity Encoder/Decoder

Encode or decode literal HTML references with explicit context, Unicode options and LF output, without parsing or rendering markup.

Open tool — HTML Entity Encoder/Decoder

Markdown Table Generator

Edit a small literal-text table, set alignment and copy GFM Markdown or import tab-separated text.

Open tool — Markdown Table Generator

Query String Parser & Builder

Edit ordered URL parameters, retain repeated names and copy a normalized query or HTTP(S) URL.

Open tool — Query String Parser & Builder

URL Encoder & Decoder

Convert a UTF-8 URL component or form value with explicit space and plus rules, then copy or download the result.

Open tool — URL Encoder & Decoder

Base64 Encoder & Decoder

Encode UTF-8 text as standard or URL-safe Base64, or decode either format with clear errors and complete text output.

Open tool — Base64 Encoder & Decoder

XML Formatter

Check namespace-aware XML 1.0, format or compact locally, and copy or download UTF-8 output.

Open tool — XML Formatter

JSON Formatter & Validator

Check JSON syntax, format or minify locally, and copy or download output while preserving original data tokens.

Open tool — JSON Formatter & Validator

SMS Character Counter & Segment Calculator

See how your message is encoded, where its segments end and what it may cost. Your text stays in your browser.

Open tool — SMS Character Counter & Segment Calculator

Social Media Character Counter

Check platform-specific limits and split posts without losing text.

Open tool — Social Media Character Counter

Character Counter

Count characters, words, sentences and paragraphs. Check word density, reading time and UTF-8 size, all in your browser.

Open tool — Character Counter

Text Size Calculator

Compare text encodings and payload sizes in your browser.

Open tool — Text Size Calculator

PDF Text Cleaner

Fix line breaks and spacing in text copied from a PDF. Preserve your original and review ambiguous hyphens before copying the cleaned text.

Open tool — PDF Text Cleaner

Fancy Text Converter

Convert supported fancy Unicode letters to normal text locally. Keep case, accents, emoji and your original text.

Open tool — Fancy Text Converter

Garbled Text Fixer

Fix garbled text and repair broken accents with a browser-based mojibake fixer. Review each possible UTF-8 reversal before applying it.

Open tool — Garbled Text Fixer

Gmail Clipping Checker

Measure email HTML bytes in UTF-8, compare them with an advisory 102,000-byte Gmail reference, and inspect size contributors locally.

Open tool — Gmail Clipping Checker
View all tools in this category