CircleCI "Build error: Unable to parse YAML"
CircleCI could not parse .circleci/config.yml as YAML. The pipeline fails before any job is scheduled - the file is malformed from indentation, a tab, or an unquoted special character.
What this error means
The pipeline is not created. CircleCI shows "Build error: Unable to parse YAML" pointing at a line and column, and no jobs run. It reproduces every push until the file is fixed.
circleci
Build error: Unable to parse YAML
while scanning for the next token
found character that cannot start any token
in 'string', line 7, column 1Common causes
Wrong indentation or a tab character
YAML forbids tabs for indentation and nests by spaces. A misaligned key or a single tab makes the parser reject the document.
Unquoted special characters
A value starting with *, &, @, {, [, or containing a colon-space, reads as YAML structure unless quoted.
How to fix it
Validate locally and fix the line
The CLI parses offline and prints the exact failing line.
Terminal
circleci config validate .circleci/config.ymlRemove tabs and quote special values
- Open the file at the reported line and column.
- Replace tabs with spaces (2 per level is the CircleCI convention).
- Quote any value containing a colon-space or starting with
*,&,@,{,[.
How to prevent it
- Run
circleci config validatein a pre-commit hook or lint job. - Configure your editor to insert spaces and show whitespace.
- Quote string values that contain colons or start with YAML indicators.
Related guides
CircleCI "Unexpected argument" / "mapping values not allowed"Fix CircleCI "Unexpected argument" and "mapping values are not allowed here" - an unquoted colon, a misindent…
CircleCI "Config does not conform to schema"Fix CircleCI "Config does not conform to schema" from circleci config validate - a misspelled key, a missing…
CircleCI "No workflow defined" - Nothing RunsFix CircleCI "No workflow defined" / no jobs triggered - a missing workflows section, an empty jobs list, or…