Percent-encode or decode URLs, query strings, and components with UTF-8 support, plus-versus-%20 handling, and batch processing for web projects offline.
Part of our Developer Tools collection — Explore more Developer Tools tools · See also: JSON Formatter, Base64 Encode / Decode.
Quick answer: URL Encoder / Decoder — Encode & decode URL components Free, no signup, runs in your browser. See below for the interactive tool, 4-step guide and FAQs.
Deep dives from the Tool4SaaS blog — tested workflows, print sizes and fixes.
Reviewed by the Tool4SaaS Editorial Team — In-house reviewers who build and test every tool locally for accuracy across current Chrome, Edge, Firefox, and Safari. Last updated: . See our authors, methodology or contact us.
Encode whenever text enters addresses, query strings, or form payloads where reserved marks would fracture routing. For illustration, a and b with ampersand becomes a percent 26 b, gaps become percent 20, and cafe accent becomes caf percent C3 A9 through UTF-8. A 2000-character address holding 40 symbols transforms instantly, preserving clicks, shares, and API calls.
No. Transformations execute solely inside this tab, so a 50KB query holding 200 parameters never traverses networks. For instance, private tokens remain resident, function. It runs on your side only: no uploads, no copies, nothing left behind. Close the tab to clear entries completely after copying results for tickets.
Select percent 20 for path segments and component values, reserving and solely for HTML form bodies under RFC 3986. For example, gaps encode as percent 20 in queries yet and in forms, while decoding restores both to gaps. Batches of 100 addresses with mixed gaps and emoji convert within a second, letting testers standardize links without manual replacement.
Retain raw letters, digits, hyphen, underscore, period, and tilde; encode everything else, especially ampersand, equals, question, hash, percent, plus, and gaps. For illustration, a value holding a and b and c demands percent shields, otherwise servers split parameters incorrectly. Review server logs for truncated values, then adopt consistent encoding helpers across frontend and backend codebases.
Percent encoding converts reserved marks into percent and two hex digits so addresses survive transit without fracturing. Example 1: a and b with ampersand becomes a percent 26 b, preserving single parameter integrity across gateways. Example 2: cafe accent becomes caf percent C3 A9 via UTF-8, while gaps become percent 20 for reliable sharing. A 2000-character address holding 40 symbols transforms within milliseconds, aiding developers, bloggers and QA engineers validating query strings. Path segments, matrix parameters, and fragment identifiers each demand distinct handling, yet core percent logic remains uniform. Overlooking encoding invites truncated requests, misrouted filters and corrupted search terms that frustrate visitors during checkout flows. Consistent helpers across frontend and backend prevent double escapes and ensure analytics capture clean campaign values daily.
Source text first maps to UTF-8 bytes, then every reserved byte becomes percent and hex for transmission. Reference mapping table: gap is percent 20 in paths | and sign is percent 2B in values | ampersand is percent 26 dividing params | equals is percent 3D joining pairs | hash is percent 23 starting fragments | non-ASCII cafe e is percent C3 A9 bytes. Use percent 20 inside paths and components and only inside form bodies per RFC 3986. Edge case: decoding and as gap in wrong context corrupts literal and signs in passwords, so confirm body type before conversion. Batch 100 addresses with emoji and gaps to verify consistent behavior before shipping integrations across browsers. Mismatched helpers that encode twice turn percent 25 into percent 2525, breaking signatures that require exact single-pass representation.
Paste address site com query q equals a and b, press Encode to receive a percent 26 b, press Decode to restore original for verification. Second trial: encode cafe and napkin phrase, observe percent C3 A9 sequences, decode to confirm round trip integrity. Limitation: extremely long 8000-character addresses may truncate inside legacy browsers, double encoding percent 25 fractures links, and encrypted tokens pasted on shared screens risk exposure. For segment inspection after encoding, see the parser at /url-parser for host path and query breakdowns. For opaque secrets requiring concealment rather than transit safety, see the encoder at /base64-tool for alternate handling. Test encoded decoded pairs across Chrome, Firefox and Safari to catch inconsistent gap handling before production release daily. Document chosen conventions for teammates.