URL Encoder and DecoderEncode components and inspect query strings
en

AppHelp

Encode, decode, and inspect URL-safe text

Convert reserved characters safely and break query strings into readable key-value rows.

Encoded or decoded output
name%3DAppHelp%20tools%26mode%3Dlocal

Query parameters

nameAppHelp tools
modelocal

Common tasks

  • url encoder and decoder online
  • free url encoder and decoder
  • url encoder and decoder no upload
  • browser local url encoder and decoder
  • url encoder and decoder for developers
  • encode url tool
  • decode url tool
  • query url tool

Quick answer

URL encoding, also called percent encoding, converts reserved characters into %HH byte sequences so text can safely appear inside URLs and query strings. This tool encodes URL components, decodes escaped text, and breaks query strings into readable key-value rows locally.

How to use

  1. 1. Paste URL text or a query stringUse a full URL, a query string, or a single component such as a search term, path segment, redirect URL, or callback value.
  2. 2. Choose encode or decodeEncode reserved characters before embedding a value in a URL. Decode percent-escaped text when reading logs, analytics links, or copied API requests.
  3. 3. Inspect parametersWhen the input contains a query string, review the parsed key-value rows to find duplicated keys, nested URLs, tracking parameters, or malformed values.

Examples

Encode a search query

Input
AppHelp tools & privacy
Output
AppHelp%20tools%20%26%20privacy

Decode percent-escaped text

Input
redirect=https%3A%2F%2Fapphelp.net%2Fen
Output
redirect=https://apphelp.net/en

Inspect query parameters

Input
https://example.com/?utm_source=newsletter&q=json%20formatter
Output
utm_source: newsletter
q: json formatter

Common use cases

  • Encode redirect URLs, search terms, callback values, and API query parameters
  • Decode analytics links, copied URLs, and server log entries
  • Inspect UTM tags and query parameters before sharing a campaign URL
  • Debug broken links caused by unescaped spaces, ampersands, hashes, or nested URLs

Edge cases

  • A full URL and a single URL component require different encoding rules
  • Spaces may appear as %20 or + depending on form/query-string context
  • A malformed percent escape such as %ZZ cannot be decoded safely
  • Encoding the same value twice creates nested escapes such as %2520

Features

  • Percent-encode strings for safe URL embedding
  • Decode URL-encoded text back to readable form
  • Optional ‘escape all characters’ mode
  • Browser-local processing

Related tools

UTM BuilderBuild campaign URLs with structured UTM parameters.Query String to JSONConvert query parameters into structured JSON.JSON String Escape / UnescapeEscape string values before embedding them in JSON request bodies.cURL to FetchConvert API requests after checking encoded URLs.

Frequently asked questions

What does it encode?
Reserved URL characters by default. Toggle ‘escape all’ to percent-encode every byte for the strictest output.
Does it handle Unicode?
Yes. UTF-8 bytes are percent-encoded so non-ASCII characters round-trip correctly through encode and decode.
Is my URL uploaded?
No. Encoding and decoding both run in your browser.