Back Encoding & Conversion

Encoding & Conversion Tools

Transform, encode, and convert data between formats with these free browser-based tools. Whether you need to encode text to Base64, percent-encode URLs for safe transmission, convert hex color codes to RGB values, escape HTML entities, embed images as data URIs, export JSON to CSV for spreadsheets, or switch between binary, decimal, and hexadecimal number systems — every conversion runs entirely client-side with zero server calls and no signup required.

11 Encoding & Conversion Tools

b64

Base64 Encoder / Decoder

Encode text and files to Base64 or decode Base64 strings instantly.

Popular

⏱

UNIX Timestamp Converter

Convert between UNIX timestamps and human-readable dates. Live clock included.

URL Encoder / Decoder

Percent-encode and decode URLs, query parameters and special characters.

🎨

Hex to RGB Converter

Convert hex color codes to RGB, RGBA and HSL with live preview and sliders.

HTML Entity Encoder / Decoder

Encode special characters to HTML entities or decode entities to text.

🖼

Image to Base64 Encoder

Convert images to Base64 data URIs for embedding in HTML, CSS and emails.

CSV

JSON to CSV Converter

Convert JSON arrays to CSV. Flatten nested objects, download for Excel or Sheets.

Number Base Converter

Convert between binary, octal, decimal and hexadecimal. Supports any base 2-36.

Y→J

YAML to JSON Converter

Convert between YAML and JSON formats instantly.

Byte / Data Size Converter

Convert between bytes, KB, MB, GB, TB and more.

rem

Pixel to REM Converter

Bidirectional px ↔ rem ↔ em with adjustable base.

New

Which encoding tool should you use?

Each encoding format solves a specific compatibility problem — sending binary through ASCII-only channels, putting special characters in URLs, embedding images without external requests. Picking the wrong format can corrupt data, leak characters, or bloat payloads by 33% unnecessarily. Use this quick guide to match the task to the right tool.

Send binary data through ASCII-only channels (email attachments, JSON payloads, JWT tokens) — use Base64 Encoder.
Put text in a URL or query parameter safely (search params, API endpoints, redirects) — use URL Encoder. URL encoding ≠ Base64.
Embed an image directly in HTML/CSS (avoiding extra HTTP requests for tiny icons) — use Image to Base64. Best for sub-10KB assets only.
Display HTML special characters as text (preventing XSS, showing <code> in posts) — use HTML Entity Encoder.
Convert hex colors to RGB/HSL for JS or CSS variables — use Hex to RGB Converter.
Export JSON API responses to a spreadsheet — use JSON to CSV Converter.
Convert YAML configs to JSON (or vice versa, e.g. Docker Compose ↔ k8s manifests) — use YAML to JSON Converter.
Switch between binary, decimal, hex, octal (bitmask debugging, color math) — use Number Base Converter.
Convert pixel values to rem for responsive design — use Pixel to REM Converter.
Compare data sizes across binary (KiB) vs decimal (KB) units — use Byte Converter.
Convert UNIX timestamps to readable dates — use UNIX Timestamp Converter.

Common encoding mistakes to avoid

Encoding twice. Base64-encoding a value that's already Base64 produces gibberish on decode. Check your data layer before re-applying.
Confusing URL encoding with Base64. Spaces become %20 in URLs, not IA==. Use the right tool — they're not interchangeable.
Embedding huge images as Base64. Data URIs add 33% overhead. For anything over 10KB, a regular <img src> request is faster.
Trusting Base64 as encryption. Base64 is encoding, not encryption — anyone can decode it. Use proper crypto for secrets.
Mixing up KB (1000) vs KiB (1024). Storage vendors use KB; OSes show KiB. A "500 GB" drive is ~465 GiB to your filesystem.

Frequently Asked Questions

Data encoding is the process of converting information from one format or representation into another. Developers rely on encoding to safely transmit data across systems that may not support certain characters — for example, Base64 encoding lets you embed binary data in text-based formats like JSON or HTML, while URL encoding ensures special characters in query strings are transmitted correctly. Encoding is essential for APIs, web forms, email attachments, and anywhere data crosses system boundaries.

Encoding transforms data into a different format for compatibility or transport — it is fully reversible and uses no secret key (e.g., Base64, URL encoding). Encryption transforms data to keep it confidential, requiring a secret key to reverse (e.g., AES, RSA). Hashing produces a fixed-length fingerprint of data that cannot be reversed, used for integrity checks and password storage (e.g., SHA-256, MD5). In short: encoding is for format, encryption is for secrecy, and hashing is for verification.

It depends on the context. Use URL encoding (percent-encoding) for query parameters and form data. Use Base64 when you need to embed binary data like images in HTML or CSS via data URIs. Use HTML entity encoding to safely display special characters like <, >, and & in web pages and prevent XSS vulnerabilities. For data exchange between systems, JSON is the standard — and when you need tabular output, converting JSON to CSV is the way to go. Each format serves a specific purpose in the web development workflow.

Other Categories