CatalogHop

WooCommerce import error: "The file is empty or using a different encoding than UTF-8, please try again with a new file."

What it means: WooCommerce reads the header row and the first product row. When there is no first product row, it shows this message, most often for a file with only the header row. Despite the wording, a file saved in another encoding usually does reach the mapping screen; its accented letters are damaged instead (see the accents page below). A completely empty file is refused earlier by WordPress with "File is empty. Please upload something more substantial."

Find the rows in your file

WooCommerce product import

The product CSV you are about to import into WooCommerce (Products, Import), or the one that just failed.

Your file stays on this device

It is read and converted by this page, inside your browser. Nothing from the file is uploaded, and the tool keeps working offline once the page has loaded.

Loading the converter...

How to fix it

  1. Open the file and check that there are product rows under the header.
  2. Save it as "CSV UTF-8" from your spreadsheet program.
  3. If your file is in another encoding on purpose, choose it under "Show advanced options", then "Character encoding of the file", on the upload screen.

Example

A file with this problem

Type,SKU,Name,Regular price

What the checker says about it

  • Line 1: The file has a header row but no products. WooCommerce shows "The file is empty or using a different encoding than UTF-8, please try again with a new file."

Once the listed rows are fixed, check the file again; the checker also looks for the other problems in WooCommerce's import code, so you do not trade one error for the next.

Other WooCommerce import errors

Sources

Based on WooCommerce 11.2.2's import code and documentation. Not tested on a live store.