URL Encode

Encode URL components or full URLs, with plus-space and per-line options.

URL Input
Encoded Output
0 characters 0 lines

What does URL Encode do?

URL Encode percent-encodes text so reserved or non-ASCII characters can be placed safely in URLs.

  • Primary use: URL Encode percent-encodes text so reserved or non-ASCII characters can be placed safely in URLs.
  • Key technical fact: Percent-encoding represents bytes as %HH, where HH is a 2-digit hexadecimal value.
  • Practical check: Validate the result before using it in authentication, signing, checksum, or transport code.
Topic Direct answer Source
Direct answer URL Encode percent-encodes text so reserved or non-ASCII characters can be placed safely in URLs. WHATWG URL Standard
Key fact Percent-encoding represents bytes as %HH, where HH is a 2-digit hexadecimal value. WHATWG URL Standard
Processing model Runs locally in the browser; no production Node server receives the input. Browser JavaScript

Encode text safely for URLs and query strings

This URL encoder converts spaces, Unicode text, reserved separators, and unsafe characters into percent-encoded form. Use it when building query parameters, redirect values, callback URLs, form submissions, API requests, or links that include user-provided text.

Percent-encoding represents bytes as %HH, where HH is a two-digit hexadecimal value. Component mode encodes separators such as & and =; full URI mode keeps URL structure characters such as :, /, ?, and & readable.

How to use

  1. Paste the text, path, query value, or URL you want to encode.
  2. Choose component mode for query values or full URI mode for an entire URL.
  3. Enable plus-style spaces or line-by-line encoding when your target system needs it.
  4. Click Encode URL, then copy or download the encoded result.

What is URL encoding?

URL encoding, also called percent-encoding, makes characters safe for placement inside a URL by replacing them with percent escapes. For example, a space can become %20, and form-style query strings may use + for spaces.

Use component encoding for a single query value, search term, token, or redirect parameter. Use full URI encoding when you already have a complete URL and want to preserve its scheme, slashes, path separators, and query structure.

Input notes

Do not double-encode unless the receiving system specifically expects it. If text already contains sequences such as %2F, encoding it again will turn the percent sign into %25.

Example

A search phrase with spaces and separators becomes safe as a query parameter value:

Input
hello world & tea=green

Component output
hello%20world%20%26%20tea%3Dgreen

With + spaces
hello+world+%26+tea%3Dgreen

MCP integration

MCP (Model Context Protocol) lets AI agents and apps discover and run Coding.Tools utilities for repeatable conversions, formatting, hashing, and generation workflows.

MCP tool name: url-encode

MCP endpoint: https://coding.tools/mcp

Call tools/list first. Each tool entry includes inputSchema, outputSchema, and examples so an AI agent or client can build valid arguments without guessing.

For tools/call, read result.content[0].text for the display value and result.structuredContent for machine parsing. Tool-level failures return isError: true; protocol failures return a JSON-RPC error.

Example tools/call request:

curl -s https://coding.tools/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "MCP-Protocol-Version: 2025-06-18" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"url-encode","arguments":{"input":"hello world & tea=green","options":{"mode":"component","spaceAsPlus":false}}}}'

Most text and data tools accept an input string plus optional options. Browser-only image tools are listed for discovery and return a web UI link when they need browser image APIs.