CSV vs XLSX: What Each Excel File Format Keeps

Software & Apps / Excel file formats / Practical comparison

Choose XLSX for an editable Excel workbook with worksheets, formulas, and presentation. Choose CSV when another system needs a flat table of text values. For many workflows, the right answer is to keep the workbook as your master and create a separate CSV for delivery.

The extension matters even when both files open in Excel and look similar on screen. A CSV can display in a grid without storing the workbook features you add during that editing session. Decide what the next person or application needs before changing formats.

01 / A table of values and a workbook serve different jobs

CSV: a portable text table

CSV means comma-separated values. The informational RFC 4180 describes a common representation of records and fields, with an optional header row and quoting rules for fields containing commas, quotes, or line breaks. It documents a common format rather than establishing a universal spreadsheet standard.

Think of CSV as the handoff layer between systems: a recipient needs to know what each column means and how to interpret its text. A column headed Account ID does not, by itself, force every importing application to treat its contents as identifiers rather than numbers.

XLSX: an Excel workbook

Microsoft identifies XLSX as an XML-based Excel workbook format. Use it for continued spreadsheet work. It retains a workbook’s structure rather than flattening everything into a text export. Office Open XML’s document representation and packaging are defined in ECMA-376.

The practical question is whether the recipient needs your model or its output. Someone adjusting assumptions in a planning workbook needs a different deliverable from an application ingesting a list of approved records.

02 / Check what survives the save

Microsoft’s feature-loss guidance explains that CSV saves displayed text and values from the active worksheet and loses formatting, graphics, and other worksheet features. Normally displayed formula results become exported values; CSV does not preserve an Excel calculation model.

Microsoft’s format reference distinguishes XLSM, which supports VBA macro code, from XLSX, which does not. If a working file already contains automation, preserve an appropriate master before making a different delivery version. Changing the extension in a filename is not a conversion.

03 / Match the format to the recipient’s next action

Ask what happens immediately after delivery. Does a person review assumptions, or does software map columns into database fields? An attractive workbook can be the wrong upload file, while a technically valid CSV can be the wrong editable report.

• Ongoing analysis: keep a workbook with clearly labeled inputs, calculations, and outputs.
• System upload: obtain the current import template and follow its accepted file types.
• Data handoff: agree on column meanings and include a short explanation of units and identifiers.
• Human review: provide enough context to understand totals, filters, and exclusions.

Hypothetical example: a small team keeps product assumptions, supplier notes, and a publish-ready catalog on separate tabs. The shop’s importer requests a CSV containing SKU, name, and price. Keep the working workbook and export the catalog table as a separate delivery file. Sending the workbook instead does not satisfy a CSV-only importer, and replacing the master with the export loses useful working context.

A useful handoff note says which file is authoritative. For example: “Use the workbook for revisions; use the dated CSV only for this upload.” That prevents an exported snapshot from silently becoming the team’s editing master.

04 / Create a separate delivery copy

Save the master in its intended workbook format first. Then create an export with a distinct name and location. Microsoft’s text-format saving instructions use File’s Save As or Save a Copy options, followed by the required file type. Available options vary with the active sheet and Excel environment.

1. Identify the table the recipient requested and confirm the appropriate worksheet is active.
2. Review headers, included records, and calculated outputs before exporting.
3. Save a separate file using the recipient’s required CSV variant.
4. Read any compatibility warning and confirm that a values-only delivery is intentional.
5. Verify the saved export before sending or uploading it.

Use filenames that reveal purpose, such as catalog-master.xlsx and catalog-upload-2026-10-25.csv. These names are examples, not required conventions. If the master uses macros, preserve its appropriate extension instead.

After exporting, check which file is currently open before making more edits. Keeping the master and delivery file in separate folders can reduce confusion, especially when a team receives several revisions in one day.

05 / Agree on columns, encoding, and separators

The receiving application’s requirements are part of the deliverable. Record the expected header names, column order if required, mandatory fields, date convention, decimal convention, and treatment of blank values. Ask whether an empty field means unknown, clear an existing value, or leave it unchanged; those outcomes belong to the importer’s rules.

CSV also needs an agreed delimiter and encoding. Microsoft’s text import/export documentation explains that separators can vary and that opening CSV uses Excel’s default interpretation settings. A file that splits correctly on one computer may need explicit import settings elsewhere.

For international text, check the receiver’s encoding requirement rather than assuming the filename tells you. Microsoft’s UTF-8 guidance explains that Excel can open UTF-8 CSV normally when a byte-order mark is present; its import tools provide an alternative when it is absent. That Excel behavior does not establish what a separate upload service accepts.

Choose a small set of representative records for checking: an identifier with a leading zero, an accented name, a decimal value, a date, an empty field, and a description containing punctuation. Use approved sample data where the real records are sensitive.

06 / Verify the saved output, not just the open workbook

Review the actual export through a controlled import preview or the receiving application’s validation step. Do not rely solely on the worksheet that was visible before saving.

• Confirm the header row, expected number of records, and required columns.
• Compare several identifiers character by character.
• Check dates and decimal values against their agreed meanings.
• Inspect non-English characters, punctuation, and multi-line descriptions.
• Compare a useful total or record count with the approved source.
• Review the importer’s rejected-row report before accepting the transfer.

If Excel changes identifiers when reopening a CSV, separate export quality from import interpretation. Our guide to importing CSV without losing leading zeros covers that specific problem. Inspecting a file should not accidentally become an unreviewed edit-and-save cycle.

Where an upload creates or updates real records, use its preview, test environment, or a small authorized sample when available. Define how you will identify duplicates and correct an incorrect mapping before sending the full file.

07 / Diagnose the format problem before converting again

Keep the last approved source while investigating. Repeated conversions without identifying the mismatch can produce several files with different problems and no clear reference version.

Frequently asked questions