string/format

URL Encode/Decode

The URL Encode/Decode tool percent-encodes or decodes text locally and separates common modes such as a general URL component, query value, and path segment. It is tuned for the small but frequent moments when copied text needs to become a safe URL fragment or readable string again.

Mode

Context

Plain text input

Output

hello%20world%20%26%20status%3Dok

Mode note

General URL component encoding.

Space handling

This mode uses %20 for spaces.

How to use it

1. Choose encode or decode mode, then pick the context that best matches your use case.
2. Paste the source text and review the converted output plus the mode explanation.
3. Use the examples panel to double-check whether spaces should become %20 or + before copying the result.

Why this tool

Built for repeat use by developers and support teams who need predictable, readable conversion output.

Core function: Percent-encode or decode strings for URLs.

Unique angle: Separate path and query examples clearly.

Examples

Copy-ready examples for common workflows

Encode a query parameter value

Input

hello world & status=ok

Output

hello+world+%26+status%3Dok in query-value mode, which mirrors form-style encoding.

Decode a copied path segment

Input

design%20system%2Ftokens

Output

design system/tokens in decode mode.

FAQ

Questions this page answers up front

Why are there multiple encoding modes?

URLs do not encode every part the same way. Query values, path segments, and whole URLs have slightly different expectations, so the tool makes that choice explicit.

When do spaces become plus signs?

In form-style query encoding, spaces are commonly represented as +. General URL component encoding uses %20 instead.

Does decoding handle plus signs too?

Yes. Query-value decoding converts + back to spaces before percent-decoding.