digtools
🔤
mojibake fixer,

Mojibake Fixer & Encoding Converter

Fix garbled text (Mojibake) instantly.A browser-based text encoding converter.

🔒️
In-Browser Processing
Nothing is sent to a server
⚡️
No Signup Required
Use instantly without creating an account
✨️
Instant Recovery
Paste text to see all encoding conversions

Text to Restore

0 chars
Drop file to load
about,

What is the Mojibake Fixer?

This free online tool automatically restores garbled (Mojibake) text just by pasting it. It auto-detects all conversion patterns between UTF-8 / Shift_JIS / EUC-JP / ISO-2022-JP and presents the most natural result.

All processing runs entirely in your browser via JavaScript — your sensitive data is never sent to any external server. No registration or login required, so you can use it with complete privacy.

how to,

How to Recover

STEP 1

Enter Text

Paste garbled text into the input area. You can also drag & drop text files (.txt, .csv) with broken encoding.

STEP 2

Check Candidates

All encoding conversion patterns are automatically verified and listed. Look for the result with the "Recommended" badge.

STEP 3

Copy Result

Click the "Copy" button in the correctly restored result block to copy the clean text to your clipboard.

glossary,

Glossary

Mojibake (Scrambled Text)
A phenomenon where the character encoding used to save a text doesn't match the encoding used to read it, resulting in scrambled, unreadable symbols (e.g., "縺ゅ>縺").
UTF-8
The universal character encoding standard of the modern web, encompassing almost all global languages. Often scrambles when mistakenly read by older software using legacy encodings.
Shift_JIS
A legacy character encoding heavily used in older Japanese Windows systems. Opening UTF-8 Japanese text in a Shift_JIS environment causes very specific Mojibake patterns.
EUC-JP / ISO-2022-JP
EUC-JP originates from older Unix/Linux platforms, while ISO-2022-JP (JIS) was the strict standard for early internet emails in Japan. Both can cause decoding mismatches.
Encoding / Decoding
Encoding transforms human-readable text into byte arrays based on a specific standard. Decoding translates bytes back to text. A mismatch during decoding causes Mojibake.
Irreversible Data Loss
When text is scrambled, sometimes bytes are entirely discarded or swapped with a literal "?" symbol by old databases, rendering it mathematically impossible to recover.
Brute-force Analysis
The tool's methodology of exhaustively testing multiple combinations of legacy encoding -> modern decoding vectors to find the one combination that reveals readable text.
faq,

FAQ

Q.Why do some texts fail to recover?
If the scrambled text was re-saved in a destructive format (like ANSI/Windows-1252), missing byte information is permanently lost. Irreversible mojibake cannot be mathematically fixed.
Q.Is it safe to paste and decode confidential work emails?
Yes. The brute-force fixing engine runs entirely client-side via JavaScript. Your text never leaves your workstation or travels to external servers.
Q.What does a pattern like "UTF-8 → Shift_JIS" mean?
It represents the "mistake" that caused the garbled text: The original document was saved in "UTF-8", but the software you are using erroneously opened it assuming it was "Shift_JIS".
Q.How do I know which of the output results is the correct one?
The tool shows attempts from all common encoding combinations. Simply scroll through the output panel and visually identify the block where the Japanese characters become a coherent, legible sentence.
Q.Can this fix the common "縺" scrambling issue?
Yes. The occurrence of characters like "縺" is the hallmark of UTF-8 text incorrectly opened as Shift_JIS. Our tool easily translates this back to correct Japanese.
Q.Can it recover emoji that turned into question marks (?)
Generally, no. If the software did not support emojis and overwrote the 4-byte characters with an actual "?" or "□" character, the original data is destroyed and cannot be recovered.
Q.How can I prevent Mojibake from happening to my team?
Ensure all team members set their text editors, IDEs, databases, and CSV export settings to use the universal "UTF-8" standard to eliminate encoding mismatches entirely.
use cases,

Use Cases

📧

Email Text Recovery

Restore garbled text from emails sent with ISO-2022-JP or Shift_JIS encoding.

📂

CSV File Repair

Fix mojibake in CSV files opened in Excel, including UTF-8 BOM issues.

🌐

Web Data Recovery

Repair garbled text from databases or API responses caused by encoding mismatches.

📋

Legacy System Migration

Convert corrupted text from old systems into proper UTF-8 encoding.

technology,

Technical Details

Why Does Mojibake Occur?

Text data is stored internally as byte sequences. The same bytes produce different characters depending on which encoding rule is used to interpret them. Mojibake occurs when the receiver tries to display bytes written in "Shift_JIS" as if they were "UTF-8".

Common Mojibake Patterns

  • UTF-8 → Shift_JIS misread: Characterized by consecutive kanji like "繧" "縺" "繝". The most common mojibake on the web.
  • Shift_JIS → UTF-8 misread: Contains control or replacement characters. Common in old CSV files.

How This Tool Works & Supported Patterns

All processing uses the modern browser TextDecoder API. It extracts each character's code point from the garbled text and brute-forces decoding across all encoding combinations to find the correct restoration.

  • Single-stage (19 patterns): Restores mojibake caused by one encoding misread (e.g., UTF-8 ↔ SJIS).
  • Multi-stage (10 patterns): Attempts to restore complex chained mojibake from 2+ misconversions (e.g., SJIS→CP1252→UTF-8).