YAML to JavaScript Converter

Paste YAML and get a JavaScript object literal — pick const, ES module export, CommonJS, IIFE, or bare expression style, and control quoting, indentation, and variable name.

Last updated: May 27, 2026

Style:

Var name: Indent: Single quotesSemicolons

YAML Input

JavaScript Output

const data = {
  server: {
    host: "localhost",
    port: 8080,
    debug: true,
  },
  database: {
    name: "myapp",
    pool: 10,
  },
  tags: [
    "web",
    "api",
  ],
};

Client-Side Processing

Input Data Stays on Device

Instant Local Execution

Find this tool useful? Support the project to keep it free!

Buy me a coffee

What is YAML to JavaScript Converter?

YAML configuration files are common in Node.js and browser tooling (Vite, Vitest, ESBuild configs started as YAML; many CI files are YAML). Sometimes you need to embed that configuration directly as a JavaScript object — for a mock, a fixture, or a hand-rolled config loader.

This tool parses YAML to a JSON value internally and then emits a JavaScript object literal with idiomatic key quoting (bare identifiers where valid, quoted strings otherwise). Choose between five output styles to match your project's module system.

How to Use YAML to JavaScript Converter

Paste YAML into the input panel.

Choose an output style: const, ES module, CommonJS, IIFE, or expression.

Set the variable name, quote style, indent, and semicolon preference.

Copy the JavaScript output.

Common Use Cases

Embedding a YAML config as a JavaScript constant for a test fixture.
Converting a Kubernetes or CI YAML file to a typed JS object for tooling.
Generating a JS module export from a YAML data file.
Creating a seed file from a YAML data definition.

Example Input and Output

A YAML mapping converts to a JavaScript const object literal.

YAML input

host: localhost
port: 8080
debug: true

JavaScript output

const data = {
  host: 'localhost',
  port: 8080,
  debug: true,
};

Privacy

All YAML parsing and JavaScript generation happen in your browser. No content is sent to a server.

YAML coverage

The internal YAML parser handles the common subset: mappings, sequences, scalars, and multi-line strings. Anchors, aliases, and YAML tags are not supported.

Frequently Asked Questions

How is this different from YAML to JSON?

JSON output uses double-quoted strings everywhere and strict JSON syntax. The JS output uses unquoted identifier keys, optional single quotes, and your choice of module wrapping.

When should I use the IIFE style?

Use IIFE when you want an immediately-invoked function expression that returns the value — useful for browser globals or older script environments without module support.

Does this send my YAML anywhere?

No. All parsing and conversion happen locally in your browser.