Convert XLSX to YAML

Why Convert XLSX to YAML?

Converting XLSX to YAML transforms your Excel spreadsheet data into the most human-readable data serialization format available. YAML's clean, indentation-based syntax makes it easy to read and edit structured data without the visual clutter of brackets, braces, or verbose markup tags. This makes YAML ideal for configuration files, data definitions, and structured content that humans frequently need to review and modify.

YAML has become the de facto standard for DevOps and infrastructure configuration. Tools like Docker Compose, Kubernetes, Ansible, GitHub Actions, and GitLab CI all use YAML for their configuration files. Converting your Excel data to YAML enables you to generate configuration data from spreadsheets, bridging the gap between business users who work in Excel and engineers who consume YAML.

YAML's native type system preserves data semantics during conversion. Numbers remain as numbers, boolean values are recognized, and strings are properly quoted when needed. This type awareness means the converted YAML data can be loaded directly into application data structures without manual type conversion.

Our converter reads the XLSX workbook, extracts data from the first sheet, and generates a YAML sequence of mappings where each spreadsheet row becomes a mapping with column headers as keys and cell values as properly typed values.

Key Benefits of Converting XLSX to YAML:

• Maximum Readability: Clean, indentation-based syntax that is easy to read and understand
• DevOps Ready: Output compatible with Docker, Kubernetes, Ansible, and CI/CD tools
• Type Preservation: Numbers, booleans, and strings are properly typed in YAML
• Comment Support: Add explanatory comments after conversion for documentation
• Version Control: Clean text diffs in Git for tracking data changes
• JSON Compatible: YAML 1.2 is a superset of JSON, enabling easy interchange

Practical Examples

Example 1: Employee Directory

Input XLSX file (employees.xlsx):

Excel Spreadsheet - Sheet1:
+--------+-----------+-------------+--------+
| Name   | Title     | Department  | Ext    |
+--------+-----------+-------------+--------+
| Alice  | Engineer  | R&D         | 1201   |
| Bob    | Designer  | UX          | 1305   |
| Carol  | Manager   | Operations  | 1102   |
+--------+-----------+-------------+--------+

Output YAML file (employees.yaml):

- Name: Alice
  Title: Engineer
  Department: R&D
  Ext: 1201
- Name: Bob
  Title: Designer
  Department: UX
  Ext: 1305
- Name: Carol
  Title: Manager
  Department: Operations
  Ext: 1102

Example 2: Service Configuration

Input XLSX file (services.xlsx):

Excel Spreadsheet - Sheet1:
+----------+------+----------+---------+---------+
| Service  | Port | Protocol | Enabled | Timeout |
+----------+------+----------+---------+---------+
| web      | 8080 | HTTP     | true    | 30      |
| api      | 3000 | HTTPS    | true    | 60      |
| cache    | 6379 | TCP      | false   | 10      |
| database | 5432 | TCP      | true    | 120     |
+----------+------+----------+---------+---------+

Output YAML file (services.yaml):

- Service: web
  Port: 8080
  Protocol: HTTP
  Enabled: true
  Timeout: 30
- Service: api
  Port: 3000
  Protocol: HTTPS
  Enabled: true
  Timeout: 60
- Service: cache
  Port: 6379
  Protocol: TCP
  Enabled: false
  Timeout: 10
- Service: database
  Port: 5432
  Protocol: TCP
  Enabled: true
  Timeout: 120

Example 3: Server Inventory

Input XLSX file (servers.xlsx):

Excel Spreadsheet - Sheet1:
+----------+----------------+------+-------+-----------+
| Hostname | IP Address     | CPU  | RAM   | OS        |
+----------+----------------+------+-------+-----------+
| web-01   | 192.168.1.10   | 4    | 16 GB | Ubuntu 22 |
| db-01    | 192.168.1.20   | 8    | 64 GB | CentOS 9  |
| cache-01 | 192.168.1.30   | 2    | 8 GB  | Debian 12 |
+----------+----------------+------+-------+-----------+

Output YAML file (servers.yaml):

- Hostname: web-01
  IP Address: 192.168.1.10
  CPU: 4
  RAM: 16 GB
  OS: Ubuntu 22
- Hostname: db-01
  IP Address: 192.168.1.20
  CPU: 8
  RAM: 64 GB
  OS: CentOS 9
- Hostname: cache-01
  IP Address: 192.168.1.30
  CPU: 2
  RAM: 8 GB
  OS: Debian 12

Frequently Asked Questions (FAQ)

Q: What is YAML format?

A: YAML (YAML Ain't Markup Language) is a human-readable data serialization language that uses indentation to represent data hierarchy. It supports scalars (strings, numbers, booleans), sequences (lists), and mappings (key-value pairs). YAML is the standard configuration format for Docker Compose, Kubernetes, Ansible, GitHub Actions, and many other DevOps tools.

Q: What is the difference between .yaml and .yml extensions?

A: Both .yaml and .yml are valid extensions for YAML files and contain identical content. The .yaml extension is the officially recommended extension per the YAML specification. The .yml extension is a historical abbreviation that remains popular due to early file system limitations. Both are universally supported by YAML-aware tools.

Q: Which worksheet is converted from the XLSX file?

A: The converter processes the first (active) worksheet in the XLSX workbook. If your file contains multiple sheets, the data from the first sheet will be extracted and converted into a YAML sequence. You can reorder sheets in Excel before conversion if you need a different sheet converted.

Q: How are data types handled in the conversion?

A: YAML has native type inference. Numeric values from Excel are output as YAML numbers (integers or floats), boolean-like values may be interpreted as YAML booleans, and text remains as strings. Values that could be ambiguously typed (like "true" as text) are quoted to preserve their string nature.

Q: Are Excel formulas preserved in the YAML output?

A: YAML does not support formulas or calculations. The converter extracts the computed values from formula cells and includes the results as properly typed YAML values. The formula expressions themselves are not transferred to the output.

Q: Can I use the output with Docker Compose or Kubernetes?

A: The generated YAML is valid YAML that can be loaded by any YAML parser. However, Docker Compose and Kubernetes expect specific key structures and schemas. You may need to restructure the output to match the required configuration format. The YAML data can serve as input for generating specific configuration files.

Q: Why does indentation matter in YAML?

A: YAML uses indentation (spaces only, not tabs) to represent the hierarchy and nesting of data structures. Incorrect indentation will cause parsing errors or incorrect data interpretation. The converter generates properly indented YAML with consistent spacing to ensure valid, parseable output.

Q: How does the converter handle large spreadsheets?

A: The converter processes spreadsheets of any reasonable size. Each row becomes a mapping in a YAML sequence, so the output grows linearly with the number of rows. YAML remains readable and parseable regardless of file size, though very large files may be better suited to streaming YAML parsers for memory efficiency.