A GitLab CI validator that catches mistakes before the runner does.

Paste the pipeline YAML into a browser-based GitLab CI validator to catch errors before you commit — no install and no push needed. This tool runs the full check set (YAML structure plus pipeline misconfigurations) entirely in your browser, so you get instant feedback on syntax errors, undefined stages, jobs without scripts, broken needs/extends, and invalid when values before the config ever reaches a GitLab runner. Paste your .gitlab-ci.yml and validate online to get a clear pass or fail with the line and reason for each problem.

Yes. GitLab’s built-in CI Lint requires a project and a sign-in, but this validator does not. You can validate a .gitlab-ci.yml without a project, an account, or a login — just paste the YAML and the GitLab CI linter runs 100% in your browser. Nothing is uploaded to a server, so you can safely check internal or proprietary pipelines, including ones with private runner tags and secret variable references.

That message means GitLab rejected your pipeline before running it — almost always because of a structural mistake rather than bad YAML. The usual causes are a job with no script / run / trigger / extends, a job whose stage is not in your stages list, needs or extends pointing at a job that does not exist, an invalid when value, or a rules block that is not a list. To fix "this GitLab CI configuration is invalid", paste your .gitlab-ci.yml here: the validator runs the same high-signal checks and tells you exactly which job and key broke, with the fix.

Run a GitLab CI YAML lint in the browser before you commit. Paste the config into this validator and it checks both the YAML and the pipeline structure — undefined stages, jobs without scripts, broken needs/extends, invalid when — so you can validate a GitLab CI pipeline before push. A clean result here is strong pre-push confidence; for absolute certainty, confirm with GitLab’s own CI Lint, which also resolves includes and project variables.

Yes. This is a free GitLab CI YAML validator with no signup, no install, and no login. It runs entirely client-side in your browser, so there is no account to create and nothing to upload. Paste your .gitlab-ci.yml and validate online instantly — the tool is free to use as often as you like.

Two things at once. First, it parses your .gitlab-ci.yml and reports YAML syntax errors, bad indentation, and structural mistakes (such as the "did not find expected key" error) with the line that broke. Second, it runs needs / rules / stages validation that matches how GitLab itself validates a config: a job with no script / run / trigger / extends, a job whose stage is not in your stages list, needs and extends references that point at jobs that do not exist, an invalid when value, a rules block that is not a list, legacy only/except, and bad image/services shapes. You get YAML errors and pipeline mistakes in one pass.

The GitLab CI "did not find expected key" error is a YAML problem, not a pipeline-logic one — it almost always comes from inconsistent indentation, a missing colon, or mixing tabs and spaces, so the parser expected a mapping key and found something else. Paste your .gitlab-ci.yml into this validator: it reports the exact line where the YAML structure broke so you can re-indent or add the missing key and re-validate.

A GitLab job has to do something. A regular job runs commands with script: (or the newer run:), a bridge job starts a downstream pipeline with trigger:, and a job can inherit any of those from another job or hidden template via extends:. A visible job that defines none of them produces the GitLab CI "job without script" error — GitLab rejects it with a message like "job config should implement a script: or a trigger: keyword". This validator flags any visible job missing all four. Hidden templates (keys starting with a dot) are allowed to be partial fragments, so they are not required to have a script.