Skip to main content

Excel to CSV: Save Product Sheets as CSV UTF-8 Without Breaking Them

Convert Excel to CSV UTF-8 without losing EAN zeros, getting semicolons or broken characters. Steps, fixes per value type and a pre-upload check.

Excel to CSV: Save Product Sheets as CSV UTF-8 Without Breaking Them

To convert Excel to CSV, open the sheet with your products, choose File > Save As (Save a Copy in Microsoft 365), pick CSV UTF-8 (Comma delimited) as the file type and save. Excel writes only the active sheet, so repeat it for each tab you need. On a Mac the menu path is the same.

That is the easy part. The conversion is where product spreadsheets break: EANs lose their leading zero or turn into 9.506E+12, a Dutch or German Excel writes semicolons instead of commas, accented characters come out as é, and a size like 3-4 becomes a date. This guide covers each of those, with the fix, and a check you can run before you upload the file to a webshop or a PIM.

Five steps to save a product sheet as CSV UTF-8

  1. Clean the sheet first. Delete instruction rows, merged title cells and empty columns above or beside the header. The first row should be the column names your importer expects, such as Handle, Title or SKU.
  2. Set identifier columns to Text. Select the EAN, GTIN, SKU and postcode-like columns, open Format Cells and choose Text, then re-enter or paste the values as text. Do this before typing or pasting; formatting a column after Excel has already converted the numbers does not bring the digits back.
  3. Save as CSV UTF-8. File > Save As (or Save a Copy), then choose CSV UTF-8 (Comma delimited). Excel warns that some features might be lost; that is expected, because a CSV holds values only.
  4. Repeat per sheet. A workbook with Products and Variants tabs becomes two CSV files. Name them so the importer order is obvious.
  5. Check the file in a text editor. Open the CSV in Notepad, TextEdit or VS Code, not in Excel. Look at the header, one EAN, one price and one description with a line break.

Step 5 matters more than it looks. Opening a CSV in Excel by double-clicking it runs Excel's conversions again, so the file can look fine in Excel while the text inside is not, or the other way around. A text editor shows exactly what the importer will read.

CSV UTF-8 or plain CSV: which option the importer expects

Excel offers several CSV types in the Save As list. They differ in encoding (how characters such as é, ß, ł and € are stored as bytes) and in line endings, not in the data you see.

Excel's CSV save options for product imports

CSV UTF-8 (Comma delimited)UTF-8CommaShopify, WooCommerce, most PIMs and marketplaces
CSV (Comma delimited)An older system code page, not UTF-8Your Windows list separatorOlder tools that ask for ANSI files
CSV (Macintosh)Legacy Mac encodingCommaVery old Mac software
CSV (MS-DOS)Legacy DOS code pageCommaVery old DOS-era systems
Text (Tab delimited)Legacy code pageTabImporters that ask for TSV; descriptions full of commas
Pick CSV UTF-8 unless an importer documents something else; the legacy options exist for old systems.

Shopify's product CSV instructions ask you to save the file in UTF-8 with LF line endings and separate every column with a comma. WooCommerce's product CSV importer documentation also says to use UTF-8, and warns that spreadsheet apps can change formatting or encoding, so you should review the saved file before importing. The Shopify CSV guide covers Shopify's columns in detail.

Two symptoms tell you the encoding is wrong. If Café shows up as Café, a UTF-8 file was read in an older Western European encoding such as Windows-1252. If it shows up as Caf? or a black diamond, the file was saved in an encoding that cannot hold the character, or read as UTF-8 when it was not. Microsoft's notes on Excel's text file formats even warn that the euro sign can turn into a question mark in a plain CSV. Letters such as the Polish ł or the Czech ř do not exist in Windows-1252 at all, so they cannot survive a file saved in it.

Why a Dutch or German Excel writes semicolons

In most European locales the decimal separator is a comma (19,99), so a comma cannot also separate columns. Excel's plain CSV option uses the Windows list separator, which in those locales is a semicolon. Microsoft's import and export guide says the default list separator is a comma, that you can change it in the Windows Region settings, and that setting the decimal separator to a comma forces Excel to use a semicolon.

