Text Encoder/Decoder Tool

Support Base64, URL, Unicode, HTML entity encoding/decoding, JWT Token parsing, base conversion and more

Encode/Decode Operations

Base64

URL

Unicode

HTML Entity

JWT Token

Base Conversion

Usage Guide

Base64 Encode/Decode

Convert text or binary data to ASCII string format, commonly used for data transmission and storage.

Use cases: Email attachments, data URLs, API transmission

URL Encode/Decode

Convert special characters in URLs to percent-encoded format to ensure correct URL transmission.

Use cases: URL parameters, query strings, link generation

Unicode Escape/Unescape

Convert Unicode characters to \uXXXX format, commonly used in JavaScript and JSON.

Use cases: JSON data, JavaScript strings, internationalization

HTML Entity Encode/Decode

Convert HTML special characters to entity references, preventing XSS attacks and display errors.

Use cases: HTML content, XSS prevention, special character display

JWT Token Parser

Parse JWT Token's header and payload parts, view token content (does not verify signature).

Use cases: API debugging, token analysis, development testing

Base Conversion

Support conversion between decimal, hexadecimal, and binary.

Use cases: Programming calculations, color codes, low-level development

Encoding/Decoding Guide

Base64: Image Embedding

Use: Embed small images in HTML/CSS without external files.
Note: Not encryption! Anyone can decode. Size increases ~33%.

URL: Chinese Characters

Use: Encode Chinese/special chars in URLs.
Example: "搜索" → %E6%90%9C%E7%B4%A2

JWT: Token Debugging

Use: Parse JWT to view user info, permissions, expiry.
Tip: Check "exp" field to verify if token expired.

HTML Entities: XSS Prevention

Use: Encode < > & " to prevent XSS attacks.
Security: Always encode user input before display.

Quick FAQ

Is Base64 encryption?

No! Base64 is encoding, not encryption. Anyone can decode it. Use AES/RSA for actual encryption.

JWT parse failed - why?

Check: 1) Token has 3 parts separated by dots, 2) No extra spaces/line breaks, 3) Starts with "eyJ".

All operations reversible?

Yes! Encode/decode pairs are fully reversible: Base64, URL, Unicode, HTML entities - 100% data recovery.

🔒 Technology & Privacy

Tech

  • • Native atob/btoa APIs
  • • encodeURIComponent for URL
  • • Regex for HTML entities
  • • RFC 4648 compliant Base64

Privacy

  • • 100% local processing
  • • Safe for tokens & secrets
  • • No upload, no logging
  • • Open source code

Performance: Base64 10KB <20ms, URL encode/decode <10ms, JWT parse <50ms, base conversion <5ms.