Skip to content
PocketCaliper
Language
Open menu

Runs locally in your browser

URL Encoder

Percent-encode query values and path segments with encodeURIComponent. Spaces become %20. Encoding stays in your browser.

Paste a search term, a callback URL, or a path piece that contains spaces and reserved characters. This encoder is for components, not whole-page slugs.

encodeURIComponent runs in this tab so query strings are built without a round trip.

How to use

  1. Paste the raw value.
  2. Encode.
  3. Copy the percent-encoded string into a query or path.

How it works

Reserved characters such as ampersand, equals, plus, and slash become percent sequences so they do not split a query.

This is not slug generation. Hyphenated lowercase titles belong on the slug tool. It is also not Base64.

Examples

  • Search query

    blue & red? becomes blue%20%26%20red%3F so the ampersand does not start a second parameter.

  • Redirect param

    https://example.com/a b encodes so a callback URL can sit safely inside ?next=

FAQ

Why is space %20 and not plus?

encodeURIComponent uses %20. Application/x-www-form-urlencoded often uses plus. This tool follows the component encoder.

Should I encode a whole URL?

Encode the parts you insert. Encoding an entire URL twice will break the scheme and host.

Is this the same as a slug?

No. Slugs strip accents and join with hyphens. URL encoding keeps meaning with percent sequences.

Does encoding happen on a server?

No. It is client-side in this tab.

Related tools