For product files this creates two problems at once. The columns are separated by semicolons where Shopify expects commas, and every price is written as 19,99 where most importers expect 19.99. Fix both before upload:

  • Use CSV UTF-8 instead of plain CSV. Check the result in a text editor: if your Excel still wrote semicolons, the importer needs a semicolon setting or you change the separator.
  • Change the separators for Excel only. Under File > Options > Advanced, clear Use system separators and set the decimal separator to a period. Microsoft warns that changing the Windows Region setting instead affects every application on the computer.
  • Or let the importer read semicolons. Many importers detect or accept a semicolon. Shopify does not, according to its CSV instructions.

EANs that lose a zero or turn into 9.506E+12

Microsoft's page on keeping leading zeros and large numbers lists the behavior that damages identifiers: Excel removes leading zeros, keeps at most 15 significant digits, and shows large numbers in scientific notation such as 1.23E+15. A 13-digit EAN fits within 15 digits, so the number itself survives, but it can still display in scientific notation.

Take GS1's demonstration GTIN 9506000134352, written as a 14-digit GTIN with a leading zero: 09506000134352. Pasted into a General-format cell, it becomes the number 9506000134352. A narrow column shows 9.506E+12. Excel's CSV format saves the text and values as they are displayed in the cells, as Microsoft's file format notes put it, so the CSV can contain 9.506E+12. An importer reads that as a different value or a broken barcode. The EAN guide explains how the digits and check digit are built, and the EAN and GTIN validator shows whether a code still checks out.

What happens to product values between Excel and CSV

GTIN 095060001343529506000134352 (zero gone)Format the column as Text before pasting
EAN 9506000134352 in a narrow column9.506E+12Text column, or widen and use format 0
Supplier code 0503E0005.03E+02 (read as scientific notation)Text column or Automatic Data Conversion off
Size 3-4 or 10-12A date (4-Mar in a US Excel)Text column; import CSVs as Text
Price 19.99 in a Dutch Excel19,99 with semicolon columnsChange separators or tell the importer
Café, Größe, ŁódźCafé, Gr??eSave as CSV UTF-8
Showing 6 of 6 rows
Most damage happens when values enter Excel, not when they leave it, so the fix is usually a Text column or a different import route.

In Excel for Microsoft 365 and Excel 2024, the Automatic Data Conversion options let you switch off removing leading zeros, truncating long numbers to 15 digits in scientific notation, converting numbers around an E to scientific notation, and converting text such as letters followed by numbers to dates. Switch them off on the computers that handle supplier files and much of the damage above never happens.

One more fix: if a file has already been through Excel and the zeros are gone, do not try to recover them with a custom number format and a re-save. Go back to the supplier's original file. Padding digits back by rule (always 13 digits) produces valid-looking codes that may not be the real ones.

Descriptions with line breaks, quotes and HTML

Long product descriptions are the second big source of broken rows. RFC 4180, the informational specification most importers follow, says fields that contain line breaks, double quotes or commas should be enclosed in double quotes, and a double quote inside such a field must be escaped by doubling it. Excel quotes such fields when it saves, but files edited by hand or exported by older systems often do not.

  • Line breaks (Alt+Enter in a cell). Fine inside a quoted field. A tool that reads line by line, or a field that lost its quotes, splits the product into two rows.
  • Inch marks and quotes. A description like Monitor 27" stand must come out as "Monitor 27"" stand" in the file. If it does not, the row shifts and every column after it is wrong.
  • HTML. Tags such as <p> and <ul> are just text to a CSV, so they survive as long as the field is quoted. Check that the importer expects HTML in that column rather than plain text.

A quick test for a large file: count the rows in the text editor and compare with the number of products. More lines than products is normal when descriptions contain line breaks; a different number of columns in some rows is not. Many import errors that look like bad data are really dirty data from a broken row.

Dates, prices and percentages in exported product sheets

