YAML indentation: tabs vs spaces (and why parsing fails)
YAML is indentation-sensitive. Learn how tabs/spaces break parsing and how to normalize YAML before converting to JSON (no upload).
Tabs are not allowed for indentation Playbook
Tabs are not allowed for indentation. Actionable remediation checklist with tool links and relevant guides.
TL;DR: Validate -> locate exact failing spot -> fix the minimal part -> re-validate.
Execution steps
- Validate input locally. Start with a validator or parser-friendly converter.
- Locate root cause. Use line/position/error token to isolate one failing place.
- Apply a minimal fix. Do not refactor all content at once.
- Re-validate and continue. Once clean, convert/export safely.
Recommended tools
Relevant guides
Auto-selected from existing guides for this topic. Need more: search by keyword.
yaml: line 2: did not find expected key: what it means and how to fix it
Fix "yaml: line 2: did not find expected key": Go/Kubernetes YAML error. What it means and the fastest fixes (indentation, tabs, lists) without uploading data.
yaml: line 2: did not find expected '-' indicator: what it means and how to fix it
Fix "yaml: line 2: did not find expected '-' indicator": Go/Kubernetes YAML error. What it means and the fastest fixes (indentation, tabs, lists) without uploading data.
yaml.composer.ComposerError: found duplicate key: what it means and how to fix it
Fix PyYAML error (found duplicate key): why it happens and the quickest fixes (indentation/tabs/duplicate keys) + local validation (no upload).
yaml: line 2: found character that cannot start any token: what it means and how to fix it
Fix "yaml: line 2: found character that cannot start any token": Go/Kubernetes YAML error. What it means and the fastest fixes (indentation, tabs, lists) without uploading data.
yaml.reader.ReaderError: unacceptable character #x0000: what it means and how to fix it
Fix PyYAML error (unacceptable character #x0000): why it happens and the quickest fixes (indentation/tabs/duplicate keys) + local validation (no upload).
yaml.parser.ParserError: while parsing a block mapping: what it means and how to fix it
Fix PyYAML error (while parsing a block mapping): why it happens and the quickest fixes (indentation/tabs/duplicate keys) + local validation (no upload).
yaml.scanner.ScannerError: while scanning a simple key: what it means and how to fix it
Fix PyYAML error (while scanning a simple key): why it happens and the quickest fixes (indentation/tabs/duplicate keys) + local validation (no upload).
Related actions
- Deep topic hub: Tabs are not allowed for indentation
- Decision comparison: Tabs are not allowed for indentation
- Alternative flows: Tabs are not allowed for indentation
- Migration path: Tabs are not allowed for indentation
- Case study: Tabs are not allowed for indentation
- Trend report: Tabs are not allowed for indentation
- Pillar for YAML
- Data asset: Tabs are not allowed for indentation
- All YAML subtopics
- Search tools for "tabs indentation yaml Tabs are not allowed for indentation"
Related playbooks
- Trailing spaces in YAML
- Unicode/encoding issues in YAML
- YAML anchors and aliases (& * )
- Special characters in YAML
- Redact secrets in YAML before sharing
- Quotes and strings in YAML
Related by intent
- Intent hub for Tabs are not allowed for indentation
- Execution playbook
- Method comparison
- Alternative flows
- Migration path
- Benchmark baseline
- Case study
- Trend report
- Cluster pillar
- Cross-cluster pillar: JSON
- Linkable data asset
Expert signal
Expert note: Tabs are not allowed for indentation usually resolves fastest when triage starts from strict validation and then branches to comparison/alternative paths based on input quality.
Data snapshot 2026
| Metric | Value |
|---|---|
| Intent confidence score | 88/100 |
| Predicted CTR uplift potential | 35% |
| Target crawl depth | < 3 clicks |
Trust note: All processing happens locally in your browser. Files are never uploaded.
Privacy & Security
All processing happens locally in your browser. Files are never uploaded.
Quick fix checklist
- Reproduce the error on a minimal input.
- Check type/format and field mapping.
- Apply the smallest safe fix.
- Validate on production-like payload.
Related by intent
Useful follow-up pages selected from real search impressions and no-click opportunities.
No-click fix: tab delimited tsvNo-click fix: guidesNo-click fix: researchRelated fix: neighbor csharp rust serde json map a string col 2 workflows data importRelated fix: neighbor csharp rust serde json string abc unit col 1 workflows data importRelated fix: neighbor csharp rust serde json boolean true a string col 1 workflows data importRelated fix: neighbor csharp csharp stj could not be converted system int32 id workflows webhooksRelated fix: neighbor csharp csharp stj could not be converted system int32 data workflows webhooksRelated fix: neighbor csharp csharp stj could not be converted system int64 data workflows webhooksRelated fix: neighbor go csharp stj could not be converted system string token runbooks data importRelated fix: neighbor csharp csharp stj could not be converted system double data workflows webhooksRelated fix: neighbor csharp csharp stj could not be converted system int32 id workflows api gatewayRelated fix: neighbor csharp csharp stj could not be converted system int32 id workflows data importRelated fix: neighbor csharp csharp stj could not be converted system decimal data workflows webhooksRelated fix: neighbor csharp csharp stj could not be converted system double id workflows data importRelated fix: neighbor csharp csharp stj could not be converted system guid payload workflows webhooksRelated fix: neighbor csharp csharp stj could not be converted system int32 user id runbooks webhooksRelated fix: neighbor csharp csharp stj could not be converted system string status runbooks webhooksRelated fix: neighbor csharp csharp stj could not be converted system string token workflows webhooksRelated fix: neighbor csharp csharp stj could not be converted system int32 data workflows api gateway