Aller au contenu principal
MyIPKit— Votre réseau, expliqué.

Encoder and decoder

Convert text to and from the encodings that turn up in URLs, headers, logs and markup: Base64, percent-encoding, hex, HTML entities, Unicode escapes and Punycode domain names. Nothing is sent.

S'exécute entièrement dans votre navigateur — rien n'est envoyé nulle part
Encode

Text is turned into UTF-8 bytes first, as almost every system does. Base64 is an encoding, not encryption: anyone can decode it.

Paste encoded text and the right decoder is picked for you.

S'exécute entièrement dans votre navigateur — rien n'est envoyé nulle part

Which encoding is this?

  • Base64 — letters, digits, + and /, often ending in = or ==. Base64URL uses - and _ instead.
  • Percent-encoding — %20, %3D and so on, in URLs and form data.
  • HTML entities — &, <, ', in page source and templates.
  • Unicode escapes — \u00e9, in JSON, JavaScript and logs.
  • Punycode — labels starting xn--, the DNS form of a domain like 한국.kr.

Is Base64 a way to hide something?

No. It only makes bytes safe to carry in text; anyone can reverse it in a second. To keep something secret, use the encryption tool.

Why does my Base64 differ from another tool’s?

Usually the character encoding: this tool encodes text as UTF-8, while some older tools use Latin-1 or UTF-16. A trailing line break in the input also changes the result.

Is what I paste sent anywhere?

No. Encoding and decoding happen in your browser, and HTML is never rendered.