A CSV holds text and keeps no formatting. What is left is the text Excel writes for each cell, which can still carry the format of your locale. Three columns need attention in product files:

  • Dates. Launch dates, sale start and end dates and best-before dates can come out as 14-11-2026 or 11/14/2026 depending on the computer. Write them as ISO dates (2026-11-14) in a Text column when the importer accepts them.
  • Prices. Remove currency symbols and thousands separators. EUR 1.299,00 should go out as 1299.00, or whatever the importer's template shows.
  • Percentages. A VAT rate formatted as 21% may be written as 21% or stored as 0.21. Check which form the importer's template uses and match it.

Google Sheets and Apple Numbers exports

Shopify recommends Google Sheets for viewing its CSV files. In Google Sheets, File > Download > Comma-separated values exports the sheet you have open as a UTF-8 file with commas between the columns. It is often the simplest way to turn a semicolon file from a European Excel into a comma file. The same leading-zero rule applies: import or paste identifiers into columns formatted as plain text.

In Numbers on a Mac, File > Export To > CSV lets you create one file per table or combine tables into one file, and the text encoding sits under Advanced Options. Choose UTF-8 there before you save.

Reopening a supplier CSV in Excel without damage

Most CSV damage happens on the way in, when someone double-clicks a supplier file to look at it and then saves it. Open it through Data > From Text/CSV instead. In the preview, choose the right file origin and delimiter, then select the identifier columns and set their data type to Text before loading. Microsoft describes the same route for keeping leading zeros and for opening UTF-8 CSV files that have no BOM.

Checks before uploading a product CSV

0 of 8 done0%

If the checklist sounds like a weekly chore, it usually is: the same supplier sheet arrives every week and someone repeats the same fixes by hand. The data entry automation guide covers which of these steps a tool can take over.

Skipping the CSV step for imports into WISEPIM

If the target is WISEPIM, you do not need to convert at all. The product importer reads .xlsx and .xls files directly. It takes the stored value of each cell rather than its display, so a 13-digit EAN in a General column stays 13 digits and date cells become ISO dates. In an .xlsx file, a number formatted with a zero mask such as 0000000000000 also keeps its leading zeros. It reads the workbook's active sheet, and when that sheet is an instruction tab it picks the one sheet that holds products.

For CSV files, the importer detects the encoding (UTF-8, UTF-16, UTF-32 or Windows-1252) and the separator (comma, semicolon, tab, pipe or tilde) and honors a sep= line at the top of the file. It flags rows that have more cells than the header before the import starts, with the row number as your spreadsheet shows it.

Columns map to product attributes once; a saved supplier profile reuses the mapping for the next delivery of the same sheet.

Values Excel already damaged before the file reached you cannot be repaired by any importer, so the Text-column habit still pays off upstream.

Diego Nijboer

CTO and Co-Founder at WISEPIM, building AI-powered solutions that transform product data management for e-commerce businesses. Over 10 years of experience solving complex technical challenges in e-commerce and PIM systems.

Frequently asked questions

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Contact Support

Open the workbook, select the sheet you want to export and choose File > Save As (or Save a Copy). In the file type list, pick CSV UTF-8 (Comma delimited) and save. Excel exports only the active sheet and warns that features may be lost, which is normal. Open the result in a text editor to check that special characters and codes came through.

Excel uses the list separator from your Windows region settings for plain CSV files. In locales that use a comma as the decimal separator, such as Dutch and German, that list separator is a semicolon. Change the separators under Excel's advanced options, use an importer that accepts semicolons, or export from Google Sheets, which writes commas.

Format the column as Text before you paste or type the values, or import the CSV through Data > From Text/CSV and set the column type to Text. In Excel for Microsoft 365 and Excel 2024 you can also switch off the automatic conversion that removes leading zeros. Formatting a column after the zeros are gone does not bring back the original values.

Both are comma-separated text files. CSV UTF-8 stores characters in UTF-8, which covers every language, while plain CSV uses an older, system-dependent code page such as Windows-1252, which cannot store characters like the Polish ł. Most webshops and PIMs, including Shopify and WooCommerce, ask for UTF-8.

Not with Save As: Excel writes only the active sheet to a CSV file, so you repeat the save for each sheet. Numbers on a Mac can export each table as its own CSV in one step. If your importer accepts Excel files directly, uploading the workbook avoids the conversion altogether.

Keep exploring

Hand-picked next steps to go deeper.

Better product data, better results.Get more sales.

4.7