Data Import & Export

Fix SQLite GUID Values Looking Different After Importing to Excel

WPS Content ManagerWPS Content Manager Oct 10, 2026 869 views

Question details

Users notice that GUIDs imported from an SQLite database into Excel display in an unrecognized hexadecimal format rather than the standard GUID format.

How to Fix SQLite GUID Values Looking Different After Importing into Excel
Product
Microsoft Excel
Device & OS
not provided
Scenario
Importing data from an SQLite database into Excel using Power Query and an SQLite ODBC driver.
Observed behavior
Standard GUIDs, such as {1bc8e695-b9F3-47BD-BFFF-382EF635B7F6}, unexpectedly appear as hexadecimal values like X'95E6C81BF3B98D47BEFFF382EF635B7F6' in the spreadsheet.
Before you start

Ensure that you have installed the correct and latest SQLite ODBC driver for your system, and verify that you have access to the Power Query Editor in your Excel workbook.

Solution 1Recommended

Convert the GUID Column to Text in Power Query

Use the Power Query Editor to explicitly define the data type of the GUID column as Text before loading it into your Excel worksheet.

Because SQLite often stores GUIDs as 16-byte binary data, Power Query may misinterpret the binary string and default to displaying it as a hexadecimal value. Forcing a text conversion inside Power Query ensures it reads the identifier as a standard string.

1
Open Power Query Editor

In Excel, navigate to the 'Data' tab on the ribbon, click on 'Get Data', and select 'Launch Power Query Editor' to view your current database connection.

2
Select the GUID Column

Scroll horizontally through your data preview to locate the specific column that contains the hexadecimal GUID values.

3
Change Data Type to Text

Right-click the column header, navigate to 'Change Type', and select 'Text'. If prompted to replace the current step or add a new one, choose to add a new step.

4
Close and Load

Click the 'Close & Load' button in the top-left corner of the Power Query Editor to apply the transformation and load the corrected text values into your Excel worksheet.

Convert the GUID Column to Text in Power Query
Format Preserved: The GUIDs should now display correctly without the X prefix, retaining their original alphanumeric string structure.
Free Microsoft Office alternative

Try WPS Office for Seamless Data Handling

If you frequently encounter complex formatting errors and database connection issues in Microsoft Office, consider switching to WPS Office. It provides a highly compatible, lightweight, and user-friendly spreadsheet environment that perfectly handles large datasets and complex CSV exports.

  1. 1. Download and Install: Visit the official WPS Office website to download the free installer for your operating system.
  2. 2. Open Your Data File: Launch WPS Spreadsheet and go to Menu > Open to import your existing .xlsx or .csv data files.
  3. 3. Format Data Easily: Use the intuitive Data tab in WPS to quickly format text, split columns, and manage external data effectively.
Full compatibility with Microsoft Excel formats (.xlsx, .xls, .csv)Lightweight application that loads large datasets quicklyFamiliar user interface requires no learning curveRobust data formatting and filtering toolsCompletely free alternative to expensive software subscriptions
microsoft office alternative - wps office

Frequently Asked Questions

Why do SQLite GUIDs change to hexadecimal when imported into Excel?

SQLite often stores GUIDs as 16-byte binary data (BLOB). When Power Query and the SQLite ODBC driver read this binary data, they translate the raw bytes into a hexadecimal string representation (starting with X) instead of a formatted string.

Does the hexadecimal representation mean my data is corrupted?

No, the underlying data is completely intact. The standard formatted GUID and the hexadecimal X value are just two different text representations of the exact same underlying byte sequence.

Can I format the hexadecimal GUID back to the standard format using Excel formulas?

Yes, you can use Excel text manipulation functions like MID, LEFT, and RIGHT combined with CONCATENATE to parse the hexadecimal string, remove the X prefix, and manually insert hyphens to recreate the standard GUID format.