YurlieEncoding & Security Tools
4 free utilities for encoding, decoding, escaping, and inspecting web payloads. 100% privacy-first and client-side.
Base64 Encoder / Decoder
Encode and decode Base64 strings instantly
URL Encoder / Decoder
Encode and decode URLs and query string parameters
JWT Decoder
Decode and inspect JSON Web Token header, payload, and claims
HTML Encoder & Decoder
Encode special characters to HTML entities or decode entities back to text
Secure, In-Browser String Serialization & Token Inspection
Data transformation is an everyday necessity for software developers building web APIs, integrating third-party OAuth2 providers, or sanitizing user inputs against Cross-Site Scripting (XSS). However, pasting authorization headers or customer data into random online converters poses severe security risks.
Yurlie's encoding suite provides a zero-risk alternative. Every utility runs in your browser sandbox: decode JWT payloads to verify claim expiration, encode binary files to Base64 data URLs, format URL query strings safely, or escape HTML markup without ever transmitting bytes across the network.
Frequently Asked Questions
What encoding and decoding tools are available on Yurlie?
Yurlie features 4 essential encoding tools: Base64 Encoder / Decoder (standard and URL-safe Base64), URL Encoder / Decoder (percent-encoding for query params), JWT Token Decoder (inspect header, payload claims, and expiration client-side), and HTML Entity Encoder / Decoder (escape XSS special characters).
Is it safe to paste confidential bearer tokens or API strings?
Yes. Unlike standard online decoder websites that transmit your inputs to a remote server, Yurlie executes all string transformations and cryptography in your browser. Sensitive JWT bearer tokens, auth cookies, and private text never touch any external server.
Does the Base64 tool support URL-safe encoding?
Yes. You can toggle between standard RFC 4648 Base64 (using + and /) and URL-safe Base64 (using - and _ without padding), making it ideal for web tokens and query parameters.
Can the JWT Decoder verify token signatures?
The JWT Decoder inspects the decoded header and payload claims (sub, exp, iat, roles) and checks expiration status. Because signature verification requires your private secret key, we intentionally avoid requesting your secret key to guarantee zero security exposure.