# loopio csv import failed encoding error: how to fix it

A Loopio CSV import encoding error means the file isnt really UTF-8, even if Excel claims it is. Open it in a plain text editor, re-save as UTF-8, and import again. Smart quotes and accented characters are the usual culprits, and they turn into garbage or kill the import.

```text
loopio csv import failed encoding error
```

## When to use this skill
- CSV import fails with an encoding error
- Imported text shows garbled characters

## When not to use this skill
- The import fails on column mapping (different skill)
- The file imports but rows are misaligned (delimiter issue)

## Tool compatibility
Loopio cloud. CSV library imports.
Related area: business SaaS platforms and vendor portals.
Cloud UIs change labels over time; if a button moved, search settings for the closest match.

## Before you start
- Sign in to the tool and keep one tab open so sessions stay clean
- Copy the exact error text and note the time it happened
- Set aside 15 to 20 minutes; most of these resolve in a single pass

## Quick diagnosis
Make sure this is the right skill before you invest the 15 minutes.
- If you are dealing with cSV import fails with an encoding error, start at step 1 below.
- If instead the import fails on column mapping (different skill), stop here; you need a different skill.
- If neither quite matches, compare your screen against the verbatim error block at the top; that block is exactly what this skill covers.

## Fix it in steps
### 1. Look at the raw bytes

```
Open the CSV in a plain text editor and scan for mojibake like black diamonds or odd symbols.
```
Expected: you spot garbled characters, usually around quotes, dashes, or accented letters.

### 2. Re-save as UTF-8

```
In your editor or spreadsheet app, explicitly save or export as CSV with UTF-8 encoding.
```
Expected: the file reopens cleanly with all characters rendering correctly.

### 3. Re-import into Loopio

```
Upload the re-saved file through the normal import flow.
```
Expected: import completes and special characters display correctly in the entries.

## Confirm each step worked
Run through this checklist before moving on. If a check fails, redo that step instead of pushing ahead.
- Step 1 (look at the raw bytes): Expected: you spot garbled characters, usually around quotes, dashes, or accented letters.
- Step 2 (re-save as utf-8): Expected: the file reopens cleanly with all characters rendering correctly.
- Step 3 (re-import into loopio): Expected: import completes and special characters display correctly in the entries.

## Quick recap
1. Look at the raw bytes
2. Re-save as UTF-8
3. Re-import into Loopio

## Still stuck?
Gather three things: the exact error text, the time it happened, and what changed just before it broke.
Check the vendor status page for an active incident. Then open a support ticket with those three things;
it cuts the back-and-forth in half. For agent runs, attach the last 50 lines of the agent log too,
since the loop or timeout signature in the log usually names the cause.

## Variant phrasings
### loopio csv import garbled text
Same encoding fix, the file was probably saved as Windows-1252. If this matches what you saw, the steps above apply as written.

### csv encoding error loopio import
Excel on Windows defaults to a legacy encoding, always re-export explicitly. If this matches what you saw, the steps above apply as written.

## Why it happens
Spreadsheets often save CSVs in a legacy Windows encoding while claiming nothing about it. Loopio reads the file as UTF-8, so every byte outside plain ASCII gets misread and the import aborts.

## Edge cases
- BOM headers are fine, Loopio handles them
- Tab-separated files renamed to .csv confuse the parser, fix the extension
- Emoji in answers survive UTF-8 fine, they only break in legacy encodings

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_jdAeZ6-9IHJoRKRE4O5HEQ