Encode text or files as Base64
Online Encoding & Decoding Tools
Base64, URL encoding, HTML entities, Unicode, binary, JWT and Basic Auth utilities in one place.
A focused entry for everyday encoding, decoding, escaping and token inspection tasks. Handle Base64 text and files, URL parameters, HTML entities, Unicode escapes, binary text, JWT payloads and Basic Auth headers locally in your browser. It also covers case conversion, Roman numerals, the NATO alphabet and color format conversion.
Built for these intents
Check URL query parameter escaping
Display HTML snippets safely
Inspect JWT and Basic Auth API credentials
Tools in this hub
Base64 Encoder / Decoder
Encode text to Base64 or decode Base64 back to plain text with full UTF-8 support. Instant bidirectional conversion with one-click copy for any string.
Base64 to File Converter
Convert any file to a Base64 data URL for embedding in HTML, CSS, JSON or email, and decode Base64 strings back into downloadable original files — all processed locally in your browser.
URL Encoder / Decoder
Encode or decode URL-safe strings using percent-encoding for query params and path segments. Essential for building safe query strings and REST API URLs.
HTML Entities
Encode or decode HTML entities for safe rendering: named and numeric references, decimal and hex codes, ready to copy. Prevents XSS in templating output.
Text to Unicode
Convert text to Unicode escape sequences (\uXXXX) and back for UTF-16. Ideal for debugging encoded strings and inspecting raw code points in one pass.
Text to Binary
Convert text to binary or back via UTF-8 encoding for ASCII and Unicode characters. Handy for low-level debugging, encoding tutorials and CTF puzzles.
JWT Parser
Decode and inspect JWT tokens (header, payload, expiry) with a signature structure check. Inspect auth claims and expiry without sending secrets or keys.
Basic Auth Generator
Turn a username and password into a Base64 credential, Authorization header and curl example for debugging HTTP Basic auth in curl, Postman or a gateway config. Everything runs locally, nothing is uploaded.
Color Converter
Convert colors between HEX, RGB and HSL formats with full alpha channel support. Alpha-aware color translation for CSS, design tools and style guides.
Case Converter
Convert text between camelCase, snake_case, kebab-case, PascalCase and CONSTANT_CASE instantly. Switch naming styles for code, configs and identifiers.
Roman Numeral Converter
Convert between Arabic numbers (1-3999) and Roman numerals instantly. Handy for chapters, outlines, clock faces, movie sequels and classic Roman notation.
Text to NATO Alphabet
Convert text to NATO phonetic alphabet (Alpha, Bravo, Charlie) for clear radio and phone communication. Spell out words letter by letter with confidence.
Suggested workflows
API auth debugging
Decode JWT payloads, generate Basic Auth headers and clean URL parameters.
Frontend escaping
Convert HTML entities, Unicode escapes and URL text to fix display issues.
File embedding
Encode local files as Base64 data URLs and copy them into configs or snippets.
Representation conversion
Convert text between case styles, Roman numerals and the NATO alphabet, and swap color values between formats.
Encoding workflow tips
Know which encoding direction you need
When you hit "garbled text", first decide whether it is URL-encoding, HTML-escaping or Base64 data. Use Base64 for text/file round-trips, the URL encoder for query strings, and HTML entities to display special characters safely in HTML text — three entries for three common debugging cases.
Covers API and frontend friction
Separate URL query from path encoding: spaces in queries are often written as + or %20, while path segments must use %20; form encoding and JSON bodies follow different rules, and mixing them causes misrouted parameters or 404s.
Base64 is transport encoding, not secrecy
Base64 is reversible and anyone can decode it; before putting it in a URL, percent-encode + / = again, and use encryption rather than encoding for sensitive data.
Sensitive data stays local
Tokens, headers and files are processed in your browser rather than sent to a remote service.
Encoding tools FAQ
Is Base64 encryption?
No. Base64 is an encoding format and can be decoded by anyone. It should not be used to protect secrets.
How is URL encoding different from HTML entities?
URL encoding is for addresses and query strings, while HTML entities are for safely displaying special characters in HTML.
Does JWT parsing verify signatures?
It decodes the header and payload by default; enter an HMAC key to verify HS256/384/512, while RS/ES need a public key on the server. A successful parse does not make the token valid.