Definition. An Excel-to-CSV workflow reads a spreadsheet and writes comma-separated data for another application. OfficeAPI documents CSV as both input and output in the Excel family, with .xlsx and .xls among the supported spreadsheet inputs. The conversion engine can run locally without sending the workbook to a hosted service.
What does the support table establish?
These 3 extensions cover common workbook and text-data entry points. The complete table also lists templates, WPS and OpenDocument inputs; see the full matrix when your workflow uses one of those sources.
| Extension | Input | Output | Role |
|---|---|---|---|
.xlsx |
Yes | Yes | Office Open XML workbook |
.xls |
Yes | No | Legacy Excel workbook |
.csv |
Yes | Yes | Comma-separated data |
CSV support does not define every export setting. The public matrix does not specify sheet selection, encoding options or formula handling. Verify the relevant behavior using the integration package and representative files before making it part of your application's contract.
Why is CSV different from a workbook?
A CSV represents rows and fields rather than the entire presentation and interaction model of a workbook. Decide which data the receiving application needs before conversion. A workbook with several sheets, formatting and formulas needs a more explicit acceptance check than a single flat table.
Consider 2 result goals: transferring tabular values, or distributing a visual representation. For the latter, spreadsheet preview or a documented PDF/image output may fit better than CSV.
How do you check a data export?
- Choose a workbook containing representative headers, dates, numeric values, empty cells and text with commas or quotation marks.
- Confirm CSV output and choose one of the 2 invocation paths.
- Keep the source workbook and converted data together while testing. Have your receiving application parse the CSV rather than checking only its filename.
- Compare expected records and field meanings, including leading zeros in identifiers and locale-sensitive dates or numbers.
For a workbook with multiple sheets, establish which results you expect and verify the integration's actual behavior. Do not infer a per-sheet export interface from the CSV row in the matrix.
What happens after conversion?
The next application owns validation and interpretation. For example, an identifier that looks numeric may need to stay text. Define those rules in the receiving workflow and keep conversion failures separate from data-validation failures. When handling many workbooks, an offline batch inventory helps retain that distinction.
Frequently asked questions
Can I export XLSB files?
XLSB is not listed as a supported conversion input in the source matrix. Preview coverage and conversion coverage are different lists.
Does CSV retain the appearance of an Excel file?
Use a visual output or preview when appearance is the requirement. CSV serves a data exchange workflow.
Is the conversion itself offline?
Yes. Any subsequent database, storage or model connection is part of your application.