Repair Base64
Base64 often gets mangled when it is copied through JSON, URLs, e-mails or logs. The repair tool applies a series of safe fixes, reports each change, and returns a clean, decodable value.
What the repair tool fixes
- Data URI prefixes (
data:image/png;base64,), PEM headers and surrounding quotes. - JSON or string escapes such as
\n,\/and\u003d. - Percent-encoding (
%2B,%2F,%3D) and spaces that replaced+after URL decoding. - URL-safe characters (
-and_), line breaks, stray symbols and wrong padding.
The repaired value always uses the standard alphabet with correct padding. If the original data was truncated, no tool can recover the missing bytes, but the rest becomes decodable.
Frequently asked questions
Why is my Base64 invalid?
Common causes are spaces or line breaks, "+" turned into spaces by URL decoding, percent-encoded characters (%2B, %2F, %3D), JSON escapes like \/ and \n, missing padding, or a data URI prefix.
Comments (0)
Questions, ideas or a bug in “Repair Base64”? Leave a comment, rate the tool, or reply to others.
No comments yet. Be the first to share your feedback!