URL Encoder / Decoder

Encode or decode query strings safely to fix broken parameters. Instant, browser-only, copy-ready output.
🔒 Browser-only ⚡ Live transform 📋 Copy-ready 🧩 Query-safe
Step 0 Load a sample (optional)
Step 1 Paste URL / query
Step 2 Choose mode
Step 3 Copy output

Examples

Click “Load example” to paste a realistic scenario (broken UTMs, query-only, already encoded…).
Tip: use Query-only mode to encode only parameters while keeping the base URL intact.
Privacy: This tool runs locally in your browser. Your input stays on your device — no uploads, no account, no server processing. Read details in Privacy.
Status ⚠️ Paste a URL or query string
Encode or decode query strings safely to fix broken parameters.
Input length
0
Output length
0
Unsafe chars
0
Query pairs
0

Related tools

📍 UTM Builder 🔗 Slug Generator 🧾 JSON Formatter

Related guides

🧠 URL Encoding Basics 🎯 Fix Broken UTM Parameters 🧩 Query String Best Practices

What is a URL Encoder / Decoder?

A URL Encoder converts unsafe characters (spaces, symbols, Unicode) into %XX sequences so links remain valid and don’t break tracking parameters. A URL Decoder does the opposite — it turns encoded text back into readable strings.

When should you use it?

Encode vs Query-only mode

Use Encode for a single value or when you want a safe URL component. Use Query-only to keep the base URL intact and encode only parameters — ideal for “broken query strings”.

FAQ

Does this tool upload my URL or data?
No. It runs locally in your browser. Your input stays on your device.
Why does “+” sometimes mean space?
Some query strings use + instead of %20 for spaces. Toggle “+ as space” to match that format.
Will decoding break my URL?
Decoding just makes it readable. If you need a valid link again, encode the values afterward.
Is Query-only safe for UTMs?
Yes. It encodes keys and values while keeping the base URL unchanged — perfect for UTM fixes.

SEO search intents (what people look for)

These intent clusters help users find the right tool fast. They’re here to match real needs (debugging, analytics, parameter fixes) — not keyword stuffing.

🔥 Most common queries

High-intent searches people type when they need URL encoding right now.

url encoder url decoder encode url online decode url online encode query string decode query string percent encoding encode spaces in url encode special characters fix broken url parameters utm parameter encoding url encode unicode browser url encoder no upload url encoder
Tip: For more traffic, publish short guides for each cluster and link them here (you already have Guides in your nav).
📍 UTM Builder 🏷️ Meta Tags 🧾 JSON Formatter 🧠 Browse guides

🎯 Long-tail questions

Question-style searches that rank easier and convert well.

how to encode a url how to decode a url what is url encoding why does url have %20 how to fix broken query params encode utm parameters with spaces difference between %20 and + how to encode unicode in url how to encode & and = how to encode url for api how to decode percent encoding query string encoding best practice
Pro move: Create 6–10 focused guides (1 topic each) and link them in “Related guides”.

🧩 Query clusters (use-cases)

Grouped by intent. Each cluster can become a mini guide later.

fix utm parameters (analytics) encode newsletter links (email) encode ad urls (ads) decode tracking links (analytics) api query encoding (dev) encode unicode / emoji (international) percent encoding table (reference) encode spaces in query (params)
Keep it clean: one guide per intent beats a huge keyword dump. Internal linking wins.

✅ Mini guidance

Quick rules that prevent broken links:

Space → %20 (or + in forms) & and = must be encoded in values Keep base URL intact (Query-only) Decode to audit tracking links Browser-only • no uploads
Scaling idea: Add a guide like “Fix Broken UTMs” and link it in the right column — super high intent.
Last updated: 2026-01-30 · Browse all tools