URL Encode / Decode
Encode or decode URL strings instantly by pasting text into the input field.
This tool supports percent-encoding commonly used in URLs, making it easy to convert special characters into a safe format
or restore encoded strings back to readable text.
It is useful for building query parameters, checking API request URLs, and debugging encoded values found in logs or configuration files.
With a single click, you can switch between encoding and decoding
and view the result immediately.
All processing is performed locally in your browser.
No input text or results are sent to any server, ensuring fast performance and privacy-safe usage.
URL Encoder and Decoder
URLs often need special characters, spaces, non-English text, and symbols to be percent-encoded. This URL encoder and decoder helps you convert readable text into URL-safe strings and decode encoded values such as %20, %2F, or UTF-8 sequences.
Common use cases
- Debug query strings: Decode parameters from tracking links, API requests, or redirects.
- Prepare safe URLs: Encode search terms, callback URLs, filenames, and form values.
- Inspect copied links: Understand what a long encoded URL actually contains.
Encoding note
Different contexts encode spaces and reserved characters differently. A value that is safe in a query parameter may not be safe in a path segment, so check the exact place where the value will be used.
Articles for this tool
How to URL Encode and Decode Strings for APIs and Query Parameters
Learn what percent encoding means, when to encode URLs, and how to inspect encoded query strings safely during API and tracking-link debugging.
How to Convert URL Parameters to JSON for UTM and API Debugging
Turn long query strings into readable JSON so you can review UTM tags, API filters, duplicated keys, and encoded values more easily—with concrete examples.
URL Mechanics and Parameter Analysis: From Encoding to JSON Conversion
Explore the structure of URLs, the necessity of Percent-Encoding, and efficient ways to handle complex query parameters in web development.
curl Options Cheat Sheet: What -X, -H and -d Actually Do
A reference for the curl options you meet in real API work: why -d already implies POST, how -d differs from --data-raw, the @ prefix that silently reads a file, single vs double quotes, and why -k and -L deserve more caution than they usually get.
Encoding vs Hashing vs Encryption: The Difference and When to Use Each
Base64 encoding, SHA-256 hashing and encryption are constantly confused, yet serve completely different purposes. A comparison table, concrete examples, and the right choice for each use case.
Recent Articles
curl Options Cheat Sheet: What -X, -H and -d Actually Do
A reference for the curl options you meet in real API work: why -d already implies POST, how -d differs from --data-raw, the @ prefix that silently reads a file, single vs double quotes, and why -k and -L deserve more caution than they usually get.
Converting Between JSON Schema and Zod: How required Maps to .optional()
Inside a two-way converter that turns JSON Schema into a Zod schema and Zod code back into JSON Schema. Covers the inverted defaults between required and .optional(), the constraint mapping table, and how the Zod side is parsed without executing any code.
SQL Clause Order Reference: Why WHERE Can't See Your SELECT Alias
The order you write SQL clauses is not the order the database runs them. A reference for the logical execution order (FROM → WHERE → GROUP BY → HAVING → SELECT → ORDER BY → LIMIT), why aliases fail in WHERE, when to use WHERE vs HAVING, and the MySQL/PostgreSQL differences that bite.
Unified Diff Format Reference: Reading @@ Hunks in git diff Output
How to read the unified diff format git produces: what the four numbers in @@ -12,7 +12,9 @@ mean, why a one-character edit shows as a whole-line replacement, the whitespace and line-ending traps, \ No newline at end of file, combined @@@ diffs on merges, and rename detection via similarity index.
UTC to JST Reference: The 9-Hour Offset, Cheat Sheet & Timezone Pitfalls
Convert between UTC and JST (Japan Standard Time) with a cheat sheet. Covers what Z and +09:00 mean in ISO 8601, when JavaScript date parsing silently shifts by 9 hours, MySQL/PostgreSQL timezone behavior, and why GitHub Actions cron always runs in UTC.
CREATE TABLE Reference: MySQL vs PostgreSQL vs SQLite Types & Constraints
A cross-database CREATE TABLE (DDL) reference with cheat sheets for data types, auto-increment keys (AUTO_INCREMENT / IDENTITY / rowid), foreign key ON DELETE behavior, and the CHECK constraint that MySQL silently ignores.