Back Encoding & Conversion

Encoding & Conversion Tools — 11 Free Browser Utilities

11 free encoding and data-conversion tools — Base64, URL encoder, hex to RGB, HTML entities, image to Base64, JSON to CSV, YAML to JSON, number base, px to rem. Browser-only, no upload, no signup.

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

Best free encoding tools for 2026 — what every developer needs

Encoding bugs are the most-reported root cause in API integration tickets across StackOverflow's 2025 developer survey: percent-encoding mismatches in URL parameters, double Base64 in JWT payloads, mojibake from UTF-8/Latin-1 confusion, and broken data URIs. The 11 tools in this category cover every encoding format a developer actually meets in 2026 — from the bedrock RFC 3548 Base64 to the modern color tokens used in CSS custom properties. Each tool runs entirely client-side via the browser's native APIs (btoa/atob for Base64, encodeURIComponent for URL, FileReader for image-to-data-URI), so confidential payloads never leave the page.

What's the difference between encoding, encryption, and hashing?

The three terms are routinely confused, and the confusion has security consequences. Encoding (Base64, URL-encoding, HTML entities) is reversible and uses no secret — anyone with the encoded string can decode it. Its purpose is data transport, not secrecy. Encryption (AES, RSA, ChaCha20) is reversible only with a key and is for confidentiality. Hashing (SHA-256, BLAKE3) is one-way and used for integrity or fingerprinting — see the Hash Generator for the latter. Treating Base64 as encryption is the #1 entry-level security bug; never put a secret value in a Base64 string and consider it "protected".

Which encoding format do I use for which job in 2026?

Use case	Format	Tool
Binary in JSON / JWT / email	Base64	Base64 Encoder
Special characters in URL path / query	Percent-encoding (RFC 3986)	URL Encoder
Embedding tiny images in HTML/CSS	data: URI (Base64)	Image to Base64
HTML / XML special characters	HTML entities (named or numeric)	HTML Entity Encoder
Color value in JS / CSS variable	Hex / RGB / HSL / OKLCH	Hex to RGB Converter
API response to spreadsheet	CSV	JSON to CSV
Docker Compose ↔ Kubernetes manifest	YAML / JSON	YAML to JSON
Bitwise / color math	Binary / decimal / hex / octal	Number Base Converter
Responsive font / spacing tokens	px ↔ rem	Pixel to REM
Storage / bandwidth math	KB / KiB / MB / MiB	Byte Converter
Database timestamp ↔ readable date	Unix epoch	UNIX Timestamp Converter

How do I encode strings online without uploading them to a server?

Every tool in this category runs in your browser. The encoding pipeline (btoa(unescape(encodeURIComponent(...))) for UTF-8-safe Base64, native encodeURIComponent for percent-encoding, FileReader.readAsDataURL for image data URIs) executes on the local thread — confidential strings never leave the page, and you can verify this by opening DevTools → Network tab and observing zero requests on encode. Avoid online encoders that require an upload or POST your input to a server endpoint; this is the most common pattern in ad-funded "free encoder" sites that index for the same keywords.

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