Convert CSV to XLSX Online

From Delimited Text to a Packaged Workbook

A CSV file is a sequence of characters arranged into records and fields, not a miniature spreadsheet. RFC 4180, published in 2005, describes the common comma-separated form and registers the media type text/csv. It permits a header row and says fields containing commas, quotation marks, carriage returns, or line feeds should be quoted. A quotation mark inside a quoted field is represented by two quotation marks, so a correct parser does not split the address "42 North St, Unit 5" into two columns. CSV itself does not contain a cell type, a formula, a font, a filter, a sheet name, or a declaration that a value is an account code rather than a number. That plain structure is why CSV is useful for data exchange and why its appearance can vary when different programs open it.

XLSX is an Office Open XML workbook package. Rather than a single stream of fields, it is a ZIP-based package of XML parts that can describe worksheets, shared strings, styles, formulas, relationships, drawings, and workbook settings. A conversion first has to decide how to parse the CSV text, then writes the resulting values into cells in a worksheet. Microsoft documents a limit of 1,048,576 rows and 16,384 columns in an Excel worksheet, with the final column named XFD. That capacity does not mean every CSV will import correctly by double-clicking it: a parser still needs the right delimiter, character encoding, and column treatment. The result becomes a genuine editable workbook, but it cannot recover design or formula logic that the flat source never carried.

Why Import Settings Become Cell Meaning

The key CSV-to-XLSX change is not compression; it is interpretation. The characters 00127, 03/04/05, and 1-2 have no built-in meaning in CSV, but spreadsheet software may turn them into a number, a locale-specific date, or another recognized value. Microsoft specifically warns that opening a CSV uses the current default data-format settings, and recommends an import route when a column must retain leading zeroes or a source date order differs from the local default. Treating a column as text before loading protects identifiers whose spelling matters. Values with more digits than a spreadsheet can display accurately should also be imported as text when they are identifiers rather than quantities. Once a value has been interpreted and saved as a different cell value, later changing its number format cannot always restore the original character sequence.

Encoding and separators are separate decisions. Microsoft says a UTF-8 CSV opens normally when it has a byte order mark, while a UTF-8 file without that marker can be loaded through Data, Get Data, From Text/CSV so the file origin is chosen deliberately. A file that appears as one long column is often using commas while the receiving computer expects semicolons, or the reverse; it is not proof of damaged data. The Text Import Wizard also permits a selected delimiter and a text qualifier, which matters when a note field contains a comma or a line break. Inspect the preview before import rather than assuming that rows are being split correctly. A dependable XLSX begins with a controlled reading of the source text, not with the extension on the filename.

Six Concrete Tradeoffs of an XLSX Copy

• Gain - editable cell structure: each parsed field becomes a cell that can be formatted, filtered, sorted, or used in a new formula after the import.
• Gain - multiple worksheet support: XLSX can hold many sheets, although one source CSV supplies only one table unless additional sheets are created later.
• Gain - explicit display choices: a text column can be marked as text, a date can receive a chosen display style, and column widths can be saved with the workbook.
• Loss - no source formulas to preserve: CSV has values only, so a workbook formula, chart, pivot table, comment, or validation rule cannot be reconstructed from it.
• Risk - changed identifiers: automatic type detection can remove leading zeroes or change date-like text unless important columns are set to text during import.
• Risk - formula execution from data: an untrusted field beginning with =, +, -, or @ can be treated as a formula by spreadsheet software.

The last point is a data-safety issue, not merely a cosmetic concern. OWASP documents CSV injection and recommends that exported untrusted text be handled so it cannot become a spreadsheet formula; its mitigation discussion includes prefixing a field with a tab inside a quoted CSV field, while noting that the tab becomes part of the data. For a local conversion, first decide whether those leading characters are meant to be formulas or literal text. For a public or shared export, sanitize untrusted fields before anybody opens the resulting workbook. Do not rely on a file appearing harmless in a text editor, because its behavior changes when a spreadsheet program assigns meaning to the characters. That is another reason a CSV-to-XLSX process needs a sample review of real edge cases.

Where CSV and XLSX Actually Open

Excel for Microsoft 365, Excel 2024, Excel 2021, Excel 2019, and Excel 2016 all have documented text-file import paths. Directly opening a .csv makes Excel use its current default data-format settings, while Data, Get Data, From Text/CSV offers a preview and a delimiter selection. The older Text Import Wizard exposes file origin, delimiters, text qualifiers, and per-column conversion choices, so it is useful when a column must stay text. Excel for the web can open workbooks, but a file that needs careful parsing is better prepared in an import interface that shows the preview. A converted XLSX should be opened in the actual receiving application, not only in the converter, because support for workbook features can differ between spreadsheet programs. A clean open without a repair warning is a practical compatibility check after the file is written.

Regional settings are a common source of surprise. Microsoft explains that the separator used when saving CSV can follow the Windows regional list separator, and that changing the Windows separator affects all applications. In regions where a comma is the decimal separator, semicolon-delimited files are common precisely because a comma already appears inside numbers. A CSV may therefore be valid for the system that produced it yet appear in one column on another system. Record the delimiter and encoding alongside a delivery file instead of assuming the extension explains both. An XLSX removes that delimiter ambiguity for the saved workbook, but the ambiguity must be solved correctly before the values become its cells.

Failures That Start Before the Workbook Exists

A shifted-column failure usually starts with a quoting mistake. Under RFC 4180, a comma inside a field must be protected by quotation marks, and an embedded quote must be doubled; simply splitting every line at every comma is not a CSV parser. A line break can also occur inside a quoted field, so counting physical lines is not a reliable count of records. Check at least one record containing a comma, a quotation mark, and a line break if the data allows such values. If the preview shifts columns after a particular row, find that source row before exporting an XLSX. Repeatedly saving a malformed import will not fix the structure; it only preserves the incorrect cells more permanently.

A second failure is silent text damage. Accented names, non-Latin scripts, and symbols can display incorrectly when an importer guesses a legacy code page instead of UTF-8. Microsoft documents the UTF-8-with-BOM behavior and the alternate controlled import path for files without a BOM. A third failure is type damage: a postal code becomes a number, or a date changes because the computer reads month and day in a different order. Compare source and output using a small test set that includes non-ASCII text, a quoted comma, a leading-zero code, a long identifier, and a date-like value. Also compare a useful row count and a total where the data has one. Those focused checks find errors that a quick look at the first three rows misses.

CSV and XLSX at a Glance

CSV-to-XLSX Questions With Specific Answers

Why did Excel remove the zeroes at the front of a code?
Directly opening a CSV lets Excel use default data-format settings. Import the column through a controlled text import and set that column to Text before loading it; formatting a number afterward may not restore the original characters.

Why is the entire CSV in column A?
The selected or expected delimiter does not match the file. In the Text/CSV preview, choose the actual comma, semicolon, tab, or other separator and confirm that a quoted comma remains inside one field.

Does converting to XLSX bring back formulas from an exported CSV?
No. CSV stores the characters representing displayed fields, not the source workbook's formula expressions or dependencies. XLSX can contain new formulas added after import, but they are not recovered source formulas.

Why are accented characters wrong after opening the CSV?
The file encoding was read as the wrong character set. Use the import route to select the correct file origin; Microsoft also documents that a UTF-8 CSV with a BOM can open normally.

Can I make an XLSX by renaming a CSV file?
No. Renaming changes only the label. A valid XLSX needs the workbook package and XML parts written by software that has parsed the CSV into cells.