Convert GitHub Actions YAML to JSON
Overview
GitHub Actions workflows live in .github/workflows/ as YAML files. When building custom Actions or writing workflow generators in JavaScript, it helps to see the exact JSON structure that the Actions runner parses. Paste any workflow YAML here — including multi-job workflows with strategy matrices, needs dependencies, and environment blocks — and inspect the JSON output.
How to Use This Tool
Copy your .github/workflows/ci.yml content and paste it into the input panel. The JSON output shows the full nested structure including jobs, steps, and trigger conditions. Use this to verify that your YAML indentation is correct before committing.
Ready to get started? It's free, no registration required, and your files never leave your device.
PDF Tool →Frequently Asked Questions
Can I convert the on: trigger block from YAML to JSON?
Yes. The on: key in GitHub Actions YAML is a reserved word in some contexts, but js-yaml handles it correctly as a string key. The JSON output will show it as the on property with push, pull_request, and other trigger objects nested beneath it.
Why does my matrix strategy look different in JSON?
YAML flow sequences ([ubuntu-latest, windows-latest]) and block sequences appear identical in the JSON output — both become JSON arrays. The visual difference is a YAML serialization choice, not a structural one.
Does this work for composite Actions action.yml files?
Yes. Composite Action definitions use the same YAML format. Paste your action.yml and inspect the runs.steps array structure in JSON to verify step ordering and input mappings.