URL Encode

Encode URL components or full URLs with options for plus-style spaces and line-by-line processing.

URL Input
1
Encoded Output
1
0 characters 0 lines

URL Encode

URL Encode converts reserved and non-ASCII characters into percent-encoded sequences that are safe to place in links, query strings, form payloads, and API requests.

The conversion runs locally in your browser and does not send URLs, tokens, or query values to a server.

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 this tool?

URL encoding, also called percent encoding, represents characters as percent signs followed by hexadecimal byte values. It keeps spaces, Unicode text, and reserved delimiters unambiguous inside URLs.

Use component encoding for values such as search terms or redirect URLs. Use full URI encoding when you want to preserve URL separators like : / ? & and =.

Input notes

Component mode uses encodeURIComponent and encodes separators. Full URI mode uses encodeURI and preserves URL structure. The plus-space option is useful for application/x-www-form-urlencoded query strings.

Example

A search phrase becomes safe for a query parameter:

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.