Back to blog
6 min read Export Guides

Broken Characters and Emojis in an Exported CSV: UTF-8 and BOM for Excel

You export posts or products to CSV, open the file in Excel, and “Café crème” turns into “Café crème”. Emojis become three or four strange characters. The file itself is fine: Excel read it with the wrong character encoding. There are two fixes: one in Import Export by RockStarLab before you export, and one in Excel when you open the file.

Free: CSV, Excel (.xlsx) and ODS export with the UTF-8 BOM option, for posts, pages, comments and media. PRO: the same for WooCommerce data, users, terms and custom post types.

Short Answer

  • In Import Export → Export, step 4, choose CSV and tick UTF-8 BOM. Excel then opens the file with the right characters.
  • Or export to XLSX (Excel) instead of CSV. An .xlsx file has no encoding question at all.
  • For a CSV without the BOM, open it in Excel with Data → From Text/CSV and set File Origin to 65001: Unicode (UTF-8).

Exports only read your content, so no backup is needed.

Why the characters break

WordPress stores text as UTF-8, and the plugin writes CSV files in UTF-8. In UTF-8, “é” takes two bytes and an emoji takes four. When you double-click a CSV, Excel for Windows often doesn’t check the encoding and reads the bytes with the legacy code page of your system, such as Windows-1252. Each byte then becomes its own character. Our four test titles looked like this when the UTF-8 bytes were read as Windows-1252:

In WordPress Read with the wrong encoding
Café crème hoodie: care guide Café crème hoodie: care guide
Größentabelle für Teamshirts Größentabelle für Teamshirts
Merch drop 🎉 spring 2026 Merch drop 🎉 spring 2026
Señora García’s embroidery order Señora García’s embroidery order

Curly apostrophes, long dashes and the euro sign break the same way, so even an English site can see “’” instead of “’”. Google Sheets and Apple Numbers read UTF-8 correctly, which is why the same file can look fine there and broken in Excel.

Fix 1: Export with a UTF-8 BOM

A byte order mark (BOM) is three invisible bytes at the start of a file: EF BB BF. They tell Excel that the file is UTF-8. To add them:

  1. Go to Import Export → Export, choose the content type, filters and columns as usual.
  2. In step 4, choose CSV.
  3. Tick UTF-8 BOM under CSV Options.
  4. If your Excel uses a semicolon as the list separator (common in Germany, France, Italy and other countries that write decimals with a comma), set Delimiter to Semicolon as well.
  5. Click Start Export and download the file.
Export step 4, CSV Options: Delimiter set to Semicolon, Include Header Row checked, UTF-8 BOM checked with the text Add a byte order mark so Excel shows accented letters and emojis correctly
UTF-8 BOM ticked, with a semicolon for European Excel.

The file starts with the BOM, followed by the header row. In a text editor it looks the same as before, because the three bytes are not shown. The first rows:

ID;post_title;author_name
2022;"Señora García’s embroidery order";admin
2021;"Merch drop 🎉 spring 2026";admin
2020;"Größentabelle für Teamshirts";admin
2019;"Café crème hoodie: care guide";admin

The BOM is off by default, because some tools that read CSV files (scripts, other importers) treat the three bytes as part of the first column name. Turn it on for files that people will open in Excel. When you import a file with a BOM back with Import Export by RockStarLab, the BOM is removed from the first column name automatically.

Fix 2: Export to Excel format

If the file is only for people who use Excel, choose XLSX (Excel) in step 4 instead of CSV. Text in an .xlsx file is always stored as Unicode, so accents and emojis are correct, and there is no delimiter to choose. Dates and numbers also arrive as cells instead of text that Excel has to guess. See exporting posts to CSV, Excel, JSON, XML and ODS.

Fix 3: Open an existing CSV correctly in Excel

If you already have a CSV without the BOM, don’t double-click it. In Excel:

  1. Open a blank workbook and go to Data → From Text/CSV.
  2. Select the file.
  3. Set File Origin to 65001: Unicode (UTF-8) and check the Delimiter.
  4. Click Load.

Microsoft describes the same steps in its answer about opening a CSV with the correct encoding. Don’t save over the original CSV from Excel with the default “CSV (Comma delimited)” type: that saves in the legacy code page and the special characters are lost in the file too. Use “CSV UTF-8 (Comma delimited)” if you need to save a CSV.

With an AI agent

An AI agent connected through the WordPress MCP Adapter (see connecting Claude Code to WordPress) can create the file with the same options. rsl-ie/export-start takes csv_use_bom and csv_delimiter in format_options. A prompt:

Export all published posts with ID, title and author name to a CSV file
named posts-for-excel. My colleagues open it in Excel with German regional
settings, so make sure accents and emojis show correctly.

In our run, the agent started the export with "csv_use_bom": true and "csv_delimiter": ";". The finished file began with the bytes EF BB BF followed by ID;post_title;author_name.

FAQ

Is the data in my CSV damaged?

No. The file contains the right UTF-8 bytes; only the program that opened it chose the wrong encoding. Open it again with the steps above. The data is damaged only if you saved it again from the program that showed the wrong characters.

Should I always add the BOM?

Add it when people will open the file in Excel. Leave it off when the file goes to a script, a feed or another system, unless that system asks for it.

Why does the file look fine in Google Sheets but not in Excel?

Google Sheets reads CSV files as UTF-8. Excel decides by itself and, without a BOM, may use the legacy code page of your system.

The characters are right, but everything is in one column. What now?

That’s the delimiter, not the encoding. Excel expects the list separator of your regional settings. Export with Semicolon as the delimiter, or choose the delimiter in Data → From Text/CSV.

Can I import a CSV that was saved in Windows-1252?

Yes. In the import file settings, set File encoding to Windows-1252 (Western European) instead of Detect automatically if accents come out wrong in the preview. Windows-1250, Windows-1251, ISO-8859 and UTF-16 files are supported too.

Get the free plugin on WordPress.org.

Dmitriy
About author

Dmitriy

WordPress Developer with 15+ years of commercial experience. Elite Author on ThemeForest and creator of custom WordPress plugins. Passionate about clean code, performance optimization, and building useful tools for the WordPress community.

JOIN THE CONVERSATION

Comments 0

Have a question or a tip to share? Leave it below.

Leave a comment

Your email address will not be published. Required fields are marked *

We store your name, email and comment to show and moderate it; your email is never published. Spam protection is provided by Cloudflare Turnstile and profile pictures by Gravatar. See our Privacy Policy.


Try the plugin with no risks!

New users get 1 month with access to all premium features. Experience the most powerful WordPress data engine today.

Download Now
Get PRO for FREE