Fix garbled characters in imported files

Prompt that finds where text gets garbled on its way from file to database and sets one encoding rule. Paste it into an AI tool of your choice, which then fixes the garbled characters.

Topic: Apps & prototypes
Type: Prompt
Level: Intermediate
Time: about 15 min

Results depend on the tool, the model and what you enter.

Result preview

Example: written by our editors, not real AI output.

Fill in

What you type stays in this browser window. We store and send nothing.

FileWhat kind of file?

SymptomWhat do you see?

PathWhere does the text go?

Your prompt

Help me fix garbled characters in imported or exported text.
File: [File]
Symptom: [Symptom]
Path: [Path]
Approach: 1. Compare a few broken strings with the correct text and name the likely mix-up, such as UTF-8 read as Latin-1 or a file saved twice. 2. Trace each step the text passes through: file, upload, parser, application, database, export. 3. Find the step where the encoding is guessed or changed, including byte order marks and spreadsheet defaults. 4. Propose one encoding for the whole path and the exact settings for reading and writing. 5. Explain whether already stored data can be repaired and how to test the repair on a copy first. 6. Write a short test with names and symbols that break most often.
Output: diagnosis with examples, list of steps with their encoding, fix per step, repair plan and test strings.

Take particular care to find the one step that changes the encoding and repair on a copy first.

Before you answer, check: Are all instructions met? If key information is missing or a placeholder in square brackets is still in the text, ask instead of guessing. Mark assumptions as assumptions.

Help me fix garbled characters in imported or exported text.
File: [File]
Symptom: [Symptom]
Path: [Path]
Approach: 1. Compare a few broken strings with the correct text and name the likely mix-up, such as UTF-8 read as Latin-1 or a file saved twice. 2. Trace each step the text passes through: file, upload, parser, application, database, export. 3. Find the step where the encoding is guessed or changed, including byte order marks and spreadsheet defaults. 4. Propose one encoding for the whole path and the exact settings for reading and writing. 5. Explain whether already stored data can be repaired and how to test the repair on a copy first. 6. Write a short test with names and symbols that break most often.
Output: diagnosis with examples, list of steps with their encoding, fix per step, repair plan and test strings.

Take particular care to find the one step that changes the encoding and repair on a copy first.

Before you answer, check: Are all instructions met? If key information is missing or a placeholder in square brackets is still in the text, ask instead of guessing. Mark assumptions as assumptions.

This is an instruction for an AI, not the result itself.

Where this prompt works

These AI tools are a good fit for this prompt:

How to use it

Fill in the fields or tap a suggestion. Leave out names, addresses and other personal data.
Copy the finished prompt into an AI tool of your choice.
Paste three to five broken strings next to the correct text; replace personal names with similar invented ones that contain the same characters.

Why does this work?

Garbled text looks chaotic, but each pattern points to one specific mix-up. Once the step is found, one setting usually fixes it.

Tips

Repair stored data on a copy first and keep a backup of the original.

You may use our prompts freely, including at work. Please do not republish them as your own collection. We give no warranty for AI results; check them yourself. Terms of use

Fix garbled characters in imported files

Result preview

Fill in

Your prompt

Where this prompt works

How to use it

Why does this work?

Tips

Also a good fit

Choose pagination for an API list New

Write an API reference people can use right away New

Plan a throttled data backfill New